panva/node-oidc-provider

OpenID Certified™ OAuth 2.0 Authorization Server implementation for Node.js

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on December 2nd, 2015
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 794
Total Stargazers: 3,815 (+0)
Total Subscribers: 65 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 6.6 hours
90th percentile: 23.3 hours
Tracked items: 6

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • bug (1)
  • triage (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

node-oidc-provider is an OpenID Certified OAuth 2.0 Authorization Server implementation for Node.js that provides a complete OIDC-compliant identity provider.

The tool solves the problem of building a standards-compliant authorization server by implementing the full OAuth 2.0 and OpenID Connect specifications along with numerous security extensions and advanced features. Rather than requiring developers to implement these complex protocols from scratch, the provider handles the protocol logic, token management, and security requirements through a configurable module that can be integrated into a Node.js application. Many features are available but not enabled by default, allowing developers to enable only what their use case requires.

Organizations building identity infrastructure or needing to operate their own authorization server should consider this tool. It suits projects that require full control over the authentication and authorization layer, need to support multiple OAuth 2.0 and OIDC flows, or must comply with financial-grade API security standards. The implementation covers a broad range of specifications including PKCE, device flow, mutual TLS authentication, JWT-secured authorization requests, pushed authorization requests, and demonstration of proof-of-possession, as well as FAPI 1.0 and FAPI 2.0 security profiles. The tool also supports experimental features including client-initiated backchannel authentication and OpenID for Verifiable Credential Issuance.

The project maintains active development with regular updates to support evolving specifications. Experimental features are released as minor version updates to signal that breaking changes may occur as specifications mature. The maintainers provide comprehensive documentation covering configuration options and maintain awareness of specification changes, releasing updates to align with new RFCs and drafts as they become available.