Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of rmediation and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
RMediation shipped a three-normal CDF, then found it was silently wrong.
RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.
The package is moving from a hand-rolled numerical layer to one that checks itself: the new default integrator escalates its node count until successive rules agree, warns when it hits the cap instead of returning a number, and exposes a diagnostics argument for the convergence estimate. The correctness fix went to dev ahead of the CRAN window rather than being held for it, which suggests wrong-answer bugs are treated as release-blocking regardless of cadence. Serial mediation is where the new surface area is concentrated.
1.7.0 exists specifically to land before CRAN's 2026-08-21 update window, so the next move is a CRAN submission promoting it to main; whether hcubature survives past that as a cross-check option is the open question.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
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 rmediation or TimescaleDB.
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
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all rmediation alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top rmediation alternatives in Analytics are ranked by recent ship velocity. Browse the "rmediation alternatives" section above for the current picks, or visit /alternatives/rmediation for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.