SecretGuardIt's way too easy to leave a secret in your code. You paste an API key "just to test it," an AI assistant inlines a real-looking token, or a password slips into a config file. The trouble is that once a secret is committed, it's already compromised — deleting it later doesn't help, because it lives on in your git history. SecretGuard watches for hardcoded secrets while you work and flags them before they ever reach a commit. It scans when you open a file and every time you save. What it catchesKnown credentials (flagged as errors): AWS keys, GitHub and GitLab tokens, OpenAI and Anthropic API keys, Stripe keys, Google API keys and OAuth secrets, Slack tokens and webhooks, SendGrid, Twilio, npm tokens, private key blocks, and JWTs. Anything that looks like a secret (flagged as warnings): any value assigned
to a secret-ish name such as Secret values are always shown truncated (like How to use itThere's nothing to set up. Open any code or config file and SecretGuard scans it
automatically. Findings appear as underlines in the editor and in the Problems
panel ( To scan on demand, open the Command Palette (
Got a false positive?Add a comment containing
Settings
SupportIf SecretGuard saved you from a security breach, consider giving it a ⭐ on GitHub and a review on the VS Code Marketplace! LicenseProprietary — all rights reserved. See LICENSE. |