EvoPhylo
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
A side-by-side editorial comparison of epiflows and epikit — 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.
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
epikit is a set of small helpers for applied epidemiology in R — age categorisation, date reconstruction from partial records, and related field-data chores, developed in the R4Epis orbit. Version 0.2.0 moved the proportion functions out to epitabulate, improved how find_date_cause(), find_start_date() and find_end_date() handle dates falling outside the period, and added a floor argument to age_categories() so the lowest band reads as under one rather than zero to zero.
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.
epikit is a set of small helpers for applied epidemiology in R — age categorisation, date reconstruction from partial records, and related field-data chores, developed in the R4Epis orbit. Version 0.2.0 moved the proportion functions out to epitabulate, improved how find_date_cause(), find_start_date() and find_end_date() handle dates falling outside the period, and added a floor argument to age_categories() so the lowest band reads as under one rather than zero to zero.
The package is being scoped down rather than built out. The 0.1.3 restructuring and the 0.2.0 handover of proportions to epitabulate are the same move made twice: push functionality into the package where it belongs and keep epikit to the toolkit that field epidemiologists reach for directly. The rest of the history is dependency compatibility work against dplyr and tibble.
With proportions gone and dependencies trimmed, the remaining functions cluster tightly around dates and age bands, so further refinement of the date-reconstruction helpers is more likely than new capability areas.
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 epikit.
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
treespace ships once every year or two, and only when CRAN or a user forces it.
Rpath 1.1.0 learns to read Ecopath's own files, easing migration off the desktop tool.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
See all epiflows alternatives → · See all epikit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — epidemiology — within Analytics. epiflows and epikit 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 epikit 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 epikit alternatives in Analytics are ranked by recent ship velocity. Browse the "epikit alternatives" section above for the current picks, or visit /alternatives/epikit-r for the full list with editorial commentary on each.