rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of epiflows and xts — release velocity, themes, recent moves, and the top alternatives to consider.
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.
xts is finished software, and its releases now track R's C API more than user requests.
xts is the time-series class underpinning much of R's financial stack, and it behaves like infrastructure: the visible releases are bug fixes, plotting repairs and conformance work. A recurring thread is removing calls R no longer considers public — SET_TYPEOF in 0.14.0 and 0.14.1, then ATTRIB() and SET_ATTRIB() in 0.14.2. Feature additions are rare and small, the last cluster being open-ended time-of-day subsetting and na.fill performance in 0.13.0.
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.
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.
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.
xts is the time-series class underpinning much of R's financial stack, and it behaves like infrastructure: the visible releases are bug fixes, plotting repairs and conformance work. A recurring thread is removing calls R no longer considers public — SET_TYPEOF in 0.14.0 and 0.14.1, then ATTRIB() and SET_ATTRIB() in 0.14.2. Feature additions are rare and small, the last cluster being open-ended time-of-day subsetting and na.fill performance in 0.13.0.
Two forces drive releases. R core keeps narrowing its public C API, and xts keeps rewriting internals to stay inside it; separately, ggplot-era changes elsewhere in the ecosystem surface plotting bugs that get fixed one report at a time. Nearly every entry credits an outside reporter, which is what maintenance of a dependency this widely used looks like.
Further C API conformance work is the safest expectation, since two consecutive releases have each removed a different non-API entry point and R has continued tightening that boundary.
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 xts.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all epiflows alternatives → · See all xts alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r, maintenance — within Analytics. epiflows and xts 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epiflows and xts 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.
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.
Top xts alternatives in Analytics are ranked by recent ship velocity. Browse the "xts alternatives" section above for the current picks, or visit /alternatives/xts-r for the full list with editorial commentary on each.