# jose@6.1.3 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-04T16:33:49.000Z
- Files reviewed: 66
- Findings: 1 low severity finding
- Report: https://security.togoder.click/npm/jose@6.1.3
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## Summary

Togoder Security scanned the npm package jose@6.1.3 on Oct 4, 2026. An AI review of 66 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

## Findings

### [low] Cryptographic Implementation

Finding ID: `NPS-A4956E6D40D6`

File: `dist/webapi/lib/decrypt.js:6`

The timingSafeEqual function uses HMAC with SHA-256 to compare buffers in a timing-safe manner, but note that HMAC key generation and signing operation may introduce variable timing based on input length. This is a known pattern in JOSE libraries and not considered malicious.

## Files reviewed

- `dist/webapi/index.js` (safe): This is a standard barrel export file for the jose library's Web API entry point, re-exporting cryptographic JWE/JWS/JWT utilities with no malicious patterns detected.
- `dist/webapi/jwe/compact/decrypt.js` (safe): No malicious patterns detected; the code is a standard JWE compact decryption implementation using internal cryptographic utilities.
- `dist/webapi/jwe/compact/encrypt.js` (safe): No malicious patterns detected; the code is a straightforward JWE compact encryption wrapper with no network, filesystem, process, or dynamic execution behavior.
- `dist/webapi/jwe/flattened/decrypt.js` (safe): This is a legitimate JWE flattened decryption implementation from the jose library with no malicious patterns detected.
- `dist/webapi/jwe/flattened/encrypt.js` (safe): No malicious patterns detected; the code implements standard JWE encryption functionality without any signs of data exfiltration, credential harvesting, obfuscation, or other security concerns.
- `dist/webapi/jwe/general/decrypt.js` (safe): No malicious patterns detected
- `dist/webapi/jwe/general/encrypt.js` (safe): No malicious patterns detected; the code implements JWE encryption logic with no exfiltration, credential harvesting, obfuscation, or other security concerns.
- `dist/webapi/jwk/embedded.js` (safe): This is a legitimate JOSE (JSON Object Signing and Encryption) EmbeddedJWK implementation that extracts and imports a public key from the JWT header; no malicious patterns detected.
- `dist/webapi/jwk/thumbprint.js` (safe): No malicious patterns detected in the JWK thumbprint calculation code; it performs standard cryptographic digest operations without network, filesystem, or process manipulation.
- `dist/webapi/jwks/local.js` (safe): No malicious patterns detected; the code is a standard JWKS local key set implementation with no network, filesystem, process, or obfuscation concerns.
- `dist/webapi/jwks/remote.js` (safe): The code is a legitimate JWKS remote key set implementation for the jose library, with no malicious patterns detected.
- `dist/webapi/jws/compact/sign.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/jws/compact/verify.js` (safe): No malicious patterns detected; the code is a standard JWS compact verification implementation.
- `dist/webapi/jws/flattened/sign.js` (safe): This is a standard JWS flattened signing implementation with no malicious patterns, external network calls, credential harvesting, or dynamic code execution.
- `dist/webapi/jws/flattened/verify.js` (safe): No malicious patterns detected; the code is a standard JWS flattened verification implementation with input validation and no network, filesystem, or dynamic execution activities.
- `dist/webapi/jws/general/sign.js` (safe): No malicious patterns detected; the code implements standard JWS multi-signature handling without network, filesystem, or dynamic execution risks.
- `dist/webapi/jws/general/verify.js` (safe): No malicious patterns detected; the code implements standard JWS verification logic with proper input validation and error handling.
- `dist/webapi/jwt/decrypt.js` (safe): Code performs standard JWT decryption and claim validation with no malicious patterns detected.
- `dist/webapi/jwt/encrypt.js` (safe): No malicious patterns detected; this is a standard JWT encryption builder with no network, filesystem, process, or dynamic code execution behavior.
- `dist/webapi/jwt/sign.js` (safe): No malicious patterns detected
- `dist/webapi/jwt/unsecured.js` (safe): No malicious patterns detected; code implements a standard unsecured JWT (alg=none) that performs only local base64url encoding/decoding and claim validation without any exfiltration, credential access, or dynamic code execution.
- `dist/webapi/jwt/verify.js` (safe): The JWT verification code contains no malicious patterns; it performs standard cryptographic verification and claim validation without any exfiltration, obfuscation, or dynamic execution.
- `dist/webapi/key/export.js` (safe): The file only re-exports key conversion functions from internal modules without any network, filesystem, process, or dynamic code execution behavior.
- `dist/webapi/key/generate_key_pair.js` (safe): This module only generates cryptographic key pairs using the Web Crypto API with strict algorithm validation and no malicious patterns, network calls, or file system access.
- `dist/webapi/key/generate_secret.js` (safe): No malicious patterns detected; the code performs standard JWK secret generation using WebCrypto APIs.
- `dist/webapi/key/import.js` (safe): No malicious patterns detected
- `dist/webapi/lib/aesgcmkw.js` (safe): The code is a straightforward implementation of AES-GCM key wrapping/unwrapping for JWE, with no malicious patterns, external calls, or obfuscation detected.
- `dist/webapi/lib/aeskw.js` (safe): No malicious patterns detected; the code is a standard AES-KW key wrapping implementation using Web Crypto API.
- `dist/webapi/lib/asn1.js` (safe): No malicious patterns detected
- `dist/webapi/lib/base64.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/buffer_utils.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/cek.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/check_cek_length.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/check_iv_length.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/check_key_length.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/check_key_type.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/crypto_key.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/decrypt.js` (safe): No malicious patterns detected; the code implements standard JWE decryption using Web Crypto API with proper error handling and timing-safe comparison.
- `dist/webapi/lib/decrypt_key_management.js` (safe): No malicious patterns detected; this is a standard JWE key management decryption module with proper input validation and no exfiltration, dynamic execution, or suspicious behavior.
- `dist/webapi/lib/digest.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/ecdhes.js` (safe): The code implements standard ECDH key derivation with Concat KDF using only Web Crypto APIs and local utilities, with no malicious patterns detected.
- `dist/webapi/lib/encrypt.js` (safe): This is legitimate JWE encryption code from a JOSE library with no malicious patterns, exfiltration, or dynamic code execution.
- `dist/webapi/lib/encrypt_key_management.js` (safe): No malicious patterns detected
- `dist/webapi/lib/get_sign_verify_key.js` (safe): No malicious patterns detected; the code only performs standard HMAC key import and signature key validation.
- `dist/webapi/lib/invalid_key_input.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/is_disjoint.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/is_jwk.js` (safe): No malicious patterns detected
- `dist/webapi/lib/is_key_like.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/is_object.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/iv.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/jwk_to_key.js` (safe): No malicious patterns detected; the code performs standard JWK to WebCrypto key conversion without network, filesystem, process, or dynamic execution behavior.
- `dist/webapi/lib/jwt_claims_set.js` (safe): No malicious patterns detected; the file implements standard JWT claim validation and building logic without any exfiltration, obfuscation, process spawning, or filesystem access.
- `dist/webapi/lib/key_to_jwk.js` (safe): No malicious patterns detected; the code performs standard key-to-JWK conversion without exfiltration, obfuscation, or suspicious behavior.
- `dist/webapi/lib/normalize_key.js` (safe): No malicious patterns detected; the code is a standard JOSE key normalization utility for converting JWK/KeyObject/CryptoKey inputs into CryptoKey objects.
- `dist/webapi/lib/pbes2kw.js` (safe): No malicious patterns detected; the code implements standard PBES2 key derivation and AES key wrapping using Web Crypto APIs without external communication or suspicious behavior.
- `dist/webapi/lib/private_symbols.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/rsaes.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/sign.js` (safe): No malicious patterns detected; the code implements standard Web Crypto signing using imported helper functions without any exfiltration, obfuscation, or suspicious behavior.
- `dist/webapi/lib/subtle_dsa.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/validate_algorithms.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/validate_crit.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/lib/verify.js` (safe): No malicious patterns detected; the code is a standard cryptographic signature verification function using the WebCrypto API with no suspicious behavior.
- `dist/webapi/util/base64url.js` (safe): Cleared by Jev triage; no further analysis needed
- `dist/webapi/util/decode_jwt.js` (safe): The decodeJwt function performs standard JWT payload decoding and validation without any malicious patterns, network activity, credential access, or dynamic code execution.
- `dist/webapi/util/decode_protected_header.js` (safe): The file contains legitimate JWT protected header decoding logic with no malicious patterns such as exfiltration, dynamic code execution, or process spawning.
- `dist/webapi/util/errors.js` (safe): Cleared by Jev triage; no further analysis needed

## Version ranges

None of the 2 scanned versions of jose are flagged high or critical. The latest scanned version, 6.2.12, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.

- 6.2.1 – 6.2.12 (`>=6.2.1 <=6.2.12`): not scanned
- 6.1.3 (`6.1.3`): clean
- 5.10.0 (`5.10.0`): not scanned
- 4.15.9 (`4.15.9`): medium (Insecure JWT implementation (algorithm: none) +4 more)

## Scanned versions

- [6.1.3](https://security.togoder.click/npm/jose@6.1.3): safe, 2026-10-04T16:33:49.000Z
- [4.15.9](https://security.togoder.click/npm/jose@4.15.9): medium, 2026-10-06T14:17:14.000Z

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology