[Snyk] Security upgrade react-router-dom from 7.2.0 to 7.12.0

[iamdrewfortini]

Snyk has created this PR to fix 5 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• examples/react-example/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-REACTROUTER-14908531	134
	Cross-site Scripting (XSS) SNYK-JS-REACTROUTER-14908293	127
	Open Redirect SNYK-JS-REACTROUTER-14908286	114
	Cross-site Scripting (XSS) SNYK-JS-REACTROUTER-14908289	114
	Cross-site Request Forgery (CSRF) SNYK-JS-REACTROUTER-14908429	97

---

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:

🦉 Open Redirect
🦉 Cross-site Scripting (XSS)

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, 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 security posture of the project by upgrading the react-router-dom dependency. The update specifically targets and resolves multiple critical and medium-severity vulnerabilities, ensuring a more secure application environment. Reviewers should pay attention to the manual pnpm-lock.yaml update requirement.

Highlights

• Dependency Upgrade: The react-router-dom dependency has been upgraded from version 7.2.0 to 7.12.0 in the examples/react-example/package.json file.
• Security Vulnerabilities Addressed: This upgrade fixes 5 identified vulnerabilities, including high-severity Cross-site Scripting (XSS) and Open Redirect issues, as well as medium-severity XSS and Cross-site Request Forgery (CSRF).
• Manual Lockfile Update Required: A warning indicates that the pnpm-lock.yaml file failed to update automatically and requires manual intervention before merging this pull request.

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. ↩

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	convex@​1.27.0

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 vite is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/vite@6.1.0 ℹ 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/vite@6.1.0. 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

[gemini-code-assist]

Code Review

This pull request from Snyk upgrades react-router-dom to version 7.12.0 to resolve several security vulnerabilities. While the change in package.json is correct, it's crucial to note that the pnpm-lock.yaml file was not automatically updated, as mentioned in the PR description. You must manually run pnpm install and commit the updated lock file to ensure the security fix is actually applied across all environments. Failure to do so will leave your application vulnerable.

[gemini-code-assist]

As noted in the pull request description, the pnpm-lock.yaml file has not been updated. This is a critical step that must be completed manually.

Without updating the lock file, your project will continue to use the old, vulnerable version of react-router-dom specified in the lock file, and the security fix will not be applied.

Please run pnpm install in the repository root to update pnpm-lock.yaml and commit the changes to this PR before merging.