tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of crul and EDIutils — release velocity, themes, recent moves, and the top alternatives to consider.
crul took mocking back from webmockr and made it a property of the client itself
crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.
The EDI data client is being dragged through its repository's identity-system migration.
EDIutils is the R client for the Environmental Data Initiative repository. The last two releases are both consequences of changes at EDI rather than in the package: 2.0.0 rewired authentication for the new EDI Identity and Access Manager and made Distinguished Names defunct in favour of EDI-IDs, and 2.1.0 handles the deprecation of the old auth token. Earlier releases were small bug fixes against repository outages and endpoint changes.
crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.
The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.
With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.
EDIutils is the R client for the Environmental Data Initiative repository. The last two releases are both consequences of changes at EDI rather than in the package: 2.0.0 rewired authentication for the new EDI Identity and Access Manager and made Distinguished Names defunct in favour of EDI-IDs, and 2.1.0 handles the deprecation of the old auth token. Earlier releases were small bug fixes against repository outages and endpoint changes.
This is a client whose roadmap belongs to its server. Every meaningful release tracks something EDI changed — a deprecated endpoint, a resource outage breaking CRAN checks, and now a whole identity system — and the package's job is to absorb the churn while keeping the R interface stable. The 2.0.0 break was handled by pointing users at where to find their new EDI-ID rather than by papering over the change.
Expect continued follow-through on the IAM migration as the old auth token is fully retired, and further releases keyed to EDI service changes rather than to new client features.
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 crul or EDIutils.
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 crul alternatives → · See all EDIutils alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. crul and EDIutils 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. crul and EDIutils 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 crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul for the full list with editorial commentary on each.
Top EDIutils alternatives in Analytics are ranked by recent ship velocity. Browse the "EDIutils alternatives" section above for the current picks, or visit /alternatives/ediutils for the full list with editorial commentary on each.