Skip to content

[Snyk] Upgrade wagmi from 2.12.12 to 2.18.2 #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Dargon789 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade wagmi from 2.12.12 to 2.18.2 #10

Dargon789 wants to merge 1 commit into from

Conversation

@Dargon789
Copy link
Owner

@Dargon789 Dargon789 commented Nov 12, 2025

snyk-top-banner

Snyk has created this PR to upgrade wagmi from 2.12.12 to 2.18.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 69 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
critical severity Missing Encryption of Sensitive Data
SNYK-JS-COINBASEWALLETSDK-8717118		 674 No Known Exploit
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577916		 674 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577917		 674 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577918		 674 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8172694		 674 No Known Exploit
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303		 674 Proof of Concept
critical severity Information Exposure
SNYK-JS-ELLIPTIC-8720086		 674 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303		 674 Proof of Concept
critical severity Information Exposure
SNYK-JS-ELLIPTIC-8720086		 674 Proof of Concept
high severity Improper Validation of Integrity Check Value
SNYK-JS-SECP256K1-8237220		 674 Proof of Concept

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
fix: upgrade wagmi from 2.12.12 to 2.18.2
1fba16c 
Snyk has created this PR to upgrade wagmi from 2.12.12 to 2.18.2.

See this package in yarn:
wagmi

See this project in Snyk:
https://app.snyk.io/org/apichanmittare/project/2749ecc3-509c-4550-ba7a-f6f899e9eb4c?utm_source=github&utm_medium=referral&page=upgrade-pr
@gemini-code-assist
Copy link

gemini-code-assist bot commented Nov 12, 2025

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 focuses on enhancing the project's security posture by upgrading the wagmi dependency to its latest stable version. This update is crucial for mitigating several identified critical and high-severity vulnerabilities, ensuring the application remains robust and protected against known exploits. The change is primarily a version bump to incorporate the latest security patches and improvements from the wagmi ecosystem.

Highlights

  • Dependency Upgrade: The wagmi library has been upgraded from version 2.12.12 to 2.18.2.
  • Security Vulnerability Fixes: This upgrade addresses multiple critical and high-severity security vulnerabilities, including 'Missing Encryption of Sensitive Data' in coinbase-wallet-sdk and 'Improper Verification of Cryptographic Signature' in elliptic and secp256k1.
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. ↩

@snyk-io
Copy link

snyk-io bot commented Nov 12, 2025

✅ 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[bot]
gemini-code-assist bot reviewed Nov 12, 2025
View reviewed changes
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, automatically generated by Snyk, upgrades the wagmi dependency from 2.12.12 to 2.18.2 to address several critical and high-severity security vulnerabilities. While this is an important and necessary update, the review has identified a critical issue: the viem dependency, a peer of wagmi, has not been upgraded alongside it. This can lead to multiple versions of viem in the project, causing potential runtime errors and incorrect behavior. It is strongly recommended to upgrade viem to a compatible version to ensure the stability and correctness of the application.

package.json
"sharp": "^0.32.6",
"viem": "^2.13.1",
"wagmi": "^2.12.12",
"wagmi": "^2.18.2",
Copy link

@gemini-code-assist gemini-code-assist bot Nov 12, 2025

Choose a reason for hiding this comment

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

critical

While upgrading wagmi is crucial for security, it's equally important to upgrade its peer dependency viem to avoid runtime issues. wagmi and viem are tightly coupled, and a version mismatch can lead to subtle bugs and errors like instanceof checks failing.

Your package.json currently specifies viem: "^2.13.1", which is outdated for this version of wagmi. Other dependencies are already pulling in much newer versions of viem (up to 2.39.0 as seen in yarn.lock), creating multiple viem versions in your node_modules.

To ensure compatibility and a single version of viem, please upgrade it in your package.json alongside wagmi. I recommend aligning it with the latest versions being used. You should modify line 28 in package.json to:

"viem": "^2.39.0"

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

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Dargon789 @snyk-bot