key-encoder
1
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
ablanksteinonenameshea256
Keywords
ellipticelliptic curveasnpemderecdsacryptocryptographyprivatekeyencodedecodesecp256k1bitcoincurveprivate keyprivate keyspublic keypublic keyskeysecdsa keyecdsa keyskey converterconvert keyskey formatkey formatterformat keyskey encoderencode keys
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is core to key encoding/decoding functionality; not a malicious payload pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/elliptic | AI (phantom-deps): @types/elliptic is a TypeScript type declaration used at compile time; not a runtime import. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 4 / 9 |
v2.0.3
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.