mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of fable and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
fable keeps widening its model shelf, one econometric class at a time
fable is the tidyverts forecasting engine, and its releases are almost entirely about which model families it can express. The 0.4.x line added the vector-error-correction and VARIMA classes plus impulse-response methods; 0.5.0 adds fractional differencing via ARFIMA. Between those, the releases are CRAN-check patches and documentation passes.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
fable is the tidyverts forecasting engine, and its releases are almost entirely about which model families it can express. The 0.4.x line added the vector-error-correction and VARIMA classes plus impulse-response methods; 0.5.0 adds fractional differencing via ARFIMA. Between those, the releases are CRAN-check patches and documentation passes.
The package is closing the gap with the older forecast package's model coverage while keeping the tidy model-specification grammar. Each substantive release is a new model class plus the generate()/IRF() plumbing to make it behave like the existing ones. Maintenance releases cluster around CRAN policy and ggplot2/tsibble compatibility rather than internal rewrites.
Expect the next substantive release to add another model class or extend generate()/IRF() coverage to the classes that still lack them, rather than change the modelling interface.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
The feature era ended before this window opened. Deploying to SageMaker, generating Docker files, storing renv lockfiles in model metadata and supporting keras, luz and recipes all landed in 0.2.1 and 0.2.2; nothing since has extended what vetiver does. What it does now is track the rest of tidymodels — when recipes gains a prototype API or probably becomes something a workflow can contain, vetiver adds a line. That is a package holding its position rather than advancing it.
The entries do not support a confident prediction of new capability. On this pattern the next release tracks another tidymodels change, most likely the postprocessing stage that workflows added in 1.3.0.
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 fable or vetiver.
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 fable alternatives → · See all vetiver alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fable and vetiver 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. fable and vetiver 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 fable alternatives in Analytics are ranked by recent ship velocity. Browse the "fable alternatives" section above for the current picks, or visit /alternatives/fable for the full list with editorial commentary on each.
Top vetiver alternatives in Analytics are ranked by recent ship velocity. Browse the "vetiver alternatives" section above for the current picks, or visit /alternatives/vetiver-r for the full list with editorial commentary on each.