simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of healthyR.data and qualpalr — 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 palette generator became a palette platform — and changed the metric behind every color it picks.
qualpalr generates maximally distinct categorical color palettes by optimizing perceptual distance, with adaptation for color vision deficiency built in from early on. Version 1.0.0 in August 2025 ended an eight-year stretch of small maintenance releases: the color-difference metric became selectable, existing palettes from ColorBrewer and Tableau became usable as input, and functions arrived to list, retrieve, extend and analyze palettes rather than only generate them. The C++ backend was rewritten as part of the same release.
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.
qualpalr generates maximally distinct categorical color palettes by optimizing perceptual distance, with adaptation for color vision deficiency built in from early on. Version 1.0.0 in August 2025 ended an eight-year stretch of small maintenance releases: the color-difference metric became selectable, existing palettes from ColorBrewer and Tableau became usable as input, and functions arrived to list, retrieve, extend and analyze palettes rather than only generate them. The C++ backend was rewritten as part of the same release.
The package is moving from a generator to a toolkit that also works on palettes it did not create. Accepting a named palette as input, extending an existing one, and analyzing an arbitrary categorical palette all point the optimization machinery outward at the palettes people already use. The color-vision-deficiency handling followed the same path, consolidating from a single cvd_severity scalar to a named vector giving protan, deuter and tritan their own severities.
Two deprecations are explicitly staged for the next major release — autopal(), with no replacement offered, and cvd_severity — so removal is the most likely next structural step. The 1.0.1 release already tracks the underlying qualpal C++ library separately, suggesting future changes may arrive from there.
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 qualpalr.
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 qualpalr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. healthyR.data and qualpalr 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 qualpalr 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 qualpalr alternatives in Analytics are ranked by recent ship velocity. Browse the "qualpalr alternatives" section above for the current picks, or visit /alternatives/qualpalr for the full list with editorial commentary on each.