Primary contracts
Reviewed 2026-10-25. These support limited local review and verification; they do not authorize account/provider operations or certify a deployment.
- RFC 7519 defines JWT claims and NumericDate semantics. The supported local profile requires expiration and explicit expected issuer/audience; other applications may use other profiles.
- RFC 8725 addresses algorithm, cryptographic-input and claim verification. Received headers never select this tool's trusted key or allowed algorithm. Inspection does not authenticate.
- PyJWT API and security changelog document the maintained verification boundary. The tested pin is 2.15.1; verification rejects older/unsupported major versions instead of silently trusting them. Cryptography 50.0.2 is the pinned optional asymmetric backend.
- OAuth security BCP, RFC 9700 distinguishes client roles and PKCE requirements. The configuration helper reviews declared public/shared-secret-confidential HTTPS web clients and S256 PKCE; it does not test registration, redirect matching or flow binding.
- NIST SP 800-63B-4 distinguishes single-factor and MFA password length, discourages mandatory composition and arbitrary periodic changes, and requires comparison of entire candidate values against a blocklist. Local checks use declared context and exact supplied values; they do not prove MFA, blocklist adequacy or deployed enforcement.
- OWASP Password Storage provides KDF review profiles. The helper supports the listed Argon2id memory/time combinations with p=1, PBKDF2-HMAC-SHA256/SHA512 and a limited legacy bcrypt review. It does not execute hashing, validate FIPS modules or infer salt/key entropy. Unsupported variants/parameters remain review items.
- OWASP Authentication and Session Management support the broader manual review. Record the actual framework/context and independent evidence before mapping a control; these references are not bundled automated application scanners.