tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
lime vs tidymodels
A side-by-side editorial comparison of lime and tidymodels — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
lime vs tidymodels: at a glance
What is lime?
The R port of LIME has shipped one commit in three years, and it was an xgboost compatibility patch
lime is the R implementation of local interpretable model-agnostic explanations, and it is effectively in preservation rather than development. Its last substantive feature release was 0.5.0 in 2019; 0.5.3 in 2022 recorded a maintainer handover and general upkeep; 0.5.4 in December 2025 exists solely to keep the package working across xgboost versions. Six releases span eight years, and only two of them contain features.
What is tidymodels?
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.
lime vs tidymodels: editorial side-by-side
lime
0.0ANALYTICS
The R port of LIME has shipped one commit in three years, and it was an xgboost compatibility patch
◆ Current state
lime is the R implementation of local interpretable model-agnostic explanations, and it is effectively in preservation rather than development. Its last substantive feature release was 0.5.0 in 2019; 0.5.3 in 2022 recorded a maintainer handover and general upkeep; 0.5.4 in December 2025 exists solely to keep the package working across xgboost versions. Six releases span eight years, and only two of them contain features.
◆ Where it's heading
The pattern is upstream-driven survival: every release since 0.5.0 responds to a change in something lime depends on — glmnet's namespace, order() semantics on data frames, xgboost's interface. The one deliberate change in that stretch was moving htmlwidgets, shiny and shinythemes to Suggests, which lightens installation for the majority of users who never open the interactive explainer. Nothing in the feed indicates work on the explanation method itself.
◆ Prediction
Expect the next release, whenever it comes, to be another compatibility patch triggered by a dependency change rather than anything touching how explanations are computed. The three-year gaps make timing unpredictable.
tidymodels
0.0ANALYTICS
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
◆ Current state
The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.
◆ Where it's heading
Release cadence tracks the ecosystem rather than any roadmap of its own: a version bump when member packages release, a tidymodels_prefer() rule when a new conflict appears — DALEX::explains() over dplyr::explains(), recipes::update() over other update() methods. Additions to the core set are the only structurally interesting events, and there have been two in seven releases. Everything else is plumbing that exists so a single library() call attaches a consistent set of versions.
◆ Prediction
The next release will most likely be another version-set update, with any new core package the only thing worth noting. Feature news for this framework will keep arriving in the member packages, not here.
Alternatives to lime and tidymodels
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 tidymodels.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all lime alternatives → · See all tidymodels alternatives →
Recent activity from lime and tidymodels
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agolimexgboost compatibility restored across versions
- 11mo agotidymodelsFix for packages omitted from attachment
- 11mo agotidymodelstailor joins the core set; base pipe replaces magrittr
- 1y agotidymodelsConflict preferences added for DALEX and recipes
- 3y agotidymodelsConflict preferences and pinned versions refreshed
- 3y agolimeMaintainer handover and general upkeep
- 4y agotidymodelsVersion refresh and testthat 3e migration
- 4y agotidymodelsRotating startup messages and an analysis template
- 5y agolimeShiny dependencies moved to Suggests
- 6y agolimeNamespace fix for glmnet changes
- 7y agolimegower_pow added and lambda aligned with the Python implementation
- 8y agolimeh2o support, NA handling, and date columns held during permutation
Frequently asked questions
What is the difference between lime and tidymodels?
Both compete on the same themes — r-packages — within Analytics. lime and tidymodels 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 tidymodels?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lime and tidymodels 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 for the full list with editorial commentary on each.
What are the best alternatives to tidymodels?
Top tidymodels alternatives in Analytics are ranked by recent ship velocity. Browse the "tidymodels alternatives" section above for the current picks, or visit /alternatives/tidymodels for the full list with editorial commentary on each.