Gathering detailed insights and metrics for oidc-provider
Installations
npm install oidc-providerDeveloper Guide
BETA
Typescript
No
Module System
ESM
Node Version
22.12.0
NPM Version
10.9.0
Score
95.4
Supply Chain
97.5
Quality
85.6
Maintenance
100
Vulnerability
100
License
Releases
240
Contributors
67
Languages
4
JavaScript
TypeScript
EJS
Procfile
JavaScript (98.76%)
TypeScript (0.63%)
EJS (0.61%)
Developer
panva
Download Statistics
Total Downloads
7,402,567
Last Day
11,072
Last Week
57,556
Last Month
202,430
Last Year
2,636,976
GitHub Statistics
3,288 Stars
2,538 Commits
772 Forks
72 Watching
4 Branches
67 Contributors
Sponsor this package
Maintainers
1
Package Meta Information
Latest Version
8.6.1
Package Id
oidc-provider@8.6.1
Unpacked Size
538.27 kB
Size
132.12 kB
File Count
200
NPM Version
10.9.0
Node Version
22.12.0
Publised On
19 Jan 2025
Total Downloads
Cumulative downloads
Total Downloads
7,402,567
Last day
-8.6%
11,072
Compared to previous day
Last week
-12.4%
57,556
Compared to previous week
Last month
-15.1%
202,430
Compared to previous month
Last year
42.6%
2,636,976
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
13
Versions
oidc-provider
This module provides an OAuth 2.0 (RFC 6749) Authorization Server with support for OpenID Connect (OIDC) and many other additional features and standards.
Table of Contents
Implemented specs & features
The following specifications are implemented by oidc-provider (not exhaustive):
Note that not all features are enabled by default, check the configuration section on how to enable them.
RFC6749- OAuth 2.0 &OIDCCore 1.0- OIDC
Discovery 1.0 - Dynamic Client Registration
- OIDC
RP-Initiated Logout 1.0 - OIDC
Back-Channel Logout 1.0 RFC7009- OAuth 2.0 Token RevocationRFC7636- Proof Key for Code Exchange (PKCE)RFC7662- OAuth 2.0 Token IntrospectionRFC8252- OAuth 2.0 for Native Apps BCP (AppAuth)RFC8628- OAuth 2.0 Device Authorization Grant (Device Flow)RFC8705- OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access Tokens (MTLS)RFC8707- OAuth 2.0 Resource IndicatorsRFC9101- OAuth 2.0 JWT-Secured Authorization Request (JAR)RFC9126- OAuth 2.0 Pushed Authorization Requests (PAR)RFC9207- OAuth 2.0 Authorization Server Issuer Identifier in Authorization ResponseRFC9449- OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer (DPoP)- Financial-grade API Security Profile 1.0 - Part 2: Advanced (
FAPI 1.0) - JWT Secured Authorization Response Mode for OAuth 2.0 (
JARM) - OIDC Client Initiated Backchannel Authentication Flow (
CIBA)
Supported Access Token formats:
The following draft specifications are implemented by oidc-provider:
- JWT Response for OAuth Token Introspection - draft 10
- Financial-grade API: Client Initiated Backchannel Authentication Profile (
FAPI-CIBA) - Implementer's Draft 01 - FAPI 2.0 Security Profile (
FAPI 2.0) - Implementer's Draft 02 - FAPI 2.0 Message Signing (
FAPI 2.0) - Implementer's Draft 01
Updates to draft specification versions are released as MINOR library versions,
if you utilize these specification implementations consider using the tilde ~ operator in your
package.json since breaking changes may be introduced as part of these version updates. Alternatively
acknowledge the version and be notified of breaking changes as part of
your CI.
Certification
Filip Skokan has certified that oidc-provider
conforms to the following profiles of the OpenID Connect™ protocol.
- Basic, Implicit, Hybrid, Config, Dynamic, Form Post, and 3rd Party-Init
- Back-Channel Logout and RP-Initiated Logout
- FAPI 1.0
- FAPI CIBA
- FAPI 2.0
Sponsor
If you want to quickly add OpenID Connect authentication to Node.js apps, feel free to check out Auth0's Node.js SDK and free plan. Create an Auth0 account; it's free!
Support
If you or your company use this module, or you need help using/upgrading the module, please consider becoming a sponsor so I can continue maintaining it and adding new features carefree. The only way to guarantee you get feedback from the author & sole maintainer of this module is to support the package through GitHub Sponsors.
Documentation & Configuration
oidc-provider can be mounted to existing connect, express, fastify, hapi, or koa applications, see how. The authorization server allows to be extended and configured in various ways to fit a variety of uses. See the documentation and example folder.
1import Provider from 'oidc-provider' 2const configuration = { 3 // refer to the documentation for other available configuration 4 clients: [ 5 { 6 client_id: 'foo', 7 client_secret: 'bar', 8 redirect_uris: ['http://lvh.me:8080/cb'], 9 // ... other client properties 10 }, 11 ], 12} 13 14const oidc = new Provider('http://localhost:3000', configuration) 15 16oidc.listen(3000, () => { 17 console.log( 18 'oidc-provider listening on port 3000, check http://localhost:3000/.well-known/openid-configuration', 19 ) 20})
Recipes
Collection of useful configuration use cases are available over at recipes.
Events
oidc-provider instances are event emitters, using event handlers you can hook into the various actions and i.e. emit metrics that react to specific triggers. See the list of available emitted event names and their description.
Supported Versions
| Version | Security Fixes 🔑 | Other Bug Fixes 🐞 | New Features ⭐ |
|---|---|---|---|
| v8.x | ✅ | ✅ | ✅ |
No vulnerabilities found.
Reason
13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE.md:0
- Info: FSF or OSI recognized license: MIT License: LICENSE.md:0
Reason
packaging workflow detected
Details
- Info: Project packages its releases by way of GitHub Actions.: .github/workflows/release.yml:8
Reason
0 existing vulnerabilities detected
Reason
SAST tool is not run on all commits -- score normalized to 5
Details
- Warn: 1 commits out of 2 are checked with a SAST tool
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/conformance.yml:175: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/conformance.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/conformance.yml:177: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/conformance.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/conformance.yml:208: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/conformance.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/conformance.yml:233: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/conformance.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:52: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:38: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/node-oidc-provider/test.yml/main?enable=pin
- Info: 0 out of 11 GitHub-owned GitHubAction dependencies pinned
- Info: 1 out of 1 third-party GitHubAction dependencies pinned
- Info: 1 out of 1 npmCommand dependencies pinned
Reason
branch protection is not maximal on development and all release branches
Details
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'force pushes' disabled on branch 'main'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'main'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'main'
- Warn: PRs are not required to make changes on branch 'main'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Reason
Found 1/29 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/release.yml:33
- Warn: no topLevel permission defined: .github/workflows/conformance.yml:1
- Warn: no topLevel permission defined: .github/workflows/lock.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Warn: no topLevel permission defined: .github/workflows/retry.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Score
5.5
/10
Last Scanned on 2025-01-20
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More