TanStack Query is not coasting on React Query nostalgia. ToolVitals measured 61 release events in 30 days and 30 GitHub releases in 90 days, and the recent release trail is not random noise. It shows a mature server-state library being pushed across framework adapters, especially around Solid 2 and the wider TanStack package set.

What TanStack Query says it is

The official TanStack site frames the larger project as “the open-source application stack for the web,” with headless, type-safe, composable tools for modern web applications. That wording matters because Query is not presented as a React-only helper anymore. The site says TanStack libraries start with a provider-agnostic core and can be used with React, Vue, Solid, Angular, vanilla JS, and other adapters.

The TanStack Query docs sharpen that into a more specific claim: “Stop syncing server data by hand.” The docs describe Query as a server-state manager that gives async data a cache, a lifecycle, and declarative APIs for fetching, sharing, refetching, mutating, and observing server state across TypeScript applications. That is the core problem. Server data is remote, shared, cached, sometimes stale by design, and often updated by background work. Query exists because trying to model that with local client-state primitives usually produces a mess of effects, reducers, duplicated fetches, and stale UI.

The GitHub repository says the same thing in plainer engineering language. It calls TanStack Query an async state management library built to simplify fetching, caching, synchronizing, and updating server state. The repository lists protocol-agnostic fetching for REST, GraphQL, promises, and similar sources. It also calls out caching, refetching, pagination, infinite scroll, mutations, dependent queries, background updates, prefetching, cancellation, and React Suspense support.

That scope explains why the project has so many packages. Query is not just useQuery for React. The local excerpts and release pages show React Query, Solid Query, Svelte Query, Vue Query, Angular Query, Lit Query, Preact Query, devtools packages, persistence packages, core packages, and lint tooling moving under the same repository. The product direction is clear: keep the server-state model stable, then make it available in the frameworks teams actually use.

TanStack Query is OSI-approved open-source software under the MIT license, according to the ToolVitals openness payload. That label is safe here. The TanStack site also emphasizes independence, no vendor lock-in, no platform bias, and no paid products in its library positioning. ToolVitals does not track hosted pricing for this tool.

The metrics say mature, not sleepy

ToolVitals gives TanStack Query a 98 ToolVitals score, a 95 health score, a 100 shipping score, and a 225.0 hot score. It tracks 49,836 GitHub stars, 61 release events in the last 30 days, 30 GitHub releases in the last 90 days, and 100 data confidence. The payload does not include 30-day commit count or active contributor count, so those should stay out of the argument.

The headline number is 61 release events in 30 days. That is high for a framework library, but it needs context. TanStack Query is a multi-package repository. One underlying change can create separate releases for Solid Query, Solid Query Devtools, Solid Query Persist Client, Angular Query Experimental, Lit Query, Preact Query Devtools, Query Core, and other packages. Release event volume is still a useful signal, but it is not the same thing as 61 independent product decisions.

That caveat makes the signal more interesting, not less. A project with many adapters has to keep versioning, dependency edges, docs generation, framework behavior, and tests aligned. The June release notes show exactly that kind of work. This is not a dormant package getting cosmetic bumps. It is a widely used server-state layer receiving adapter maintenance and beta migration work across several framework surfaces.

Compared with related tools in the ToolVitals payload, TanStack Query sits in a strong middle position. Next.js has 140,233 stars, a 229.2 hot score, a 100 shipping score, and 46 release events in 30 days. Vite has 81,661 stars, a 223.0 hot score, a 100 shipping score, and 12 release events in 30 days. TanStack Query has fewer stars than both Next.js and Vite, but its 61 release events are higher than both. That does not make it bigger. It says its release machinery is unusually active for its size.

LangChain is hotter by ToolVitals numbers, with a 239.7 hot score, 140,348 stars, and 34 release events in 30 days. n8n has 82 release events in 30 days and a 235.0 hot score, but ToolVitals classifies n8n as fair-code, not OSI-approved open source. TanStack Query is a different kind of bet: smaller than the largest developer platforms by stars, more actively released than several larger framework peers, and cleanly MIT licensed.

The recent releases point to adapter depth

The most useful first-party evidence is the June 26 release set. The GitHub release release-2026-06-26-1226 is marked as a pre-release and includes fixes for Solid Query rendering resolved SSR values for deferred queries, Solid Query Devtools mount and unmount behavior, mutation subscriber scope, and Solid 2.0 test usage. The same release includes refactors for Solid 2 reactivity compliance and updating Solid Query v6 work to Solid 2.

