Find secrets your code leaves behind in memory.
Identifies missing or compiler-weakened wiping of sensitive data and produces an evidence-backed security report.
When to use it
Use when auditing cryptographic code, authentication systems, or other security-critical code that handles sensitive data.
Give it a codebase to audit for secrets left in memory; it returns the final report in the conversation.
What you provide
C/C++ audits require clang on PATH; preflight fails without it because IR and assembly analysis are unavailable.
Rust audits require cargo with the nightly toolchain for MIR and LLVM IR emission.
The Python analysis tools declare Python 3.11 or newer.
Rust audits require uv on PATH to run the Python analysis scripts.
No additional actions listed.