barelyhuman/zustand
stale
significant_divergence
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.
SHUBHAMRAJPUT9665/zustand
stale
significant_divergence
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.
JawadErfani01/zustand
stale
significant_divergence
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.
byteab/zustand
stale
significant_divergence
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.
Magicianred/zustand
stale
significant_divergence
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.
JeremyRH/zustand
stale
significant_divergence
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.
daisenqiu399/zustand
stale
significant_divergence
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.
xfactor-toml/zustand
stale
significant_divergence
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.