← Back to home
Comparison · Analytics

flashlight vs intsurv

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

Shared themes:r-package

flashlight vs intsurv: at a glance

Featureflashlightintsurv
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmodel-interpretability, explainable-ai, deprecation, api-contractionsurvival-analysis, cure-models, censored-data, regularization
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is flashlight?

flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.

flashlight computes model-agnostic interpretability output — variable importance, partial dependence and effect profiles, breakdown plots — for fitted models in R. Version 1.0.0 in October 2025 executed a contraction announced two years earlier: add_shap() is deprecated in favour of the separate kernelshap and fastshap packages, type = "shap" is gone from every light_* function that accepted it, and eight previously exported helpers became internal. The release also restored compatibility with ggplot2 v4.

Read the full flashlight trajectory →

What is intsurv?

A Cox cure-rate model package woke up after four years to simplify its own interface.

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

Read the full intsurv trajectory →

flashlight vs intsurv: editorial side-by-side

F
flashlight
ANALYTICS
0.0

flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.

◆ Current state

flashlight computes model-agnostic interpretability output — variable importance, partial dependence and effect profiles, breakdown plots — for fitted models in R. Version 1.0.0 in October 2025 executed a contraction announced two years earlier: add_shap() is deprecated in favour of the separate kernelshap and fastshap packages, type = "shap" is gone from every light_* function that accepted it, and eight previously exported helpers became internal. The release also restored compatibility with ggplot2 v4.

◆ Where it's heading

The package is narrowing rather than growing, and doing it on a published schedule — 0.9.0 listed the breaking changes, 1.0.0 applied them essentially unchanged. Handing SHAP computation to dedicated packages leaves flashlight as an effects-and-profiles visualization layer rather than an all-purpose interpretability toolkit. Removing the ability to rename result columns via options() points the same way: fewer configuration surfaces, a smaller contract to maintain.

◆ Prediction

With the deprecation list from 0.9.0 now fully applied, the next releases most likely remove the functions currently deprecated rather than adding capability, and continue tracking ggplot2. The entries show no new analysis method in progress.

I
intsurv
ANALYTICS
0.0

A Cox cure-rate model package woke up after four years to simplify its own interface.

◆ Current state

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

◆ Where it's heading

The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.

◆ Prediction

The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.

Alternatives to flashlight and intsurv

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 flashlight or intsurv.

See all flashlight alternatives → · See all intsurv alternatives →

Recent activity from flashlight and intsurv

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

  1. 10mo agoflashlightSHAP handed off to kernelshap as the public API shrinks
  2. 10mo agointsurvModel configuration moves into dedicated control functions
  3. 3y agoflashlightBreaking changes for 1.0.0 announced two years ahead
  4. 4y agoflashlightMaintenance release covering package generation
  5. 5y agoflashlightggpubr dependency removed
  6. 5y agointsurvCross-validated model selection and offset terms added
  7. 6y agointsurvC++ headers relocated so other packages can link them
  8. 7y agointsurvCox cure models for uncertain event status arrive
  9. 7y agointsurvParameter initialization methods added to the alpha
  10. 7y agointsurvAlpha cut for paper submission and simulation reproducibility

Frequently asked questions

What is the difference between flashlight and intsurv?

Both compete on the same themes — r-package — within Analytics. flashlight and intsurv 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 flashlight better than intsurv?

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

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

What are the best alternatives to intsurv?

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