[AH7]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-NODEMAILER-20158380	828
	Uncontrolled Recursion SNYK-JS-NODEMAILER-20158384	803

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Recursion

[AH7]

This is a major upgrade across 8 major versions (v2.7.2 → v10.0.6) and introduces significant breaking changes that require developer action.

Key Breaking Changes:

• Node.js Requirement: Nodemailer v10 requires Node.js v20 or later. Support for all older Node.js versions has been dropped. [1, 5]
• TypeScript Integration: Nodemailer v10 and later are written in TypeScript and include their own type definitions. The @types/nodemailer package is no longer needed and must be removed from your project to avoid conflicting type declarations. [2]
• API and Configuration: While the core createTransport and sendMail methods still exist, there have been numerous changes to configuration options, authentication methods (especially for OAuth2), and the structure of response objects since version 2. [1]
• Stricter Validation: Many security vulnerabilities have been fixed since v2, leading to stricter parsing and validation of email addresses, headers, and content. Applications relying on previous, more lenient behavior may break. [11, 13, 14]

Recommendation: Due to the extensive changes, a direct upgrade is not recommended. A thorough review of the current implementation against the latest Nodemailer documentation is required. Expect to refactor code related to transport creation, authentication, and message options. Thorough testing of all email-sending functionality is critical before deployment.

Source: Nodemailer Documentation

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.