Will It Vibe?Weak bcrypt cost factor (< 10)
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A bcrypt cost/rounds factor below 10 makes password hashes far cheaper to brute-force. Modern guidance is a cost of at least 10, tuned upward to your hardware.
Why it matters
The bcrypt cost factor sets how much work each hash takes; a cost below 10 makes offline brute-forcing of a stolen password database far cheaper. The factor is exponential, so each increment doubles the effort an attacker must spend. A low cost quietly weakens otherwise-correct password hashing.
How to fix it
Set the bcrypt cost to at least 10, and tune it so a single hash takes roughly 100 to 250 milliseconds on your production hardware (commonly cost 11 to 13 today). Rehash a user password with the higher cost on their next successful login so existing hashes upgrade over time. Revisit the cost periodically as hardware improves.
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