+0
Daily
9,268
stars
462
forks
34
watchers
288
prs
223
issues
23
releases
README
jwt-go A go (or 'golang' for search engine friendliness) implementation of JSON Web Tokens. Starting with v4.0.0 this project adds Go module support, but maintains backward compatibility with older v3.x.y tags and upstream github.com/dgrijalva/jwt-go. See the MIGRATION_GUIDE.md for more information. Version v5.0.0 introduces major improvements to the validation of tokens, but is not entirely backward compatible. After the original author of the library suggested migrating the maintenance of jwt-go, a dedicated team of open source maintainers decided to clone the existing library into this repository. See dgrijalva/jwt-go462 for a detailed discussion on this topic. SECURITY NOTICE: Some older versions of Go have a security issue in the crypto/elliptic. The recommendation is to upgrade to at least 1.15 See issue dgrijalva/jwt-go216 for more detail. SECURITY NOTICE: It's important that you validate the alg presented is what you expect. This library attempts to make it easy to do the right thing by requiring key types to match the expected alg, but you should take the extra step to verify it in your usage. See the examples provided. Supported Go versions Our support of Go versions is aligned with Go's version release policy. So we will support a major version of Go until there are two newer major releases. We no longer support building jwt-go with unsupported Go versions, as these contain security vulnerabilities that will not be fixed. What the heck is a JWT? JWT.io has a great introduction to JSON Web Tokens. In short, it's a signed JSON object that does something useful (for example, authentication). It's commonly used for Bearer tokens in Oauth 2. A token is made of three parts, separated by .'s. The first two parts are JSON objects, that have been base64url encoded. The last part is the signature, encoded the same way. The first part is called the header. It contains the necessary information for verifying the last part, the signature. For example, which encryption method was used for signing and what key was used. The part in the middle is the interesting bit. It's called the Claims and contains the actual stuff you care about. Refer to RFC 7519 for information about reserved keys and the proper way to add your own. What's in the box? This library supports the parsing and verification as well as the generation and signing of JWTs. Current supported signing algorithms are HMAC SHA, RSA, RSA-PSS, and ECDSA, though hooks are present for adding your own. Installation Guidelines 1. To install the jwt package, you first need to have Go installed, then you can use the command below to add jwt-go as a dependency in your Go program. sh go get -u github.com/golang-jwt/jwt/v5 2. Import it in your code: go import "github.com/golang-jwt/jwt/v5" Usage A detailed usage guide, including how to sign and verify tokens can be found on our documentation website. Examples See the project documentation for ex
Top issues
#168Supporting alternative base64/json encoder/decoder9 comments · 2022-02-17#508Support for ML-DSA (FIPS-204) post-quantum signing algorithm8 comments · 2026-05-07#499`5.3.1` now treats malformed signatures as an error in `ParseUnverified`, which does not align with the documented behavior7 comments · 2026-03-13#489IssuedAt claim is not verified when jwt.WithIssuedAt() option is given to Parser6 comments · 2025-12-08#479Does not support JSON Canonicalization Scheme6 comments · 2025-10-14#400Add option to change time precision for creation/parsing tokens.5 comments · 2024-07-23#385Consider validating key length5 comments · 2024-04-05#335Development Roadmap4 comments · 2023-08-14
Discussions
#506Why doesnt the Claims interface doesnt have a method defined to query for jti field as specified in https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.71 comments · 2026-04-27#460Extra features and functionality for next major version, from other RFCs relating to JWT or for exported helper functions2 comments · 2025-08-04#444Will jwt-go version 3.2.2 be getting a patch for CVE-2025-302041 comments · 2025-06-03#439[help] Is WithValidMethods parser option actually used?1 comments · 2025-04-03#436Questions about CVE-2025-302041 comments · 2025-03-26#431Why does the parser pass 'false' as required to the VerifyNotBefore and VerifyIssuedAt?3 comments · 2025-01-16#388Can we generate Token Pair, long-live (refresh) token and expiry token0 comments · 2024-05-11#380How to validate custom claims with _arbitrary_ additional claims?2 comments · 2024-02-26
Latest release
v5.3.1 v5.3.1 2026-01-28What's Changed 🔐 Features Add spellcheck Github action to catch common spelling mistakes by @equalsgibson in https://github.com/golang-jwt/jwt/pull/458 Add WithNotBeforeRequired parser option and add test coverage by @equalsgibson in https://github.com/golang-jwt/jwt/pull/456 Update godoc example func to properly refer to NewWithClaims() by @equalsgibson in https://github.com/golang-jwt/jwt/pull/459 Update github workflows by @mfridman in https://github.com/golang-jwt/jwt/pull/462 Additional test for CustomClaims that validates unmarshalling behaviour by @equalsgibson in https://gi