silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of scoringutils and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
scoringutils pushes forecast scoring past univariate outcomes into multivariate and ordinal ones.
scoringutils evaluates probabilistic forecasts in R. Since the 2.0.0 rewrite it is organised around typed forecast objects — quantile, sample, binary, point, nominal — built by as_forecast_<type>() constructors and scored through S3 methods. Version 2.2.0 adds multivariate sample and point types with the variogram score, and 2.1.0 added ordinal forecasts.
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.
scoringutils evaluates probabilistic forecasts in R. Since the 2.0.0 rewrite it is organised around typed forecast objects — quantile, sample, binary, point, nominal — built by as_forecast_<type>() constructors and scored through S3 methods. Version 2.2.0 adds multivariate sample and point types with the variogram score, and 2.1.0 added ordinal forecasts.
The forecast-type system introduced in 2.0.0 is the engine of everything since: each release fits another outcome shape into it rather than reworking the scoring interface. Multivariate support is the largest of those additions because it scores the dependence structure between variables, not just marginal accuracy. Type and constructor names are still being reconciled — forecast_sample_multivariate was renamed to forecast_multivariate_sample with a deprecation window.
Expect further forecast types and metrics slotted into the same constructor pattern, and the deprecated forecast_sample_multivariate alias and is_forecast_sample_multivariate() to be removed once that window closes.
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 scoringutils or TimescaleDB.
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.
OpenCTI spends a release unblocking queues and hardening upserts
See all scoringutils 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 0.0), with 0 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. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 scoringutils alternatives in Analytics are ranked by recent ship velocity. Browse the "scoringutils alternatives" section above for the current picks, or visit /alternatives/scoringutils 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.