[Snyk] Fix for 6 vulnerabilities

[skmezanul]

Snyk has created this PR to fix 6 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
	Prototype Pollution SNYK-JS-PARSE-13551630	818
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	791
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIMECOREJS3-9397696	666
	Prototype Pollution SNYK-JS-PARSE-13053302	654
	Server-side Request Forgery (SSRF) SNYK-JS-REQUEST-3361831	646
	Prototype Pollution SNYK-JS-TOUGHCOOKIE-5672873	646

---

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)
🦉 Prototype Pollution
🦉 Server-side Request Forgery (SSRF)

[gemini-code-assist]

Summary of Changes

Hello @skmezanul, 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 significantly improve the security posture of the project by automatically patching several critical and high-severity vulnerabilities found in its npm dependencies. By upgrading specific packages, it mitigates known risks, although a manual step is required to fully synchronize the dependency lock file.

Highlights

• Vulnerability Fixes: This pull request addresses six identified security vulnerabilities within the project's npm dependencies, including critical and high-severity issues like Prototype Pollution, Predictable Value Range, Regular Expression Denial of Service (ReDoS), and Server-side Request Forgery (SSRF).
• Dependency Upgrades: To resolve these vulnerabilities, the PR updates two key dependencies: "@parse/push-adapter" from version "4.1.2" to "7.0.0" and "parse" from "4.0.1" to "7.0.1" in the "package.json" file.
• Manual Intervention Required: A warning indicates that the "package-lock.json" file was not automatically updated and requires manual intervention before merging to ensure dependency consistency and proper resolution of the vulnerabilities.

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, automatically generated by Snyk, addresses 6 security vulnerabilities by upgrading @parse/push-adapter and parse dependencies. While fixing security issues is important, both of these upgrades are major version jumps (@parse/push-adapter: 4.x to 7.x, parse: 4.x to 7.x), and Snyk has marked this PR as containing breaking changes. This introduces a significant risk of regressions. It is critical to thoroughly test the application, especially push notifications and core functionalities relying on the Parse JS SDK. Additionally, as noted in the PR description, package-lock.json needs to be updated manually before merging.

[gemini-code-assist]

This is a major version upgrade for @parse/push-adapter from 4.1.2 to 7.0.0. Major versions can introduce breaking changes, and Snyk has flagged this PR as containing a breaking change. Please carefully review the changelog for @parse/push-adapter and thoroughly test the push notification functionality to ensure there are no regressions.

[gemini-code-assist]

This upgrades the parse (Parse JS SDK) package from version 4.0.1 to 7.0.1. This is a significant major version jump and likely contains breaking changes. Given how extensively the Parse SDK is used throughout this project (for error handling, initialization, etc.), it's crucial to test the application thoroughly to catch any potential issues arising from this upgrade. Please consult the Parse JS SDK release notes for versions 5, 6, and 7 for details on breaking changes.