← Back to home
Comparison · Analytics

intsurv vs lavaanExtra

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

Shared themes:r-package

intsurv vs lavaanExtra: at a glance

FeatureintsurvlavaanExtra
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationr-package, structural-equation-modeling, lavaan, apa-reporting
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 lavaanExtra?

SEM reporting helpers converging on APA output, one CRAN resubmission at a time.

lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.

Read the full lavaanExtra trajectory →

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

L
lavaanExtra
ANALYTICS
0.0

SEM reporting helpers converging on APA output, one CRAN resubmission at a time.

◆ Current state

lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.

◆ Where it's heading

The package generalises its own vocabulary as it goes: lavaan_ind() became lavaan_defined() once it turned out to extract any user-defined parameter, and lavaan_cov() was split so lavaan_cor() covers actual correlations. Methodological positions are taken alongside the API - dropping the estimate argument from lavaan_reg() to force reporting both standardized and unstandardized values, and updating the RMSEA benchmark to Schreiber (2017). Rémi Thériault maintains it next to rempsyc, which formats output to match. Note that 0.1.5 restates the whole 0.1.4.x development series in one body.

◆ Prediction

The pattern points to another nice_* helper aimed at a reporting step that currently needs hand formatting, arriving with the usual CRAN resubmission behind it.

Alternatives to intsurv and lavaanExtra

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

See all intsurv alternatives → · See all lavaanExtra alternatives →

Recent activity from intsurv and lavaanExtra

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

  1. 10mo agointsurvModel configuration moves into dedicated control functions
  2. 2y agolavaanExtraCRAN resubmission for a unicode problem
  3. 2y agolavaanExtralavaan_ind renamed to lavaan_defined; thresholds supported
  4. 2y agolavaanExtranice_modindices flags redundant items
  5. 3y agolavaanExtraSuggested dependency versions checked correctly
  6. 3y agolavaanExtraTests run without suggested dependencies
  7. 3y agolavaanExtraFit benchmarks updated and correlations split from covariances
  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 lavaanExtra?

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

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

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