RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of dbt Core and scoringutils — release velocity, themes, recent moves, and the top alternatives to consider.
dbt-core spent a day backporting one deprecation warning across eight EOL branches — the message is: upgrade.
dbt-core maintains an unusually wide set of live branches, and on August 14 it cut releases for 1.1 through 1.8 in a single day. Every one of them carries the same single feature: a warning when the user is running a deprecated dbt version. The older branches picked up a few long-standing backports alongside it — semver comparison, JSON log formatting, seeds from stored manifest data — and 1.4 through 1.6 dropped Python 3.8 testing now that it is end of life.
scoringutils pushes forecast scoring past univariate outcomes into multivariate and ordinal ones.
scoringutils evaluates probabilistic forecasts in R. Since the 2.0.0 rewrite it is organised around typed forecast objects — quantile, sample, binary, point, nominal — built by as_forecast_<type>() constructors and scored through S3 methods. Version 2.2.0 adds multivariate sample and point types with the variogram score, and 2.1.0 added ordinal forecasts.
dbt-core maintains an unusually wide set of live branches, and on August 14 it cut releases for 1.1 through 1.8 in a single day. Every one of them carries the same single feature: a warning when the user is running a deprecated dbt version. The older branches picked up a few long-standing backports alongside it — semver comparison, JSON log formatting, seeds from stored manifest data — and 1.4 through 1.6 dropped Python 3.8 testing now that it is end of life.
This is a coordinated deprecation campaign rather than product work. Shipping the same warning to every ancient branch at once is how a maintainer starts reclaiming a support surface, and the parallel removal of Python 3.8 support points the same way. The actual development is happening on 1.11 and 1.12, where recent releases sync JSON schemas from dbt-fusion and fix adapter config recognition — the branch where the Fusion engine transition is visible.
Expect formal end-of-life announcements for the branches that just received the warning, and continued dbt-fusion schema convergence on 1.12. The backport waves should thin out once the deprecated branches are formally retired.
scoringutils evaluates probabilistic forecasts in R. Since the 2.0.0 rewrite it is organised around typed forecast objects — quantile, sample, binary, point, nominal — built by as_forecast_<type>() constructors and scored through S3 methods. Version 2.2.0 adds multivariate sample and point types with the variogram score, and 2.1.0 added ordinal forecasts.
The forecast-type system introduced in 2.0.0 is the engine of everything since: each release fits another outcome shape into it rather than reworking the scoring interface. Multivariate support is the largest of those additions because it scores the dependence structure between variables, not just marginal accuracy. Type and constructor names are still being reconciled — forecast_sample_multivariate was renamed to forecast_multivariate_sample with a deprecation window.
Expect further forecast types and metrics slotted into the same constructor pattern, and the deprecated forecast_sample_multivariate alias and is_forecast_sample_multivariate() to be removed once that window closes.
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 dbt Core or scoringutils.
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 dbt Core alternatives → · See all scoringutils alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.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.
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
Top scoringutils alternatives in Analytics are ranked by recent ship velocity. Browse the "scoringutils alternatives" section above for the current picks, or visit /alternatives/scoringutils for the full list with editorial commentary on each.