The package-specific release pages tell the same story from another angle. @tanstack/solid-query@6.0.0-beta.5, @tanstack/solid-query-devtools@6.0.0-beta.5, and @tanstack/solid-query-persist-client@6.0.0-beta.5 all cite the upgrade to Solid v2 beta 15 through pull request #10616. The shared dependency updates make the release cluster look noisy in a feed, but the content is coherent. Solid support is being moved through a v6 beta line while Solid itself is moving through v2 beta releases.

The June 23 releases broaden that picture. @tanstack/angular-query-experimental@5.101.1 and @tanstack/lit-query@0.2.8 both update dependencies to @tanstack/query-core@5.101.1. @tanstack/preact-query-devtools@5.101.1 updates its related Preact Query and Query Devtools dependencies. The @tanstack/eslint-plugin-query@5.101.1 release exists in the same group even though the local excerpt contains no detailed changes.

The interpretation is conservative: TanStack Query is investing in framework adapters and package alignment, not only in the React path. The evidence does not prove equal feature maturity across every adapter. Angular is explicitly labeled experimental in the package name. Solid v6 is in beta. Lit is on a much lower version line. Still, the repository and release pages show an active attempt to keep the server-state core useful outside React.

That matters for technical teams that have more than one frontend. A React-only data library can be enough when a company standardizes hard on React. TanStack Query is more attractive when teams have React in the main app, Solid or Vue in newer surfaces, Angular in older admin tooling, or Lit components in embedded products. The best reason to evaluate it is not hype. It is that query keys, cache lifecycles, invalidation, background updates, and mutation workflows become a shared mental model across UI stacks.

What the numbers can mislead you about

ToolVitals can measure visible activity. It sees stars, releases, release events, openness signals, data confidence, and related health indicators such as site checks when available. It does not see whether a cache strategy fits your application, whether your team will misuse invalidation, whether devtools catch your real bugs, or whether a migration from another data layer will pay back its cost.

Release velocity can also punish projects that package carefully. TanStack Query’s 61 release events in 30 days look dramatic beside Vite’s 12, but a multi-adapter package set will naturally produce more release objects. The correct read is not “61 big launches.” The correct read is “a high-touch package family with many adapter surfaces and active release automation.”

Stars have their own trap. 49,836 GitHub stars is a strong adoption signal, but stars are not installs, production usage, revenue, support quality, or maintenance capacity. The TanStack Query docs page includes public popularity counters, but this post uses ToolVitals as the source of truth for tracked stars and activity figures. That keeps the scoring argument consistent.

A skeptical buyer should ask boring questions before adopting. Which adapters are first-class for your framework? How much stale data can your product tolerate? What are the retry defaults? Who owns query key design? How will you test optimistic mutations and rollback paths? TanStack Query gives you good primitives, but it will not save a team that treats cache invalidation as an afterthought.

What maintainers should notice

The release notes are helpful because they make adapter work legible. The June 26 notes name Solid SSR behavior, devtools lifecycle behavior, mutation subscriber scope, Solid 2 reactivity compliance, and docs generation cleanup. That is the kind of specificity technical readers trust.

The weak spot is feed readability. ToolVitals sees many release events, and casual readers can confuse package churn with strategic change. Maintainers could make this even clearer by grouping release summaries around themes: Solid 2 migration, Query Core dependency propagation, devtools alignment, documentation tooling, and experimental adapter status. The raw release stream is transparent, but a monthly engineering note would translate the work for teams choosing a data layer.

That recommendation is not cosmetic. Multi-framework libraries need confidence. Buyers want to know which adapter is stable, which is beta, which is experimental, and which release train carries breaking risk. TanStack already exposes much of that through package names and release notes. A higher-level release digest would reduce the work required to understand the direction.

Recommendation

If your team builds TypeScript frontends and keeps reimplementing server-state behavior with effects, reducers, custom stores, and manual refetch flags, evaluate TanStack Query. The official docs describe the right problem, the GitHub repository shows broad server-state primitives, and ToolVitals measures a project that is both mature and actively shipping.

The best fit is a team that wants a shared model for caching, mutations, invalidation, background refetching, and devtools across more than one frontend surface. The caution is adapter maturity. React users are on the safest path. Solid teams should look closely at the v6 beta and Solid 2 release notes. Angular users should treat the experimental package name seriously.

TanStack Query’s current signal is simple: 49,836 stars, a 98 ToolVitals score, 100 shipping score, 61 release events in 30 days, MIT licensing, and first-party evidence of serious adapter work. If server-state bugs are eating your frontend time, this is one of the few libraries where the activity is not just noise. It maps directly to the hard parts teams keep rebuilding badly.

Sources