← Back to home
Comparison · Analytics

lime vs rtflite

A side-by-side editorial comparison of lime and rtflite — release velocity, themes, recent moves, and the top alternatives to consider.

lime vs rtflite: at a glance

Featurelimertflite
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesexplainability, machine-learning, maintenance-mode, r-packagesclinical-reporting, python, document-conversion, rtf
Last editorial update50m ago1h ago
WebsiteVisit →Visit →

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.

Read the full lime trajectory →

What is rtflite?

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.

Read the full rtflite trajectory →

lime vs rtflite: editorial side-by-side

L
lime
ANALYTICS
0.0

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.

R
rtflite
ANALYTICS
0.0

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

◆ Current state

rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.

◆ Where it's heading

Every format addition routes through the same LibreOffice converter rather than a per-format implementation, and 2.4.0's breaking change made that converter an injectable object you can configure and reuse. That is the shape of a package expecting to run inside a pipeline that produces hundreds of tables, not one that converts a document at a time. The recent quiet — snapshot tests moved onto `pytest-r-snapshot`, docs migrated, pandas and pyarrow dropped from dev dependencies — reads as work to stay dependency-light while the surface stabilizes.

◆ Prediction

With the export matrix filled in and three consecutive infrastructure-only releases, the next substantive change is most likely on the input side — table construction and pagination — since `page_by` and `subline_by` are the only feature area still generating bug reports in these notes.

Alternatives to lime and rtflite

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 rtflite.

See all lime alternatives → · See all rtflite alternatives →

Recent activity from lime and rtflite

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agortfliteMulti-section body typing tightened; pandas dropped from dev deps
  2. 7mo agortfliteAPI reference renders Pydantic field metadata
  3. 7mo agortfliteDocumentation site migrated to Zensical
  4. 7mo agortfliteSnapshot tests moved to pytest-r-snapshot
  5. 7mo agortfliteHTML and PDF export complete the output matrix
  6. 7mo agortfliteLibreOffice conversion becomes an injectable converter object
  7. 8mo agolimexgboost compatibility restored across versions
  8. 3y agolimeMaintainer handover and general upkeep
  9. 5y agolimeShiny dependencies moved to Suggests
  10. 6y agolimeNamespace fix for glmnet changes
  11. 7y agolimegower_pow added and lambda aligned with the Python implementation
  12. 8y agolimeh2o support, NA handling, and date columns held during permutation

Frequently asked questions

What is the difference between lime and rtflite?

They serve adjacent needs but don't currently overlap on shipped themes. lime and rtflite 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 rtflite?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lime and rtflite 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 rtflite?

Top rtflite alternatives in Analytics are ranked by recent ship velocity. Browse the "rtflite alternatives" section above for the current picks, or visit /alternatives/rtflite for the full list with editorial commentary on each.