← Back to home
Comparison · Analytics

intsurv vs vinereg

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

Shared themes:r-package

intsurv vs vinereg: at a glance

Featureintsurvvinereg
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationr-package, copulas, regression, conditional-density
Last editorial update3h ago1h 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 vinereg?

Conditional density and log-likelihood fill out a vine copula regression package.

vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.

Read the full vinereg trajectory →

intsurv vs vinereg: 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.

V
vinereg
ANALYTICS
0.0

Conditional density and log-likelihood fill out a vine copula regression package.

◆ Current state

vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.

◆ Where it's heading

Work has concentrated on evaluation rather than fitting: cll() in 0.9.0, pdf() in 0.10.0, and the discrete-variable correction in 0.11.0 all concern what can be computed from a model already fitted. Releases arrive in same-day pairs, and the notes are terse enough that 0.10.0 reuses 0.9.0's wording verbatim, describing pdf() with cll()'s sentence. Version floors also track the sibling packages - kde1d here, rvinecopulib in 0.8.3.

◆ Prediction

Given the shared release rhythm across the stack, the next entry is as likely to be a dependency-driven bump as a new function; the discrete-variable path is the one area these notes show as recently unstable.

Alternatives to intsurv and vinereg

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

See all intsurv alternatives → · See all vinereg alternatives →

Recent activity from intsurv and vinereg

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

  1. 10mo agointsurvModel configuration moves into dedicated control functions
  2. 1y agovineregDiscrete conditional densities fixed; kde1d 1.1.0 required
  3. 1y agovineregpdf() added for conditional density
  4. 2y agovineregBoost compile flag and a weights error fixed
  5. 2y agovineregcll() computes conditional log-likelihood
  6. 4y agovineregvinecopulib floor raised for RcppThread compatibility
  7. 4y agovineregcpit() fixed and external marginals allowed via uscale
  8. 5y agointsurvCross-validated model selection and offset terms added
  9. 6y agointsurvC++ headers relocated so other packages can link them
  10. 7y agointsurvCox cure models for uncertain event status arrive
  11. 7y agointsurvParameter initialization methods added to the alpha
  12. 7y agointsurvAlpha cut for paper submission and simulation reproducibility

Frequently asked questions

What is the difference between intsurv and vinereg?

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

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

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