tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of excluder and forestly — 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.
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.
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.
forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.
The arc runs from a fixed interactive widget toward a configurable one with two output modes. Nearly every new argument in the last two releases exists to remove something from the display or relabel it, which suggests the users driving development are producing outputs for others to review under conventions they do not control. The x-axis range, column header, figure header and slider range arguments point the same way — this is a tool being fitted into standardised reporting rather than used ad hoc.
Given that the last two releases have consisted almost entirely of display-control arguments, the next is likely more of the same, applied to whichever parts of the interactive layout are still fixed.
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 forestly.
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 forestly 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 forestly 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 forestly 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 forestly alternatives in Analytics are ranked by recent ship velocity. Browse the "forestly alternatives" section above for the current picks, or visit /alternatives/forestly for the full list with editorial commentary on each.