diffie-hellman
pure js diffie-hellman
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:miller-rabin | AI (dependencies): miller-rabin is a legitimate crypto-browserify ecosystem library by the same author; its use for primality testing in DH key generation is expected and stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 10M+ weekly downloads and 4000+ day history; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change was in 2015; cwmma is the package author (Calvin Metcalf) and a long-standing trusted npm publisher. Legitimate maintainer. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.0.3 | 3 / 2 | |
| 5.0.2 | 3 / 2 | |
| 5.0.1 | 3 / 2 | |
| 5.0.0 | 3 / 2 | |
| 4.0.0 | 3 / 2 | |
| 3.0.2 | 3 / 2 | |
| 3.0.1 | 3 / 2 | |
| 3.0.0 | 3 / 2 | |
| 2.2.3 | 2 / 2 | |
| 2.2.2 | 2 / 2 | |
| 2.2.1 | 2 / 2 | |
| 2.2.0 | 2 / 2 | |
| 2.1.0 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.1.2 | 1 / 2 | |
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.3 | 1 / 2 | |
| 1.0.2 | 1 / 2 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 0 / 0 |
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2015-10-27. 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.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.