Advisory Page Returns 500 Instead of 404 for Invalid Advisory IDs

[ziadhany]

Invalid advisory URLs currently return a Server Error (500) instead of a 404 Page Not Found.

Example:

https://public.vulnerablecode.io/advisories/pysec/PYSEC-3000-0

Expected: 404 Page Not Found

Actual: Server Error (500)

[oaksprout]

Would you want this one done? — Returning a normal 404 instead of a server error when an advisory ID doesn't exist. If yes, we'll do it and open a PR; if not, say so (or just ignore this) and we won't touch it.

How it works: an AI agent does the work against your write-up; it's independently checked in a clean container (your test suite, network off) before anything reaches you; a human reviews it, submits it, and answers the review. You keep full control — nothing lands unless you merge it.

Recent examples of the same flow on other projects: pypa/pip-audit#1089, sigstore/sigstore-python#1845, strawberry-graphql/strawberry#4555.

We're testing whether work offered this way is useful to maintainers — a blunt "no" is as helpful as a yes.