Gathering detailed insights and metrics for jose
Gathering detailed insights and metrics for jose
JWA, JWS, JWE, JWT, JWK, JWKS for Node.js, Browser, Cloudflare Workers, Deno, Bun, and other Web-interoperable runtimes
Installations
npm install joseDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Node Version
22.17.0
NPM Version
10.9.2
Score
99.8
Supply Chain
100
Quality
90.5
Maintenance
100
Vulnerability
100
License
Releases
239
Languages
3
TypeScript
JavaScript
Shell
TypeScript (86.22%)
JavaScript (13.14%)
Shell (0.64%)
Developer
panva
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
6,698 Stars
1,686 Commits
346 Forks
39 Watchers
5 Branches
31 Contributors
Updated on Jul 18, 2025
Sponsor this package
Maintainers
1
Package Meta Information
Latest Version
6.0.12
Package Id
jose@6.0.12
Unpacked Size
244.37 kB
Size
47.45 kB
File Count
102
NPM Version
10.9.2
Node Version
22.17.0
Published on
Jul 15, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
No dependencies detected.
jose
jose is JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. The module is designed to work across various Web-interoperable runtimes including Node.js, browsers, Cloudflare Workers, Deno, Bun, and others.
Sponsor
If you want to quickly add JWT authentication to JavaScript apps, feel free to check out Auth0's JavaScript SDK and free plan. Create an Auth0 account; it's free!
💗 Help the project
Support from the community to continue maintaining and improving this module is welcome. If you find the module useful, please consider supporting the project by becoming a sponsor.
Dependencies: 0
jose has no dependencies and it exports tree-shakeable ESM1.
Documentation
jose is distributed via npmjs.com, jsr.io, jsdelivr.com, and github.com.
example ESM import1
1import * as jose from 'jose'
JSON Web Tokens (JWT)
The jose module supports JSON Web Tokens (JWT) and provides functionality for signing and verifying tokens, as well as their JWT Claims Set validation.
- JWT Claims Set Validation & Signature Verification using the
jwtVerifyfunction - Signing using the
SignJWTclass - Utility functions
- Decoding Token's Protected Header
- Decoding JWT Claims Set prior to its validation
Encrypted JSON Web Tokens
The jose module supports encrypted JSON Web Tokens and provides functionality for encrypting and decrypting tokens, as well as their JWT Claims Set validation.
- Decryption & JWT Claims Set Validation using the
jwtDecryptfunction - Encryption using the
EncryptJWTclass - Utility functions
Key Utilities
The jose module supports importing, exporting, and generating keys and secrets in various formats, including PEM formats like SPKI, X.509 certificate, and PKCS #8, as well as JSON Web Key (JWK).
- Key Import Functions
- Key and Secret Generation Functions
- Key Export Functions
JSON Web Signature (JWS)
The jose module supports signing and verification of JWS messages with arbitrary payloads in Compact, Flattened JSON, and General JSON serialization syntaxes.
- Signing - Compact, Flattened JSON, General JSON
- Verification - Compact, Flattened JSON, General JSON
- Utility functions
JSON Web Encryption (JWE)
The jose module supports encryption and decryption of JWE messages with arbitrary plaintext in Compact, Flattened JSON, and General JSON serialization syntaxes.
- Encryption - Compact, Flattened JSON, General JSON
- Decryption - Compact, Flattened JSON, General JSON
- Utility functions
Other
The following are additional features and utilities provided by the jose module:
- Calculating JWK Thumbprint
- Calculating JWK Thumbprint URI
- Verification using a JWK Embedded in a JWS Header
- Unsecured JWT
- JOSE Errors
Supported Runtimes
The jose module is compatible with JavaScript runtimes that support the utilized Web API globals and standard built-in objects or are Node.js.
The following runtimes are supported (this is not an exhaustive list):
Please note that certain algorithms may not be available depending on the runtime used. You can find a list of available algorithms for each runtime in the specific issue links provided above.
Supported Versions
| Version | Security Fixes 🔑 | Other Bug Fixes 🐞 | New Features ⭐ | Runtime and Module type |
|---|---|---|---|---|
| v6.x | Security Policy | ✅ | ✅ | Universal2 ESM1 |
| v5.x | Security Policy | ❌ | ❌ | Universal2 CJS + ESM |
| v4.x | Security Policy | ❌ | ❌ | Universal2 CJS + ESM |
| v2.x | Security Policy | ❌ | ❌ | Node.js CJS |
Specifications
Details
- JSON Web Signature (JWS) - RFC7515
- JSON Web Encryption (JWE) - RFC7516
- JSON Web Key (JWK) - RFC7517
- JSON Web Algorithms (JWA) - RFC7518
- JSON Web Token (JWT) - RFC7519
- JSON Web Key Thumbprint - RFC7638
- JSON Web Key Thumbprint URI - RFC9278
- JWS Unencoded Payload Option - RFC7797
- CFRG Elliptic Curve ECDH and Signatures - RFC8037
The algorithm implementations in jose have been tested using test vectors from their respective specifications as well as RFC7520.
Footnotes
Moderate
5.3/10
Summary
jose vulnerable to resource exhaustion via specifically crafted JWE with compressed plaintext
Affected Versions
< 2.0.7
Patched Versions
2.0.7
Moderate
5.3/10
Summary
jose vulnerable to resource exhaustion via specifically crafted JWE with compressed plaintext
Affected Versions
>= 3.0.0, <= 4.15.4
Patched Versions
4.15.5
Moderate
5.3/10
Summary
JOSE vulnerable to resource exhaustion via specifically crafted JWE
Affected Versions
>= 4.0.0, <= 4.9.1
Patched Versions
4.9.2
Moderate
5.3/10
Summary
JOSE vulnerable to resource exhaustion via specifically crafted JWE
Affected Versions
>= 3.0.0, <= 3.20.3
Patched Versions
3.20.4
Moderate
5.3/10
Summary
JOSE vulnerable to resource exhaustion via specifically crafted JWE
Affected Versions
>= 2.0.0, <= 2.0.5
Patched Versions
2.0.6
Moderate
5.3/10
Summary
JOSE vulnerable to resource exhaustion via specifically crafted JWE
Affected Versions
>= 1.0.0, <= 1.28.1
Patched Versions
1.28.2
Moderate
5.9/10
Summary
Padding Oracle Attack due to Observable Timing Discrepancy in jose
Affected Versions
>= 3.0.0, < 3.11.4
Patched Versions
3.11.4
Moderate
5.9/10
Summary
Padding Oracle Attack due to Observable Timing Discrepancy in jose
Affected Versions
>= 2.0.0, < 2.0.5
Patched Versions
2.0.5
Moderate
5.9/10
Summary
Padding Oracle Attack due to Observable Timing Discrepancy in jose
Affected Versions
>= 1.0.0, < 1.28.1
Patched Versions
1.28.1
Reason
30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Reason
security policy file detected
Details
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
Reason
no dangerous workflow patterns detected
Reason
GitHub workflow tokens follow principle of least privilege
Details
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release.yml:46
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/release.yml:60
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/release.yml:80
- Warn: jobLevel 'actions' permission set to 'write': .github/workflows/retry.yml:15
- Info: found token with 'none' permissions: .github/workflows/build.yml:1
- Info: found token with 'none' permissions: .github/workflows/lock.yml:1
- Info: found token with 'none' permissions: .github/workflows/release.yml:1
- Info: found token with 'none' permissions: .github/workflows/retry.yml:1
- Info: found token with 'none' permissions: .github/workflows/test.yml:1
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:13
Reason
0 existing vulnerabilities detected
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 0/30 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/build.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/build.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/build.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:37: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/build.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:63: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:84: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:88: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:37: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:74: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:91: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:93: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:54: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:107: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:109: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:133: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:135: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:155: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:157: update your workflow using https://app.stepsecurity.io/secureworkflow/panva/jose/test.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:164
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:99
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:115
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:141
- Info: 0 out of 25 GitHub-owned GitHubAction dependencies pinned
- Info: 1 out of 4 third-party GitHubAction dependencies pinned
- Info: 0 out of 4 npmCommand dependencies pinned
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Score
6.4
/10
Last Scanned on 2025-07-07
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