simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of healthyR.data and reda — release velocity, themes, recent moves, and the top alternatives to consider.
From a bundled hospital dataset to a live CMS API client.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.
reda provides nonparametric mean cumulative function estimation, gamma-frailty rate regression, and event-data simulation for recurrent-event survival analysis. The core API settled at 0.5.0 when Recur() replaced Survr() and the MCF internals moved to C++. Everything since has been consolidation: small argument additions, method completions, and CRAN hygiene.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.
With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.
reda provides nonparametric mean cumulative function estimation, gamma-frailty rate regression, and event-data simulation for recurrent-event survival analysis. The core API settled at 0.5.0 when Recur() replaced Survr() and the MCF internals moved to C++. Everything since has been consolidation: small argument additions, method completions, and CRAN hygiene.
The last three releases contain no new modelling capability at all — a dependency reshuffle, a test-example correction, and a print-order fix. The package is being kept installable and correct rather than extended. Its tightest coupling is to splines2, a sibling package from the same maintainer, which supplies the derivative machinery reda depends on.
Expect continued small-cadence CRAN-compliance releases tracking ggplot2 and splines2 changes. The entries show no in-progress feature work, so a substantive release would have to arrive without warning from this feed.
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 healthyR.data or reda.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all healthyR.data alternatives → · See all reda alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. healthyR.data and reda 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. healthyR.data and reda 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 healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data for the full list with editorial commentary on each.
Top reda alternatives in Analytics are ranked by recent ship velocity. Browse the "reda alternatives" section above for the current picks, or visit /alternatives/reda for the full list with editorial commentary on each.