imap
An IMAP module for node.js that makes communicating with IMAP servers easy
imap@0.8.19 was published on 2016-12-06. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.8.0.
All imap versions · Permanent reference to 0.8.19
Package specifications
| Version | 0.8.19 |
|---|---|
| License declaration | Not declared |
| Published | 2016-12-06T17:03:49.686Z |
| Node.js requirement | >=0.8.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/Connection |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 2222 |
| Repository forks | 386 |
Install imap 0.8.19
npm install imap@0.8.19 pnpm add imap@0.8.19 yarn add imap@0.8.19
Runtime dependencies
- utf7 >=1.0.2
- readable-stream 1.1.x
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- core-util-is@1.0.3 — indirect
- inherits@2.0.4 — indirect
- isarray@0.0.1 — indirect
- readable-stream@1.1.14 — direct
- semver@5.3.0 — indirect
- string_decoder@0.10.31 — indirect
- utf7@1.0.2 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 0/10 — Found 2/29 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/imap/0.8.19 — retrieved 2026-10-29T08:06:22.772Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/imap/versions/0.8.19:dependencies — retrieved 2026-10-29T08:06:22.773Z
- https://api.deps.dev/v3/systems/npm/packages/imap/versions/0.8.19 — retrieved 2026-10-29T08:06:22.703Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fmscdex%2Fnode-imap — retrieved 2026-10-29T08:06:23.301Z