metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of giscoR and mlr3cmprsk — release velocity, themes, recent moves, and the top alternatives to consider.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
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.
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
The package is decoupling itself from Eurostat's publication calendar. Historically each new GISCO vintage required a release that bumped default years and rebuilt an internal dataset; after 1.0.0 a user can call gisco_get_cached_db(update_cache = TRUE) and reach new data without waiting. The follow-up releases are consistent with a project in consolidation — fixing the cache it just introduced, exposing a timeout for slow downloads, and tidying internals.
With the database now self-updating, expect releases to shift toward download reliability and new GISCO endpoints rather than annual dataset bumps; the timeout option in 1.1.0 suggests large downloads are the current pain point.
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.
The package assembled a working evaluation stack fast. It started with the Aalen-Johansen estimator as a non-parametric baseline, added Fine-Gray as a regression alternative, then filled in the scoring side with an AUC refactor and a fixed-time Brier score. Development has run in lockstep with survdistr and mlr3extralearners, which picked up the dependency at 1.5.2.
The visible gaps are more learners — cause-specific Cox and boosting variants — and the tuning and pipeline integration the rest of mlr3 expects; the measure side currently looks further along than the model side.
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 giscoR or mlr3cmprsk.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all giscoR alternatives → · See all mlr3cmprsk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. giscoR and mlr3cmprsk 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. giscoR and mlr3cmprsk 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.
Top giscoR alternatives in Analytics are ranked by recent ship velocity. Browse the "giscoR alternatives" section above for the current picks, or visit /alternatives/giscor for the full list with editorial commentary on each.
Top mlr3cmprsk alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3cmprsk alternatives" section above for the current picks, or visit /alternatives/mlr3cmprsk for the full list with editorial commentary on each.