RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of npi and shapviz — release velocity, themes, recent moves, and the top alternatives to consider.
An R client for the US provider registry, tightening its types and edge-case handling
npi wraps the US National Provider Identifier registry API for R users, covering search, validation and summarisation of provider records. The one release in view is a consolidation pass rather than new surface: input normalisation, vectorised validation, and a typed empty result instead of an ambiguous one when a search finds nothing.
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
shapviz turns SHAP values from XGBoost, LightGBM, H2O, kernelshap and other sources into standard diagnostic plots — importance, dependence, waterfall, force and interaction. Recent work is plot ergonomics: shared y-axis control across dependence plots, a bar view for interaction values, and axis collection via patchwork. The two most recent releases are pure compatibility and bug fixes.
npi wraps the US National Provider Identifier registry API for R users, covering search, validation and summarisation of provider records. The one release in view is a consolidation pass rather than new surface: input normalisation, vectorised validation, and a typed empty result instead of an ambiguous one when a search finds nothing.
The work is aimed at making the package behave predictably inside larger pipelines. Returning a typed empty `npi_results` object on no matches, and having `npi_is_valid()` accept vectors and return logical vectors, both remove branches a caller would otherwise write by hand. The bug fix follows the same line — `npi_summarize()` no longer drops input rows when a record's nested address or taxonomy data is missing.
With a single release visible there is not enough of a pattern to predict a direction confidently; the changes here suggest continued interface tidying rather than new API coverage, but that is one data point.
shapviz turns SHAP values from XGBoost, LightGBM, H2O, kernelshap and other sources into standard diagnostic plots — importance, dependence, waterfall, force and interaction. Recent work is plot ergonomics: shared y-axis control across dependence plots, a bar view for interaction values, and axis collection via patchwork. The two most recent releases are pure compatibility and bug fixes.
Two threads run in parallel here. One is visual refinement converging on conventions from Python's shap — the 0.10.0 notes openly float switching share_y to TRUE to match it. The other is connector maintenance, keeping pace with H2O, XGBoost 1.x and 2.x, shapr and permshap as each changes. Neither thread adds new explanation methods; shapviz's job is presentation, and it is being polished rather than extended.
Expect share_y = TRUE to become the default and further ggplot2 4.x fallout, with connector updates arriving as the upstream SHAP packages release.
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 npi or shapviz.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. npi and shapviz 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. npi and shapviz 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 npi alternatives in Analytics are ranked by recent ship velocity. Browse the "npi alternatives" section above for the current picks, or visit /alternatives/npi-r for the full list with editorial commentary on each.
Top shapviz alternatives in Analytics are ranked by recent ship velocity. Browse the "shapviz alternatives" section above for the current picks, or visit /alternatives/shapviz for the full list with editorial commentary on each.