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 vdiffr — 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().
vdiffr finished its job in 2021 and has been tracking compilers ever since.
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
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.
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
The package reached its intended shape at 1.0.0, when snapshot management moved to testthat and vdiffr shed most of its own R and JavaScript code to become a reproducible SVG engine and nothing more. There is not much left to add to that, and the release stream since reads accordingly: it moves when a compiler, an R version, or testthat moves. For a testing dependency this is a healthy end state, though it does mean the package inherits whatever the graphics engine does to snapshot stability.
The entries do not support predicting a feature release. The likely next change is a compatibility fix prompted by a compiler or a testthat change, as every release since 1.0.2 has been.
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 vdiffr.
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 vdiffr 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 vdiffr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vdiffr alternatives" section above for the current picks, or visit /alternatives/vdiffr for the full list with editorial commentary on each.