tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of lime and rlistings — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
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.
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.
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.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
The package is progressively delegating pagination to formatters rather than implementing it — paginate_listing() was refactored to call formatters' paginate_to_mpfs() directly, and truetype font support arrived through a new formatters API. That reduces duplicated logic but ties the package's page-break behaviour to a dependency it shares with rtables. Feature work beyond pagination is thin: better error messages for unsupported column classes, a cheatsheet.
Expect pagination fidelity to remain the focus, with changes arriving as formatters exposes more of its layout machinery rather than as rlistings-native features.
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 rlistings.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all lime alternatives → · See all rlistings alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lime and rlistings 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lime and rlistings 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.
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.
Top rlistings alternatives in Analytics are ranked by recent ship velocity. Browse the "rlistings alternatives" section above for the current picks, or visit /alternatives/rlistings for the full list with editorial commentary on each.