tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
lime vs vetiver
A side-by-side editorial comparison of lime and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:maintenance
lime vs vetiver: at a glance
What is lime?
lime survives on compatibility patches years after its research moment
lime brings local interpretable model-agnostic explanations to R. Its substantive development finished around 0.5.0 in 2019, which added argument pass-through to predict(), a gower_pow tuning knob and a batch of fixes. Since then there have been three releases: a namespace fix, a maintainer handover to Emil Hvitfeldt with general upkeep, and a patch to work across xgboost versions.
What is vetiver?
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.
lime vs vetiver: editorial side-by-side
lime
0.0ANALYTICS
lime survives on compatibility patches years after its research moment
◆ Current state
lime brings local interpretable model-agnostic explanations to R. Its substantive development finished around 0.5.0 in 2019, which added argument pass-through to predict(), a gower_pow tuning knob and a batch of fixes. Since then there have been three releases: a namespace fix, a maintainer handover to Emil Hvitfeldt with general upkeep, and a patch to work across xgboost versions.
◆ Where it's heading
The package is in custodial maintenance — kept installable and compatible with the model packages it explains, rather than developed. The 2022 handover is the most consequential entry in the window because it determined that the package would keep getting patches at all.
◆ Prediction
Expect the next release to be another compatibility fix triggered by an upstream model package, not new explanation methods.
vetiver
0.0ANALYTICS
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to lime and vetiver
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 lime or vetiver.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
patchwork
patchwork stopped being a ggplot composer and became a page composer.
See all lime alternatives → · See all vetiver alternatives →
Recent activity from lime and vetiver
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agovetiverSupport all versions of xgboost
- 8mo agolimeCompatibility across all xgboost versions
- 9mo agovetiverFirst release in two years catches up with recipes and probably
- 2y agovetiverFix plumber file generation bug
- 2y agovetiverFix plumber generation for board_url() pins
- 3y agovetivervetiver 0.2.3
- 3y agovetiverModels expose their input prototype over HTTP
- 3y agolimeMaintainer handover to Emil Hvitfeldt
- 5y agolimeorder() fix and lighter dependencies
- 6y agolimeNamespace fix following glmnet changes
- 7y agolimeexplain() gains pass-through args and gower_pow tuning
- 8y agolimeh2o support, NA handling and date feature types
Frequently asked questions
What is the difference between lime and vetiver?
Both compete on the same themes — maintenance — within Analytics. lime 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.
Is lime better than vetiver?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lime 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.
What are the best alternatives to lime?
Top lime alternatives in Analytics are ranked by recent ship velocity. Browse the "lime alternatives" section above for the current picks, or visit /alternatives/lime-r for the full list with editorial commentary on each.
What are the best alternatives to vetiver?
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.