tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of hoardr and posteriordb — release velocity, themes, recent moves, and the top alternatives to consider.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
hoardr manages local cache directories for other R packages — where files go, how they are keyed, whether they exist. It underpins caching in several rOpenSci data clients. The last functional additions were in 2018; everything since is a patch issued because CRAN reported a test failure or the maintainer changed.
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
posteriordb distributes Bayesian models with data and reference posterior draws so inference algorithms can be benchmarked against a common target. It reached 1.0.0 alongside a published paper, and ships both R and Python access. Recent work is about the metadata around the draws — licences, machine-readable dataset descriptors, and additional summary statistics.
hoardr manages local cache directories for other R packages — where files go, how they are keyed, whether they exist. It underpins caching in several rOpenSci data clients. The last functional additions were in 2018; everything since is a patch issued because CRAN reported a test failure or the maintainer changed.
This is infrastructure that has reached its final shape. Three of the last three releases were reactive: two responses to CRAN test-failure notifications, one to a maintainer handover. The single behavioural change in that stretch — forward slashes in paths on every operating system — is a consistency fix for downstream packages rather than a feature. Its release cadence is set by CRAN's checks, not by demand.
Expect the next release to be triggered by another CRAN check failure rather than by new functionality, matching every release since 2018.
posteriordb distributes Bayesian models with data and reference posterior draws so inference algorithms can be benchmarked against a common target. It reached 1.0.0 alongside a published paper, and ships both R and Python access. Recent work is about the metadata around the draws — licences, machine-readable dataset descriptors, and additional summary statistics.
The database is maturing from a model collection into a citable benchmark asset: licence information per model, a Croissant metadata file for dataset discovery, and summary statistics like mean squared value and lag-1 autocorrelation that let users judge whether reference draws are good enough for their comparison. Earlier releases were about content and correctness; current ones are about making the content machine-readable and verifiable.
Further work should continue on draw-quality diagnostics and metadata rather than model count, since the last two releases both added ways to assess the reference draws instead of adding posteriors.
Other Analytics 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 hoardr or posteriordb.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all hoardr alternatives → · See all posteriordb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. hoardr and posteriordb 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. hoardr and posteriordb 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 Analytics products to evaluate alongside.
Top hoardr alternatives in Analytics are ranked by recent ship velocity. Browse the "hoardr alternatives" section above for the current picks, or visit /alternatives/hoardr for the full list with editorial commentary on each.
Top posteriordb alternatives in Analytics are ranked by recent ship velocity. Browse the "posteriordb alternatives" section above for the current picks, or visit /alternatives/posteriordb for the full list with editorial commentary on each.