Customer statement totals
All clear
No verified vulnerabilities and code craft 298/300.
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.
- 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.reports:statement_totalsStart with the changed symbol.
What it found
{ "id": "app.services.reports:statement_totals", "kind": "function", "file": "app/services/reports.py", "lines": [ 9, 20 ], "params": [ "customer_id" ], "entry_point": false, "route": null, "depends_on": [], "untrusted_inputs": [], "dangerous_calls": [], "has_docstring": true } callers: (none) callees: app.services.billing:BillingService (app/services/billing.py:8-39) via line 16 app.services.billing:BillingService.invoices_for_customer (app/services/billing.py:16-22) via line 16 [tainted args]