Qwik is still in beta, and it is shipping like a framework trying to prove a hard thesis. ToolVitals gives it a 97 score, 94 health, 100 shipping, 21,986 GitHub stars, and 12 release events in the last 30 days. The homepage says the quiet part out loud, deliver instant apps at scale, then backs that up with resumability and skipped hydration.
The interesting part is not just velocity. It is the shape of the releases. In @qwik.dev/core@2.0.0-beta.31, the team added negative intervals for useAsync so cache invalidation can happen without recalculation, plus asyncSignal.invalidate(info) for passing context into the calculation path. In @qwik.dev/core@2.0.0-beta.32, that API shifts again, interval becomes expires, poll appears, and Qwik adds passive:eventname and capture:eventname markers for JSX event handlers. That looks like a team tightening the framework contract, not just sanding off bugs.
The optimizer release points the same way. @qwik.dev/optimizer@2.1.0-beta.2 adds inline @qwik-disable-next-line hints and supports passive browser listeners. Qwik is betting that developer ergonomics matter, but only after the execution model is right. The repo README says it wants the fastest possible page load times with almost no JavaScript, and the recent releases show that the team is still tuning how that promise works in practice.
What the data does not tell you
ToolVitals sees releases, stars, commits, SSL, and uptime. It does not see code quality, user satisfaction, revenue, or whether the product feels good in production. The release notes prove active maintenance and a live beta, not that the architecture wins every real-world benchmark.
The data also does not prove adoption depth. 21,986 stars is a solid signal, but it is still much smaller than the biggest frameworks in the category. The release cadence says Qwik is moving. It does not say the market has already decided.
Competitor context
Next.js is larger, with 139,156 stars and 30 release events in the last 30 days. TanStack Query has 49,220 stars and 8 release events in the same window. Qwik sits below both on size, but it is shipping faster than TanStack Query and not far behind the broader framework cadence you see in Next.js.
Bottom line
If your team cares more about load behavior than default familiarity, Qwik deserves a serious evaluation. If you need a framework that feels settled, wait. The release notes show a team still shaping the contract, and that is exactly what a serious beta should look like.