r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
lime vs pkglite
A side-by-side editorial comparison of lime and pkglite — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
lime vs pkglite: 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 pkglite?
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.
lime vs pkglite: 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.
pkglite
0.0ANALYTICS
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
◆ Current state
pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.
◆ Where it's heading
The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.
◆ Prediction
Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.
Alternatives to lime and pkglite
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 pkglite.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all lime alternatives → · See all pkglite alternatives →
Recent activity from lime and pkglite
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agopkgliteMaintainer email and CI workflow updates
- 8mo agolimexgboost compatibility restored across versions
- 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
- 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
- 2y agopkgliteTest helpers moved to helper.R
- 3y agopkgliteMore file types recognised; cli dependency dropped
- 3y agolimeMaintainer handover and general upkeep
- 5y agopkgliteFile collections gain merge, prune, and a tests 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 pkglite?
Both compete on the same themes — r-packages — within Analytics. lime and pkglite 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 pkglite?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lime and pkglite 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 pkglite?
Top pkglite alternatives in Analytics are ranked by recent ship velocity. Browse the "pkglite alternatives" section above for the current picks, or visit /alternatives/pkglite for the full list with editorial commentary on each.