auth0/node-jsonwebtoken

JsonWebToken implementation for node.js http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 3rd, 2026
Created on July 1st, 2013
Open Issues & Pull Requests: 209 (+0)
GitHub issues: Enabled
Number of forks: 1,286
Total Stargazers: 18,195 (+0)
Total Subscribers: 250 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

node-jsonwebtoken is a JSON Web Token implementation for Node.js that signs and verifies JWTs according to the RFC 7519 specification.

The tool solves the problem of securely creating and validating JSON Web Tokens in Node.js applications. It provides two core operations: signing tokens with a secret or private key using algorithms like HMAC, RSA, and ECDSA, and verifying tokens to ensure their authenticity. The implementation builds on node-jws for the underlying JSON Web Signature functionality. The sign method accepts a payload as an object, buffer, or string, along with a secret or private key, and can operate either synchronously or asynchronously via callback. The tool handles standard JWT claims like expiration time and enforces security constraints such as minimum RSA key sizes.

Developers should adopt this tool if they need straightforward JWT handling in Node.js without building cryptographic signing and verification from scratch. It suits applications requiring stateless authentication, API token management, or OAuth-style token flows. The project maintains migration guides between major versions, indicating attention to breaking changes across releases.

The project attracts substantial real-world usage, with nearly all open issues originating from external users rather than the core team. Responses to issues and pull requests typically arrive within one to two weeks. Development activity centers on new feature requests, suggesting the tool continues to evolve in response to user needs rather than being in maintenance-only mode.