nodemailer 1.3.0

Easy as cake e-mail sending from your Node.js applications

nodemailer@1.3.0 was published on 2014-09-12. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.

Deprecated: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/

All nodemailer versions · Permanent reference to 1.3.0 · Latest release

Package specifications

Version1.3.0
License declarationMIT
Published2014-09-12T11:57:30.564Z
Node.js requirement>=0.10.0
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrysrc/nodemailer.js
Side effects declarationNot declared
Direct advisories15
Resolved graph dependencies26
Repository stars17690
Repository forks1437

Install nodemailer 1.3.0

npm install nodemailer@1.3.0
pnpm add nodemailer@1.3.0
yarn add nodemailer@1.3.0

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.

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.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Code-Review1/10 — Found 5/27 approved changesets -- score normalized to 1
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies1/10 — dependency not pinned by hash detected -- score normalized to 1
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST3/10 — SAST tool is not run on all commits -- score normalized to 3
Packaging10/10 — packaging workflow detected

Evidence and freshness