mailparser 3.13.0

Parse e-mails

mailparser@3.13.0 was published on 2026-10-29. Its manifest declares 8 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.0.0.

All mailparser versions · Permanent reference to 3.13.0 · Latest release

Package specifications

Version3.13.0
License declarationMIT
Published2026-10-29T07:59:37.984Z
Node.js requirement>=20.0.0
Type declarationsBundled declarations
Runtime dependency count8
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size239.93 KiB
Published file count38
Package typemodule
ES module entryNot declared
Default entry./dist/cjs/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars1672
Repository forks290

Install mailparser 3.13.0

npm install mailparser@3.13.0
pnpm add mailparser@3.13.0
yarn add mailparser@3.13.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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-Review0/10 — Found 0/18 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 23 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
SAST1/10 — SAST tool is not run on all commits -- score normalized to 1
Packaging10/10 — packaging workflow detected

Evidence and freshness