mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of modeldata and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
The tidymodels example-data package grows one dataset at a time, on nobody's schedule
modeldata exists to supply the datasets and simulation functions that tidymodels documentation, tests, and teaching material depend on. Releases arrive roughly once or twice a year and consist almost entirely of new data sets plus occasional simulation methods. The most recent work adds a Worley (1987) regression simulation and moves the package off the magrittr pipe onto base R's.
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.
modeldata exists to supply the datasets and simulation functions that tidymodels documentation, tests, and teaching material depend on. Releases arrive roughly once or twice a year and consist almost entirely of new data sets plus occasional simulation methods. The most recent work adds a Worley (1987) regression simulation and moves the package off the magrittr pipe onto base R's.
Two lines run through the history: broadening coverage of task types — ordinal classification, multinomial, regression, QSAR-style chemistry data — and building out synthetic simulation so tutorials can demonstrate a method without shipping a real dataset for it. The simulation side has grown from a single regression generator into a family with logistic and multinomial variants and a keep_truth option that exposes the error-free outcome. Infrastructure changes appear only when the wider tidyverse moves, as the base-pipe transition shows.
The pattern points to another simulation method or a dataset filling a task type the collection still lacks, rather than any change in what the package does.
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 modeldata 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 modeldata alternatives → · See all vetiver alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. modeldata 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. modeldata 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 modeldata alternatives in Analytics are ranked by recent ship velocity. Browse the "modeldata alternatives" section above for the current picks, or visit /alternatives/modeldata 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.