create-ecdh 4.0.4
createECDH but browserifiable
create-ecdh@4.0.4 was published on 2020-08-04. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All create-ecdh versions · Permanent reference to 4.0.4 · Latest release
Package specifications
| Version | 4.0.4 |
|---|---|
| License declaration | MIT |
| Published | 2020-08-04T16:09:48.587Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 5.28 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 25 |
| Repository forks | 15 |
Install create-ecdh 4.0.4
npm install create-ecdh@4.0.4 pnpm add create-ecdh@4.0.4 yarn add create-ecdh@4.0.4
Runtime dependencies
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- bn.js@4.12.5 — direct
- brorand@1.1.0 — indirect
- elliptic@6.6.1 — direct
- hash.js@1.1.7 — indirect
- hmac-drbg@1.0.1 — indirect
- inherits@2.0.4 — indirect
- minimalistic-assert@1.0.1 — indirect
- minimalistic-crypto-utils@1.0.1 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Code-Review | 2/10 — Found 6/29 approved changesets -- score normalized to 2 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
Evidence and freshness
- https://registry.npmjs.org/create-ecdh/4.0.4 — retrieved 2026-10-29T10:33:08.611Z
- https://api.deps.dev/v3/systems/npm/packages/create-ecdh/versions/4.0.4:dependencies — retrieved 2026-10-29T09:00:36.012Z
- https://api.deps.dev/v3/systems/npm/packages/create-ecdh/versions/4.0.4 — retrieved 2026-10-29T09:00:35.965Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fcrypto-browserify%2FcreateECDH — retrieved 2026-10-29T09:00:36.154Z