Will It Vibe?CREATE/ALTER USER with a plaintext password literal
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 15 points from that category, once per scan, no matter how many places it turns up.
What it detects
A CREATE USER/ALTER USER/CREATE ROLE statement sets a password to a literal string instead of a bind parameter or a pre-hashed value, so the working credential lives in source control for anyone with repo access.
Why it matters
A password written as a literal string in CREATE USER/ALTER USER/CREATE ROLE lives in source control exactly like any other committed secret: every clone, every CI log, and everyone with repository access has it, and it stays valid until someone remembers to rotate it. These statements are frequently copied from a local setup script into a real migration without ever being replaced with a placeholder.
How to fix it
Replace the literal with an environment-variable substitution your migration tool supports, or generate/rotate the password out of band and store only a pre-hashed value the database accepts directly. Add the variable name to a tracked .env.example with a placeholder, and rotate any credential that was already committed.
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