hypercore-protocol 6.4.2

Stream that implements the hypercore protocol

hypercore-protocol@6.4.2 was published on 2017-11-15. Its manifest declares 7 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 hypercore-protocol versions · Permanent reference to 6.4.2 · Latest release

Package specifications

Version	6.4.2
License declaration	MIT
Published	2017-11-15T21:22:18.357Z
Node.js requirement	Not declared
Type declarations	Not declared
Runtime dependency count	7
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	76
Repository stars	113
Repository forks	45

Install hypercore-protocol 6.4.2

npm install hypercore-protocol@6.4.2
pnpm add hypercore-protocol@6.4.2
yarn add hypercore-protocol@6.4.2

Runtime dependencies

brfs ^1.4.3
inherits ^2.0.3
protocol-buffers ^3.2.1
readable-stream ^2.2.6
sodium-universal ^2.0.0
sorted-indexof ^1.0.0
varint ^5.0.0

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.

brfs@1.6.1 — direct
inherits@2.0.4 — direct
protocol-buffers@3.2.1 — direct
readable-stream@2.3.8 — direct
sodium-universal@2.0.0 — direct
sorted-indexof@1.0.0 — direct
varint@5.0.2 — direct
quote-stream@1.0.2 — indirect
resolve@1.22.13 — indirect
static-module@2.2.5 — indirect
through2@2.0.5 — indirect
generate-function@2.3.1 — indirect
generate-object-property@1.2.0 — indirect
protocol-buffers-schema@3.6.1 — indirect
signed-varint@2.0.1 — indirect
core-util-is@1.0.3 — indirect
isarray@1.0.0 — indirect
process-nextick-args@2.0.1 — indirect
safe-buffer@5.1.2 — indirect
string_decoder@1.1.1 — indirect
util-deprecate@1.0.2 — indirect
sodium-javascript@0.5.6 — indirect
sodium-native@2.4.9 — indirect
buffer-equal@0.0.1 — indirect
minimist@1.2.8 — indirect
es-errors@1.3.0 — indirect
is-core-module@2.17.0 — indirect
path-parse@1.0.7 — indirect
supports-preserve-symlinks-flag@1.0.0 — indirect
concat-stream@1.6.2 — indirect
convert-source-map@1.9.0 — indirect
duplexer2@0.1.4 — indirect
escodegen@1.9.1 — indirect
falafel@2.2.5 — indirect
has@1.0.4 — indirect
magic-string@0.22.5 — indirect
merge-source-map@1.0.4 — indirect
object-inspect@1.4.1 — indirect
shallow-copy@0.0.1 — indirect
static-eval@2.1.1 — indirect
xtend@4.0.2 — indirect
is-property@1.0.2 — indirect
blake2b@2.1.4 — indirect
nanoassert@1.1.0 — indirect
siphash24@1.3.1 — indirect
xsalsa20@1.2.0 — indirect
ini@1.3.8 — indirect
nan@2.30.0 — indirect
node-gyp-build@4.8.4 — indirect
hasown@2.0.4 — indirect
buffer-from@1.1.2 — indirect
typedarray@0.0.6 — indirect
esprima@3.1.3 — indirect
estraverse@4.3.0 — indirect
esutils@2.0.3 — indirect
optionator@0.8.3 — indirect
source-map@0.6.1 — indirect
acorn@7.4.1 — indirect
isarray@2.0.5 — indirect
vlq@0.2.3 — indirect
source-map@0.5.7 — indirect
escodegen@2.1.0 — indirect
blake2b-wasm@2.4.0 — indirect
nanoassert@2.0.0 — indirect
nanoassert@2.0.0 — indirect
function-bind@1.1.2 — indirect
deep-is@0.1.4 — indirect
fast-levenshtein@2.0.6 — indirect
levn@0.3.0 — indirect
prelude-ls@1.1.2 — indirect
type-check@0.3.2 — indirect
word-wrap@1.2.5 — indirect
esprima@4.0.1 — indirect
estraverse@5.3.0 — indirect
b4a@1.9.0 — indirect
nanoassert@2.0.0 — 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.

Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts	10/10 — no binaries found in the repo
Code-Review	1/10 — Found 4/29 approved changesets -- score normalized to 1
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
Security-Policy	0/10 — security policy file not detected
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/hypercore-protocol/6.4.2 — retrieved 2026-10-29T15:14:52.038Z
https://api.deps.dev/v3/projects/github.com%2Fmafintosh%2Fhypercore-protocol — retrieved 2026-10-29T14:34:59.552Z
https://api.deps.dev/v3/systems/npm/packages/hypercore-protocol/versions/6.4.2 — retrieved 2026-10-29T15:14:52.630Z
https://api.deps.dev/v3/systems/npm/packages/hypercore-protocol/versions/6.4.2:dependencies — retrieved 2026-10-29T15:14:52.675Z