Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of ggstatsplot and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
ggstatsplot produces ggplot2 graphics with statistical test results embedded in the subtitle and caption — comparisons, correlations, contingency tables, histograms. Since the 2019 refactoring that moved all statistical computation into the separate statsExpressions package, its own release notes have been dominated by upstream tracking: adapting to ggplot2, dplyr, purrr and easystats changes. The 1.0.0 release in April 2026 breaks that run with real additions to the contingency-table functions.
Rho's release machinery finally produced a stable build — and it shipped no new product.
Rho is an R IDE that has just moved from an all-prerelease train to a stable 0.4.0, and its public feed remains almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. The releases since then have been distribution work: a signed automatic updater shared across Windows, macOS and Linux, then the stable build that packages it.
ggstatsplot produces ggplot2 graphics with statistical test results embedded in the subtitle and caption — comparisons, correlations, contingency tables, histograms. Since the 2019 refactoring that moved all statistical computation into the separate statsExpressions package, its own release notes have been dominated by upstream tracking: adapting to ggplot2, dplyr, purrr and easystats changes. The 1.0.0 release in April 2026 breaks that run with real additions to the contingency-table functions.
The architecture explains the cadence. With statistics living in statsExpressions, ggstatsplot's own releases are mostly the tax of sitting on top of a fast-moving plotting and tidyverse stack — five of the six most recent entries change nothing a user would notice. When substantive work does arrive it clusters in the plotting layer's coverage of test families, as in 1.0.0's one-sample goodness-of-fit support and pairwise contingency analyses. The maintainer is also visibly deliberate about scope, having removed the normality-curve overlay in 0.12.4 for being unrelated to the analysis in question.
Expect continued parity work across the plot family — features that exist in one function being extended to its siblings, as goodness-of-fit support moved from ggpiestats to ggbarstats — punctuated by maintenance releases tracking ggplot2 and easystats.
Rho is an R IDE that has just moved from an all-prerelease train to a stable 0.4.0, and its public feed remains almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. The releases since then have been distribution work: a signed automatic updater shared across Windows, macOS and Linux, then the stable build that packages it.
The project is building an agentic R IDE but publishing like a regulated release process: signed evidence, checksums bound to exact commits, and limitations named out loud rather than buried. That discipline has now paid off in the only way it could — 0.4.0 stable ships a Windows installer, a notarized macOS disk image and a Linux AppImage that can all update themselves, with failed verification preserving the running version. The feed's long-standing pattern of dev.NN builds with no final has broken; feature work and shipping work were on separate tracks, and the shipping track arrived first.
With distribution solved, the next entry that matters is the first one describing product capability again rather than packaging. The unresolved item these releases name themselves is Windows trust: the installer is still signed with a SignPath Free Trial self-signed certificate that SmartScreen may warn on.
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 ggstatsplot or Rho.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all ggstatsplot alternatives → · See all Rho alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top ggstatsplot alternatives in Analytics are ranked by recent ship velocity. Browse the "ggstatsplot alternatives" section above for the current picks, or visit /alternatives/ggstatsplot for the full list with editorial commentary on each.
Top Rho alternatives in Analytics are ranked by recent ship velocity. Browse the "Rho alternatives" section above for the current picks, or visit /alternatives/yulab-smu-rho for the full list with editorial commentary on each.