Hardcoded API keys & tokens
A secret key committed directly in source code is visible to everyone with repo access — and to anyone who ever clones it. Even after deletion the key persists in git history and must be rotated immediately.
HOW VIBECHECK DETECTS THIS
vibecheck clones your repository and runs Gitleaks, Semgrep, njsscan, and a suite of custom checks targeting patterns common in AI-generated code. This check is part of the Secrets & Exposure category. When a matching pattern is found, Claude triages the finding and produces a plain-English explanation and a concrete fix — no security expertise required.
FREE SCAN
Check your repo for this and 50+ other issues
Connect GitHub → vibecheck scans for secrets, unauthenticated routes, RLS gaps, injection, and more. Claude explains every finding. Free for 2 repos.
scan my repo for free →