About Zustand
Minimal state manager for React with hooks-based API, immutable updates, and no boilerplate; scales from small widgets to larger apps.
๐ป Bear necessities for state management in React
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-18).
Activity on 34 of 90 tracked days in the last 90 and 7 of 30 in the last 30.
Merged 25 of 48 PRs opened and closed 3 of 3 issues opened over the last 90 tracked days โ PR flow carries 55% of this component, issue flow 45%.
4 releases in the last 180 days, 2 in the last 90 and 0 in the last 30 โ a steady cadence scores highest.
Last push 6 days ago โ freshness decays as pushes age (roughly halves every 83 days without a push).
2 open issues against 58,448 stars โ about 0 open issues per 1,000 stars. Lighter backlogs score higher.
Modeled โ lower is better; concentration of commits in few maintainers. Contributors graph
Minimal state manager for React with hooks-based API, immutable updates, and no boilerplate; scales from small widgets to larger apps.
Join the conversation
Share what you know about zustand โ 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 zustand.
Project Q&A
Browse implementation threads tied directly to pmndrs/zustand. Each question links through to the full answer page.
Be the first to ask how teams run zustand 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 zustand โ a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post