[Snyk] Security upgrade react-scripts from 1.0.14 to 4.0.0

[saurabharch]

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

Snyk changed the following file(s):

• app/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	863

---

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.

[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, automatically generated by Snyk, aims to enhance the project's security posture by upgrading a key dependency. The primary goal is to mitigate a critical vulnerability identified in the existing react-scripts package by moving to a much newer, more secure version. Given the major version jump, it's important to verify that the application continues to function as expected after this update.

Highlights

• Security Upgrade: Upgraded the react-scripts dependency from version 1.0.14 to 4.0.0 to address a critical security vulnerability.
• Vulnerability Fix: This pull request specifically fixes the 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150), which has a critical severity score of 863.
• Major Version Bump: The upgrade involves a significant major version change for react-scripts (from 1.x to 4.x), which may introduce breaking changes and requires thorough testing to ensure application compatibility.

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, upgrades react-scripts from version 1.0.14 to 4.0.0 to resolve a security vulnerability. My review highlights the critical nature of this major version upgrade. While essential for security, this change introduces significant breaking changes that will likely impact the build, development server, and testing environment. I have added a comment to emphasize the need for a thorough migration and testing process before merging.

[gemini-code-assist]

Upgrading react-scripts from v1.0.14 to v4.0.0 is a major change with significant breaking changes. While this fixes a security vulnerability, merging it without a proper migration plan will likely break the application.

Potential Issues:

• Breaking Changes: This jump spans multiple major versions of react-scripts, which means underlying tools like Webpack, Babel, Jest, and ESLint have been upgraded. This will require code and configuration changes. Refer to the official Create React App migration guides for assistance.
• Environment & Dependencies: react-scripts v4 has updated Node.js and peer dependency requirements (e.g., for React).

Action Required:
Before merging, a full migration and testing process is critical. This includes:

1. Resolving any new dependency conflicts after npm install.
2. Testing the development server (npm start).
3. Verifying production builds (npm run build).
4. Running the entire test suite (npm test).
5. Performing a full manual regression test of the application.

This PR should be seen as the start of a migration project, not a simple update.