← Home

jose

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

12
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

panva

Keywords

akpbrowserbuncloudflarecompactdecodedecryptdenodetachedececdsaed25519eddsaedgeelectronembeddedencryptflattenedgeneraljosejson web tokenjsonwebtokenjwajwejwkjwksjwsjwt-decodejwtml-dsanetlifynextnextjsoctokppayloadpempkcs8rsasignsignaturespkivalidatevercelverifywebcryptoworkerdworkersx509

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher moved from panva's personal account to GitHub Actions CI/CD publishing with SLSA provenance; this is a security improvement, not a risk. ai
provenance slsa-provenance AI (provenance): SLSA provenance attestation confirms legitimate CI/CD pipeline publishing. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy is an artifact of new major version line (v6); v5.x was actively maintained. Package has 235 versions and 66.7M weekly downloads. ai
source-diff large-new-source-files AI (source-diff): New major version (v6) with restructured dist layout; 66 new files is expected for a clean JOSE library with many subpath exports. ai
typosquat typosquat.levenshtein:jest AI (typosquat): jose is the canonical JOSE (JSON Object Signing and Encryption) library, not a typosquat of jest. The name is a well-known cryptography acronym with 66M weekly downloads and 3888 days of history. ai
typosquat typosquat.levenshtein:joi AI (typosquat): jose is the canonical JOSE cryptography library, not a typosquat of joi. Completely different domain and purpose; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
6.2.3 0 / 0
6.2.2 0 / 0
6.2.1 0 / 0
6.2.0 0 / 0
6.1.3 0 / 0
6.1.2 0 / 0
6.1.1 0 / 0
6.1.0 0 / 0
6.0.13 0 / 0
6.0.12 0 / 0
6.0.11 0 / 0
5.9.2 0 / 0

v6.2.1

2 findings
HIGH Publisher changed: panva → GitHub Actions (on 2026-03-09) provenance

This version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.2.0

2 findings
HIGH Publisher changed: panva → GitHub Actions (on 2026-03-05) provenance

This version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.1.3

2 findings
HIGH Publisher changed: panva → GitHub Actions (on 2025-12-02) provenance

This version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.1.2

2 findings
HIGH Publisher changed: panva → GitHub Actions (on 2025-11-15) provenance

This version was published by a different npm account than previous versions on 2025-11-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.1.1

2 findings
HIGH Publisher changed: panva → GitHub Actions (on 2025-11-09) provenance

This version was published by a different npm account than previous versions on 2025-11-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.1.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.0.13

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.0.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.0.11

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.9.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.