Passport is Express-compatible authentication
middleware for Node.js.
Passport's sole purpose is to authenticate requests, which it does through an
extensible set of plugins known as strategies. Passport does not mount
routes or assume any particular database schema, which maximizes flexibility and
allows application-level decisions to be made by the developer. The API is
simple: you provide Passport a request to authenticate, and Passport provides
hooks for controlling what occurs when authentication succeeds or fails.
Passport uses the concept of strategies to authenticate requests. Strategies
can range from verifying username and password credentials, delegated
authentication using OAuth (for example, via Facebook
or Twitter), or federated authentication using OpenID.
Before authenticating requests, the strategy (or strategies) used by an
application must be configured.
There are 480+ strategies. Find the ones you want at: passportjs.org
Sessions
Passport will maintain persistent login sessions. In order for persistent
sessions to work, the authenticated user must be serialized to the session, and
deserialized when subsequent requests are made.
Passport does not impose any restrictions on how your user records are stored.
Instead, you provide functions to Passport which implements the necessary
serialization and deserialization logic. In a typical application, this will be
as simple as serializing the user ID, and finding the user by ID when
deserializing.
To use Passport in an Express or
Connect-based application, configure it
with the required passport.initialize() middleware. If your application uses
persistent login sessions (recommended, but not required), passport.session()
middleware must also be used.
Passport vulnerable to session regeneration when a users logs in or out
Affected Versions
< 0.6.0
Patched Versions
0.6.0
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Info: project has a license file: LICENSE:0
Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/27 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Warn: no topLevel permission defined: .github/workflows/node.yml:1
Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport/node.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.yml:38: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport/node.yml/master?enable=pin
Warn: npmCommand not pinned by hash: .github/workflows/node.yml:42
Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 1 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
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
Reason
project is not fuzzed
Details
Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Warn: 0 commits out of 4 are checked with a SAST tool
Score
3.4
/10
Last Scanned on 2024-12-02
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.