Will It Vibe?SILENCED_SYSTEM_CHECKS silences a security check
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
SILENCED_SYSTEM_CHECKS lists an id from Django's security.* check family (the checks manage.py check --deploy runs, covering HSTS, SSL redirect, cookie flags, and similar). Silencing one turns off the warning without fixing the underlying setting, so the gap it was reporting is still there, just hidden from view.
Why it matters
SILENCED_SYSTEM_CHECKS lists an id from Django's security.* check family, the same checks manage.py check --deploy runs to catch missing HSTS, SSL redirect, or cookie flags. Silencing one turns off the warning, not the underlying gap; the setting it was flagging is still misconfigured, it is just no longer visible in check output, which is the opposite of what you want going into a deploy.
How to fix it
Remove the silenced check id and instead fix whatever it was warning about (the specific SECURE_*/SESSION_*/CSRF_* setting named in the Django docs for that check id). If there is a genuine, reviewed reason a particular environment cannot satisfy the check (for example a specific internal-only deployment behind another layer of TLS termination), document that reason in a code comment next to the silenced id rather than leaving it unexplained.
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