tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of excluder and mantis — 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.
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.
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.
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 excluder 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 excluder 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. excluder 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. excluder 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 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 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.