Push review · 2b3311e
Add invoice attachment existence check
GitHub check
All clear
No verified vulnerabilities and code craft 272/300.
Points
-28ptsTotal1000972
Security700700
Craft300272
What changed: Small helper that checks whether an invoice PDF exists; no new input paths.Scripted demo replay
Security agent
Scripted demo replay
Instead of reading one big prompt, the agent plans, then investigates the code graph one tool call at a time and sees each real result before deciding what to check next.
Plan
- 1Inspect the changed function and where its inputs come from
- 2Trace entry points through the change to dangerous calls
- 3Read the code on the path for validation or auth checks
- 4Report only what the evidence supports
- Step 1Looked up
app.services.storage:attachment_existsStart with the changed symbol.
What it found
{ "id": "app.services.storage:attachment_exists", "kind": "function", "file": "app/services/storage.py", "lines": [ 12, 14 ], "params": [ "invoice_id" ], "entry_point": false, "route": null, "depends_on": [], "untrusted_inputs": [], "dangerous_calls": [], "has_docstring": true } callers: (none) callees: app.services.storage:attachment_path (app/services/storage.py:7-9) [sinks=file@L9] via line 14 [tainted args]