← Back to home
Comparison · Analytics

churon vs intsurv

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

churon vs intsurv: at a glance

Featurechuronintsurv
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesonnx runtime, rust bindings, cran compliance, machine learningsurvival-analysis, cure-models, censored-data, regularization
Last editorial update1h ago43m ago
WebsiteVisit →Visit →

What is churon?

churon is spending its entire release history getting a Rust ONNX binding through CRAN.

An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.

Read the full churon 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 →

churon vs intsurv: editorial side-by-side

C
churon
ANALYTICS
0.0

churon is spending its entire release history getting a Rust ONNX binding through CRAN.

◆ Current state

An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.

◆ Where it's heading

Every visible decision is set by CRAN's build environment rather than by the package's own roadmap — pinned to an older ort release, vendored dependencies restructured for offline builds, and a dedicated CI job that simulates CRAN without network access. That is the standing cost of shipping a Rust-backed inference binding through R's distribution channel, and it is consuming the release stream entirely.

◆ Prediction

Expect the ort pin to move forward only when CRAN's Windows toolchain reaches a newer Rust, since that constraint is stated explicitly as the reason for the downgrade.

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

See all churon alternatives → · See all intsurv alternatives →

Recent activity from churon and intsurv

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

  1. 7mo agochuronVendored Rust sources bundled for offline CRAN builds
  2. 7mo agochuronort pinned back to rc.10 for CRAN Windows builds
  3. 7mo agochuronVersion bump and wasm fix reverted
  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 churon and intsurv?

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

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

Top churon alternatives in Analytics are ranked by recent ship velocity. Browse the "churon alternatives" section above for the current picks, or visit /alternatives/churon 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.