devto 2026-06-23 원문 보기 ↗
We've all done it: pasted an API key into a file "just to test," then a week later
it's in your git history, a screenshot, or a livestream. Most secret scanners —
gitleaks, trufflehog — run in CI, after the secret is already committed.
So I built Secret Guardian, a VS Code extension that catches secrets live, in
the editor, the moment they appear — and visually masks them so they never show
up in screenshots or screen-shares.
👉 Secret Guardian on the VS Code Marketplace (free)
Two layers: tight regexes for known formats (e.g. AKIA…, ghp_…), and an
entropy + context check for unknown secrets (high Shannon entropy assigned to a
secret-like name), with placeholders like your_api_key filtered out.
Install from the Marketplace,
open a file, paste a fake key. I'd love feedback on accuracy and false positives.