Live data loaded
Use it for prioritization
Counts and cards can guide triage, but still validate affected assets, source confidence, vendor guidance, and business impact before disruptive work.
Status
Check API health, feed freshness, D1 storage, and live advisory stream state.
This page helps confirm whether Vuln Signal is serving live data through Cloudflare Pages Functions, persisting snapshots in D1, and which upstream sources are currently represented.
Runtime Overview
Health, storage, and upstream freshness in one operational view
Lookup Tool Shortcuts
Interpretation Guide
What to do when a live-derived page looks empty, stale, or surprising
Demo or cached data
Treat it as orientation
Demo-backed or cached views are useful for checking workflow and layout. They should not become current risk claims without source validation.
Filtered empty
Try broader context
An empty filtered view can mean the filter is narrow, not that risk is absent. Clear filters, use Search, or pivot to Site Map before concluding there is nothing to review.
Unavailable
Check health before action
If the API, news stream, or live-derived campaign view is unavailable, avoid urgent claims based on missing counts. Use Diagnostics and original sources first.
Degraded feed
Treat counts as partial
Degraded upstream sources, parser errors, or missing live endpoints can make queues look lighter than reality. Use Status details as a data-quality signal before reporting totals.
Parser yield
Know what was extracted
Parser yield explains how many structured records were extracted from upstream material. Low yield can mean format changes or quiet sources; it is not proof that no vulnerabilities exist.
Data Transparency
How to interpret live, cached, unavailable, and derived states
If status is degraded: treat live-derived counts as incomplete, check Diagnostics, and rely on saved or manually validated source links before making urgent decisions.
Live Advisory Stream