mailcomposer 3.3.2
Compose E-Mail messages
mailcomposer@3.3.2 was published on 2016-01-20. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: This project is unmaintained
All mailcomposer versions · Permanent reference to 3.3.2 · Latest release
Package specifications
| Version | 3.3.2 |
|---|---|
| License declaration | MIT |
| Published | 2016-01-20T21:16:05.810Z |
| Node.js requirement | Not declared |
| 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/mailcomposer |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 209 |
| Repository forks | 62 |
Install mailcomposer 3.3.2
npm install mailcomposer@3.3.2 pnpm add mailcomposer@3.3.2 yarn add mailcomposer@3.3.2
Runtime dependencies
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.
- addressparser@1.0.0 — indirect
- buildmail@3.3.2 — direct
- iconv-lite@0.4.13 — indirect
- libbase64@0.1.0 — indirect
- libmime@2.0.0 — direct
- libqp@1.1.0 — indirect
- nodemailer-fetch@1.2.1 — indirect
- nodemailer-shared@1.0.3 — indirect
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.
| Maintained | 0/10 — project is archived |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Code-Review | 0/10 — Found 0/2 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 0/10 — license file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/mailcomposer/3.3.2 — retrieved 2026-10-29T11:25:19.705Z
- https://api.deps.dev/v3/projects/github.com%2Fandris9%2Fmailcomposer — retrieved 2026-10-29T08:49:47.153Z
- https://api.deps.dev/v3/systems/npm/packages/mailcomposer/versions/3.3.2 — retrieved 2026-10-29T11:25:20.349Z
- https://api.deps.dev/v3/systems/npm/packages/mailcomposer/versions/3.3.2:dependencies — retrieved 2026-10-29T11:25:20.367Z