tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of posteriordb and wikitaxa — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A six-year silence broken by a dependency that CRAN deleted underneath it
wikitaxa is the rOpenSci client for pulling taxonomic records out of Wikipedia, Wikidata, Wikispecies and Wikicommons, and it has been feature-complete since 2017. The v0.5.0 release in February 2026 arrived after nearly six years of silence, and it exists because CRAN archived WikidataR — the library wikitaxa used to reach Wikidata. The fix routes those calls through WikipediR directly, which removes a third-party single point of failure from the package's dependency graph.
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.
wikitaxa is the rOpenSci client for pulling taxonomic records out of Wikipedia, Wikidata, Wikispecies and Wikicommons, and it has been feature-complete since 2017. The v0.5.0 release in February 2026 arrived after nearly six years of silence, and it exists because CRAN archived WikidataR — the library wikitaxa used to reach Wikidata. The fix routes those calls through WikipediR directly, which removes a third-party single point of failure from the package's dependency graph.
Every release in this window is repair, not expansion: parser fixes for Wikicommons classification pages, common-name handling in the Wikispecies parser, and the Wikidata backend swap. The one functional addition across six entries is the `wiki` language parameter in v0.1.4. This is a package in maintenance-on-demand mode, where the trigger for a release is an upstream break rather than a roadmap.
Expect the next release to be reactive again — another upstream parser break or a CRAN policy notice — rather than new endpoints. Nothing in these entries indicates planned feature work.
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 posteriordb or wikitaxa.
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.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
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.
See all posteriordb alternatives → · See all wikitaxa alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. posteriordb and wikitaxa 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. posteriordb and wikitaxa 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 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.
Top wikitaxa alternatives in Analytics are ranked by recent ship velocity. Browse the "wikitaxa alternatives" section above for the current picks, or visit /alternatives/wikitaxa for the full list with editorial commentary on each.