[Snyk] Security upgrade pm2 from 5.3.0 to 6.0.9

[saurabharch]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PM2-10335843	666

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
rollout	Error			Sep 4, 2025 2:13am

[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 is an automated security fix initiated by Snyk to resolve a known vulnerability in one of the project's npm dependencies. The update aims to enhance the project's security posture by patching a critical issue without introducing new features or functional changes.

Highlights

• Security Upgrade: This pull request upgrades the pm2 dependency from version 5.3.0 to 6.0.9 to address a Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-PM2-10335843).

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 PR addresses a security vulnerability by upgrading pm2 from v5.3.0 to v6.0.9. This is a positive security improvement. However, this is a major version upgrade, which Snyk has correctly identified as a potential breaking change. Major version bumps can introduce incompatibilities in CLI commands, configuration files, or programmatic APIs. Before merging, it's critical to conduct thorough testing of all application functionality that relies on pm2, including startup, restart, and deployment scripts, to prevent any regressions in production. I've added a specific comment highlighting the risks associated with this major version bump.

[gemini-code-assist]

This upgrade to pm2 is a major version bump from v5 to v6. Major versions often contain breaking changes, and the Snyk metadata for this PR confirms this with isBreakingChange:true. For example, the programmatic API has been changed to be promise-based, which could affect any custom scripts using it. Even CLI behavior and configuration options might have changed. It is highly recommended to review the PM2 v6 changelog and perform thorough regression testing on all pm2-related functionality (e.g., npm run restart, deployments) before merging.