Will It Vibe?AUTH_PASSWORD_VALIDATORS is empty
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
AUTH_PASSWORD_VALIDATORS is set to an empty list, which turns off all of Django's built-in password-strength checks (minimum length, similarity to user attributes, common-password list, all-numeric rejection). Accounts can then be created with trivially guessable passwords.
Why it matters
AUTH_PASSWORD_VALIDATORS = [] turns off every one of the password-strength checks Django ships with by default: minimum length, similarity to the username/email, membership in a list of the most common leaked passwords, and rejecting all-numeric passwords. Users can then set "12345678" or their own username as a password, which is the first thing a credential-stuffing or brute-force attempt will try.
How to fix it
Restore the default validator list (or a project-specific superset of it): UserAttributeSimilarityValidator, MinimumLengthValidator, CommonPasswordValidator, and NumericPasswordValidator, exactly as Django's startproject template configures them. Tighten MinimumLengthValidator's min_length if the project wants a higher bar than Django's default of 8.
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