A JWT is decoded or signed with the none algorithm.
Why AI tools produce this: AI coding tools generate this anti-pattern by default, it appears in a large share of AI-written auth code.
Why this matters
The none algorithm means the token is NOT cryptographically signed, so any attacker can forge a token with arbitrary claims and have it accepted, a complete authentication bypass (CVE-class JWT alg=none vulnerability).
Never allow none. Pin a strong signing algorithm explicitly: jwt.decode(token, key, algorithms=["RS256"]) for verification, or jwt.encode(claims, key, algorithm="RS256") (also ES256 / HS256) when issuing tokens. Never include "none" in the algorithms allowlist.
Suppressing this rule
If a finding is a genuine false positive, scope the suppression to the exact line and leave a reason, never disable the rule project-wide. Disable directives are line-scoped by design.
# oauthlint-disable-next-line auth.py.jwt.alg-none -- <reason>