ipfs-core-utils 0.0.0

Package to share code between ipfs and ipfs-http-client

ipfs-core-utils@0.0.0 was published on 2020-03-20. Its manifest declares 11 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: js-IPFS has been deprecated in favour of Helia - please see https://github.com/ipfs/js-ipfs/issues/4336 for details

All ipfs-core-utils versions · Permanent reference to 0.0.0 · Latest release

Package specifications

Version0.0.0
License declarationMIT
Published2020-03-20T13:28:53.264Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count11
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size18.80 KiB
Published file count7
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies31
Repository stars7385
Repository forks1202

Install ipfs-core-utils 0.0.0

npm install ipfs-core-utils@0.0.0
pnpm add ipfs-core-utils@0.0.0
yarn add ipfs-core-utils@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.

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.

Code-Review1/10 — Found 4/27 approved changesets -- score normalized to 1
Maintained0/10 — project is archived
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness