simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of healthyR.data and hoopr — 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.
hoopR rebuilds its HTTP layer on httr2 to stop segfaulting on modern systems
hoopR is the sportsdataverse R package for basketball data, wrapping ESPN, NBA Stats, NBA G-League, NCAA and KenPom behind a single set of loaders. Version 3.0.0 replaces httr with httr2 across every one of those backends, drops httr from Imports, and routes all calls through shared internal retry and response helpers. The change is breaking, and it exists because the old stack segfaulted against libcurl 8.x and curl 7.0.0.
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.
hoopR is the sportsdataverse R package for basketball data, wrapping ESPN, NBA Stats, NBA G-League, NCAA and KenPom behind a single set of loaders. Version 3.0.0 replaces httr with httr2 across every one of those backends, drops httr from Imports, and routes all calls through shared internal retry and response helpers. The change is breaking, and it exists because the old stack segfaulted against libcurl 8.x and curl 7.0.0.
The package's history is two distinct eras. Through 2021-2023 it grew by endpoint accretion — ESPN stat functions, G-League coverage, the NBA live and boxscore V3 families, on-court players in play-by-play — expanding what could be pulled. The recent work is consolidation instead: one HTTP pipeline, one messaging library, data served from the shared sportsdataverse-data releases rather than per-package repositories. The centre of gravity has moved from adding endpoints to making the plumbing survive its dependencies.
With the HTTP layer unified behind shared helpers, expect the sibling sportsdataverse packages to follow the same httr2 migration, and hoopR's own next releases to resume endpoint work now that requests run through one pipeline.
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 hoopr.
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 hoopr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — api-client — within Analytics. healthyR.data and hoopr 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 hoopr 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 hoopr alternatives in Analytics are ranked by recent ship velocity. Browse the "hoopr alternatives" section above for the current picks, or visit /alternatives/hoopr for the full list with editorial commentary on each.