OpenEXR
A second IDManifest flaw lands two weeks after OpenEXR's forty-CVE sweep
A side-by-side editorial comparison of HeroUI and shadcn/ui — release velocity, themes, recent moves, and the top alternatives to consider.
HeroUI grew a component catalogue, then wired it into a chat editor.
The feed runs from March 2024 to July 2025 and stops there, so nothing here describes the last twelve months. Across that stretch the pattern is consistent: batches of components counted in the headline, a page reorganisation once the catalogue outgrew a flat list, framework currency with React 19 and Next.js 15 and later TailwindCSS v4, and a rebrand from NextUI Pro to HeroUI Pro in January 2025. The one change of kind is instant editing of any component inside HeroUI Chat.
shadcn/ui is turning a component registry into infrastructure for AI app UIs.
shadcn/ui has stopped being just a Radix-based component registry. It now supports three primitive bases - Radix, Base UI (the default since July) and React Aria - and has been shipping registry infrastructure of its own: GitHub-repo registries in June, server-side search in July. The newest work sits outside components entirely, in @shadcn/helpers, a utility package aimed at AI SDK and TanStack AI.
The feed runs from March 2024 to July 2025 and stops there, so nothing here describes the last twelve months. Across that stretch the pattern is consistent: batches of components counted in the headline, a page reorganisation once the catalogue outgrew a flat list, framework currency with React 19 and Next.js 15 and later TailwindCSS v4, and a rebrand from NextUI Pro to HeroUI Pro in January 2025. The one change of kind is instant editing of any component inside HeroUI Chat.
The archived arc moves from selling a catalogue to selling a workflow — a component is worth more if it can be customised where it is chosen rather than copied into an editor first. Framework support releases show the other constant: a paid component library lives or dies on how quickly it tracks the framework underneath it. What has happened since July 2025 is not visible from this source.
No recent entries support a confident prediction; the actionable finding is that this feed has been silent for roughly a year and needs re-pointing before HeroUI's direction can be read.
shadcn/ui has stopped being just a Radix-based component registry. It now supports three primitive bases - Radix, Base UI (the default since July) and React Aria - and has been shipping registry infrastructure of its own: GitHub-repo registries in June, server-side search in July. The newest work sits outside components entirely, in @shadcn/helpers, a utility package aimed at AI SDK and TanStack AI.
Two arcs run in parallel. One is decoupling from any single primitive vendor, which turns the registry into a distribution layer rather than a wrapper around Radix. The other is a push up the stack into AI application code - chat interface components in June, typeset for streaming text in July, and now mocks for paused tool calls and approvals. The components are becoming a means to a larger surface.
Expect the helpers line to keep extending along agent-workflow states - the entries so far move from introduction, to chat surfaces, to human-in-the-loop - and more composite patterns like Questionnaire rather than new primitives.
Other Design products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either HeroUI or shadcn/ui.
A second IDManifest flaw lands two weeks after OpenEXR's forty-CVE sweep
Mediamodifier's feed is a template catalog: one mockup per entry, several a day.
Spectra Blocks spends its first six weeks patching what 1.0 shipped.
Storybook is turning its component workshop into a tool surface agents can call.
Picsart bolts on every new video model within days — WAN 3.0 pushes single takes to 30 seconds.
Visme extended past documents into no-code microsites, then hardened the layout and brand layer.
See all HeroUI alternatives → · See all shadcn/ui alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. shadcn/ui is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. shadcn/ui is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Design products to evaluate alongside.
Top HeroUI alternatives in Design are ranked by recent ship velocity. Browse the "HeroUI alternatives" section above for the current picks, or visit /alternatives/heroui for the full list with editorial commentary on each.
Top shadcn/ui alternatives in Design are ranked by recent ship velocity. Browse the "shadcn/ui alternatives" section above for the current picks, or visit /alternatives/shadcn for the full list with editorial commentary on each.