A dormant MRI tissue-classification package revived under a new maintainer.
DHARMa alternatives
The best DHARMa alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 16, 2026
Looking for the best alternatives to DHARMa? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, DHARMa shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About DHARMa
DHARMa changed how GLMM residuals are simulated, so the same code now returns different numbers.
DHARMa generates scaled quantile residuals for fitted GLMMs and runs the dispersion, uniformity, and autocorrelation tests built on them. Version 0.5.0 changed the default simulation for hierarchical models from the model's own default, mostly unconditional, to conditional simulation, and states plainly that residuals will differ from those computed by older versions. The same release added brms to the supported model set and reworked how predictors are passed to plotting and testing functions.
Velocity 0.0 · Last update 30m ago
Top 12 alternatives to DHARMa
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
A moderation-analysis package now pointing users at its own siblings for the harder work.
New R package downscaling coarse climate rasters onto fine terrain, now five times cheaper per call.
A structural-equation model comparison package whose feed carries links, not release notes.
R became a deployable MCP server, not just a local one.
Forecast-hub scoring that learned to handle joint, sample-based predictions.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A research-project workflow package where the interesting work is in the plumbing.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
DHARMa vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| DHARMa (baseline) | 0.0 | 0 | residual-diagnosticsglmmbreaking-change | Conditional simulation becomes the GLMM default, changing residuals |
| mritc | 5.0 | 0 | medical-imagingr-packagemaintainer-change | — |
| stdmod | 2.5 | 0 | moderation-analysisregressionstatistics | — |
| topocast | 2.5 | 0 | geospatialclimate-datadownscaling | — |
| modelbpp | 2.5 | 0 | structural-equation-modelingstatisticsr-package | — |
| mcptools | 2.5 | 0 | mcpllm-toolingr-package | mcptools runs as a Posit Connect R API engine |
| hubEvals | 2.5 | 0 | forecast-evaluationscoringepidemiology | Sample output types and multivariate compound scoring |
| compositional.mle | 0.0 | 0 | maximum-likelihoodoptimizationfunctional-api | Solvers become composable values, and the package is renamed |
| nabla | 0.0 | 0 | automatic-differentiationdual-numberspure-r | Arbitrary-order exact derivatives arrive; compiled code removed |
| snowflakeauth | 0.0 | 0 | authenticationsnowflakeoidc | — |
| kwb.geosalz | 0.0 | 0 | groundwaterresearch-workflowreproducibility | — |
| cyclocomp | 0.0 | 0 | static-analysiscode-complexitylinting | — |
| revdbayes | 0.0 | 0 | extreme-value-theorybayesianrcpp | — |
The 12 best DHARMa alternatives, in depth
1. mritc · velocity 5.0
A dormant MRI tissue-classification package revived under a new maintainer.
Its velocity score of 5.0/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, mritc focuses on medical imaging, r package and maintainer change.
mritc and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. stdmod · velocity 2.5
A moderation-analysis package now pointing users at its own siblings for the harder work.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, stdmod focuses on moderation analysis, regression and statistics.
stdmod and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. topocast · velocity 2.5
New R package downscaling coarse climate rasters onto fine terrain, now five times cheaper per call.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, topocast focuses on geospatial, climate data and downscaling.
topocast and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. modelbpp · velocity 2.5
A structural-equation model comparison package whose feed carries links, not release notes.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, modelbpp focuses on structural equation modeling, statistics and r package.
modelbpp and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. mcptools · velocity 2.5
R became a deployable MCP server, not just a local one.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “mcptools runs as a Posit Connect R API engine”.
Where DHARMa leans on residual diagnostics, glmm and breaking change, mcptools focuses on mcp, llm tooling and r package.
mcptools and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. hubEvals · velocity 2.5
Forecast-hub scoring that learned to handle joint, sample-based predictions.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Sample output types and multivariate compound scoring”.
Where DHARMa leans on residual diagnostics, glmm and breaking change, hubEvals focuses on forecast evaluation, scoring and epidemiology.
hubEvals and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. compositional.mle · velocity 0.0
An MLE package rebuilt around composable solvers, then renamed to match.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Solvers become composable values, and the package is renamed”.
Where DHARMa leans on residual diagnostics, glmm and breaking change, compositional.mle focuses on maximum likelihood, optimization and functional api.
compositional.mle and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full compositional.mle trajectory → · Compare DHARMa vs compositional.mle →
8. nabla · velocity 0.0
Nabla dropped its C++ engine to chase exact derivatives at any order.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Arbitrary-order exact derivatives arrive; compiled code removed”.
Where DHARMa leans on residual diagnostics, glmm and breaking change, nabla focuses on automatic differentiation, dual numbers and pure r.
nabla and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. snowflakeauth · velocity 0.0
Eight months from first release to keyring caching and workload identity.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, snowflakeauth focuses on authentication, snowflake and oidc.
snowflakeauth and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full snowflakeauth trajectory → · Compare DHARMa vs snowflakeauth →
10. kwb.geosalz · velocity 0.0
A research-project workflow package where the interesting work is in the plumbing.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, kwb.geosalz focuses on groundwater, research workflow and reproducibility.
kwb.geosalz and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full kwb.geosalz trajectory → · Compare DHARMa vs kwb.geosalz →
11. cyclocomp · velocity 0.0
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, cyclocomp focuses on static analysis, code complexity and linting.
cyclocomp and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. revdbayes · velocity 0.0
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where DHARMa leans on residual diagnostics, glmm and breaking change, revdbayes focuses on extreme value theory, bayesian and rcpp.
revdbayes and DHARMa have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to DHARMa?
The top DHARMa alternatives we currently track in analytics tools are mritc, stdmod, topocast, modelbpp, mcptools, ranked by recent ship velocity.
How is this list of DHARMa alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare DHARMa directly with one of these alternatives?
Yes — every card has a "Compare with DHARMa" link to a side-by-side /compare page.