mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of tidytext and Trackingplan — release velocity, themes, recent moves, and the top alternatives to consider.
Finished, widely taught, and shipping roxygen fixes.
tidytext is the package that made unnest_tokens() and the tidy-data approach to text analysis standard, and it has reached the point where its releases contain nothing to announce. The last three are roxygen package anchors, alt text on vignette figures, and a single bug fix in one stm tidier. The most recent substantive changes were in 0.4.0 and 0.3.3 — stm tidiers for high FREX and lift words, a labels function for scale_x_reordered(), and support for tidying STM models that use content covariates.
Trackingplan turns tracking-plan validation into AI-assisted, consent-aware observability.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
tidytext is the package that made unnest_tokens() and the tidy-data approach to text analysis standard, and it has reached the point where its releases contain nothing to announce. The last three are roxygen package anchors, alt text on vignette figures, and a single bug fix in one stm tidier. The most recent substantive changes were in 0.4.0 and 0.3.3 — stm tidiers for high FREX and lift words, a labels function for scale_x_reordered(), and support for tidying STM models that use content covariates.
The direction is stability, and the release triggers are external. quanteda releases force updates to the dfm tidiers, a Matrix release forces another, tokenizers deprecating its tweet tokenizer forces removal of the tweet-specific functions here, and CRAN's Rd anchor requirement produces a release of its own. Nothing in the recent stream suggests new capability is planned, and for a package this embedded in teaching material that is a defensible position rather than a problem.
The entries do not support predicting new features. The likely next release is another compatibility update prompted by quanteda, stm, or a CRAN documentation requirement.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
The product is moving from passive tracking-plan validation toward active, guided remediation. Each release tightens the loop between detecting a problem (a warning, a consent gap) and resolving it — AI Debugger is spreading from generic warnings to consent warnings, and the UI is being rebuilt around single-surface investigation rather than scattered reports.
Expect AI Debugger to reach more warning types and Consent Monitoring to add further CMP integrations, continuing the pattern of extending both features to new surfaces rather than shipping a new pillar.
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 tidytext or Trackingplan.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk swallowed anomalize whole, then went quiet for two years
modelbased is turning marginal effects into a full contrast grammar
easystats' parameters package absorbs one more model class every few weeks
See all tidytext alternatives → · See all Trackingplan alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Trackingplan is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Trackingplan is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top tidytext alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytext alternatives" section above for the current picks, or visit /alternatives/tidytext for the full list with editorial commentary on each.
Top Trackingplan alternatives in Analytics are ranked by recent ship velocity. Browse the "Trackingplan alternatives" section above for the current picks, or visit /alternatives/trackingplan for the full list with editorial commentary on each.