Next.js is not coasting on framework incumbency. ToolVitals shows 31 release events in 30 days, 30 GitHub releases in 90 days, a 100 shipping score, and 139,314 GitHub stars. The public release trail backs the shape of that signal: this is a mature project still cutting canaries at startup speed.

The interesting part is not the count by itself. It is what is inside the recent canaries.

The Next.js site still positions the project plainly as “The React Framework for the Web,” with built-in routing, data fetching, Server Actions, React Server Components, image and font optimization, streaming, route handlers, middleware, and the current Next.js 16 release notes linked from the homepage. That matches the repo description, “The React Framework,” but the release notes show a broader bet than a React wrapper.

Recent canaries touch streaming in draft mode, cache components, route-level revalidation, metadata routes, robots.ts directives, Turbopack asset prefix behavior, trace-server loading, Rust crate dependencies, CI, Playwright traces, and test stability. That is boring in the best technical sense. Next.js is spending release bandwidth on the plumbing that decides whether large apps build, cache, stream, and debug predictably.

The signal in the canary stream

A framework with 139,314 stars does not need canary churn to prove demand. Next.js already has that. The 31 release events in 30 days say something different: Vercel is treating framework infrastructure as a constantly moving surface, especially around caching, streaming, Turbopack, and developer workflow.

Next.js 16 makes that direction explicit. The release post calls out Cache Components, Devtools MCP, the proxy.ts replacement for middleware naming, improved logging, stable Turbopack, React Compiler support, enhanced routing, and React 19.2 support. ToolVitals does not score feature quality, but the first-party material shows the team pushing on full-stack React architecture, not just page routing.

The canary notes are also a useful reality check. Several recent entries are operational: preserve Playwright traces on failure, fix deploy tests under AI coding assistants, remove leftover Turbopack manifests, optimize trace loading, speed up native postinstall scripts, and adjust release scripts. That is not launch-post theater. It is maintenance work on a very large codebase.

What ToolVitals can and cannot infer

ToolVitals can say Next.js is heavily maintained by public release activity. It can say the project has a 95 health score, a 100 shipping score, a 94 ToolVitals score, and 96 data confidence. It can also say the repo and website were reachable during this check, and that recent first-party releases are real GitHub prereleases.

ToolVitals cannot say the latest canaries are safe for your production app. It cannot measure upgrade pain, runtime regressions, issue response quality, commercial adoption, developer happiness, or whether Turbopack is faster for your particular monorepo. It sees public maintenance signals, not lived production outcomes.

That matters here because high release velocity cuts both ways. A fast canary stream is great if you need fixes quickly or track framework internals closely. It is noise if your team wants a quiet dependency with rare changes.

How it compares

Against related framework tools in the payload, Next.js is the outlier on release volume. TanStack Query shows 8 release events in 30 days and 49,341 stars. Qwik shows 12 release events in 30 days and 22,001 stars. Next.js shows 31 release events in 30 days and 139,314 stars.

LangChain is close on cadence with 36 release events in 30 days and 136,054 stars, but it sits in developer tools, not the framework category. That comparison is still useful: Next.js is shipping at a pace more like a fast-moving AI tooling project than a settled web framework.

Recommendation

If your team is building a serious React application with server rendering, streaming, caching, and routing requirements, evaluate Next.js because the maintenance signal is unusually strong and the current product direction matches those problems.

Do not adopt it just because the score is high. If your app is small, static, or allergic to framework churn, the same 31 release events that look healthy to ToolVitals may be more movement than you want. Pick Next.js when you need the framework surface area it is actively investing in, especially caching, Turbopack, React Server Components, and full-stack React workflows.

Sources