rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
Comparison · Analytics
epiflows vs treeshap
A side-by-side editorial comparison of epiflows and treeshap — release velocity, themes, recent moves, and the top alternatives to consider.
epiflows vs treeshap: at a glance
What is epiflows?
epiflows has shipped four releases in eight years, none of which changed the code.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
What is treeshap?
treeshap keeps widening its tree-model coverage while the SHAP math stays put.
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
epiflows vs treeshap: editorial side-by-side
epiflows
0.0ANALYTICS
epiflows has shipped four releases in eight years, none of which changed the code.
◆ Current state
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
◆ Where it's heading
The package is being kept installable rather than developed. The one recent release is dependency maintenance contributed from outside, which is the pattern for RECON-era epidemiology packages that have outlived their original project funding. Two separate entries are both labelled version 0.2.1, so even the version history is not a reliable guide to what changed.
◆ Prediction
Any further releases will most likely be more deprecation cleanup to keep the package on CRAN; there is nothing in the record suggesting active development has resumed.
treeshap
0.0ANALYTICS
treeshap keeps widening its tree-model coverage while the SHAP math stays put.
◆ Current state
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
◆ Where it's heading
The direction is breadth of model support rather than new explanation methods: every release since the first CRAN submission adds or repairs a unify() backend. Maintenance is community-driven, with named contributors fixing the framework they personally use. Nothing in these entries points at work on the SHAP algorithms themselves.
◆ Prediction
Expect the next release to add or repair another unify() adapter as a contributor brings their own framework, rather than to change how explanations are computed.
Alternatives to epiflows and treeshap
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 epiflows or treeshap.
epikit
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
mutagen
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
broman
A statistician's personal toolbox, growing one plotting utility at a time
qtl
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all epiflows alternatives → · See all treeshap alternatives →
Recent activity from epiflows and treeshap
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agotreeshapGPBoost support lands; xgboost adapter repaired
- 5mo agoepiflowsDeprecated ggplot2 and tibble calls replaced
- 2y agotreeshapFixes broken lightgbm.unify examples
- 2y agotreeshapMulti-output model explanations added
- 2y agotreeshapFirst CRAN release consolidates the unify() adapters ⚡
- 3y agoepiflowsRoxygen patch for CRAN checks
- 7y agoepiflowsFirst Zenodo archival tag
- 8y agoepiflowsFirst CRAN release
Frequently asked questions
What is the difference between epiflows and treeshap?
They serve adjacent needs but don't currently overlap on shipped themes. epiflows and treeshap 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.
Is epiflows better than treeshap?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epiflows and treeshap 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.
What are the best alternatives to epiflows?
Top epiflows alternatives in Analytics are ranked by recent ship velocity. Browse the "epiflows alternatives" section above for the current picks, or visit /alternatives/epiflows-r for the full list with editorial commentary on each.
What are the best alternatives to treeshap?
Top treeshap alternatives in Analytics are ranked by recent ship velocity. Browse the "treeshap alternatives" section above for the current picks, or visit /alternatives/treeshap for the full list with editorial commentary on each.