mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
A side-by-side editorial comparison of mlr3proba and Trackingplan — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3proba provides probabilistic supervised learning for mlr3 — survival analysis, density estimation, and the measures that go with them. Recent releases are almost entirely upkeep: a distr6 fork to work around an upstream problem, an ooplah fix, a predict-type correction, and registration in mlr_reflections$loaded_packages. The one deletion is telling, with LearnerDensPenalized removed after pendensity left CRAN.
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.
mlr3proba provides probabilistic supervised learning for mlr3 — survival analysis, density estimation, and the measures that go with them. Recent releases are almost entirely upkeep: a distr6 fork to work around an upstream problem, an ooplah fix, a predict-type correction, and registration in mlr_reflections$loaded_packages. The one deletion is telling, with LearnerDensPenalized removed after pendensity left CRAN.
The package is being pared back rather than extended. Its README now points at survdistr and mlr3cmprsk as matured alternatives for parts of what it covers, which reads as scope being handed off, while the Cox proportional-hazards autoplot arrived from mlr3viz in the other direction. Several fixes exist to route around dependencies that broke or disappeared, which is the recurring cost of building on a long chain of specialized CRAN packages.
The dependency churn suggests more consolidation — further reliance on survdistr and mlr3cmprsk, and more learners retired when the package underneath them goes unmaintained.
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 mlr3proba or Trackingplan.
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
A finished Bayesian model-comparison package in pure maintenance mode
See all mlr3proba 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 mlr3proba alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3proba alternatives" section above for the current picks, or visit /alternatives/mlr3proba 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.