[Snyk] Fix for 4 vulnerabilities

[saurabharch]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled Recursion SNYK-JS-NODEMAILER-14157156	803
	Interpretation Conflict SNYK-JS-NODEFORGE-14114940	751
	Uncontrolled Recursion SNYK-JS-NODEFORGE-14125745	721
	Integer Overflow or Wraparound SNYK-JS-NODEFORGE-14125097	601

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rollout	Error			Dec 4, 2025 8:42am

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to bolster the project's security by resolving four identified vulnerabilities within its npm dependencies. It achieves this by upgrading the @parse/node-apn and nodemailer packages to their more secure versions. Reviewers should pay close attention to the dependency updates and ensure the package-lock.json is manually updated to reflect these changes accurately.

Highlights

• Automated Security Fix: This pull request was automatically generated by Snyk to address identified security vulnerabilities in the project's npm dependencies.
• Vulnerability Resolution: Four vulnerabilities have been targeted for remediation, including critical and high severity issues related to Uncontrolled Recursion, Interpretation Conflict, and Integer Overflow or Wraparound.
• Dependency Upgrades: Key dependencies, specifically @parse/node-apn and nodemailer, have been upgraded to their latest secure versions to mitigate the reported vulnerabilities.
• Manual Action Required: A manual update of the package-lock.json file is required as Snyk was unable to update it automatically, which is crucial for ensuring consistent dependency resolution.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request from Snyk aims to fix security vulnerabilities by upgrading @parse/node-apn and nodemailer. However, the proposed changes have critical flaws. The target version for nodemailer (7.0.11) does not exist, which will break the build. The upgrade for @parse/node-apn is a major version jump (v5 to v7) that includes breaking changes, specifically the removal of callback support, which your project seems to rely on. This will likely break push notifications. I recommend manually updating these dependencies to versions that fix the vulnerabilities without introducing these issues. Also, remember to regenerate and commit package-lock.json after making the changes.

[gemini-code-assist]

The nodemailer package is being updated to version 7.0.11, which does not exist in the npm registry. This will cause npm install to fail. To fix the Snyk vulnerability SNYK-JS-NODEMAILER-14157156, you should update to a version like 6.9.8 or higher within the 6.x series. The latest version is 6.9.13.

Suggested change

	"nodemailer": "^7.0.11",
	"nodemailer": "^6.9.13",

[gemini-code-assist]

This is a major version upgrade from v5 to v7 for @parse/node-apn. Version 6 of this library introduced a significant breaking change by removing support for callbacks and moving to a Promise-based API. Your code in src/jobs/PushNotification.js appears to use a callback-style API via the rollout-pushnotification wrapper. This update is very likely to break Apple Push Notifications. Please verify compatibility and update your code to use Promises if necessary before merging this change. Given the risk, you might want to find the minimum version that fixes the vulnerability without introducing breaking changes.