node-jose
A JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for current web browsers and node.js-based servers
1
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
linuxwolfmwegmanjustaugustus
Keywords
cryptojosejwajwejwkjws
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://www.cisco.com | AI (email-domain): The 'email' field is actually the Cisco website URL used as author contact, not an email address. Cisco's domain is active and legitimate. Analyzer is misinterpreting a URL as an email domain. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex literals in this crypto library are standard algorithm constants (e.g., AES-KW IV per RFC 3394). Not obfuscation or malicious payload hiding. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of X.509 certs from JWS x5c headers is standard JOSE/JWS processing per RFC 7515. Expected behavior for a JOSE library. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 9 / 5 |
v2.2.0
2 findings
HIGH
Unclaimed maintainer email domain: https://www.cisco.com
email-domain
Maintainer email 'https://www.cisco.com' uses domain 'https://www.cisco.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.