tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
ggeffects vs lime
A side-by-side editorial comparison of ggeffects and lime — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-stats
ggeffects vs lime: at a glance
What is ggeffects?
ggeffects hands its contrast engine to modelbased and keeps the interface
ggeffects computes and plots marginal effects for a long tail of R model classes. Its recent line has two threads: steadily broadening model support and argument surface, and repeatedly absorbing breaking changes from the packages it computes on top of. In 2.2.0 it stopped absorbing them and delegated test_predictions() and johnson_neyman() to modelbased instead.
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.
ggeffects vs lime: editorial side-by-side
ggeffects
0.0ANALYTICS
ggeffects hands its contrast engine to modelbased and keeps the interface
◆ Current state
ggeffects computes and plots marginal effects for a long tail of R model classes. Its recent line has two threads: steadily broadening model support and argument surface, and repeatedly absorbing breaking changes from the packages it computes on top of. In 2.2.0 it stopped absorbing them and delegated test_predictions() and johnson_neyman() to modelbased instead.
◆ Where it's heading
The package is settling into a front-end role — a consistent predict_response() interface over other people's estimation engines — rather than owning the computation itself. The 2.x releases also show a pattern of removing deprecated arguments and clarifying mixed-model semantics, so the interface is being tightened as the backend is outsourced.
◆ Prediction
Expect the features lost in the modelbased handover to return as that package's contrast and slope estimation matures, rather than being reimplemented locally.
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.
Alternatives to ggeffects and lime
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 ggeffects or lime.
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.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all ggeffects alternatives → · See all lime alternatives →
Recent activity from ggeffects and lime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agolimeCompatibility across all xgboost versions
- 1y agoggeffectsggeffects delegates contrasts and slopes to modelbased ⚡
- 1y agoggeffectsFive focal terms and formula-based contrast tests
- 1y agoggeffectsMixed-model predictions split type from interval
- 1y agoggeffectsBias correction for back-transformed mixed-model predictions
- 1y agoggeffectsSupport for WeightIt model classes
- 2y agoggeffectsglmgee support and vcov controls for ggemmeans()
- 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 ggeffects and lime?
Both compete on the same themes — r-stats — within Analytics. ggeffects and lime 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 ggeffects better than lime?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggeffects and lime 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 ggeffects?
Top ggeffects alternatives in Analytics are ranked by recent ship velocity. Browse the "ggeffects alternatives" section above for the current picks, or visit /alternatives/ggeffects for the full list with editorial commentary on each.
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.