TanStack Query is not a sleepy package. The repo has 49,220 stars, 4,611 commits, 2,055 tags, 43 branches, and 30 releases in the last 90 days. ToolVitals gives it a 97 score, with 95 on health and 100 on shipping. That is platform-level motion, not maintenance theater.
The official site frames TanStack as the open-source application stack for the web, and Query’s docs describe it as powerful asynchronous state management for TS/JS apps across React, Vue, Solid, Svelte, and Angular. The docs keep the pitch concrete, fetch, cache, update, and wrangle async data without global state. The bet is simple. Query is the data layer inside a multi-framework stack, not a React-only helper.
What the release trail says
The most interesting signal is not the star count. It is the release discipline. TanStack announced Solid 2.0 beta support in Query, Router, and Start on Apr 10, and the GitHub repo TanStack/query shows a fresh main-branch commit from Apr 26 plus a March release-workflow change. The team is still tightening integrations and pushing framework coverage, which is exactly what a serious library looks like when it becomes infrastructure.
What the data does not tell you
This data does not tell you whether Query is easy to adopt, fast in your app, or loved by every team. ToolVitals sees stars, commits, releases, SSL, and uptime. It does not see code quality, migration pain, incident rates, developer sentiment, or whether the abstraction fits your architecture. The 66 open issues and 86 open PRs are backlog shape, not a verdict.
Framework peers
Against other frameworks in the ToolVitals set, Query sits in a strong but not extreme spot. Next.js has 139,156 stars and 30 release events in 30 days. Qwik has 21,986 stars and 12 release events in 30 days. Query sits at 49,220 stars and 8 release events in 30 days. It is smaller than Next.js, bigger than Qwik, and still clearly moving.
Bottom line
If your team needs a server-state layer for a multi-framework app, evaluate TanStack Query first. The numbers say it is stable, widely adopted, and still shipping. If you want a quiet utility with no churn, this is the wrong bet. If you want a mature data layer that still gets real attention across React, Solid, Svelte, Vue, and Angular, this is one of the safest choices in the category.