Load the safe example. It declares HS256, includes example.test and demo-user claims, fixed 2030 NumericDate values and a deliberately meaningless signature segment. The result must say NOT VERIFIED even though all three segments decode cleanly.

Check numeric precision

The payload includes the integer 900719925474099312345. The pretty JSON output must retain every digit. This fixture catches implementations that parse through JavaScript Number and silently round the claim.

Verification checklist

After inspecting structure, verify the compact token with a maintained JOSE library in the service that receives it. Pin the allowed algorithm; select the trusted key by reviewed policy; validate the signature before trusting claims; then enforce issuer, audience, subject, expiry, not-before, clock tolerance and application-specific requirements. Reject unexpected critical headers and duplicate data before authorization. JWTLens deliberately performs none of these trust decisions.