Apache CloudStack
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
A side-by-side editorial comparison of Fission and Verdaccio — release velocity, themes, recent moves, and the top alternatives to consider.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
The next-7 prerelease line is short and almost entirely maintenance. Its one substantive release adopted @verdaccio/server and deleted the local api, web, and storage forks, leaving a thin Storage wrapper behind only to keep callback-based storage plugins working. Everything since has been dependency retargeting, a lint and format toolchain swap, and a tag whose body reads 'chore: trigger release'.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
The next-7 prerelease line is short and almost entirely maintenance. Its one substantive release adopted @verdaccio/server and deleted the local api, web, and storage forks, leaving a thin Storage wrapper behind only to keep callback-based storage plugins working. Everything since has been dependency retargeting, a lint and format toolchain swap, and a tag whose body reads 'chore: trigger release'.
This is consolidation ahead of a major: the project is collapsing code it had been carrying in-tree back onto shared packages and standardising tooling around oxlint and oxfmt. The remaining compatibility shim is the visible unfinished business — it exists purely for legacy plugins, and it is the last thing standing between this line and a clean server dependency.
Removing the legacy storage wrapper is the decision this line is heading toward, and it breaks callback-based storage plugins when it lands, so expect it to arrive with the 7.0.0 final rather than in another next tag. Until then the prerelease stream will keep producing tags with no user-visible content.
Other Infra & APIs 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 Fission or Verdaccio.
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Kinsta is moving MyKinsta's controls into its API, one surface per month
Observability lands on OpenTelemetry semconv in the LTS train
Canvas agents gain memory, and onboarding moves into the editor
Security and governance controls catch up to the Copilot build-out
authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO
See all Fission alternatives → · See all Verdaccio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Verdaccio is currently shipping more aggressively (velocity 2.5 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. Verdaccio is currently shipping more aggressively (velocity 2.5 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 Infra & APIs products to evaluate alongside.
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.
Top Verdaccio alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Verdaccio alternatives" section above for the current picks, or visit /alternatives/verdaccio for the full list with editorial commentary on each.