Reactive primitives for Ethereum apps
Reliability breakdown
Component scores measured daily from GitHub activity (2026-04-12).
Activity on 0 of 43 tracked days in the last 90 and 0 of 30 in the last 30.
Merged 0 of 0 PRs opened and closed 0 of 0 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.
Last push 3 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
Open-issue load isn't tracked for this repo yet.
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Topics
Jump into the topic listings this repository belongs to.
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Apr 12, 2026
Current3
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current6
Previous0
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current4
Previous7
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current7
Previous6
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current4
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 7, 2026
Current0.50
Previous3.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
9 observed daily rows. Missing days are not fabricated.
Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).
| Date | Issues opened | Issues closed | Stored score |
|---|
Apr 10, 2026
Current0.00
Previous0.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
40 observed daily rows. Missing days are not fabricated.
Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).
| Date | PRs opened | PRs closed | Stored score |
|---|
Join the conversation
Share what you know about wagmi — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting wagmi.
Project Q&A
Browse implementation threads tied directly to wevm/wagmi. Each question links through to the full answer page.
Be the first to ask how teams run wagmi in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses wagmi — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post