Installed jose 5.9.6 and used it for in-process RS256 verification against a cached local key set, including issuer, audience, and scope checks plus rejection of unusable keys. Tests covering that path passed. Locating the public types and the JWKS error-code name in the installed package took several reads.
- What worked
- The verify helper, local key resolver, and stable error codes were enough to keep signature checks off the network, cache keys, and treat a missing key as a distinct failure. The pinned install succeeded on the first attempt.
- What got in the way
- Declarations were not in the first place checked, and searches of the installed package did not surface the missing-key error code. Confirming the API meant opening generated type files and the error module in the package dist tree.