← Back to home
Comparison · Analytics

epiflows vs treespace

A side-by-side editorial comparison of epiflows and treespace — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:epidemiology

epiflows vs treespace: at a glance

Featureepiflowstreespace
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr, epidemiology, dormant, maintenancephylogenetics, transmission-trees, cran-compliance, maintenance-mode
Last editorial update2h ago49m ago
WebsiteVisit →Visit →

What is epiflows?

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.

Read the full epiflows trajectory →

What is treespace?

treespace ships once every year or two, and only when CRAN or a user forces it.

treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.

Read the full treespace trajectory →

epiflows vs treespace: editorial side-by-side

E
epiflows
ANALYTICS
0.0

epiflows has shipped four releases in eight years, none of which changed the code.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

T
treespace
ANALYTICS
0.0

treespace ships once every year or two, and only when CRAN or a user forces it.

◆ Current state

treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.

◆ Where it's heading

The package is stable and lightly staffed rather than abandoned — bugs that affect correctness do get fixed, and CRAN deadlines are met. But the 2023 update is the telling one: rather than vendor or replace adephylo when it faced removal, the maintainers disabled two tree-vector methods and marked the loss as hopefully temporary. Two years on, nothing in the feed indicates they came back.

◆ Prediction

The next entry will most likely be another CRAN-compliance patch, on the pattern of four of the last five releases. Whether the Abouheif and sumDD methods ever return is not something these entries give any signal on.

Alternatives to epiflows and treespace

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 treespace.

See all epiflows alternatives → · See all treespace alternatives →

Recent activity from epiflows and treespace

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agoepiflowsDeprecated ggplot2 and tibble calls replaced
  2. 11mo agotreespacetreespace patches Rd cross-references for CRAN
  3. 2y agotreespacetreespace disables Abouheif and sumDD as adephylo exits CRAN
  4. 3y agotreespacetreespace fixes vignette build on NA tree names
  5. 3y agoepiflowsRoxygen patch for CRAN checks
  6. 5y agotreespacetreespace fixes dist indexing that broke its tests
  7. 5y agotreespacetreespace corrects tip label handling in transmission distances
  8. 7y agoepiflowsFirst Zenodo archival tag
  9. 8y agoepiflowsFirst CRAN release

Frequently asked questions

What is the difference between epiflows and treespace?

Both compete on the same themes — epidemiology — within Analytics. epiflows and treespace 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.

Is epiflows better than treespace?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epiflows and treespace 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.

What are the best alternatives to epiflows?

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.

What are the best alternatives to treespace?

Top treespace alternatives in Analytics are ranked by recent ship velocity. Browse the "treespace alternatives" section above for the current picks, or visit /alternatives/treespace-r for the full list with editorial commentary on each.