reduxjs/redux

Choose this fork only if you need the older docs/site customization history; for production or ongoing Redux work, the upstream repo is the better base because this fork is stale and substantially behind.

Prefer upstream unless you specifically need a frozen legacy Redux teaching fork. This fork is stale, materially behind, and better suited to legacy maintenance or historical reference than active development.

Choose the fork only if you want its custom docs-site experience or a frozen legacy snapshot. For anything current, maintainable, or library-focused, upstream Redux is the better choice.

Prefer the fork only if you need a historical, self-contained Redux snapshot. If you want a current Redux base, upstream is the clear choice.

Prefer upstream unless you explicitly need an archival 2018-era Redux snapshot. This fork offers some reproducible example setup, but it is far too stale for most new adopters.

Choose upstream unless you explicitly need an early historical snapshot. This fork looks too stale and too far from current Redux to be a good adoption target for new work.

Prefer upstream Redux unless you explicitly want a dormant snapshot. This fork offers no visible added capability and is materially behind upstream, so it is a poor choice for new adoption.

Prefer upstream unless you need a frozen 2022-era snapshot. This fork shows no added capability and is materially behind current Redux, so it is a poor choice for adopters who want maintained features, fixes, or ecosystem compatibility.