Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of igoR and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
igoR reached 1.0.0 with no user-visible change, then spent three releases on AI-assisted cleanup
igoR provides access to Intergovernmental Organizations (IGO) databases from the Correlates of War project. The dataset and public API have been stable for years; recent releases are almost entirely maintenance. 1.0.0 in January 2026 raised the minimum R version to 3.6.0 and stated explicitly that users would see no change.
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.
igoR provides access to Intergovernmental Organizations (IGO) databases from the Correlates of War project. The dataset and public API have been stable for years; recent releases are almost entirely maintenance. 1.0.0 in January 2026 raised the minimum R version to 3.6.0 and stated explicitly that users would see no change.
Development has shifted to documentation and internal consistency, and the mechanism is notable: 1.0.2 and 1.0.3 both describe AI-assisted editing and refactoring, part of a sweep the same maintainer ran across several packages in mid-2026. The one substantive fix in the window is igo_dyadic() computing dyadid from both state codes as documented. Everything else is dependency bumps and message wording.
With the internals refactored and documentation reviewed, further releases are likely to track upstream Correlates of War data updates rather than change the API. The entries give no indication of a pending data revision.
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 igoR or OpenCTI.
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 igoR alternatives → · See all OpenCTI 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 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 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 igoR alternatives in Analytics are ranked by recent ship velocity. Browse the "igoR alternatives" section above for the current picks, or visit /alternatives/igor 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.