Will It Vibe?AWS secret access key
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 value assigned to aws_secret_access_key matches the AWS 40-character secret format. This is the half that actually authenticates requests.
Why it matters
The AWS secret access key is the half that actually signs requests, so a committed 40-character secret is a working credential. Combined with the access key ID it gives full programmatic access at the scope of the associated user. It stays in git history after you edit the line.
How to fix it
Read the secret from the environment or an IAM role instead of embedding it. Keep the real value in an untracked credentials file or your host secret store, and put a placeholder in .env.example. Deactivate and delete the exposed key pair in IAM afterward.
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