tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of mantis and posteriordb — release velocity, themes, recent moves, and the top alternatives to consider.
Thirteen months of rOpenSci review turned a pre-release into a 1.0 with a stable API
mantis builds interactive time-series reports — heatmaps, multipanel plots, alert tables — over routinely collected data, and its release history is essentially an rOpenSci peer-review log. The package went from a January 2025 pre-release that warned of breaking changes ahead, through submission and CRAN acceptance, to a 1.0.0 in October 2025 that locked the API. Since then it has shipped only two small fixes, the most recent chasing a dplyr 1.2.0 deprecation.
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.
mantis builds interactive time-series reports — heatmaps, multipanel plots, alert tables — over routinely collected data, and its release history is essentially an rOpenSci peer-review log. The package went from a January 2025 pre-release that warned of breaking changes ahead, through submission and CRAN acceptance, to a 1.0.0 in October 2025 that locked the API. Since then it has shipped only two small fixes, the most recent chasing a dplyr 1.2.0 deprecation.
The breaking changes cluster entirely below 1.0.0 and stop there: `period` became `timepoint_unit`, `save_directory`/`save_filename` became `file`, `function_call` became `expression`. Post-1.0 the work is defensive — stricter POSIXt validation, timepoint limits that clamp to the data rather than inventing plot points, daylight-savings handling. The feed reads as a package that has finished defining itself and is now maintaining compatibility with the tidyverse underneath it.
With the API frozen and review complete, expect the next release to be another upstream-compatibility fix rather than new report types. There is no signal in these entries about planned feature work.
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 mantis 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.
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 mantis 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. mantis 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. mantis 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 mantis alternatives in Analytics are ranked by recent ship velocity. Browse the "mantis alternatives" section above for the current picks, or visit /alternatives/mantis 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.