tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of excluder and wikitaxa — 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 six-year silence broken by a dependency that CRAN deleted underneath it
wikitaxa is the rOpenSci client for pulling taxonomic records out of Wikipedia, Wikidata, Wikispecies and Wikicommons, and it has been feature-complete since 2017. The v0.5.0 release in February 2026 arrived after nearly six years of silence, and it exists because CRAN archived WikidataR — the library wikitaxa used to reach Wikidata. The fix routes those calls through WikipediR directly, which removes a third-party single point of failure from the package's dependency graph.
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.
wikitaxa is the rOpenSci client for pulling taxonomic records out of Wikipedia, Wikidata, Wikispecies and Wikicommons, and it has been feature-complete since 2017. The v0.5.0 release in February 2026 arrived after nearly six years of silence, and it exists because CRAN archived WikidataR — the library wikitaxa used to reach Wikidata. The fix routes those calls through WikipediR directly, which removes a third-party single point of failure from the package's dependency graph.
Every release in this window is repair, not expansion: parser fixes for Wikicommons classification pages, common-name handling in the Wikispecies parser, and the Wikidata backend swap. The one functional addition across six entries is the `wiki` language parameter in v0.1.4. This is a package in maintenance-on-demand mode, where the trigger for a release is an upstream break rather than a roadmap.
Expect the next release to be reactive again — another upstream parser break or a CRAN policy notice — rather than new endpoints. Nothing in these entries indicates 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 wikitaxa.
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 wikitaxa alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Analytics. excluder and wikitaxa 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 wikitaxa 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 wikitaxa alternatives in Analytics are ranked by recent ship velocity. Browse the "wikitaxa alternatives" section above for the current picks, or visit /alternatives/wikitaxa for the full list with editorial commentary on each.