tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of broom and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
broom's release calendar is now set by CRAN checks, not by new tidiers.
broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.
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.
broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.
Carrying hundreds of tidier methods for model classes it does not own, broom's workload is dominated by other projects' breaking changes and CRAN's evolving checks. New tidier coverage has largely migrated to the packages that define the models, leaving broom as a compatibility surface.
Expect the cadence to stay reactive, with releases triggered by r-devel check failures and upstream API shifts rather than expanded model coverage.
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 broom or vetiver.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
patchwork stopped being a ggplot composer and became a page composer.
See all broom alternatives → · See all vetiver alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Analytics. broom 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. broom 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 broom alternatives in Analytics are ranked by recent ship velocity. Browse the "broom alternatives" section above for the current picks, or visit /alternatives/broom 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.