Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of OpenCTI and simmer.plot — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The plotting companion to simmer, shipping only when the simulator or a graphics dependency moves.
simmer.plot renders discrete-event simulation output — S3 plot() methods over get_mon_arrivals(), get_mon_attributes() and get_mon_resources(), plus trajectory diagrams drawn through DiagrammeR. Since 0.1.12 the methods attach to the monitoring data itself rather than the simulation environment, and 0.1.18 finished that migration by deleting the deprecated environment-level methods.
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.
simmer.plot renders discrete-event simulation output — S3 plot() methods over get_mon_arrivals(), get_mon_attributes() and get_mon_resources(), plus trajectory diagrams drawn through DiagrammeR. Since 0.1.12 the methods attach to the monitoring data itself rather than the simulation environment, and 0.1.18 finished that migration by deleting the deprecated environment-level methods.
This package moves when something it depends on moves. Its history is a sequence of parser fixes for new simmer trajectory formats, DiagrammeR and tidyr and dplyr version bumps, and ggplot2 workarounds. The one clear internal decision — plotting monitor output instead of the environment — was made in 2017 and completed six years later. The 2025 release fixes documentation cross-references and nothing else.
The next release most likely follows a simmer trajectory-format change or a CRAN documentation policy, matching every recent entry. There is no visible feature work in the pipeline.
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 simmer.plot.
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 OpenCTI alternatives → · See all simmer.plot 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 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 simmer.plot alternatives in Analytics are ranked by recent ship velocity. Browse the "simmer.plot alternatives" section above for the current picks, or visit /alternatives/simmer-plot for the full list with editorial commentary on each.