← Home

jsrsasign

npm Repository Homepage
3
Versions
—
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

kjur

Keywords

cryptocryptographyCipherRSAECDSADSARSAPSSPKCS#1PKCS#5PKCS#8private keypublic keyCSRPKCS#10hash functionHMacASN.1certificateX.509CRLOCSPRFC 3161Digital TimestampTimestampTime Stamp TokenCMSCryptgraphic Message SyntaxPKCS#7SignatureDigital SignaturesigningMessage DigestJSON Web TokenJWTJSON Web SignatureJWSJSON Web KeyJWKJOSEJWA

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is fundamental to this crypto/JWT library's core functionality; stable false positive across all versions. ai

Versions (showing 3 of 3)

Version Deps Published
11.1.3 0 / 1
11.1.2 0 / 1
11.1.1 0 / 1

v11.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.