← Back to home
Comparison · Analytics

hubPredEvalsData vs OpenCTI

A side-by-side editorial comparison of hubPredEvalsData and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.

hubPredEvalsData vs OpenCTI: at a glance

FeaturehubPredEvalsDataOpenCTI
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d00
Top themesforecast-evaluation, hubverse, configuration, dashboardsthreat-intelligence, stix, data-model, ingestion
Last editorial update2d ago15h ago
WebsiteVisit →Visit →

What is hubPredEvalsData?

The pipeline turning hub forecasts into dashboard-ready evaluation data.

hubPredEvalsData generates the scored evaluation data that hubverse prediction dashboards read, driven by a predevals-config.yml and scoring through hubEvals underneath. It is the youngest package in this part of the stack and the fastest-moving in configuration terms, having already passed a breaking 1.0.0 and a schema-versioned feature addition. Its output contract is a scores.csv file consumed downstream, which shapes what its releases care about.

Read the full hubPredEvalsData trajectory →

What is OpenCTI?

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.

Read the full OpenCTI trajectory →

hubPredEvalsData vs OpenCTI: editorial side-by-side

H0.0

The pipeline turning hub forecasts into dashboard-ready evaluation data.

◆ Current state

hubPredEvalsData generates the scored evaluation data that hubverse prediction dashboards read, driven by a predevals-config.yml and scoring through hubEvals underneath. It is the youngest package in this part of the stack and the fastest-moving in configuration terms, having already passed a breaking 1.0.0 and a schema-versioned feature addition. Its output contract is a scores.csv file consumed downstream, which shapes what its releases care about.

◆ Where it's heading

Each release widens what the config file can express — round selection, then scale transformations with per-target overrides, then target labelling pulled from the hub's own task metadata. The pattern is consistent: capability that already exists in hubEvals gets a declarative surface here so hub maintainers configure it rather than write code. Recent attention to byte-stable output ordering shows the file is being treated as a reproducible artifact, not just a report.

◆ Prediction

Expect the config schema to keep absorbing hubEvals capabilities as declarative options, with continued attention to making scores.csv reproducible and diffable between runs.

O
OpenCTI
ANALYTICS
6.3

OpenCTI spends a release unblocking queues and hardening upserts

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to hubPredEvalsData and OpenCTI

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 hubPredEvalsData or OpenCTI.

See all hubPredEvalsData alternatives → · See all OpenCTI alternatives →

Recent activity from hubPredEvalsData and OpenCTI

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoOpenCTIMalformed STIX no longer blocks worker queues indefinitely
  2. 4d agoOpenCTILTS branch gets the security backport: access-scoped streams, dependency sweep
  3. 7d agoOpenCTIMass operations can now edit relation start and stop times
  4. 11d agoOpenCTISaved searches and dashboard filters become shareable and reusable
  5. 15d agoOpenCTIData sanity operations can be stopped mid-run
  6. 20d agoOpenCTIIntegrations experience reworked around the new catalog, plus draft approval workflows
  7. 1mo agohubPredEvalsDataTarget names pulled from hub metadata; scores.csv made byte-stable
  8. 2mo agohubPredEvalsDataVersioned target data with an as_of column no longer fails scoring
  9. 2mo agohubPredEvalsDataScale transformations become configurable per target
  10. 4mo agohubPredEvalsDataMulti-round hub support via a required rounds_idx property (breaking)

Frequently asked questions

What is the difference between hubPredEvalsData and OpenCTI?

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.

Is hubPredEvalsData better than OpenCTI?

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.

What are the best alternatives to hubPredEvalsData?

Top hubPredEvalsData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubPredEvalsData alternatives" section above for the current picks, or visit /alternatives/hubpredevalsdata for the full list with editorial commentary on each.

What are the best alternatives to OpenCTI?

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.