[Snyk] Security upgrade react-scripts from 4.0.1 to 5.0.0

[Amjad992]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	713
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	708
	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-JS-TAR-6476909	646
	Arbitrary File Write SNYK-JS-TAR-1579147	639
	Arbitrary File Write SNYK-JS-TAR-1579152	639
	Arbitrary File Write SNYK-JS-TAR-1579155	639
	Arbitrary File Overwrite SNYK-JS-TAR-1536528	624
	Arbitrary File Overwrite SNYK-JS-TAR-1536531	624
	Regular Expression Denial of Service (ReDoS) SNYK-JS-TAR-1536758	410

---

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:

🦉 Arbitrary File Overwrite
🦉 Regular Expression Denial of Service (ReDoS)

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR upgrades react-scripts from 4.0.1 to 5.0.0 to address 9 security vulnerabilities, including high-severity issues with arbitrary file writes and medium-severity cryptographic and resource exhaustion vulnerabilities in transitive dependencies (tar, elliptic).

Changes:

• Updated react-scripts from 4.0.1 to 5.0.0 in package.json
• Updated package-lock.json with new dependency tree for react-scripts 5.0.0

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

🔴 Critical | This upgrade introduces a compatibility issue. React-scripts 5.0.0 requires React 18 as a peer dependency, but this project is currently using React 17.0.1. This will likely cause runtime errors or installation failures. You need to either upgrade React and React-DOM to version 18, or use react-scripts 4.0.3 instead, which is the latest 4.x version that fixes the security vulnerabilities while maintaining React 17 compatibility.

Suggested change

	"react-scripts": "5.0.0",
	"react-scripts": "4.0.3",

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	react-scripts@​5.0.0
	react@​17.0.1
	react-qr-reader@​2.2.1
	qrcode@​1.4.4
	react-dom@​17.0.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: package-lock.json → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report