[Snyk] Fix for 5 vulnerabilities

[saurabharch]

Snyk has created this PR to fix 5 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
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	863
	Excessive Platform Resource Consumption within a Loop SNYK-JS-BRACES-6838727	696
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	589
	Prototype Pollution SNYK-JS-UNSETVALUE-2400660	589

---

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:

🦉 Inefficient Regular Expression Complexity
🦉 Prototype Pollution

[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 generated by Snyk. Its primary purpose is to enhance the project's security posture by upgrading specific npm dependencies to patched versions, thereby mitigating five identified vulnerabilities, including critical and high-severity issues.

Highlights

• Automated Security Remediation: This pull request was automatically created by Snyk to address identified security vulnerabilities within the project's npm dependencies.
• Vulnerability Fixes: The PR aims to fix 5 vulnerabilities, including one critical ('Predictable Value Range from Previous Values'), three high ('Excessive Platform Resource Consumption within a Loop', 'Inefficient Regular Expression Complexity', 'Prototype Pollution'), and one medium severity issue ('Missing Release of Resource after Effective Lifetime').
• Dependency Upgrades: The core changes involve upgrading jest from version 24.7.1 to 27.0.0 and node-sass from ^4.12.0 to ^9.0.0 in the package.json file to resolve the reported security flaws.

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 or fill out our survey to provide feedback.

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 several security vulnerabilities by upgrading jest and node-sass. While security fixes are important, these upgrades are major version jumps and introduce significant breaking changes that need to be handled carefully.

My review includes two main points:

1. Critical: The jest upgrade from v24 to v27 will likely break your tests due to an incompatible test environment package (jest-environment-jsdom-fourteen) and missing dependencies (jest-environment-jsdom). Manual intervention is required to fix the test setup.
2. High: The node-sass upgrade to v9 has strict Node.js version requirements that may break your build. Furthermore, node-sass is deprecated. I've recommended migrating to the modern sass package instead.

Please review the detailed comments and take the necessary actions to ensure your application remains stable and your build process doesn't break after merging these changes.

[gemini-code-assist]

This upgrade of jest from v24 to v27 is a major leap and introduces significant breaking changes that are likely to break your test suite.

Key issues to consider:

• Incompatible Test Environment: Your project uses jest-environment-jsdom-fourteen (line 47), which has a peer dependency on jest@^24.0.0 and is not compatible with Jest 27.
• Missing jest-environment-jsdom: Since Jest v27, jest-environment-jsdom is no longer bundled with Jest and must be installed separately. This dependency is missing from the PR.
• Default Environment Change: Jest v27 defaults to the node test environment. Your React application tests will fail without a jsdom environment correctly configured.

Recommendation:
Before merging, you will need to:

1. Remove the jest-environment-jsdom-fourteen dependency.
2. Add jest-environment-jsdom as a new dev dependency.
3. Update your Jest configuration to set testEnvironment: 'jsdom'.
4. Consider removing the explicit jest-resolve dependency (line 48), as it should be managed by jest itself.

Without these changes, your tests are almost certain to fail.

[gemini-code-assist]

While upgrading node-sass fixes the vulnerability, this change carries risks and uses a deprecated package.

• Node.js Version Incompatibility: node-sass@9.0.0 requires Node.js v16, v18, or v20. This is a strict requirement and will break your build if your development or CI environments use an older version of Node.js.
• Deprecated Package: node-sass is officially deprecated. The recommended replacement is sass (Dart Sass), which is actively maintained, faster, and easier to install as it doesn't have native binary dependencies.

I strongly recommend migrating to sass instead of continuing with node-sass. This is a more robust and future-proof solution that also resolves the security vulnerability. Note that you may need to ensure your sass-loader version is recent enough (v8+) to automatically use sass.

    "sass": "^1.69.5",