tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of mantis and riem — 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 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.
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.
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 mantis 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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. mantis 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. mantis 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 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 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.