dowhy
DoWhy adds one estimation method a year and keeps its identification edge.
A side-by-side editorial comparison of OpenCTI and StatsBase.jl — release velocity, themes, recent moves, and the top alternatives to consider.
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
The centre of gravity is moving from OpenCTI as a self-contained platform to OpenCTI as a client of Filigran's wider ecosystem — connectors sourced from a catalog with support tiers, custom views deployed from XTM Hub, an MCP server exposed through XTM One. The workflow engine is maturing in parallel, picking up draft approval, transition restrictions and full reset. Telemetry coverage expanded significantly in the same period, which is what makes the catalog's adoption measurable.
Expect more of the platform's configuration surface — dashboards, playbooks, mappers — to become distributable through XTM Hub the way custom views and connectors already are. The workflow approval features suggest governance controls are the next area to fill in.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
This is the shape of a foundational Julia package that has reached its intended scope: the API is settled, and maintenance means keeping compat bounds current and closing long-tail correctness issues raised by users. Nothing in the feed suggests new statistical capability is being staged. The most likely reason is that new work now lands in the downstream packages that build on StatsBase rather than in StatsBase itself.
Expect more 0.34.x patches on the same rhythm — CompatHelper bumps and occasional user-reported edge-case fixes — with no signal in these entries that a 0.35 or 1.0 is being prepared.
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 OpenCTI or StatsBase.jl.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
Iris ships steadily on a two-a-year cadence, but its feed publishes only pointers.
Shiny made reactive apps observable, then gave them a way to tear themselves down
See all OpenCTI alternatives → · See all StatsBase.jl alternatives →
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 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. OpenCTI 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 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.
Top StatsBase.jl alternatives in Analytics are ranked by recent ship velocity. Browse the "StatsBase.jl alternatives" section above for the current picks, or visit /alternatives/statsbase-jl for the full list with editorial commentary on each.