tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of riem and wikitaxa — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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 riem 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.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all riem alternatives → · See all wikitaxa alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. riem 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. riem 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 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.
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.