churon
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
A side-by-side editorial comparison of ecodive and rfm — release velocity, themes, recent moves, and the top alternatives to consider.
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.
A customer segmentation package that went quiet for six years and returned with dependency hygiene
rfm computes recency, frequency and monetary segmentation for customer analytics in R. The feature surface was set early: 0.1.0 shipped a Shiny app and customer-level input, 0.2.0 added default segments and median statistics, 0.2.1 added user-specified score thresholds and returnable plot objects. Then nothing for nearly six years. Version 0.4.0 in April 2026 fixes a missing-column error and a customer id fault, and moves plotly and gganimate from Suggests to Imports.
ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.
This is a package that made its breaking changes deliberately and in a cluster. After 2.0.0 reoriented input and removed the weighted parameter, 2.1.0 superseded rescale with norm, and 2.2.6 changed norm's default from percent to none and removed it from some beta functions entirely. That last one matters more than it reads: normalisation defaults silently change the numbers a metric returns, and the direction is toward making the user state their choice rather than inheriting one.
With the metric surface broad and the normalisation interface now explicit, expect the next releases to stabilise — documentation and edge-case handling around CLR and rarefaction rather than another interface break.
rfm computes recency, frequency and monetary segmentation for customer analytics in R. The feature surface was set early: 0.1.0 shipped a Shiny app and customer-level input, 0.2.0 added default segments and median statistics, 0.2.1 added user-specified score thresholds and returnable plot objects. Then nothing for nearly six years. Version 0.4.0 in April 2026 fixes a missing-column error and a customer id fault, and moves plotly and gganimate from Suggests to Imports.
The 0.4.0 release says more about maintenance posture than about product direction — the version jump past 0.3.x with only two bug fixes and a dependency reshuffle suggests a package being brought back to a releasable state rather than resuming development. Promoting plotly and gganimate to Imports makes the visualization stack mandatory, which is a heavier install in exchange for a simpler code path. The core RFM computation itself has not changed in this window.
The entries show a package returning from dormancy rather than pursuing a roadmap, so further small fixes are more likely than new segmentation capability.
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 ecodive or rfm.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
rainette rebuilt its Reinert clustering in 0.2.0, tuned it in 0.3.0, and has coasted since.
questionr's survey helpers are finished; recent releases only keep pace with R-devel.
washdata is a fixed survey dataset; eight years of releases have changed only its packaging.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. ecodive and rfm 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. ecodive and rfm 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 ecodive alternatives in Analytics are ranked by recent ship velocity. Browse the "ecodive alternatives" section above for the current picks, or visit /alternatives/ecodive for the full list with editorial commentary on each.
Top rfm alternatives in Analytics are ranked by recent ship velocity. Browse the "rfm alternatives" section above for the current picks, or visit /alternatives/rfm for the full list with editorial commentary on each.