Skip to content

[Snyk] Security upgrade wagmi from 2.14.15 to 3.0.0#1

Open
snyk-io[bot] wants to merge 1 commit intomainfrom
snyk-fix-d4247b8b9bd569beb6a37314cc88f9b5
Open

[Snyk] Security upgrade wagmi from 2.14.15 to 3.0.0#1
snyk-io[bot] wants to merge 1 commit intomainfrom
snyk-fix-d4247b8b9bd569beb6a37314cc88f9b5

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io bot commented Dec 2, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • examples/next-wagmi-solana-bitcoin-app-router/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
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303
  786  

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.

…duce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-ELLIPTIC-8187303
@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Dec 2, 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.

"react-dom": "19.0.0",
"viem": "2.23.13",
"wagmi": "2.14.15"
"wagmi": "3.0.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: Upgrading wagmi to v3.0.0 breaks useAccount imports, causing module load failure.
Severity: CRITICAL | Confidence: High

🔍 Detailed Analysis

The application attempts to import useAccount from the wagmi package in examples/next-wagmi-solana-bitcoin-app-router/src/components/ConnectButton.tsx. However, wagmi version 3.0.0, which is introduced by this pull request, has removed the useAccount hook, renaming it to useConnection. This will cause an immediate module load failure and prevent the application from starting due to a non-existent export.

💡 Suggested Fix

Update all instances of useAccount to useConnection and other renamed hooks in the codebase to align with wagmi v3.0.0 API changes.

🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: examples/next-wagmi-solana-bitcoin-app-router/package.json#L23

Potential issue: The application attempts to import `useAccount` from the `wagmi`
package in
`examples/next-wagmi-solana-bitcoin-app-router/src/components/ConnectButton.tsx`.
However, `wagmi` version 3.0.0, which is introduced by this pull request, has removed
the `useAccount` hook, renaming it to `useConnection`. This will cause an immediate
module load failure and prevent the application from starting due to a non-existent
export.

Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 4940458

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.

0 participants