[Snyk] Security upgrade react-scripts from 1.1.5 to 2.0.3

[saurabharch]

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

Snyk changed the following file(s):

• fixtures/concurrent/time-slicing/package.json
• fixtures/concurrent/time-slicing/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-JSYAML-13961110	631

---

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:

🦉 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, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the react-scripts dependency. The upgrade specifically targets and resolves a 'Prototype Pollution' vulnerability, ensuring that the application remains protected against known security risks. The changes primarily involve updating the react-scripts version from ^1.1.4 to ^2.0.3 in package.json and consequently, yarn.lock within the fixtures/concurrent/time-slicing/ directory.

Highlights

• Security Vulnerability Fix: This pull request addresses a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) by upgrading the react-scripts dependency.
• Dependency Upgrade: The react-scripts package has been upgraded from version ^1.1.4 to ^2.0.3 in the fixtures/concurrent/time-slicing/package.json file.
• Automated PR: This PR was automatically generated by Snyk to propose the necessary security fix.

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, aims to fix a prototype pollution vulnerability in js-yaml by upgrading react-scripts from version 1.1.4 to 2.0.3. While this does resolve the security issue, this is a major version upgrade for react-scripts which introduces breaking changes. Specifically, the new version of react-scripts is incompatible with the experimental version of React used in this fixture. This will likely break the build. I've provided a comment with a safer alternative using yarn resolutions to patch the vulnerability without the disruptive upgrade. I recommend adopting that approach instead.

[gemini-code-assist]

While this upgrade to react-scripts@^2.0.3 fixes the js-yaml vulnerability, it's a major version bump from 1.x to 2.x. This new version of react-scripts requires react@^16.3.2 and react-dom@^16.3.2, but this project uses the highly experimental 0.0.0-experimental-269dd6ec5 versions. This incompatibility is very likely to break this fixture.

A safer approach to fix the security vulnerability without introducing breaking changes would be to use yarn resolutions to force js-yaml to a secure version. You can do this by adding the following to this package.json and running yarn install:

"resolutions": {
  "js-yaml": "^3.13.1"
}

I recommend reverting this change and using the resolutions method instead.

Suggested change

	"react-scripts": "^2.0.3",
	"react-scripts": "^1.1.4",