mailparser 3.9.8 → 3.9.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,3 +1,3 @@
1
1
  {
2
- ".": "3.9.8"
2
+ ".": "3.9.10"
3
3
  }
package/CHANGELOG.md CHANGED
@@ -1,5 +1,19 @@
1
1
  # Changelog
2
2
 
3
+ ## [3.9.10](https://github.com/nodemailer/mailparser/compare/v3.9.9...v3.9.10) (2026-06-15)
4
+
5
+
6
+ ### Bug Fixes
7
+
8
+ * bump dependencies (nodemailer 9, eslint 10.5, prettier 3.8.4) ([262ecff](https://github.com/nodemailer/mailparser/commit/262ecffcd649a6b0d4164271cc7a2662f9789f64))
9
+
10
+ ## [3.9.9](https://github.com/nodemailer/mailparser/compare/v3.9.8...v3.9.9) (2026-05-29)
11
+
12
+
13
+ ### Bug Fixes
14
+
15
+ * bumped deps ([7a83b91](https://github.com/nodemailer/mailparser/commit/7a83b9184509c15faa580e91ac7a7b1e8f3b1090))
16
+
3
17
  ## [3.9.8](https://github.com/nodemailer/mailparser/compare/v3.9.7...v3.9.8) (2026-04-08)
4
18
 
5
19
 
package/SECURITY.md ADDED
@@ -0,0 +1,89 @@
1
+ # Security Policy
2
+
3
+ mailparser is an email parsing library for Node.js. It is routinely pointed at
4
+ untrusted, adversarial, and malformed messages, so parser robustness is a
5
+ security concern: a crafted message should never be able to crash the host
6
+ process, exhaust memory or CPU, pollute prototypes, or leak data across parses.
7
+ We take security reports seriously and aim to respond quickly.
8
+
9
+ ## Supported Versions
10
+
11
+ Security fixes are released only against the latest version. We do not backport
12
+ patches to older releases - upgrading to the current 3.x release line is the
13
+ supported way to receive security updates.
14
+
15
+ | Version | Supported |
16
+ | ------- | ------------------ |
17
+ | 3.x | :white_check_mark: |
18
+ | < 3.0 | :x: |
19
+
20
+ If you are on an older version, please upgrade. See the release notes at
21
+ <https://github.com/nodemailer/mailparser/releases> before updating.
22
+
23
+ > [!NOTE]
24
+ > mailparser is in maintenance mode - it receives security updates and critical
25
+ > bug fixes only. For new projects, consider
26
+ > [PostalMime](https://github.com/postalsys/postal-mime), which works in both
27
+ > Node.js and browser environments.
28
+
29
+ ## Reporting a Vulnerability
30
+
31
+ **Please do not report security vulnerabilities through public GitHub issues,
32
+ pull requests, or discussions.**
33
+
34
+ Report privately through one of the following channels:
35
+
36
+ 1. **GitHub Security Advisories (preferred).** Open a private report at
37
+ <https://github.com/nodemailer/mailparser/security/advisories/new>. This keeps
38
+ the discussion private until a fix is published and lets us credit you.
39
+ 2. **Email.** Send details to **andris@postalsys.com**. Encrypt sensitive
40
+ details if possible.
41
+
42
+ When reporting, please include as much of the following as you can:
43
+
44
+ - The affected version(s) and environment (mailparser version, Node.js version,
45
+ OS).
46
+ - A clear description of the issue and its impact (e.g. denial of service via
47
+ CPU or memory exhaustion, ReDoS, prototype pollution, unhandled exception that
48
+ crashes the process, information disclosure between parses).
49
+ - A minimal proof of concept - ideally the raw `.eml` sample or a short script
50
+ that reproduces the issue.
51
+ - Any suggested remediation, if you have one.
52
+
53
+ We are a small team, so there is no guaranteed response time - sometimes reports
54
+ are handled within hours, sometimes they take longer. Accepted issues are fixed
55
+ in a new release and coordinated through a GitHub Security Advisory, and
56
+ reporters who wish to be named are credited.
57
+
58
+ ## CVEs
59
+
60
+ We track and disclose vulnerabilities through GitHub Security Advisories. We do
61
+ not request or manage CVE identifiers ourselves. If you need a CVE assigned for a
62
+ reported issue, please request one yourself - for example, through GitHub's own
63
+ CVE request flow on the published advisory, or another CNA.
64
+
65
+ ## Scope
66
+
67
+ In scope: the mailparser library source in this repository - the streaming MIME
68
+ parser (`MailParser`), the convenience parser (`simpleParser`), header and
69
+ address decoding, charset/transfer-encoding handling, and attachment and HTML/
70
+ text extraction. Of particular interest are inputs that cause unbounded resource
71
+ consumption, catastrophic regular-expression backtracking, prototype pollution,
72
+ or process crashes.
73
+
74
+ Out of scope:
75
+
76
+ - Vulnerabilities in your own application code that consumes mailparser output.
77
+ Parsed email content is attacker-controlled data; you must sanitize and escape
78
+ it before rendering, storing, or executing it. In particular, the `html` field
79
+ is not sanitized for safe display in a browser.
80
+ - Vulnerabilities in third-party dependencies that are already tracked and fixed
81
+ upstream - report those to the respective project (we will still bump the
82
+ dependency once a fix is available).
83
+ - Issues that require an already-compromised host or a malicious local
84
+ environment.
85
+ - Resource consumption that is proportional to a legitimately large input (for
86
+ example, parsing a genuine 100MB message uses memory) rather than amplified by
87
+ a crafted small input.
88
+
89
+ Thank you for helping keep mailparser and its users safe.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mailparser",
3
- "version": "3.9.8",
3
+ "version": "3.9.10",
4
4
  "description": "Parse e-mails",
5
5
  "main": "index.js",
6
6
  "scripts": {
@@ -20,28 +20,28 @@
20
20
  "dependencies": {
21
21
  "encoding-japanese": "2.2.0",
22
22
  "he": "1.2.0",
23
- "html-to-text": "9.0.5",
23
+ "html-to-text": "10.0.0",
24
24
  "iconv-lite": "0.7.2",
25
25
  "libmime": "5.3.8",
26
- "linkify-it": "5.0.0",
27
- "@zone-eu/mailsplit": "5.4.8",
28
- "nodemailer": "8.0.5",
26
+ "linkify-it": "5.0.1",
27
+ "@zone-eu/mailsplit": "5.4.12",
28
+ "nodemailer": "9.0.0",
29
29
  "punycode.js": "2.3.1",
30
30
  "tlds": "1.261.0"
31
31
  },
32
32
  "devDependencies": {
33
33
  "@eslint/eslintrc": "3.3.5",
34
34
  "@eslint/js": "10.0.1",
35
- "ajv": "8.18.0",
36
- "eslint": "10.2.0",
35
+ "ajv": "8.20.0",
36
+ "eslint": "10.5.0",
37
37
  "eslint-config-nodemailer": "1.2.0",
38
38
  "eslint-config-prettier": "10.1.8",
39
- "grunt": "1.6.1",
39
+ "grunt": "1.6.2",
40
40
  "grunt-cli": "1.5.0",
41
41
  "grunt-contrib-nodeunit": "5.0.0",
42
42
  "grunt-eslint": "26.0.0",
43
43
  "iconv": "3.0.1",
44
- "prettier": "3.8.1",
44
+ "prettier": "3.8.4",
45
45
  "random-message": "1.1.0"
46
46
  },
47
47
  "repository": {
@@ -1,4 +0,0 @@
1
- # These are supported funding model platforms
2
-
3
- github: [andris9] # enable once enrolled
4
- custom: ['https://www.paypal.me/nodemailer']
@@ -1,36 +0,0 @@
1
- on:
2
- push:
3
- branches:
4
- - master
5
-
6
- permissions:
7
- contents: write
8
- pull-requests: write
9
- issues: write
10
- id-token: write
11
-
12
- name: release
13
- jobs:
14
- release-please:
15
- runs-on: ubuntu-latest
16
- outputs:
17
- release_created: ${{ steps.release.outputs.release_created }}
18
- steps:
19
- - uses: googleapis/release-please-action@v4
20
- id: release
21
-
22
- publish:
23
- needs: release-please
24
- if: ${{ needs.release-please.outputs.release_created }}
25
- runs-on: ubuntu-latest
26
- permissions:
27
- contents: read
28
- id-token: write
29
- steps:
30
- - uses: actions/checkout@v4
31
- - uses: actions/setup-node@v4
32
- with:
33
- node-version: 24
34
- registry-url: 'https://registry.npmjs.org'
35
- - run: npm ci
36
- - run: npm publish --provenance --access public
@@ -1,24 +0,0 @@
1
- name: 'Close stale issues and PRs'
2
- on:
3
- schedule:
4
- - cron: '30 1 * * *'
5
-
6
- jobs:
7
- stale:
8
- runs-on: ubuntu-latest
9
- steps:
10
- - uses: actions/stale@v8
11
- with:
12
- stale-issue-message: 'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
13
- stale-pr-message: 'This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.'
14
- close-issue-message: 'This issue was closed because it has been stalled for 15 days with no activity.'
15
- close-pr-message: 'This PR was closed because it has been stalled for 20 days with no activity.'
16
- days-before-issue-stale: 30
17
- days-before-pr-stale: 45
18
- days-before-issue-close: 15
19
- days-before-pr-close: 20
20
- stale-issue-label: 'no-issue-activity'
21
- exempt-issue-labels: 'pending,work-in-progress'
22
- stale-pr-label: 'no-pr-activity'
23
- exempt-pr-labels: 'awaiting-approval,work-in-progress'
24
- repo-token: ${{ secrets.GITHUB_TOKEN }}
@@ -1,21 +0,0 @@
1
- name: Run tests
2
-
3
- on:
4
- push:
5
- pull_request:
6
-
7
- jobs:
8
- test:
9
- strategy:
10
- matrix:
11
- node: [22.x, 24.x]
12
- os: [ubuntu-latest]
13
- runs-on: ${{ matrix.os }}
14
- steps:
15
- - uses: actions/checkout@v4
16
- - name: Use Node.js ${{ matrix.node }}
17
- uses: actions/setup-node@v4
18
- with:
19
- node-version: ${{ matrix.node }}
20
- - run: npm install
21
- - run: npm test
package/.ncurc.js DELETED
@@ -1,6 +0,0 @@
1
- 'use strict';
2
-
3
- module.exports = {
4
- upgrade: true,
5
- reject: []
6
- };