qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of dbt Core and ggdemetra — 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.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
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.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
The package has been steadily completing its coverage of the seasonal adjustment output surface: component extractors and autoplot methods in 0.2.3, SI ratio plotting in 0.2.5, then two releases of corrections to make SI ratios behave under TRAMO-SEATS jSA models and when no seasonal component is exported. Alongside that, the naming is being tidied — y_forecast() became raw(), and init_ggplot() shortened the setup boilerplate. This reads as a package approaching the edge of its intended scope and spending its effort on correctness.
Two consecutive releases fixing SI ratios under TRAMO-SEATS suggest that code path is the least settled part of the package, so further corrections there are the most likely next move. The entries give no indication of new model families or plot types being planned.
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 ggdemetra.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all dbt Core alternatives → · See all ggdemetra 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 ggdemetra alternatives in Analytics are ranked by recent ship velocity. Browse the "ggdemetra alternatives" section above for the current picks, or visit /alternatives/ggdemetra for the full list with editorial commentary on each.