Add whatileaked to Static Analysis & Linters - #105
Open
tomas-sereikis wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds whatileaked, which scans what a coding agent has already written to local disk.
Transcripts (Claude Code, Codex, Cursor) hold credentials that were already sent to a model provider. Instruction and memory files (CLAUDE.md, AGENTS.md) are the sharper case, because the agent re-reads them at the start of every session, so a credential there keeps leaking until someone edits the file. Both are scanned, and
wiperedacts findings in place while keeping the files valid.Detection uses the gitleaks rule set unmodified. It never prints a credential, only a rule name and a one-way fingerprint, so output is safe to paste into an issue. No network request, zero dependencies, MIT.
Sits next to Aguara in this section: Aguara analyses skill and MCP configs before deployment, this one looks at the history the agent left behind afterwards.
Disclosure: I wrote it. We also sell a proxy that redacts credentials before they leave the machine, so the scanner is standalone and dependency-free on purpose, to make it auditable.