L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A side-by-side editorial comparison of eratosthenes and whirl — release velocity, themes, recent moves, and the top alternatives to consider.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
whirl turned script logging into a standardized provenance artifact regulators can read.
A parallel R script runner that produces execution logs, aimed at regulated analysis environments. The 0.3.0 release added write_biocompute(), emitting logs as BioCompute Objects in standardized JSON, and simplified the approved-package check to a plain package@version vector. Since then the work has been about what the log can be trusted to contain: an environment_secrets option to keep secret variables out of it, direct versus indirect package usage distinguished and highlighted against the approved list, and the same approval check extended to Python packages.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.
With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.
A parallel R script runner that produces execution logs, aimed at regulated analysis environments. The 0.3.0 release added write_biocompute(), emitting logs as BioCompute Objects in standardized JSON, and simplified the approved-package check to a plain package@version vector. Since then the work has been about what the log can be trusted to contain: an environment_secrets option to keep secret variables out of it, direct versus indirect package usage distinguished and highlighted against the approved list, and the same approval check extended to Python packages.
The through-line is the log as evidence rather than as debugging output. Every recent addition either widens what the log proves — which packages were really used, in which language, against which approved list — or narrows what it must not leak. Setting options only through an explicit with_options argument to run() and getting renv library paths right for Quarto both point the same way: reproducible, auditable child sessions with nothing implicit.
Expect the approved-package and provenance machinery to keep expanding across languages and environments, since Python approval checks followed the R ones and both feed the same log.
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 eratosthenes or whirl.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
See all eratosthenes alternatives → · See all whirl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. eratosthenes 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. eratosthenes 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 eratosthenes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "eratosthenes alternatives" section above for the current picks, or visit /alternatives/eratosthenes for the full list with editorial commentary on each.
Top whirl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "whirl alternatives" section above for the current picks, or visit /alternatives/whirl for the full list with editorial commentary on each.