tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of chromer and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
A chromosome-count database client that only ever ships when the upstream API moves.
chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.
The package is functionally complete and externally driven — its release cadence is a record of the CCDB's hosting history rather than of any development plan. The defensive work in 0.4, which added an internal check for whether the database is down and skips tests accordingly, shows the maintainer treating upstream instability as the permanent condition rather than an incident.
The next release will most likely be triggered by another CCDB endpoint or format change; nothing in the history suggests new functionality is planned.
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
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 chromer or webmockr.
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 chromer alternatives → · See all webmockr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. chromer and webmockr 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. chromer and webmockr 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 chromer alternatives in Analytics are ranked by recent ship velocity. Browse the "chromer alternatives" section above for the current picks, or visit /alternatives/chromer for the full list with editorial commentary on each.
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.