Second-pass security review for every pull request, before a human opens the diff

Every review surfaces missing JWT verification, missing ownership checks on resource lookups, and the implicit-trust paths that let a request reach data it should not. Findings anchor to a concrete path:line in the diff so the security team reads the failing line, not a generic alert.

We grep every diff for credential-looking strings, then trace the call sites the credential feeds into. Patterns include the obvious (a literal api_key= in a config file) and the subtle (a base64 blob that decodes to a real key). Each finding carries the exact path:line so the rotation task has a starting point.

A second pass that specifically hunts user-controlled input reaching a sink — string concatenation into a SQL query, a shell command, a template renderer, or an LLM prompt. Severity reflects reach: a public-route injection lands critical; an admin-only template injection lands advisory.

Many code reviews skip the deserialize-the-bytes side of the data plane. VeriFlow surfaces the paths where untrusted bytes are decoded into live Python or live JS — the gadgets that turn a YAML payload into server-side code execution.

Every manifest change in the diff is checked against advisory databases the second pass keeps in mind. A dep added without a pin, a CVE landed mid-week, or a maintainer-handoff signal all reach the review — the same review the security team can audit.

Each finding is bucketed into one of two severities: critical (reachable, exploitable, on a public route) or advisory (codepath exists but is gated, or the surface is admin-only). When the upstream pass returns no findings, the top-level severity is none. When the pass is unable to run deterministically, the badge is unavailable — never a fabrication.