npm package

jose

6.0.10

Default version

Published

Description

JWA, JWS, JWE, JWT, JWK, JWKS for Node.js, Browser, Cloudflare Workers, Deno, Bun, and other Web-interoperable runtimes

Attestations

SLSA Provenance Attestation
This version has a SLSA provenance attestation.
VERIFIEDThe Sigstore bundle containing this attestation was verified using sigstore-go.

Repository
github.com/panva/jose (e1cfc)
Build config
github.com/panva/jose/.github/workflows/release.yml
Built by
GHA on GitHub
Log date
The time this entry was integrated into the rekor transparency log.
(index 180710390)
Workflow run
13806242036
SLSA Version
1
To verify the attestation, run the "npm audit signatures" command or download the attestations bundle from NPM and use the slsa-verifier tool.

Links

Origin
Homepage
Repo
Issues
Attestations

Projects

panva/jose

GitHub

JWA, JWS, JWE, JWT, JWK, JWKS for Node.js, Browser, Cloudflare Workers, Deno, Bun, and other Web-interoperable runtimes

 333 forks
 6k 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
5.6/10
Scorecard as of .
Dangerous-Workflow
10/10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning
no dangerous workflow patterns detected
Security-Policy
10/10
Determines if the project has published a security policy.
Reasoning
security policy file detected
Code-Review
0/10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning
Found 0/30 approved changesets -- score normalized to 0
Maintained
10/10
Determines if the project is "actively maintained".
Reasoning
30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts
10/10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning
no binaries found in the repo
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
Token-Permissions
0/10
Determines if the project's workflows follow the principle of least privilege.
Reasoning
detected GitHub workflow tokens with excessive permissions
SAST
0/10
Determines if the project uses static code analysis.
Reasoning
no SAST tool 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
License
10/10
Determines if the project has defined a license.
Reasoning
license file detected
Fuzzing
0/10
Determines if the project uses fuzzing.
Reasoning
project is not fuzzed
Branch-Protection
3/10
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning
branch protection is not maximal on development and all release branches
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

Project metadata as of .