Will It Vibe?PEM private key block
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 25 points from that category, once per scan, no matter how many places it turns up.
What it detects
A PEM private key header (RSA/EC/DSA/PKCS8) was found in a committed file. Whoever has the key can impersonate the server or decrypt its traffic.
Why it matters
A committed PEM private key lets anyone with the repo impersonate the server, decrypt its TLS traffic, or sign as the key owner. Private keys rarely expire on their own, so an old leak stays exploitable for years. Git history keeps the key even after you delete the file.
How to fix it
Remove the key material from source and load it at runtime from a secret manager or a mounted path outside the repo. Treat the exposed key as compromised: regenerate it and redeploy the matching certificate or public key. Add key file patterns to .gitignore.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo