RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of modeltime.ensemble and npi — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
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.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.
Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.
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.
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 modeltime.ensemble or npi.
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
See all modeltime.ensemble alternatives → · See all npi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. modeltime.ensemble and npi 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. modeltime.ensemble and npi 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 modeltime.ensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.ensemble alternatives" section above for the current picks, or visit /alternatives/modeltime-ensemble for the full list with editorial commentary on each.
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.