tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of metatools and riem — release velocity, themes, recent moves, and the top alternatives to consider.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
The package's development has been concentrated on one function, combine_supp(), which is where the messy realities of supplemental qualifiers surface — whitespace in join keys, empty supp datasets, colliding names. 0.1.6 also drew three first-time contributors, which is the healthiest signal in the history, but no release has followed. Sibling packages have meanwhile been dropping metatools as a dependency.
Without a release in two years the package looks stable rather than active; the plausible trigger is a controlled-terminology or dplyr change that forces the checks to be updated.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.
With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing again.
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 metatools or riem.
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.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all metatools alternatives → · See all riem alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. metatools and riem 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. metatools and riem 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 metatools alternatives in Analytics are ranked by recent ship velocity. Browse the "metatools alternatives" section above for the current picks, or visit /alternatives/metatools for the full list with editorial commentary on each.
Top riem alternatives in Analytics are ranked by recent ship velocity. Browse the "riem alternatives" section above for the current picks, or visit /alternatives/riem for the full list with editorial commentary on each.