monitOS
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
A side-by-side editorial comparison of cfrnow and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
A Bayesian real-time CFR estimator that now ships stratified fits and posterior-predictive checks
cfrnow estimates case fatality ratios from line-list data while an outbreak is still running, using a Bayesian mixture-cure survival model registered as an `epidist` model type. Three releases in a month took it from first public release to stratified, partially-pooled fits with posterior-predictive checking. It leans on `distspec` for delay parameterisation, which reached CRAN alongside the 0.2.1 patch.
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.
cfrnow estimates case fatality ratios from line-list data while an outbreak is still running, using a Bayesian mixture-cure survival model registered as an `epidist` model type. Three releases in a month took it from first public release to stratified, partially-pooled fits with posterior-predictive checking. It leans on `distspec` for delay parameterisation, which reached CRAN alongside the 0.2.1 patch.
The arc runs from producing a single corrected CFR number toward supporting a full model-checking workflow. 0.2.0 added the pieces a modeller needs to defend an estimate: replicate line lists replayed through the real-time truncation, an ascertainment-ratio correction for when fatal and non-fatal cases enter the line list at different rates, and per-group CFRs from `brms` formulas. Delay coverage widened from LogNormal and Gamma to Weibull in the same release.
Expect the next release to keep widening covariate and pooling support rather than adding new outcome types, since every 0.2.0 addition extended the existing formula interface instead of replacing it.
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.
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 cfrnow or dbt Core.
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.
filtro moves to S7 and multiplies its feature-scoring methods in a single release.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
See all cfrnow alternatives → · See all dbt Core 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 5.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 5.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 cfrnow alternatives in Analytics are ranked by recent ship velocity. Browse the "cfrnow alternatives" section above for the current picks, or visit /alternatives/cfrnow for the full list with editorial commentary on each.
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.