[Snyk] Fix for 6 vulnerabilities

[Dargon789]

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

Snyk changed the following file(s):

• examples/ui-demo/package.json

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.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Missing Origin Validation in WebSockets SNYK-JS-NEXT-10259370	****
	Missing Source Correlation of Multiple Independent Data SNYK-JS-NEXT-12265451	****
	Server-side Request Forgery (SSRF) SNYK-JS-NEXT-12299318	****
	Use of Cache Containing Sensitive Information SNYK-JS-NEXT-12301496	****
	Deserialization of Untrusted Data SNYK-JS-NEXT-14400636	****
	HTTP Request Smuggling SNYK-JS-H3-15010914	636

---

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:

🦉 Server-side Request Forgery (SSRF)
🦉 Deserialization of Untrusted Data

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

[snyk-io]

⚠️ Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, 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, focuses on enhancing the security posture of the ui-demo example by upgrading key yarn dependencies. The primary goal is to remediate several identified vulnerabilities, ranging from low to high severity, through targeted package version bumps.

Highlights

• Dependency Upgrades: The next framework was updated from 14.2.29 to 14.2.35, and the wagmi library was upgraded from 2.15.5 to 3.0.0.
• Vulnerability Fixes: These dependency updates resolve six identified vulnerabilities, including high-severity issues such as Server-side Request Forgery (SSRF) and Deserialization of Untrusted Data.
• Manual yarn.lock Update Required: The yarn.lock file could not be automatically updated and requires manual intervention before this PR can be merged.
• Zero-Install Users Note: Users leveraging Yarn's zero-installs feature will need to manually run yarn to update their .yarn/cache/ directory.

Changelog

• examples/ui-demo/package.json
  • Upgraded next from 14.2.29 to 14.2.35.
  • Upgraded wagmi from 2.15.5 to 3.0.0.

Activity

• This pull request was automatically generated by Snyk to address security vulnerabilities.
• It proposes dependency upgrades to fix 6 identified vulnerabilities.
• A warning indicates that the yarn.lock file requires manual update.

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 updates "next" and "wagmi" dependencies in "examples/ui-demo/package.json" to address reported vulnerabilities. While the dependency versions are updated, the PR description indicates that the "yarn.lock" file was not updated. It is critical to synchronize "yarn.lock" with these changes to ensure dependency consistency and effective vulnerability remediation. Additionally, the upgrade of "wagmi" to a new major version ("3.0.0") is flagged as a breaking change, which requires careful testing to prevent regressions.

[gemini-code-assist]

The package.json file has been updated with new versions for next and wagmi. However, the PR description explicitly states that yarn.lock failed to update. It is crucial to ensure that yarn.lock is synchronized with these package.json changes to guarantee that the correct dependency versions are installed and that the reported vulnerabilities are actually fixed. Without an updated yarn.lock, the project might still be using older, vulnerable versions of these packages, or face unexpected dependency resolution issues. Please run yarn install or yarn upgrade to update yarn.lock before merging.

[gemini-code-assist]

The wagmi package has been updated from 2.15.5 to 3.0.0. This is a major version upgrade, which often introduces breaking changes. The Snyk metadata also indicates isBreakingChange: true. It's important to thoroughly test the application to ensure that this major version bump does not introduce regressions or require code modifications to adapt to wagmi v3.0.0's API changes.