[Snyk] Fix for 7 vulnerabilities

[Dargon789]

Snyk has created this PR to fix 7 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
	HTTP Request Smuggling SNYK-JS-H3-15010914
	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
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645

---

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
🦉 Allocation of Resources Without Limits or Throttling

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 3 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, addresses critical security vulnerabilities within the ui-demo example's yarn dependencies. The core change involves updating the next and wagmi packages to their latest versions to incorporate necessary security patches. It is important to note that a manual update of the yarn.lock file is required to fully apply these security fixes.

Highlights

• Dependency Upgrades: The next dependency has been upgraded from version 14.2.29 to 15.5.10, and the wagmi dependency has been upgraded from 2.15.5 to 3.0.0 in the examples/ui-demo/package.json file.
• Vulnerability Fixes: These dependency upgrades are intended to fix 7 identified vulnerabilities, including high-severity issues such as HTTP Request Smuggling, Server-side Request Forgery (SSRF), Deserialization of Untrusted Data, and Allocation of Resources Without Limits or Throttling.
• Manual yarn.lock Update Required: Snyk reported a failure to update the yarn.lock file, which means a manual update is required before merging this pull request, especially for projects utilizing Yarn's zero-installs feature.

Changelog

• examples/ui-demo/package.json
  • Updated the next dependency from 14.2.29 to 15.5.10.
  • Updated the wagmi dependency from 2.15.5 to 3.0.0.

Activity

• This pull request was automatically created by Snyk to fix 7 vulnerabilities in the yarn dependencies.
• The PR description includes a warning that the yarn.lock file failed to update and requires manual intervention.
• Guidance is provided for users of Yarn's zero-installs feature regarding the .yarn/cache/ directory.
• Links to Snyk's project report, PR template customization, project settings, and documentation on upgrade logic are included.
• Interactive lessons on Server-side Request Forgery (SSRF), Deserialization of Untrusted Data, and Allocation of Resources Without Limits or Throttling are linked for educational purposes.

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, proposes upgrading next and wagmi to fix security vulnerabilities. However, both upgrades are major version bumps (next 14->15, wagmi 2->3) and introduce significant breaking changes that will likely break the application. The wagmi upgrade conflicts with peer dependencies in other packages in this monorepo and a yarn resolution in the root package.json. The next upgrade to v15 requires React 19, while the project uses React 18. Furthermore, the PR description notes that yarn.lock has not been updated, which is a critical step. Due to these critical issues, this PR cannot be merged as-is and requires a significant migration effort across the repository.

[gemini-code-assist]

Upgrading next from version 14 to 15 is a major version bump that introduces significant breaking changes. Next.js 15 uses React 19, but this project is currently configured with "react": "^18". This version mismatch will cause build failures or runtime errors. A full migration following the Next.js upgrade guide is required before this change can be safely merged.

[gemini-code-assist]

Upgrading wagmi from version 2 to 3 is a major version bump with breaking changes. This upgrade will cause dependency conflicts within the monorepo:

• The @account-kit/core and @account-kit/react packages have a peer dependency on wagmi: "^2.15.5".
• The root package.json enforces wagmi: "2.15.5" via yarn resolutions.

To resolve this, wagmi must be upgraded across all dependent packages in the monorepo, and the code must be adapted to the new breaking changes.