silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of loo and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.
OpenCTI spends a release unblocking queues and hardening upserts
7.260817.0 is a fix release. The most consequential item is malformed STIX messages nacking forever and blocking worker queues indefinitely — a stall in the ingestion path rather than a display bug. Alongside it: upsert clearing an existing createdBy when incoming confidence is higher, draft upserts crashing on existing attack patterns, OTP handling in the stream middleware, and case template relation authorization. Score fields were added to threat actor groups, intrusion sets and malware.
loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.
The package is being brought in line with the current PSIS literature rather than extended with new features, and the practical effect is that the numbers practitioners quote in papers keep changing meaning. Work is increasingly delegated to posterior for shared computations, and the project has added contributor process, benchmarks and a published AI contribution policy.
Expect further work on comparison diagnostics — the p_worse and diag_* columns are new enough that their defaults and documentation will likely be revised next.
7.260817.0 is a fix release. The most consequential item is malformed STIX messages nacking forever and blocking worker queues indefinitely — a stall in the ingestion path rather than a display bug. Alongside it: upsert clearing an existing createdBy when incoming confidence is higher, draft upserts crashing on existing attack patterns, OTP handling in the stream middleware, and case template relation authorization. Score fields were added to threat actor groups, intrusion sets and malware.
The platform's feature energy went into the connector catalog and integrations rework in July, and the releases since have been consolidating: mass operations on relation times, shareable saved searches, and now a pass over ingestion robustness. Adding score to more entity types continues the slow enrichment of the data model that runs underneath the feature work.
Given score arriving on three entity types in one release, expect it to keep spreading across the data model, and the queue-blocking class of bug to draw more worker-side hardening.
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 loo or OpenCTI.
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.
Mimir's feed is a weekly Helm bot, with the 3.2 candidate the only real release in months
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 loo alternatives in Analytics are ranked by recent ship velocity. Browse the "loo alternatives" section above for the current picks, or visit /alternatives/loo for the full list with editorial commentary on each.
Top OpenCTI alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenCTI alternatives" section above for the current picks, or visit /alternatives/opencti for the full list with editorial commentary on each.