tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of easystats and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
easystats is the meta-package for the easystats ecosystem, which spans insight, parameters, performance and their siblings. It ships almost no statistics of its own; its releases add installation helpers, ecosystem introspection functions and vignettes. The consequential release in this window is 0.7.0, which moved the whole ecosystem to an MIT license.
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.
easystats is the meta-package for the easystats ecosystem, which spans insight, parameters, performance and their siblings. It ships almost no statistics of its own; its releases add installation helpers, ecosystem introspection functions and vignettes. The consequential release in this window is 0.7.0, which moved the whole ecosystem to an MIT license.
Work concentrates on making the ecosystem legible and installable as a unit: easystats_packages() to enumerate it, easystats_citations() to count its citations, pak and r-universe support to install it, and a complete-workflow vignette to show it in use. Underneath that, 0.7.0 settled the licensing and formalized the author list. The pattern is a project tending its own boundaries rather than adding capability.
The recent additions are all introspection and installation helpers, so the next release most likely adds another of those or refreshes component versions rather than changing what the ecosystem 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 easystats 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 easystats 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. easystats 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. easystats 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 easystats alternatives in Analytics are ranked by recent ship velocity. Browse the "easystats alternatives" section above for the current picks, or visit /alternatives/easystats 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.