tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of excluder and ijtiff — release velocity, themes, recent moves, and the top alternatives to consider.
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.
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.
excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.
The package is stable and its maintenance load comes from things it does not control: the {iptools} package leaving CRAN, {tidyselect} deprecating the .data pronoun, IP-geolocation tests breaking when the underlying address data shifts. Much of that work is about staying installable, not about better exclusions. Note that several of these entries were backfilled into the feed within the same two-minute window and are not in version order.
The next release will most likely be another dependency or CRAN-check response rather than a new exclusion criterion, following the pattern of the last three.
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 excluder 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.
See all excluder alternatives → · See all ijtiff alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. excluder 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. excluder 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 excluder alternatives in Analytics are ranked by recent ship velocity. Browse the "excluder alternatives" section above for the current picks, or visit /alternatives/excluder 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.