Apache CloudStack
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
A side-by-side editorial comparison of HydroPortailStats and Verdaccio — release velocity, themes, recent moves, and the top alternatives to consider.
France's national flood statistics, ported out of Fortran and into R.
HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.
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'.
HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.
The package started as a straight extraction of the portal's existing functions and is now absorbing the surrounding legacy toolchain: HBay was a separate compiled program with its own config files, and this release brings both the method and its configuration format inside R. Releases are sparse — three in two years, with an eighteen-month gap before the latest — and the intervening one was CRAN paperwork.
The HBay import came with a configuration-file reader for continuity with the old executable, which suggests further legacy hydrological tooling could follow the same path; the entries name no specific next target.
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 HydroPortailStats 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 HydroPortailStats 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 HydroPortailStats alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HydroPortailStats alternatives" section above for the current picks, or visit /alternatives/hydroportailstats 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.