Analog shipped 40 release events in 30 days and 30 GitHub releases in 90 days. That is the signal. This is not a quiet Angular side project, it is a fast-moving fullstack framework with active work happening across stable, beta, and alpha channels.

The official site positions Analog as a fullstack meta-framework for Angular, powered by Vite and Nitro. Its public pitch is specific: Vite and Vitest support, hybrid SSR and SSG, file-based routing, API routes, and server-side data fetching. The GitHub repository repeats the same framing: “The fullstack meta-framework for Angular. Powered by Vite and Nitro.”

The interesting part is where the releases concentrate

The recent release notes are not splashy marketing drops. They are compiler and integration work.

The v2.5.0 release is packed with angular-compiler fixes, including type-only import elision, signal API downleveling, Angular v19 and v20 defensive handling, and Ivy metadata output details. The v2.5.1 beta releases then keep tightening vite-plugin-angular behavior, including fastCompile handling, defer walker behavior, and @defer nested inside @switch and @case.

That suggests Analog is betting on being more than routing sugar for Angular. It is working close to the compilation path, Vite integration, and Nitro-backed prerendering. The v3.0.0 alpha track adds the same flavor of work, with fixes around content slugs, CSS ?inline imports, TypeScript extension matching, plus a fastCompile registry hook and recursive prerender option.

This is maintenance-heavy work. That is a compliment. Framework users feel polish most when compiler edge cases stop breaking their builds.

ToolVitals reads this as active, not automatically mature

ToolVitals gives Analog a 100 shipping score, 92 health score, and 90 ToolVitals score. It also records 3,118 GitHub stars and a 212.7 hot score, with 77 data confidence.

Those numbers support one claim cleanly: Analog is being actively maintained and released. They do not prove that the framework is the right default for every Angular team.

What the data does not tell us

ToolVitals sees releases, stars, website availability, SSL, and related public signals. It does not see code quality, production adoption, revenue, support load, user satisfaction, migration pain, or whether your specific Angular app will build cleanly.

The recent release notes also show a lot of bug-fix velocity. That can mean strong maintenance. It can also mean the compiler and Vite integration surface is sharp. The safe read is simple: Analog is moving quickly in a technically demanding part of the Angular stack.

Compared with nearby framework entries

Analog has far fewer stars than TanStack Query, 3,118 versus 49,341, but it shipped many more release events in the last 30 days, 40 versus 8. That comparison is not product-for-product, TanStack Query solves a different problem, but it does show Analog’s current release cadence is unusually high for the Frameworks & Libraries category.

Qwik has 22,001 stars and 12 release events in 30 days. Analog has fewer stars but more than triple the recent release events. Again, this is not a popularity win. It is a shipping signal.

Recommendation

If your team already uses Angular and wants Vite, SSR or SSG, file-based routing, API routes, and Nitro-style fullstack deployment in one framework, evaluate Analog now. Start with a non-critical app or a migration spike, because the release stream shows serious momentum, but also a lot of ongoing compiler and integration churn.

Sources