PyPI package

oauthenticator

17.3.0

Default version

Published

Description

OAuthenticator: Authenticate JupyterHub users with common OAuth providers

Attestations

PyPI Publish Attestation
This version has a PyPI Publish attestation.
VERIFIEDThe Sigstore bundle containing this attestation was verified using sigstore-go.

Repository
github.com/jupyterhub/oauthenticator (10901)
Publish config
github.com/jupyterhub/oauthenticator/.github/workflows/release.yaml
Published by
GHA on GitHub
Log date
The time this entry was integrated into the rekor transparency log.
(index 154731785)

Links

Origin
Attestations

Projects

jupyterhub/oauthenticator

GitHub

OAuth + JupyterHub Authenticator = OAuthenticator

 368 forks
 429 stars

OpenSSF scorecard

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.

View information about checks and how to fix failures.

Score
4.6/10
Scorecard as of .
Code-Review
5/10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning
Found 5/10 approved changesets -- score normalized to 5
Maintained
9/10
Determines if the project is "actively maintained".
Reasoning
9 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 9
Dangerous-Workflow
10/10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning
no dangerous workflow patterns detected
Binary-Artifacts
10/10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning
no binaries found in the repo
Token-Permissions
0/10
Determines if the project's workflows follow the principle of least privilege.
Reasoning
detected GitHub workflow tokens with excessive permissions
CII-Best-Practices
0/10
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning
no effort to earn an OpenSSF best practices badge detected
Fuzzing
0/10
Determines if the project uses fuzzing.
Reasoning
project is not fuzzed
License
10/10
Determines if the project has defined a license.
Reasoning
license file detected
Pinned-Dependencies
0/10
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning
dependency not pinned by hash detected -- score normalized to 0
Security-Policy
0/10
Determines if the project has published a security policy.
Reasoning
security policy file not detected
Packaging
10/10
Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.
Reasoning
packaging workflow detected
Vulnerabilities
0/10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning
14 existing vulnerabilities detected
SAST
0/10
Determines if the project uses static code analysis.
Reasoning
SAST tool is not run on all commits -- score normalized to 0

Project metadata as of .