secp256k1-browserify 0.0.0
secp256k1-node compatability for browserify
secp256k1-browserify@0.0.0 was published on 2015-08-07. 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.
Deprecated: secp256k1 now inculdes browser compentents
All secp256k1-browserify versions · Permanent reference to 0.0.0 · Latest release
Package specifications
| Version | 0.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2015-08-07T18:23:18.535Z |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install secp256k1-browserify 0.0.0
npm install secp256k1-browserify@0.0.0 pnpm add secp256k1-browserify@0.0.0 yarn add secp256k1-browserify@0.0.0
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@3.3.0 — direct
- brorand@1.1.0 — indirect
- elliptic@5.2.1 — direct
- hash.js@1.1.7 — indirect
- inherits@2.0.4 — indirect
- minimalistic-assert@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.
Evidence and freshness
- https://registry.npmjs.org/secp256k1-browserify/0.0.0 — retrieved 2026-10-30T23:21:51.929Z
- https://api.deps.dev/v3/systems/npm/packages/secp256k1-browserify/versions/0.0.0 — retrieved 2026-10-30T23:21:52.363Z
- https://api.deps.dev/v3/systems/npm/packages/secp256k1-browserify/versions/0.0.0:dependencies — retrieved 2026-10-30T23:21:52.388Z