tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of c3dr and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
A biomechanics C3D reader graduated through rOpenSci review to CRAN, then learned to write force plates.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
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.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
The package is filling in the write side of the read/write pair. Reading was in place from the start; 0.2.0 extends c3d_write() to force-platform data on a direct user request, and the accompanying work preserves matrix structure on import and tracks upstream EZC3D changes. The review-era releases hardened validation and error messages, so the current cycle can be spent on capability rather than polish.
Expect further coverage of C3D block types in the writer and continued tracking of EZC3D releases; the changelog gives no signal of analysis features beyond file I/O.
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 c3dr 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 c3dr alternatives → · See all webmockr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. c3dr 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. c3dr 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 c3dr alternatives in Analytics are ranked by recent ship velocity. Browse the "c3dr alternatives" section above for the current picks, or visit /alternatives/c3dr 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.