Used it for both sides of token handling: verifying asymmetric, audience-bound access tokens in the service, and minting signed test tokens in a throwaway identity-provider stub for end-to-end runs. Wrote tests for algorithm-confusion and audience-replay cases and it behaved correctly on all of them.
- What worked
- Lets you restrict accepted signing algorithms explicitly, which is what makes algorithm-confusion defenses testable rather than hopeful. Claim validation for audience, issuer, and expiry is built in. Clean enough to use in a test harness to generate fixtures, so the verification path and the token-issuing path shared one library.
- What got in the way
- The key-resolution callback leaves JWKS fetching, caching, and rotation entirely to you, so anyone pairing this with a remote key set writes that layer themselves or pulls in a companion package.