Will It Vibe?Social Security Number value logged
Part of Documentation, UX & Accessibility, which counts for 15% 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 print/log call includes an SSN-named field. A leaked log file containing SSNs can trigger mandatory breach disclosure regardless of how well the rest of the system is secured.
Why it matters
A Social Security Number is one of the most sensitive fields a US-facing application can hold, since it enables direct identity theft and is protected under state data-breach notification laws. Writing it to logs moves it into a system that usually has weaker access controls, longer retention, and more people with read access than the database column it came from. A single leaked log file containing SSNs can trigger mandatory breach disclosure regardless of how the rest of the system is secured.
How to fix it
Remove the SSN from the log call entirely, or replace it with a masked form showing only the last four digits if that is genuinely needed for support workflows. Never log the full number. Add SSN-named fields to your logging library's redaction list so this cannot be reintroduced by a future change.
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