jwa
JWA implementation (supports all JWS algorithms)
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:ecdsa-sig-formatter | AI (dependencies): ecdsa-sig-formatter is a well-known, pinned dependency appropriate for a JWA/ECDSA implementation; stable false positive for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the legitimate first release of a 13+ year old JWA library by a trusted publisher; not indicative of malicious intent. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): omsmith added as maintainer in 2015 with a strong track record. Consistent with legitimate project handoff, not a compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ecdsa-sig-formatter is a legitimate, well-known dependency for ECDSA signature format conversion in JWA/JWS implementations. Functionally justified addition. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2015, well before Sigstore provenance was available. Not a meaningful risk signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to omsmith occurred in 2015; omsmith has a strong track record (19 approved, 0 rejected). Legitimate maintainer transition on a well-established open-source JWT library. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): jwa is a standard acronym for JSON Web Algorithms; no plausible intent to impersonate koa. False positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): jwa is a standard acronym for JSON Web Algorithms; no plausible intent to impersonate joi. False positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 3 / 4 | |
| 2.0.0 | 3 / 4 | |
| 1.4.2 | 3 / 4 | |
| 1.4.1 | 3 / 4 | |
| 1.4.0 | 3 / 4 | |
| 1.3.0 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.6 | 3 / 3 | |
| 1.1.5 | 4 / 2 | |
| 1.1.4 | 4 / 2 | |
| 1.1.3 | 3 / 2 | |
| 1.1.2 | 3 / 2 | |
| 1.1.1 | 3 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.2 | 3 / 1 | |
| 1.0.1 | 3 / 1 | |
| 1.0.0 | 2 / 1 | |
| 0.0.3 | 2 / 1 | |
| 0.0.2 | 1 / 1 | |
| 0.0.1 | 1 / 1 | |
| 0.0.0 | 1 / 1 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
2 findingsThis version was published by a different npm account than previous versions on 2019-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
2 findingsThis version was published by a different npm account than previous versions on 2018-05-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
2 findingsThis version was published by a different npm account than previous versions on 2016-12-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
2 findingsThis version was published by a different npm account than previous versions on 2016-11-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2015-11-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2015-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2015-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.