create-ecdh
createECDH but browserifiable
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from dcousens to cwmma (Calvin Metcalf, the package author) in 2015 is a legitimate maintainer transition within the crypto-browserify org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is 4186 days old with 10.3M weekly downloads; inflated-semver and short-README signals are false positives for this well-established utility package. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a standard cryptographic library for ECDH; its use is appropriate and expected for this package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4186 days old and predates Sigstore provenance; low risk given publisher track record and ecosystem trust. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.4 | 2 / 3 | |
| 4.0.3 | 2 / 3 | |
| 4.0.0 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.0.2 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 2 |
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.