simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of healthyR.data and regfusionr — 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.
Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed
regfusionr maps coordinates between volumetric brain templates (MNI152, Colin27) and the fsaverage surface. After four dormant years it returned in July 2026 with a release that fixes a coordinate-indexing bug, unblocks a previously disabled function, and completes the template-by-method matrix so all four combinations answer point queries. It also breaks compatibility by switching to the standard FREESURFER_HOME environment variable.
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.
regfusionr maps coordinates between volumetric brain templates (MNI152, Colin27) and the fsaverage surface. After four dormant years it returned in July 2026 with a release that fixes a coordinate-indexing bug, unblocks a previously disabled function, and completes the template-by-method matrix so all four combinations answer point queries. It also breaks compatibility by switching to the standard FREESURFER_HOME environment variable.
The package moved from a partial implementation to a complete one in a single release. Before this, vol_coords_to_fsaverage returned coordinates indexed by query position rather than by vertex index — results that looked plausible and were wrong — and fsaverage_to_vol was guarded behind a stop(). Both are now resolved, and the new Colin27 and MNI152 convenience functions make the mapping bidirectional. The sibling package haze shipped a maintenance release 56 minutes later, marking this as a coordinated sweep across the maintainer's neuroimaging stack.
With the four template-by-method combinations closed and the coordinate bug fixed, the next release is more likely to be CRAN-adjacent packaging or documentation than new mapping capability.
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 regfusionr.
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 regfusionr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. regfusionr is currently shipping more aggressively (velocity 3.8 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. regfusionr is currently shipping more aggressively (velocity 3.8 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 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 regfusionr alternatives in Analytics are ranked by recent ship velocity. Browse the "regfusionr alternatives" section above for the current picks, or visit /alternatives/regfusionr for the full list with editorial commentary on each.