wevm/wagmi

Reactive primitives for Ethereum apps

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 9th, 2026
Created on November 23rd, 2021
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 1,440
Total Stargazers: 6,747 (+0)
Total Subscribers: 40 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 536 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 2

Top labels

  • Needs Reproduction (48)
  • Area: Docs (17)
  • Good First Issue (7)

Most active issues this week

Detailed Description

Wagmi is a reactive primitives library for building Ethereum applications with React and Vue.

The library addresses the challenge of managing blockchain state and interactions in decentralized applications by providing hooks and composables that handle wallet connections, contract interactions, and on-chain data fetching. It abstracts away the complexity of managing asynchronous blockchain operations and state synchronization, allowing developers to work with reactive primitives that automatically update when blockchain data changes. The tool builds on Viem, a low-level Ethereum library, to provide higher-level abstractions suited to frontend frameworks.

Wagmi suits developers building dApps with React or Vue who want to avoid boilerplate around wallet management and contract calls. It works well for applications that need to respond reactively to blockchain state changes and user interactions with smart contracts. The library is particularly valuable for teams that want framework-level abstractions rather than managing raw Ethereum JSON-RPC calls directly.

The project maintains active community engagement through GitHub discussions and a Discord server for peer support. Development activity shows consistent attention to code quality, with test coverage tracked and security practices formalized through OpenSSF best practices compliance.