Next.js is not coasting on React mindshare. ToolVitals sees 7 release events in 30 days, 30 releases in 90 days, a 100 shipping score, and 139557 GitHub stars. For a framework this mature, that is not maintenance mode. It is heavy machinery still moving.

The interesting signal is the shape of the recent canary releases. The v16.3.0-canary line is full of changes around Turbopack, caching, React Server Components paths, streaming, CI, tests, and developer workflow. That matches the official positioning: Next.js sells itself as the React framework for the web, with full-stack features, routing, rendering, caching, and production tooling built in.

This is the bet: Next.js is trying to make the framework boundary wider, not smaller. The Next.js 16 announcement frames the release around Turbopack, caching, architecture, Devtools MCP, and React 19.2 support. The canary releases after that read like follow-through, not a marketing artifact.

The canary stream is the story

The recent release notes are not all headline features. That is the point.

v16.3.0-canary.6 includes route-level revalidation behavior, Turbopack worker asset prefix work, server HMR for metadata routes, next/image error handling, RSC request header validation, and an edge runtime deprecation note. v16.3.0-canary.8 includes streaming fixes for draft mode cache components and metadata support in robots.ts. v16.3.0-canary.3 includes React canary movement, a new ESLint rule, cache-busting changes, Turbopack docs and edge case support, and AGENTS.md / CLAUDE.md generation in next dev.

That mix says the team is fighting on three fronts at once: runtime correctness, build system performance, and developer workflow. The AGENTS.md / CLAUDE.md item is especially telling. Next.js is not treating AI coding assistants as outside the framework experience. It is beginning to shape the local dev environment around them.

The ToolVitals score reflects that breadth. Next.js has a 98 ToolVitals score, 95 health score, and 100 shipping score. Those are not quality guarantees. They are activity and maintenance signals, and here the signals are strong.

What ToolVitals cannot infer

ToolVitals can see releases, stars, uptime-style signals, licensing metadata, and scoring inputs. It cannot tell whether a migration to Next.js 16 will be painless for your app. It cannot measure your build time, your cache invalidation bugs, your hosting bill, or whether your team likes the App Router.

It also cannot judge code quality from release count alone. Seven release events in 30 days can mean velocity. It can also mean churn. For Next.js, the browsed release notes show a lot of low-level framework work, test work, and build-tool work, so the conservative read is: active development is real, but teams should still test canary changes against their own workloads.

The license signal is clear. The payload classifies Next.js as OSI-approved OSS, and the repository license page shows MIT. That supports calling Next.js open source, not merely source-available or fair-code.

Comparisons worth making

Among related framework tools, TanStack Query has 49488 GitHub stars, a 96 shipping score, and 7 release events in 30 days. Next.js matches that 30-day release-event count while operating at a much larger star base, 139557 stars, and with a 100 shipping score.

Analog shows 10 release events in 30 days and a 98 shipping score, but at 3123 GitHub stars. That makes Analog look fast-moving for its size. Next.js looks different: huge, mature, and still shipping at a top-tier cadence.

Compared with broader developer tools, LangChain posted 18 release events in 30 days with 137425 stars and a 100 shipping score. Next.js has fewer 30-day release events, but nearly the same star scale and a higher ToolVitals score of 98 versus the related-tool data shown here only where supplied. The fair comparison is not that Next.js is the fastest project in the set. It is that it remains extremely active for a foundational framework.

Recommendation

If your team is already committed to React and wants one framework to handle routing, rendering, caching, server actions, image optimization, and production build tooling, evaluate Next.js seriously. The activity data supports that it is maintained hard, not just famous.

If your team needs a quiet dependency with minimal framework churn, do not blindly chase the canary stream. Track stable releases, read the upgrade guide, and test caching, streaming, and Turbopack behavior in your own app before moving production.

The concrete read: Next.js is still a default choice for React application teams that want a full-stack framework and can absorb active framework evolution. The release cadence is a feature if you need the platform to keep moving. It is a cost if your priority is calm.

Sources