tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of bayesplot and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
bayesplot keeps widening its posterior-check catalogue while absorbing each ggplot2 break.
bayesplot supplies the plotting layer for Stan-adjacent Bayesian workflows: posterior predictive checks, MCMC diagnostics and LOO diagnostics. Releases through 2025 alternate between new plot families and keeping pace with ggplot2, which changed behavior twice in the visible window. Contributions increasingly arrive from outside the core Stan team.
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.
bayesplot supplies the plotting layer for Stan-adjacent Bayesian workflows: posterior predictive checks, MCMC diagnostics and LOO diagnostics. Releases through 2025 alternate between new plot families and keeping pace with ggplot2, which changed behavior twice in the visible window. Contributions increasingly arrive from outside the core Stan team.
Two forces drive the release line: expanding what can be checked visually, and absorbing upstream ggplot2 churn. The 1.13-1.14 pair shows the first, adding LOO-PIT ECDF plots, quantile dot plots and discrete-data handling across the stat family, while 1.12 and 1.15 are largely spent on ggplot2 3.6 and 4.0 compatibility. The recurring new-contributor lists suggest maintenance load is being spread rather than concentrated.
Discrete-data support has rolled out plot family by plot family across three releases; the next release most likely continues that sweep and finishes the ggplot2 v4 adaptation.
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 bayesplot 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 bayesplot 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. bayesplot 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. bayesplot 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 bayesplot alternatives in Analytics are ranked by recent ship velocity. Browse the "bayesplot alternatives" section above for the current picks, or visit /alternatives/bayesplot 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.