metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of cfr and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
cfr packaged delay-corrected severity estimation, then went quiet on maintenance.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
Rho is building an agentic R IDE in public, one signed prerelease at a time.
Rho ships only development prereleases — a Windows build stamp in July, then two 0.4.0 candidates in August. The 0.4.0-dev.39 notes are the first to describe the product rather than the build: provider-first model settings with capability-based routing, project-scoped agent conversations with bounded concurrency and per-file Apply/Undo, and AGPL-3.0-only licensing. Release engineering gets as much text as features — signing, notarization, checksums, and an actor-bound acceptance record.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.
The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.
Rho ships only development prereleases — a Windows build stamp in July, then two 0.4.0 candidates in August. The 0.4.0-dev.39 notes are the first to describe the product rather than the build: provider-first model settings with capability-based routing, project-scoped agent conversations with bounded concurrency and per-file Apply/Undo, and AGPL-3.0-only licensing. Release engineering gets as much text as features — signing, notarization, checksums, and an actor-bound acceptance record.
The direction is an R IDE where a model-driven agent edits files under explicit user control, with the provider left open rather than bundled. Each release tightens the evidence chain around the binaries at least as hard as it tightens the feature set, and the notes name exactly which human checks were skipped and why. Nothing in the feed is presented as production-ready.
Expect the 0.4.0 line to keep iterating as dev builds until a Windows device and an enabled-Gatekeeper Mac clear the two outstanding human checks; a stable tag looks unlikely before that.
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 cfr or Rho.
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.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top cfr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfr alternatives" section above for the current picks, or visit /alternatives/cfr for the full list with editorial commentary on each.
Top Rho alternatives in Analytics are ranked by recent ship velocity. Browse the "Rho alternatives" section above for the current picks, or visit /alternatives/yulab-smu-rho for the full list with editorial commentary on each.