tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of crul and ijtiff — 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.
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
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.
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
Two threads run through the window. The C layer is being hardened — memory leaks in tag handling, buffer cleanup, PROTECT errors, validation of malformed files — which is the kind of work that surfaces when a package gets run against real-world files at volume. Separately, the R layer is shedding dependencies, with base graphics replacing imager for display. Both make the package cheaper and safer to depend on rather than more capable.
Expect continued C-level correctness work rather than format features, since three of the last three substantive releases were memory or compiler fixes.
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 ijtiff.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. crul and ijtiff 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 ijtiff 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 ijtiff alternatives in Analytics are ranked by recent ship velocity. Browse the "ijtiff alternatives" section above for the current picks, or visit /alternatives/ijtiff for the full list with editorial commentary on each.