HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of bkmrhat and mize — release velocity, themes, recent moves, and the top alternatives to consider.
A parallel-chain helper for bkmr that has settled into pure upkeep.
bkmrhat wraps Bayesian kernel machine regression (bkmr) so users can run and diagnose multiple MCMC chains in parallel, then combine or continue them. The functional surface has been stable since 2022, when chain-combining picked up a low-memory path and a seed-collision bug was corrected. The most recent release adds only diagnostic metadata to the package description.
A numerical optimization toolkit that has been feature-complete and quiet since 2017
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
bkmrhat wraps Bayesian kernel machine regression (bkmr) so users can run and diagnose multiple MCMC chains in parallel, then combine or continue them. The functional surface has been stable since 2022, when chain-combining picked up a low-memory path and a seed-collision bug was corrected. The most recent release adds only diagnostic metadata to the package description.
Three releases across five years, and the newest carries no user-facing change at all. The package is in maintenance: it does what it set out to do for bkmr users, and updates now arrive only when CRAN or an upstream dependency forces them.
Expect the next release to be another compliance or dependency-driven patch rather than new functionality; the entries show no in-progress feature work.
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
The pattern is a stable library rather than an abandoned one. Fixes address real reports - a bracket_step error when the Schmidt line search exhausts its function evaluation budget, an incorrect gradient count under backtracking with a specified step_down - and the maintainer used one release note to clarify that backtracking behaviour differs depending on whether step_down is supplied, which reads as answering a recurring question. The five and a half year gap between 0.2.4 and 0.2.5 is the clearest signal: the package is maintained on demand, not developed.
Expect nothing until an R or CRAN policy change forces another compliance patch, which is what triggered the most recent release.
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 bkmrhat or mize.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
A column-key toolkit for stitching decades of ecological field data into one table.
See all bkmrhat alternatives → · See all mize alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, maintenance — within Infra & APIs. bkmrhat and mize are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. bkmrhat and mize are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top bkmrhat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bkmrhat alternatives" section above for the current picks, or visit /alternatives/bkmrhat for the full list with editorial commentary on each.
Top mize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mize alternatives" section above for the current picks, or visit /alternatives/mize for the full list with editorial commentary on each.