ANALYTICS
mirai removed its dispatcher process and added memory backpressure to the queue.
Alternatives · analytics tools
mlr3cmprsk alternatives
The best mlr3cmprsk alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to mlr3cmprsk? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, mlr3cmprsk shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About mlr3cmprsk
Competing risks arrive in mlr3, going from a non-parametric baseline to Fine-Gray regression in seven weeks.
mlr3cmprsk extends mlr3 to competing-risks analysis: learners predicting cumulative incidence functions, plus measures to score them. It appeared in February 2026 and reached 0.0.5 by April, adding a Fine-Gray learner and a Brier score along the way. The version numbers say pre-release; the cadence says active build-out.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to mlr3cmprsk
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
ggsurvfit is in correctness-and-compatibility mode, not feature mode.
ANALYTICS
nanonext keeps shrinking its build requirements while adding messaging primitives.
ANALYTICS
DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.
ANALYTICS
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
ANALYTICS
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
ANALYTICS
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
ANALYTICS
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
ANALYTICS
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
ANALYTICS
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
ANALYTICS
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
ANALYTICS
The EDI data client is being dragged through its repository's identity-system migration.
mlr3cmprsk vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| mlr3cmprsk (baseline) | 0.0 | 0 | mlr3competing-riskssurvival-analysis | Fine-Gray learner brings regression modelling to competing risks |
| mirai | 2.5 | 0 | parallel-computingasyncbackpressure | Dispatcher becomes a thread, and the queue gains a memory budget |
| ggsurvfit | 2.5 | 0 | survival-analysisggplot2competing-risks | — |
| nanonext | 2.5 | 0 | async-messagingnnghttp-server | Zero-copy message forwarding, and cmake dropped from the build |
| DataSpaceR | 2.5 | 0 | hiv-researchimmunology-dataapi-client | Query API rebuilt and DAASH antibody sequence access added |
| metatools | 0.0 | 0 | pharmaversesdtmadam | — |
| marquee | 0.0 | 0 | r-libtypographymarkdown | — |
| logrx | 0.0 | 0 | pharmaverseloggingclinical-trials | — |
| lobstr | 0.0 | 0 | r-libintrospectionmemory | truelength reporting dropped for public C API compliance |
| GSODR | 0.0 | 0 | ropensciweather-datar-package | — |
| giscoR | 0.0 | 0 | eurostatgeospatialropensci | 1.0 caches the dataset index so new vintages need no release |
| FedData | 0.0 | 0 | ropenscigeospatialr-package | sp and raster dropped; everything returns terra or sf |
| EDIutils | 0.0 | 0 | ropenscir-packageapi-client | EDI-IDs replace Distinguished Names as authentication moves to IAM |
The 12 best mlr3cmprsk alternatives, in depth
1. mirai · velocity 2.5
Mirai removed its dispatcher process and added memory backpressure to the queue.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Dispatcher becomes a thread, and the queue gains a memory budget”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, mirai focuses on parallel computing, async and backpressure.
mirai and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. ggsurvfit · velocity 2.5
Ggsurvfit is in correctness-and-compatibility mode, not feature mode.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, ggsurvfit focuses on survival analysis, ggplot2 and competing risks.
ggsurvfit and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ggsurvfit trajectory → · Compare mlr3cmprsk vs ggsurvfit →
3. nanonext · velocity 2.5
Nanonext keeps shrinking its build requirements while adding messaging primitives.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Zero-copy message forwarding, and cmake dropped from the build”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, nanonext focuses on async messaging, nng and http server.
nanonext and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full nanonext trajectory → · Compare mlr3cmprsk vs nanonext →
4. DataSpaceR · velocity 2.5
DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Query API rebuilt and DAASH antibody sequence access added”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, DataSpaceR focuses on hiv research, immunology data and api client.
DataSpaceR and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full DataSpaceR trajectory → · Compare mlr3cmprsk vs DataSpaceR →
5. metatools · velocity 0.0
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, metatools focuses on pharmaverse, sdtm and adam.
metatools and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full metatools trajectory → · Compare mlr3cmprsk vs metatools →
6. marquee · velocity 0.0
Marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, marquee focuses on r lib, typography and markdown.
marquee and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. logrx · velocity 0.0
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, logrx focuses on pharmaverse, logging and clinical trials.
logrx and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. lobstr · velocity 0.0
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “truelength reporting dropped for public C API compliance”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, lobstr focuses on r lib, introspection and memory.
lobstr and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. GSODR · velocity 0.0
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, GSODR focuses on ropensci, weather data and r package.
GSODR and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. giscoR · velocity 0.0
GiscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0 caches the dataset index so new vintages need no release”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, giscoR focuses on eurostat, geospatial and ropensci.
giscoR and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. FedData · velocity 0.0
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “sp and raster dropped; everything returns terra or sf”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, FedData focuses on ropensci, geospatial and r package.
FedData and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. EDIutils · velocity 0.0
The EDI data client is being dragged through its repository's identity-system migration.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “EDI-IDs replace Distinguished Names as authentication moves to IAM”.
Where mlr3cmprsk leans on mlr3, competing risks and survival analysis, EDIutils focuses on ropensci, r package and api client.
EDIutils and mlr3cmprsk have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full EDIutils trajectory → · Compare mlr3cmprsk vs EDIutils →
Frequently asked questions
What are the best alternatives to mlr3cmprsk?
The top mlr3cmprsk alternatives we currently track in analytics tools are mirai, ggsurvfit, nanonext, DataSpaceR, metatools, ranked by recent ship velocity.
How is this list of mlr3cmprsk alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare mlr3cmprsk directly with one of these alternatives?
Yes — every card has a "Compare with mlr3cmprsk" link to a side-by-side /compare page.