ANALYTICS
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Alternatives · analytics tools
lime alternatives
The best lime alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to lime? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, lime shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About 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.
Velocity 0.0 · Last update 48m ago
Top 12 alternatives to lime
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
ANALYTICS
crul took mocking back from webmockr and made it a property of the client itself
ANALYTICS
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
ANALYTICS
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
ANALYTICS
Six years since the last functional change, and Google renamed the service it wraps in the release before that
ANALYTICS
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
ANALYTICS
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
ANALYTICS
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
ANALYTICS
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
ANALYTICS
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers
lime vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| lime (baseline) | 0.0 | 0 | explainabilitymachine-learningmaintenance-mode | — |
| r2rtf | 0.0 | 0 | clinical-reportingrtfinternationalization | Chinese character support arrives via an i18n font path |
| DoseFinding | 0.0 | 0 | dose-responsemcp-modclinical-trials | Model averaging arrives for dose-response fitting |
| webmockr | 0.0 | 0 | http-mockingtestinghttr2 | httr2 joins httr and crul as a supported client |
| crul | 0.0 | 0 | http-clientasyncmocking | Mocking becomes a client parameter, independent of webmockr |
| dendroNetwork | 0.0 | 0 | dendrochronologynetwork-analysiscytoscape | — |
| chattr | 0.0 | 0 | llmrstudioide-integration | All model integration moves to ellmer, direct backends removed |
| cloudml | 0.0 | 0 | machine-learninggoogle-cloudtensorflow | — |
| tidymodels | 0.0 | 0 | tidymodelsmeta-packagedependency-management | — |
| datapack | 0.0 | 0 | research-datadataoneprovenance | Assembled data packages become editable in place |
| USAboundaries | 0.0 | 0 | geospatialcensus-datasf | Data split into a companion package; all boundaries become sf |
| slider | 0.0 | 0 | sliding-windowstidyversec-api-compliance | — |
| simtrial | 0.0 | 0 | clinical-trialsgroup-sequentialsurvival-analysis | RMST and milestone tests, plus a user-definable cut and test framework |
The 12 best lime alternatives, in depth
1. r2rtf · velocity 0.0
The clinical-report table engine learned Chinese, then learned to leave RTF entirely.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Chinese character support arrives via an i18n font path”.
Where lime leans on explainability, machine learning and maintenance mode, r2rtf focuses on clinical reporting, rtf and internationalization.
r2rtf and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. DoseFinding · velocity 0.0
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Model averaging arrives for dose-response fitting”.
Where lime leans on explainability, machine learning and maintenance mode, DoseFinding focuses on dose response, mcp mod and clinical trials.
DoseFinding and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full DoseFinding trajectory → · Compare lime vs DoseFinding →
3. webmockr · velocity 0.0
The stubbing library added httr2 support, then spent a year cutting itself free of everything else.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “httr2 joins httr and crul as a supported client”.
Where lime leans on explainability, machine learning and maintenance mode, webmockr focuses on http mocking, testing and httr2.
webmockr and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. crul · velocity 0.0
Crul took mocking back from webmockr and made it a property of the client itself.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Mocking becomes a client parameter, independent of webmockr”.
Where lime leans on explainability, machine learning and maintenance mode, crul focuses on http client, async and mocking.
crul and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. dendroNetwork · velocity 0.0
Six releases, six identical bodies — the feed carries the package abstract instead of release notes.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where lime leans on explainability, machine learning and maintenance mode, dendroNetwork focuses on dendrochronology, network analysis and cytoscape.
dendroNetwork and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full dendroNetwork trajectory → · Compare lime vs dendroNetwork →
6. chattr · velocity 0.0
Chattr deleted every LLM integration it had written and outsourced the lot to ellmer.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “All model integration moves to ellmer, direct backends removed”.
Where lime leans on explainability, machine learning and maintenance mode, chattr focuses on llm, rstudio and ide integration.
chattr and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. cloudml · velocity 0.0
Six years since the last functional change, and Google renamed the service it wraps in the release before that.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where lime leans on explainability, machine learning and maintenance mode, cloudml focuses on machine learning, google cloud and tensorflow.
cloudml and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. tidymodels · velocity 0.0
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where lime leans on explainability, machine learning and maintenance mode, tidymodels focuses on tidymodels, meta package and dependency management.
tidymodels and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. datapack · velocity 0.0
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Assembled data packages become editable in place”.
Where lime leans on explainability, machine learning and maintenance mode, datapack focuses on research data, dataone and provenance.
datapack and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. USAboundaries · velocity 0.0
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Data split into a companion package; all boundaries become sf”.
Where lime leans on explainability, machine learning and maintenance mode, USAboundaries focuses on geospatial, census data and sf.
USAboundaries and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full USAboundaries trajectory → · Compare lime vs USAboundaries →
11. slider · velocity 0.0
Feature-complete since 2021, and every release since has been paying CRAN's C API bill.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where lime leans on explainability, machine learning and maintenance mode, slider focuses on sliding windows, tidyverse and c api compliance.
slider and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. simtrial · velocity 0.0
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “RMST and milestone tests, plus a user-definable cut and test framework”.
Where lime leans on explainability, machine learning and maintenance mode, simtrial focuses on clinical trials, group sequential and survival analysis.
simtrial and lime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to lime?
The top lime alternatives we currently track in analytics tools are r2rtf, DoseFinding, webmockr, crul, dendroNetwork, ranked by recent ship velocity.
How is this list of lime alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare lime directly with one of these alternatives?
Yes — every card has a "Compare with lime" link to a side-by-side /compare page.