← Back to home
Comparison · Analytics

intsurv vs probmed

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

intsurv vs probmed: at a glance

Featureintsurvprobmed
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationcausal mediation, effect size, semiparametric inference, cross-fitting
Last editorial update45m ago6h ago
WebsiteVisit →Visit →

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 →

What is probmed?

probmed went from one probabilistic effect size to a family of them in sixteen days.

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

Read the full probmed trajectory →

intsurv vs probmed: editorial side-by-side

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.

P
probmed
ANALYTICS
0.0

probmed went from one probabilistic effect size to a family of them in sixteen days.

◆ Current state

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

◆ Where it's heading

The pace is manuscript-driven — estimators arrive with their citations attached and vignettes alongside, and the 0.1.0 notes correct the estimand itself against a manuscript definition rather than fixing a bug in code. Each release adds inference machinery as well as point estimates: percentile-bootstrap intervals and Fieller sets in 0.3.0, a deterministic MBCO interval in 0.2.0 that avoids resampling entirely. The gauge residual and the pmed_sensitivity() helper suggest a growing concern with when the estimand does not decompose at all.

◆ Prediction

0.3.0 shipped a sensitivity helper for shared mediator-outcome confounding and a diagnostic that flags non-decomposability, so the next release most likely extends that diagnostic side rather than adding a fifth estimator family.

Alternatives to intsurv and probmed

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

See all intsurv alternatives → · See all probmed alternatives →

Recent activity from intsurv and probmed

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

  1. 1mo agoprobmedFour estimator families on a cross-fitted corner-EIF core
  2. 2mo agoprobmedParallel mediators and a resampling-free MBCO interval
  3. 2mo agoprobmedFirst release: pmed() with the estimand corrected
  4. 10mo agointsurvModel configuration moves into dedicated control functions
  5. 5y agointsurvCross-validated model selection and offset terms added
  6. 6y agointsurvC++ headers relocated so other packages can link them
  7. 7y agointsurvCox cure models for uncertain event status arrive
  8. 7y agointsurvParameter initialization methods added to the alpha
  9. 7y agointsurvAlpha cut for paper submission and simulation reproducibility

Frequently asked questions

What is the difference between intsurv and probmed?

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

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

What are the best alternatives to probmed?

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