TanStack/query

Choose this fork only if you want a customized, older TanStack Query baseline and are willing to own the maintenance burden. For most adopters, upstream is the safer choice because this fork is materially stale and has enough divergence to make future upgrades expensive.

Prefer this fork only if you need the legacy React Query codebase exactly as-is. For new work, or if you want active maintenance and current ecosystem support, upstream TanStack Query is the safer choice.

Choose this fork only if you need its local API/tooling changes and can tolerate major upstream drift. If you want the safest path for new projects or low-maintenance adoption, upstream is the better default.

Choose this fork only if you need the older React Query lineage and are willing to own maintenance. For most adopters, upstream TanStack Query is the safer default because it is far more current, broader in scope, and actively maintained.

Choose this fork only if you specifically need an older, frozen TanStack Query baseline. For most adopters, upstream is the better choice because this fork is far behind and likely missing important fixes and developer tooling.

Choose this fork only if you need the old React-only React Query line and are comfortable owning maintenance. If you want current features, active fixes, or multi-framework support, upstream TanStack Query is the better choice.

Choose this fork only if you need a frozen, React-only legacy base. For new work or active maintenance, upstream TanStack Query is the better choice.

Prefer this fork only if you need an old React-only baseline and are willing to maintain it yourself. For most teams, modern upstream is the better choice because it is active, broader in scope, and much less risky to adopt.

Choose this fork only if you are maintaining legacy code that depends on its older React-only behavior or its small local tweaks. For new work, or if you need current features, active maintenance, or multi-framework support, upstream is the better choice.