# Feed scorecard

> How the platform grades the Wahukeza first-party threat feed: corroboration, uniqueness and allowlist collisions over thirty days. Sample values for now.

Source: https://wahukeza.com/scorecard

Resources · Feed scorecard

## The feed, graded by the platform itself.

A daily job measures the first-party feed against the external sources the platform ingests, the exchange’s independent reports and the allowlist, and nobody edits the result. When the public scorecard goes live, this page will show it, on a bad day too. Until then, the figures below are a sample.

sample snapshot · 2026-09-19 · 18,422 indicators measuredsample values · not live data

There is no public scorecard instance yet. Every number and line on this page is an illustrative sample, not a measurement. It will be replaced by the platform’s own figures when the public scorecard endpoint is live.

-   Corroboration
    
    62%sample
    
    Share of mature exchange observables that at least two independent instances reported. Higher means the sensors see real things.
    
-   Uniqueness
    
    37%sample
    
    Share of the feed with no evidence from any OSINT or commercial feed the deployment ingests. Only as meaningful as that deployment’s own feed coverage.
    
-   Allowlist collisions
    
    0.40%sample
    
    Share of the feed that matches the allowlist. Lower is better; this is the poisoning signal.
    

30-day history · samplecorroborationuniquenesscollisions ×50

How it is computed

## Three ratios, one job, no editing.

A daily job snapshots the first-party feed and computes each ratio over the trailing window. Nobody edits the result; once live, this page reads the platform’s own endpoint directly.

-   What counts as first-party
    
    Active indicators evidenced by the platform’s own sensor telemetry or promoted by the collective exchange, never third-party feed content, and never sharing-group deliveries.
    
-   Corroboration
    
    An exchange observable old enough for peers to have seen the same attacker counts as corroborated when at least two distinct, enabled instances reported it. Measured only where an exchange hive runs.
    
-   Uniqueness
    
    An indicator is unique when none of its evidence comes from an OSINT or commercial feed on the deployment. A deployment running few connectors reports a high number that means little, and the scorecard says so.
    
-   Allowlist collisions
    
    Counted when a feed indicator matches an allowlist entry; the exchange keeps a collision counter per contributor and never promotes an allowlisted value.
    

## Pull the feed and check it yourself.

The first-party feed is selectable on every export path. Ask for a feed key, or for the anonymous public tier when a deployment enables it.

[Book a demo](https://wahukeza.com/contact?intent=demo)

[Exchange & feed product](https://wahukeza.com/platform/exchange)