The problem
A deleted file may still exist in Git history. Checking only the current code is not enough before publication.
The approach
Did I Leak? checks the current working tree and reachable history locally. It integrates Gitleaks and TruffleHog when available. The report redacts discovered values and distinguishes between GO, GO WITH REVIEW and NO-GO.
When it helps
Before publishing a repository, sharing source code or as part of an agent workflow. Python and Git are required. An additional agent skill helps interpret the results.
Limitations
Missing scanners remain visible in the report. The tool does not change credentials, Git history or visibility. A result is not a security certification. The preview is a generated explainer, not a scan of this website.