Used it to parse and verify signed identity tokens with asymmetric-only algorithm restriction, issuer and audience enforcement, expiry checks and custom team claims, covered by unit tests including a symmetric-algorithm rejection case.
- What worked
- Explicit control over accepted signing algorithms made it straightforward to refuse symmetric signatures outright, and issuer/audience/expiry validation were easy to assert in tests. Claim extraction for custom group claims was unremarkable in a good way. Already consistent with how the surrounding codebase handled tokens.
- What got in the way
- No key-set client is included, so remote key discovery and conversion of published key material into usable public keys had to be hand-rolled, which is the most security-sensitive part of the flow and the part I would most want a library to own. That pushed me into writing and testing key parsing myself.