paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of EvoPhylo and xts — release velocity, themes, recent moves, and the top alternatives to consider.
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
EvoPhylo handles post-processing for Bayesian evolutionary rate and fossilized birth-death analyses, originally against MrBayes output. The 0.3.2 release added BEAST2 support for both FBD functions and rates analysis, making it usable by labs on either platform. Since then there has been one clock-partition fix and, in August 2025, a release whose notes say only that there are updated functions and bug fixes.
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.
EvoPhylo handles post-processing for Bayesian evolutionary rate and fossilized birth-death analyses, originally against MrBayes output. The 0.3.2 release added BEAST2 support for both FBD functions and rates analysis, making it usable by labs on either platform. Since then there has been one clock-partition fix and, in August 2025, a release whose notes say only that there are updated functions and bug fixes.
The package's substantive arc ended with the 0.3.2 publication release, which arrived with peer-review revisions and three first-time contributors — the shape of software built to accompany a paper. What follows is thin: a MrBayes plotting correction in 0.3.3, then a two-year gap and a release with no described contents. The August 2025 entry may contain real work, but the notes give a reader nothing to judge.
Without release notes on the latest version there is no observable basis for predicting the next move; the two-year gap before it suggests activity tied to specific research needs rather than a maintenance cadence.
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 EvoPhylo or xts.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
See all EvoPhylo alternatives → · See all xts alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. EvoPhylo 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. EvoPhylo 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 EvoPhylo alternatives in Analytics are ranked by recent ship velocity. Browse the "EvoPhylo alternatives" section above for the current picks, or visit /alternatives/evophylo 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.