Collection operations
Is collection running?
Backlog enrichment is scheduled hourly, discovery every six hours, and branch checks weekly for the detailed-case watchlist. This page reads recorded results; a configured schedule alone does not establish successful collection.
Loading recorded status…
- Successful backlog enrichment
- Unknown
- Successful scheduled enrichment
- Unknown
- Latest successful discovery search
- Unknown
- Successful weekly branch job
- Unknown
- Watchlist checked within eight days
- Unknown
- Public repositories outside the watchlist
- Unknown
Enabled search rules
| Rule | Interval | Latest result | Last run (UTC) |
|---|
File review queue
Queue totals count distinct repository/path/blob versions, not repositories or infected devices. A partial search can still collect useful candidates while leaving results uncollected.
What remains outside this status
Fresh runs do not establish complete coverage. GitHub indexing and pagination gaps, unsupported task templates and unresolved payloads remain visible in the evidence audits. Weekly checks record branch metadata; they do not automatically recover every force push or re-analyze every payload.
The OSM adapter checks the reviewed watchlist weekly when its API credential is configured and produces a private artifact for a publication PR. See the dated per-repository comparison. On-chain and urlscan adapters remain unconnected. A versioned policy can identify previously reviewed malicious content privately. Public updates remain reviewed snapshots; the private admin provides an automatic-publication eligibility preview. Discord delivery is available when its private webhook is configured. This page does not verify webhook configuration or delivery.
Scheduled-trigger telemetry starts with collector v3. Earlier manual tests cannot populate that field. If the status API is unavailable, freshness cannot be assessed here.
Collection architecture → · Latest search audit → · Private rules and run history → · Status JSON ↓