/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

pmndrs/zustand

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:50:09.639Z

3mo ago

pmndrs/zustand

pmndrs/zustand is a popular React state-management library focused on a small, hook-based API with minimal boilerplate. It is active, not archived, and the repo shows recent maintenance as of March 2026. It ships documentation, examples, tests, and TypeScript support, so forks are most likely interesting if you want to customize or extend a widely used React state library rather than start from scratch.

Loading tags...

Stars57,562

Forks2,010

Default branchmain

Last pushed2026-03-24T00:14:03Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you specifically want its custom docs/demo direction and are willing to own long-term maintenance. If you want a current, well-supported Zustand baseline, upstream is the better choice.

Prefer upstream unless you specifically need this older, docs-heavy fork as a customization base or reference snapshot. The fork is stale, substantially diverged, and does not show clear evidence of new core capabilities that would outweigh the maintenance cost.

Prefer upstream unless you specifically need this fork’s older, customized documentation/test baseline. The fork looks materially stale and divergent, so it is better suited to legacy support or experimentation than production adoption.

Choose this fork only if you need its older build targets or existing local customizations. For new work, upstream Zustand is the better default because it is active, substantially newer, and much lower risk.

Prefer this fork only if you need an archived-style Zustand snapshot with custom learning material or older behavior. For production use, the active upstream is the safer choice because this fork is materially behind and appears to have stalled years ago.

Choose upstream unless you specifically need this fork's older customizations or are maintaining legacy behavior. The fork is materially stale and divergent, so it is best viewed as a historical/custom downstream, not the default adoption choice.

Prefer upstream `pmndrs/zustand` unless you specifically need this exact snapshot for local work. This fork does not show meaningful added capabilities, and its 27-commit lag makes it a weaker choice for adoption than upstream.

Prefer upstream unless you specifically need this older snapshot. This fork adds no evident capabilities and is materially behind on maintenance, so it is only attractive as a frozen baseline or archival copy.

Prefer this fork only if its documentation and workflow customizations are the goal. If you want the current zustand library with active maintenance, upstream is the better default.

Prefer this fork only if you specifically want its custom docs/workflows and are comfortable owning upstream backports. If you want the latest maintained Zustand behavior, upstream is the safer default.

Fork comparison

barelyhuman/zustand

38/100

stale

significant_divergence

Prefer this fork only if you specifically want its custom docs/demo direction and are willing to own long-term maintenance. If you want a current, well-supported Zustand baseline, upstream is the better choice.

Likely purpose

To maintain a customized teaching/demo-oriented Zustand distribution with rewritten docs, updated example tooling, and local test changes rather than staying current with upstream releases.

Best for

Teams that want to host or adapt their own Zustand documentation/demo site.; Developers maintaining a forked teaching repo or workshop materials.; Users who need a customized snapshot and do not plan to follow upstream closely.

Additional features

Expanded learning and tutorial material, especially in `docs/learn` and `docs/guides`.
Customized demo/example workflow, including large changes to `examples/demo` and package lockfiles.
Updated test coverage and type-test behavior around middleware, devtools, and async persistence.
Documentation restructuring and link fixes that appear aimed at making the fork easier to use as a standalone reference site.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

It is about 200 commits behind upstream, so it likely misses newer Zustand fixes, API refinements, and release packaging updates from 2023-2026.
Recent upstream improvements in `persist` and `devtools` behavior are absent unless they were manually backported.
Current upstream docs, examples, and build/release workflow changes are not reflected here.
The fork appears not to track ongoing upstream maintenance, which raises the risk of stale guidance and unresolved bugs.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.

Strengths

Useful if you want a frozen, customized Zustand learning site or demo environment.
Large doc and tutorial edits suggest stronger emphasis on onboarding and explanation than upstream.
The fork still preserves the core Zustand identity and broad React state-management use case.

Risks

High drift from upstream makes future merges expensive.
Staleness increases the chance of outdated docs, outdated dependency resolution, and missing bug fixes.
Consumers may assume upstream parity and get surprised by behavioral differences or missing fixes.