← Back to home
Comparison · Analytics

haze vs healthyR.data

A side-by-side editorial comparison of haze and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

haze vs healthyR.data: at a glance

FeaturehazehealthyR.data
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesneuroimaging, mesh-processing, interpolation, r-packager-package, healthcare-data, cms, api-client
Last editorial update9h ago2h ago
WebsiteVisit →Visit →

What is haze?

Four dormant years end with a modernization pass and an off-by-one fix in the C++ core

haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.

Read the full haze trajectory →

What is healthyR.data?

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.

Read the full healthyR.data trajectory →

haze vs healthyR.data: editorial side-by-side

H
haze
ANALYTICS
2.5

Four dormant years end with a modernization pass and an off-by-one fix in the C++ core

◆ Current state

haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.

◆ Where it's heading

The July 2026 release arrived 56 minutes after its sibling regfusionr 0.3.0 from the same maintainer, which is the tell: this is a maintainer sweeping a set of related neuroimaging packages back into working order, not independent development on haze itself. haze is the dependency, regfusionr the consumer, and the substantive work sits on the regfusionr side. The off-by-one correction is the only change here that alters results.

◆ Prediction

Expect haze to move only when a downstream dfsp-spirit package needs it to — its cadence is driven by the sibling packages, not by its own roadmap.

H
healthyR.data
ANALYTICS
0.0

From a bundled hospital dataset to a live CMS API client.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.

Alternatives to haze and healthyR.data

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 haze or healthyR.data.

See all haze alternatives → · See all healthyR.data alternatives →

Recent activity from haze and healthyR.data

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 18d agohazeVersion 0.3.0 -- Fixes and modernization
  2. 1y agohealthyR.datahttr2 compatibility fix
  3. 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
  4. 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data
  5. 3y agohealthyR.dataTwenty CMS measure accessors added
  6. 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
  7. 4y agohazev0.2.0 -- kdtrees
  8. 4y agohazev0.1.0: Initial release
  9. 5y agohealthyR.dataxz compression added to meet CRAN size policy

Frequently asked questions

What is the difference between haze and healthyR.data?

Both compete on the same themes — r-package — within Analytics. haze is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.

Is haze better than healthyR.data?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. haze is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.

What are the best alternatives to haze?

Top haze alternatives in Analytics are ranked by recent ship velocity. Browse the "haze alternatives" section above for the current picks, or visit /alternatives/haze for the full list with editorial commentary on each.

What are the best alternatives to healthyR.data?

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.