[Snyk] Fix for 2 vulnerabilities

[saurabharch]

Snyk has created this PR to fix 2 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
	Malicious Package SNYK-JS-DEBUG-12552895	965
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-12613773	738

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[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 resolving two identified vulnerabilities. It achieves this by updating key npm dependencies, specifically axios and react-scripts, to versions that mitigate a critical malicious package issue and a medium-severity resource allocation vulnerability.

Highlights

• Security Vulnerability Fixes: This pull request addresses and fixes two identified security vulnerabilities: a critical 'Malicious Package' issue (SNYK-JS-DEBUG-12552895) and a medium-severity 'Allocation of Resources Without Limits or Throttling' issue (SNYK-JS-AXIOS-12613773).
• Dependency Upgrades: To resolve the vulnerabilities, the axios dependency has been upgraded from ^0.17.0 to ^1.12.0, and react-scripts has been updated from 1.0.14 to 5.0.0.
• Automated PR Generation: This pull request was automatically generated by Snyk to provide a direct fix for the detected security concerns.

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 pull request from Snyk updates axios and react-scripts to fix security vulnerabilities. While necessary, these are major version upgrades that introduce significant breaking changes. The react-scripts update from v1 to v5 is particularly high-risk and will likely require a considerable migration effort, including updating Node.js and React versions. The axios update also carries risk of breaking changes, especially in error handling. It is critical to thoroughly test the application and resolve any resulting issues before merging.

[gemini-code-assist]

Upgrading react-scripts from 1.0.14 to 5.0.0 is a massive jump across 4 major versions and will almost certainly introduce breaking changes that break your application. You should expect to perform a significant migration effort. Key considerations include:

• Node.js Version: react-scripts@5 requires Node.js 14+.
• React Version: It is designed for React 17/18. Your project's [email protected] is likely incompatible and will need to be upgraded.
• Toolchain Updates: This brings in major updates like Webpack 5 and Babel 7, which may have their own breaking changes affecting your project if you have any custom configurations.

Before merging, it is essential to test the build, start, and all application functionality thoroughly on a separate branch and address any resulting issues.

[gemini-code-assist]

The upgrade of axios from ^0.17.0 to ^1.12.0 is a major version jump from a pre-1.0 release. This may introduce breaking changes, particularly in error handling. The structure of the error object in .catch() blocks might have changed. Please review the axios changelog and test API calls that handle errors, such as the one in app/src/helpers/upload.js.