Scenario
Your CI pipeline flagged a HIGH severity finding in a pull request. The developer who wrote the code is unfamiliar with the vulnerability class. You need to understand it, fix it, and ship it — fast.Step 1: Find out what’s flagged
Step 2: Get the AI explanation
Step 3: Verify the finding
The confidence is 62% — this might be a false positive. Check the file:requireAuth middleware. Confirm:
Step 4: Generate an AI fix
userId matches the
authenticated user? IDOR (Insecure Direct Object Reference) is
common here — fetching billing for any userId when the caller can
only see their own is also a vulnerability.
Step 6: Rescan to confirm
After merging:Time invested
| Step | Time |
|---|---|
zenveil list | 5 seconds |
zenveil explain | 30 seconds |
| Manual verification | 2 minutes |
zenveil fix | 45 seconds |
| Apply fix + test + PR | 10 minutes |
| Total | ~13 minutes |