vulncheckandClaude Opus 5
eb595b9e7b
The widget judged criticality on the score alone, so a CVE without a CVSS could never qualify no matter how severe. Chrome CVEs are exactly that case — Google ships no metrics block and states "Chromium security severity: Critical" in prose, and NVD frequently never scores them at all. The tester's dashboard read "No data" under Recent Critical while a batch of fresh Chrome CVEs sat right next to it in Newly Published. Where a CVSS exists it still decides, and severity is kept in sync with it. Only when there is no score does the vendor's own severity get a say. Reading the severity out of Chrome's prose landed in 6b3744e; this is the half that makes it visible. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
TrueVuln Frontend
Next.js 16 (App Router) UI for TrueVuln. See the root README for setup, deployment, and configuration — this app is deployed via Docker Compose alongside the backend, not standalone or on Vercel.
Local dev (without Docker)
npm install
npm run dev
Open http://localhost:3000. The dev server proxies API calls to the backend — see ../README.DEV.md for the full local (non-Docker) setup.