tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of forcis and posteriordb — release velocity, themes, recent moves, and the top alternatives to consider.
A foraminifera data-access package whose entire release history is the rOpenSci review process.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
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.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
The package is moving from research artifact to reviewed, distributable infrastructure — submitted to rOpenSci at 0.1.0, integrated review feedback at 1.0.0, cleared CRAN at 1.0.1. That arc is complete, so the next phase should be the first release driven by users rather than reviewers.
With review and CRAN acceptance both behind it, the next release is most likely to track upstream FORCIS database changes or add query conveniences; the entries themselves say nothing about planned features.
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 forcis 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 forcis 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. forcis 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. forcis 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 forcis alternatives in Analytics are ranked by recent ship velocity. Browse the "forcis alternatives" section above for the current picks, or visit /alternatives/forcis 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.