tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of ijtiff and mantis — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Thirteen months of rOpenSci review turned a pre-release into a 1.0 with a stable API
mantis builds interactive time-series reports — heatmaps, multipanel plots, alert tables — over routinely collected data, and its release history is essentially an rOpenSci peer-review log. The package went from a January 2025 pre-release that warned of breaking changes ahead, through submission and CRAN acceptance, to a 1.0.0 in October 2025 that locked the API. Since then it has shipped only two small fixes, the most recent chasing a dplyr 1.2.0 deprecation.
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.
mantis builds interactive time-series reports — heatmaps, multipanel plots, alert tables — over routinely collected data, and its release history is essentially an rOpenSci peer-review log. The package went from a January 2025 pre-release that warned of breaking changes ahead, through submission and CRAN acceptance, to a 1.0.0 in October 2025 that locked the API. Since then it has shipped only two small fixes, the most recent chasing a dplyr 1.2.0 deprecation.
The breaking changes cluster entirely below 1.0.0 and stop there: `period` became `timepoint_unit`, `save_directory`/`save_filename` became `file`, `function_call` became `expression`. Post-1.0 the work is defensive — stricter POSIXt validation, timepoint limits that clamp to the data rather than inventing plot points, daylight-savings handling. The feed reads as a package that has finished defining itself and is now maintaining compatibility with the tidyverse underneath it.
With the API frozen and review complete, expect the next release to be another upstream-compatibility fix rather than new report types. There is no signal in these entries about 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 ijtiff or mantis.
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 ijtiff alternatives → · See all mantis alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ijtiff and mantis 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. ijtiff and mantis 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 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.
Top mantis alternatives in Analytics are ranked by recent ship velocity. Browse the "mantis alternatives" section above for the current picks, or visit /alternatives/mantis for the full list with editorial commentary on each.