arulesViz
arulesViz finished its move to ggplot2 and has been coasting on maintenance since.
A side-by-side editorial comparison of epiflows and paletteer — 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.
A palette aggregator that grows by absorbing other packages, not by changing shape
paletteer collects colour palettes from across the R ecosystem behind one consistent interface, so users can reference any of them by a single name rather than installing each source package. Its function surface has been essentially fixed for years; what changes each release is the catalogue. Version 1.7.0 pulls in palettes from ButterflyColors, feathers, ggsci, khroma, PrettyCols, tayloRswift, blueycolors, amerika, Rdune and poisonfrogs, and tightens argument checking.
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.
paletteer collects colour palettes from across the R ecosystem behind one consistent interface, so users can reference any of them by a single name rather than installing each source package. Its function surface has been essentially fixed for years; what changes each release is the catalogue. Version 1.7.0 pulls in palettes from ButterflyColors, feathers, ggsci, khroma, PrettyCols, tayloRswift, blueycolors, amerika, Rdune and poisonfrogs, and tightens argument checking.
This is a catalogue, and catalogues grow by ingestion. Every substantive release since 1.3.0 is a list of source packages absorbed, in batches of tens to low hundreds of palettes, with occasional maintenance on the metadata tables that describe them. Release cadence follows contributor pull requests rather than any internal roadmap — roughly one release every one to two years, each bundling whatever accumulated.
Expect the same: another release when enough new source packages have been proposed, likely paired with further work on palettes_c_names and palettes_d_names, the only part of the package that has been iterated on for its own sake.
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 paletteer.
arulesViz finished its move to ggplot2 and has been coasting on maintenance since.
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.
See all epiflows alternatives → · See all paletteer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. epiflows and paletteer 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 paletteer 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 paletteer alternatives in Analytics are ranked by recent ship velocity. Browse the "paletteer alternatives" section above for the current picks, or visit /alternatives/paletteer-r for the full list with editorial commentary on each.