INFRA · APIS
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Alternatives · developer tools
HydroPortailStats alternatives
The best HydroPortailStats alternatives in developer tools, ranked by Sparkpulse's velocity_score.
Updated Aug 18, 2026
Looking for the best alternatives to HydroPortailStats? Sparkpulse tracks and ranks 12 alternatives in developer tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, HydroPortailStats shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About HydroPortailStats
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.
Velocity 0.0 · Last update 29m ago
Top 12 alternatives to HydroPortailStats
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
INFRA · APIS
Fast design-based estimators for experiments, coasting on CRAN patches.
INFRA · APIS
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
INFRA · APIS
IP address vectors for R that hit 1.0 and then went quiet.
INFRA · APIS
A column-key toolkit for stitching decades of ecological field data into one table.
INFRA · APIS
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
INFRA · APIS
Bayesian luminescence dating that finally replaced its folder-structure input format.
INFRA · APIS
An epidemic-economic model teaching its interventions to react to the outbreak itself.
INFRA · APIS
A parallel-chain helper for bkmr that has settled into pure upkeep.
INFRA · APIS
A cancer driver prioritization package that ships rarely and mostly to stay installable
INFRA · APIS
A meteorology ggplot2 extension where the netCDF reader became the main event
INFRA · APIS
An isotope geolocation package still recovering from the r-spatial retirement
HydroPortailStats vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| HydroPortailStats (baseline) | 0.0 | 0 | hydrologyflood-frequencybayesian-statistics | Historical flood records enter the estimator via an HBay port |
| bsvarSIGNs | 0.0 | 0 | bayesian-statisticseconometricsstructural-var | Launch: sign, zero and narrative restrictions for bsvars |
| estimatr | 0.0 | 0 | causal-inferenceexperimentsrobust-standard-errors | — |
| ggdist | 0.0 | 0 | data-visualizationuncertaintybayesian-statistics | Blurred dotplots draw Monte Carlo error; weights reach every estimator |
| ipaddress | 0.0 | 0 | networkingip-addressesrcpp | 1.0.0 breaks the interface to make it vector-native |
| ltertools | 0.0 | 0 | data-harmonizationecologylter | — |
| finnts | 0.0 | 0 | forecastingtime-seriestidymodels | — |
| BayLum | 0.0 | 0 | bayesian-statisticsluminescence-datinggeochronology | One data-file function and a YAML config replace the folder layout |
| daedalus | 0.0 | 0 | epidemic-modellinghealth-economicsnpi-policy | Interventions now lift in response to live R_t |
| bkmrhat | 0.0 | 0 | bayesian-statisticsmcmcparallel-computing | — |
| driveR | 0.0 | 0 | cancer-genomicsbioinformaticsr-package | — |
| metR | 0.0 | 0 | meteorologyggplot2r-package | — |
| IsoriX | 0.0 | 0 | stable-isotopesgeolocationr-package | — |
The 12 best HydroPortailStats alternatives, in depth
1. bsvarSIGNs · velocity 0.0
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Launch: sign, zero and narrative restrictions for bsvars”.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, bsvarSIGNs focuses on bayesian statistics, econometrics and structural var.
bsvarSIGNs and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full bsvarSIGNs trajectory → · Compare HydroPortailStats vs bsvarSIGNs →
2. estimatr · velocity 0.0
Fast design-based estimators for experiments, coasting on CRAN patches.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, estimatr focuses on causal inference, experiments and robust standard errors.
estimatr and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full estimatr trajectory → · Compare HydroPortailStats vs estimatr →
3. ggdist · velocity 0.0
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Blurred dotplots draw Monte Carlo error; weights reach every estimator”.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, ggdist focuses on data visualization, uncertainty and bayesian statistics.
ggdist and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ggdist trajectory → · Compare HydroPortailStats vs ggdist →
4. ipaddress · velocity 0.0
IP address vectors for R that hit 1.0 and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0.0 breaks the interface to make it vector-native”.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, ipaddress focuses on networking, ip addresses and rcpp.
ipaddress and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ipaddress trajectory → · Compare HydroPortailStats vs ipaddress →
5. ltertools · velocity 0.0
A column-key toolkit for stitching decades of ecological field data into one table.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, ltertools focuses on data harmonization, ecology and lter.
ltertools and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ltertools trajectory → · Compare HydroPortailStats vs ltertools →
6. finnts · velocity 0.0
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, finnts focuses on forecasting, time series and tidymodels.
finnts and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full finnts trajectory → · Compare HydroPortailStats vs finnts →
7. BayLum · velocity 0.0
Bayesian luminescence dating that finally replaced its folder-structure input format.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “One data-file function and a YAML config replace the folder layout”.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, BayLum focuses on bayesian statistics, luminescence dating and geochronology.
BayLum and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full BayLum trajectory → · Compare HydroPortailStats vs BayLum →
8. daedalus · velocity 0.0
An epidemic-economic model teaching its interventions to react to the outbreak itself.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Interventions now lift in response to live R_t”.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, daedalus focuses on epidemic modelling, health economics and npi policy.
daedalus and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full daedalus trajectory → · Compare HydroPortailStats vs daedalus →
9. bkmrhat · velocity 0.0
A parallel-chain helper for bkmr that has settled into pure upkeep.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, bkmrhat focuses on bayesian statistics, mcmc and parallel computing.
bkmrhat and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full bkmrhat trajectory → · Compare HydroPortailStats vs bkmrhat →
10. driveR · velocity 0.0
A cancer driver prioritization package that ships rarely and mostly to stay installable.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, driveR focuses on cancer genomics, bioinformatics and r package.
driveR and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full driveR trajectory → · Compare HydroPortailStats vs driveR →
11. metR · velocity 0.0
A meteorology ggplot2 extension where the netCDF reader became the main event.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, metR focuses on meteorology, ggplot2 and r package.
metR and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full metR trajectory → · Compare HydroPortailStats vs metR →
12. IsoriX · velocity 0.0
An isotope geolocation package still recovering from the r-spatial retirement.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where HydroPortailStats leans on hydrology, flood frequency and bayesian statistics, IsoriX focuses on stable isotopes, geolocation and r package.
IsoriX and HydroPortailStats have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full IsoriX trajectory → · Compare HydroPortailStats vs IsoriX →
Frequently asked questions
What are the best alternatives to HydroPortailStats?
The top HydroPortailStats alternatives we currently track in developer tools are bsvarSIGNs, estimatr, ggdist, ipaddress, ltertools, ranked by recent ship velocity.
How is this list of HydroPortailStats alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare HydroPortailStats directly with one of these alternatives?
Yes — every card has a "Compare with HydroPortailStats" link to a side-by-side /compare page.