← Back to home
Comparison · Analytics

censored vs lime

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

Shared themes:r-stats

censored vs lime: at a glance

Featurecensoredlime
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, tidymodels, parsnip, enginesinterpretability, machine-learning, r-stats, maintenance
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

What is censored?

censored keeps survival models aligned with parsnip's shifting prediction contracts

censored supplies survival-analysis engines to parsnip, and its release history is dominated by staying in step with the rest of tidymodels rather than shipping independent features. The 0.2.0 and 0.3.0 releases added engines and prediction types; everything since has been contract alignment — quantile prediction format, hardhat test adaptation, flexsurv preparation.

Read the full censored trajectory →

What is lime?

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.

Read the full lime trajectory →

censored vs lime: editorial side-by-side

C
censored
ANALYTICS
0.0

censored keeps survival models aligned with parsnip's shifting prediction contracts

◆ Current state

censored supplies survival-analysis engines to parsnip, and its release history is dominated by staying in step with the rest of tidymodels rather than shipping independent features. The 0.2.0 and 0.3.0 releases added engines and prediction types; everything since has been contract alignment — quantile prediction format, hardhat test adaptation, flexsurv preparation.

◆ Where it's heading

The package is settling into a downstream role where parsnip and hardhat set the interface and censored implements it for censored regression. Breaking changes arrive from upstream, not from new ideas here. The substantive engine work — aorsf, flexsurvspline, glmnet multi_predict — is behind it, and recent cycles are thin.

◆ Prediction

Expect the next releases to track further parsnip prediction-type changes rather than add engines; the entries do not show new survival methods in progress.

L
lime
ANALYTICS
0.0

lime survives on compatibility patches years after its research moment

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect the next release to be another compatibility fix triggered by an upstream model package, not new explanation methods.

Alternatives to censored and lime

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 censored or lime.

See all censored alternatives → · See all lime alternatives →

Recent activity from censored and lime

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

  1. 4mo agocensoredcensored 0.3.4
  2. 8mo agolimeCompatibility across all xgboost versions
  3. 1y agocensoredQuantile prediction format follows new parsnip requirements
  4. 2y agocensoredSurvival probabilities at infinite evaluation times now computed
  5. 2y agocensoredcensored 0.3.1
  6. 2y agocensoredmulti_predict() for all glmnet prediction types; aorsf predicts time
  7. 3y agocensoredeval_time replaces time; matrix fitting for censored regression
  8. 3y agolimeMaintainer handover to Emil Hvitfeldt
  9. 5y agolimeorder() fix and lighter dependencies
  10. 6y agolimeNamespace fix following glmnet changes
  11. 7y agolimeexplain() gains pass-through args and gower_pow tuning
  12. 8y agolimeh2o support, NA handling and date feature types

Frequently asked questions

What is the difference between censored and lime?

Both compete on the same themes — r-stats — within Analytics. censored and lime 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 censored better than lime?

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

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

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-r for the full list with editorial commentary on each.