Will It Vibe?JWT signature verification disabled
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
Decoding a JWT with verify_signature=false / verify=False trusts unverified claims, which is equivalent to accepting a forged token.
Why it matters
Decoding a JWT with signature verification turned off (verify_signature=false / verify=False) means the server reads the claims without checking they came from a trusted issuer. An attacker can hand-craft a token with any claims they like. It is equivalent to accepting a forged token.
How to fix it
Always verify the signature: call the verifying decode with the correct key and an explicit algorithms allowlist. If you only need to read a claim before verification (for example to pick a key by kid), read the header without trusting the payload, then verify fully before using any claim. Never make an authorization decision on an unverified token.
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