Agent security testing thread: capture evidence before deleting the dependency graph

krishnan · x · 2026-11-18

Part 6/8 of @krishnan's thread on agent security testing. He proposes a test worth running: pinned dependency trees with known indirect vulnerabilities, including two versions of the same package, compared against an independently checked reference. Require a dependency path and an advisory for every finding, and measure setup time and missed findings.

This builds on part 5/8: deletion is the step to design. Before the graph goes, capture pinned inputs, queries, dependency paths and advisory evidence — the launch post describes a report but not what backs each finding, and deleting the database does not preserve that evidence.

Original post →

More from coding & agent

coding & agent channel →