tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of lime and Neo4j — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | lime | Neo4j |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | interpretability, machine-learning, r-stats, maintenance | graph-database, graph-data-science, free-tier, access-control |
| Last editorial update | 1h ago | 18h ago |
| Website | Visit → | — |
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.
Neo4j moves its full graph algorithm catalog onto the free tier and adds attribute-based access control.
Neo4j is pushing capability downward and outward at the same time. The complete Graph Data Science catalog — 65+ algorithms — now runs on AuraDB Free in isolated, unbilled sessions, while Business Critical and Virtual Dedicated Cloud tiers gain attribute-based access control with time-windowed permissions and IdP claim mapping. Around those, the Aura platform continues its monthly cadence: Cypher 25 picked up GROUP BY and a GQL cardinality function, quantized vector search reached general availability, and the Query editor gained persistent tabs.
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.
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.
Expect the next release to be another compatibility fix triggered by an upstream model package, not new explanation methods.
Neo4j is pushing capability downward and outward at the same time. The complete Graph Data Science catalog — 65+ algorithms — now runs on AuraDB Free in isolated, unbilled sessions, while Business Critical and Virtual Dedicated Cloud tiers gain attribute-based access control with time-windowed permissions and IdP claim mapping. Around those, the Aura platform continues its monthly cadence: Cypher 25 picked up GROUP BY and a GQL cardinality function, quantized vector search reached general availability, and the Query editor gained persistent tabs.
The shape here is a funnel. Free-tier users get the algorithm catalog and hosted MCP access with no billing and no setup, which lowers the cost of the first serious graph experiment to nothing; enterprise tiers get the governance controls that make an expansion defensible. Cypher is simultaneously being pulled toward the GQL standard and extended with new surfaces — auth rules, grouping clauses — so the query language is absorbing work that used to sit in configuration and driver code.
Expect ABAC to descend to Professional tiers and the Aura Graph Analytics free session limits to become the pressure point Neo4j uses to convert experiments into paid capacity. The unresolved question from these entries is whether MCP for Aura reaches Virtual Dedicated Cloud, which is listed as pending.
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 Neo4j.
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.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Neo4j is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. 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. Neo4j is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
Top Neo4j alternatives in Analytics are ranked by recent ship velocity. Browse the "Neo4j alternatives" section above for the current picks, or visit /alternatives/neo4j for the full list with editorial commentary on each.