tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
ggraph vs lime
A side-by-side editorial comparison of ggraph and lime — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-statsmaintenance
ggraph vs lime: at a glance
What is ggraph?
ggraph has settled into ggplot2 compatibility duty
ggraph provides the grammar of graphics for network and tree data. Its recent releases are compatibility and bug-fix work — a collapse fix in get_edges() alongside ggplot2 v4.0.0 upkeep, and before that a pipe rollback. The last release with real content was 2.2.0, a long list of layout and edge-geom corrections.
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.
ggraph vs lime: editorial side-by-side
ggraph
0.0ANALYTICS
ggraph has settled into ggplot2 compatibility duty
◆ Current state
ggraph provides the grammar of graphics for network and tree data. Its recent releases are compatibility and bug-fix work — a collapse fix in get_edges() alongside ggplot2 v4.0.0 upkeep, and before that a pipe rollback. The last release with real content was 2.2.0, a long list of layout and edge-geom corrections.
◆ Where it's heading
The feature surface looks finished and the maintenance is about keeping it working under a moving ggplot2. The one architectural move in this window — pushing dendrogram layout into compiled code to escape R's recursion limits, back in 2.1.0 — was about scaling existing features, not adding new ones.
◆ Prediction
Expect the next release to follow ggplot2 4.0.0 rather than introduce layouts or edge geoms.
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 ggraph 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 ggraph 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.
Recent activity from ggraph and lime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agolimeCompatibility across all xgboost versions
- 11mo agoggraphget_edges() collapse fix and ggplot2 v4 upkeep
- 2y agoggraphNative pipe usage rolled back
- 2y agoggraphLayout precision and edge geom fixes across the package
- 3y agoggraphBinned edge scales and compiled dendrogram layouts
- 3y agolimeMaintainer handover to Emil Hvitfeldt
- 5y agolimeorder() fix and lighter dependencies
- 5y agoggraphC++11 pinned to fix std::random_shuffle deprecation
- 5y agoggraphFaceting and edge geom bug fixes
- 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 ggraph and lime?
Both compete on the same themes — r-stats, maintenance — within Analytics. ggraph 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 ggraph better than lime?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggraph 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 ggraph?
Top ggraph alternatives in Analytics are ranked by recent ship velocity. Browse the "ggraph alternatives" section above for the current picks, or visit /alternatives/ggraph 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.