hypercore-index 5.1.1
Linear asynchronous stateful indexing of a hypercore feed
hypercore-index@5.1.1 was published on 2017-03-05. Its manifest declares 1 runtime dependency 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-index versions · Permanent reference to 5.1.1 · Latest release
Package specifications
| Version | 5.1.1 |
|---|---|
| License declaration | MIT |
| Published | 2017-03-05T09:50:47.490Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 24 |
| Repository forks | 5 |
Install hypercore-index 5.1.1
npm install hypercore-index@5.1.1 pnpm add hypercore-index@5.1.1 yarn add hypercore-index@5.1.1
Runtime dependencies
- stream-each ^1.1.2
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.
- end-of-stream@1.4.5 — indirect
- once@1.4.0 — indirect
- stream-each@1.2.3 — direct
- stream-shift@1.0.3 — indirect
- wrappy@1.0.2 — 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 3/13 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 |
| 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-index/5.1.1 — retrieved 2026-10-29T20:16:57.673Z
- https://api.deps.dev/v3/systems/npm/packages/hypercore-index/versions/5.1.1 — retrieved 2026-10-29T20:16:58.224Z
- https://api.deps.dev/v3/systems/npm/packages/hypercore-index/versions/5.1.1:dependencies — retrieved 2026-10-29T20:16:58.234Z
- https://api.deps.dev/v3/projects/github.com%2Fjuliangruber%2Fhypercore-index — retrieved 2026-10-29T20:16:58.815Z