Skip to content

[Snyk] Security upgrade wagmi from 2.12.12 to 3.0.0#22

Open
Dargon789 wants to merge 1 commit intomainfrom
snyk-fix-6366f1d45e3d3ae25409c2df6b8c4614
Open

[Snyk] Security upgrade wagmi from 2.12.12 to 3.0.0#22
Dargon789 wants to merge 1 commit intomainfrom
snyk-fix-6366f1d45e3d3ae25409c2df6b8c4614

Conversation

@Dargon789
Copy link
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • 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
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  708  
high severity 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@snyk-io
Copy link

snyk-io bot commented Jan 22, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

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

@gemini-code-assist
Copy link

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! 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, performs a critical security upgrade by updating the wagmi dependency to its major version 3.0.0. This update is essential for mitigating two significant vulnerabilities, including a high-severity HTTP Request Smuggling issue, thereby enhancing the project's overall security posture.

Highlights

  • Dependency Upgrade: The wagmi package has been upgraded from version 2.12.12 to 3.0.0. This is a major version bump, which may introduce breaking changes.
  • Security Fixes: This upgrade addresses two identified vulnerabilities: "Use of a Cryptographic Primitive with a Risky Implementation" (medium severity, score 708) and "HTTP Request Smuggling" (high severity, score 636).
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request upgrades the wagmi dependency from version 2.12.12 to 3.0.0 to address reported security vulnerabilities. This is a major version upgrade, and the pull request description explicitly states that it introduces breaking changes. It is crucial to ensure that all consuming code is updated to be compatible with the new wagmi v3 API to prevent runtime issues.

"sharp": "^0.32.6",
"viem": "^2.13.1",
"wagmi": "^2.12.12",
"wagmi": "^3.0.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Upgrading wagmi to a new major version (3.0.0) implies significant breaking changes, as also indicated in the PR description. Merely updating the version in package.json is insufficient. The application code, particularly components/shared/WalletProvider.tsx which utilizes WagmiProvider and getDefaultConfig, needs to be reviewed and updated to align with the wagmi v3 API. Failure to do so could lead to runtime errors and unexpected behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments