unstale

npm / mailparser

mailparser

What changed in mailparser 3, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.

4 security12 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli on npm

mailparser 316 changes

Security 4

  • Bounds scanning of untrusted text bodies.

    3.9.16release notes

  • Prevents RFC 2047 encoded words from fabricating addresses during address decoding.

    3.9.4release notes

  • mailparser vulnerable to Cross-site Scripting

    3.9.3security advisory

  • URLs and link text are now escaped to prevent XSS.

    3.9.3release notes

Fixes and other changes 12

  • A decoded display name is no longer turned into an address.

    3.9.40release notes

  • The message is kept when its HTML cannot be converted to text.

    3.9.40release notes

  • An unavailable checksum algorithm is reported as a parser error.

    3.9.33release notes

  • Honours backpressure when handling attachments.

    3.9.30release notes

  • Caps inlined CID images.

    3.9.30release notes

  • Reports errors from the splitter that occur late.

    3.9.30release notes

  • Derives partId from the part number.

    3.9.30release notes

  • Ensures settlement happens only once.

    3.9.30release notes

  • Declares the Node 20 minimum requirement that the package already had, helping developers identify the required runtime.

    3.9.22release notes

  • Decode iso-8859-8-i and iso-8859-8-e charsets as iso-8859-8.

    3.9.12release notes

  • False values are filtered from empty References headers.

    3.9.4release notes

  • Parsing of unquoted commas in display names is fixed, so addresses with those display names can be parsed correctly.

    3.9.4release notes