ipfs-core-types 0.5.0
IPFS interface definitions used by implementations for API compatibility.
ipfs-core-types@0.5.0 was published on 2021-05-26. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package 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-types versions · Permanent reference to 0.5.0 · Latest release
Package specifications
| Version | 0.5.0 |
|---|---|
| License declaration | (Apache-2.0 OR MIT) |
| Published | 2021-05-26T09:32:47.525Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 74.69 KiB |
| Published file count | 29 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 64 |
| Repository stars | 7385 |
| Repository forks | 1202 |
Install ipfs-core-types 0.5.0
npm install ipfs-core-types@0.5.0 pnpm add ipfs-core-types@0.5.0 yarn add ipfs-core-types@0.5.0
Runtime dependencies
- cids ^1.1.6
- interface-datastore ^4.0.0
- ipld-block ^0.11.1
- multiaddr ^9.0.1
- multibase ^4.0.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.
- cids@1.1.9 — direct
- interface-datastore@4.0.2 — direct
- ipld-block@0.11.1 — direct
- multiaddr@9.0.2 — direct
- multibase@4.0.6 — direct
- multicodec@3.2.1 — indirect
- multihashes@4.0.3 — indirect
- uint8arrays@3.1.1 — indirect
- err-code@3.0.1 — indirect
- interface-store@0.0.2 — indirect
- ipfs-utils@8.1.6 — indirect
- iso-random-stream@2.0.2 — indirect
- it-all@1.0.6 — indirect
- it-drain@1.0.5 — indirect
- it-filter@1.0.3 — indirect
- it-take@1.0.2 — indirect
- nanoid@3.3.20 — indirect
- uint8arrays@2.1.10 — indirect
- dns-over-http-resolver@1.2.3 — indirect
- is-ip@3.1.0 — indirect
- uint8arrays@2.1.10 — indirect
- varint@6.0.0 — indirect
- @multiformats/base-x@4.0.1 — indirect
- varint@5.0.2 — indirect
- multiformats@9.9.0 — indirect
- abort-controller@3.0.0 — indirect
- any-signal@2.1.2 — indirect
- buffer@6.0.3 — indirect
- electron-fetch@1.9.1 — indirect
- is-electron@2.2.2 — indirect
- iso-url@1.2.1 — indirect
- it-glob@0.0.14 — indirect
- it-to-stream@1.0.0 — indirect
- merge-options@3.0.4 — indirect
- native-abort-controller@1.0.4 — indirect
- native-fetch@3.0.0 — indirect
- react-native-fetch-api@2.0.0 — indirect
- stream-to-it@0.2.4 — indirect
- events@3.3.0 — indirect
- readable-stream@3.6.2 — indirect
- debug@4.4.3 — indirect
- receptacle@1.3.2 — indirect
- ip-regex@4.3.0 — indirect
- event-target-shim@5.0.1 — indirect
- base64-js@1.5.1 — indirect
- ieee754@1.2.1 — indirect
- encoding@0.1.14 — indirect
- @types/minimatch@3.0.5 — indirect
- minimatch@3.1.5 — indirect
- fast-fifo@1.3.2 — indirect
- get-iterator@1.0.2 — indirect
- p-defer@3.0.0 — indirect
- p-fifo@1.0.0 — indirect
- is-plain-obj@2.1.0 — indirect
- inherits@2.0.4 — indirect
- string_decoder@1.3.0 — indirect
- util-deprecate@1.0.2 — indirect
- ms@2.1.3 — indirect
- iconv-lite@0.7.3 — indirect
- brace-expansion@1.1.21 — indirect
- safe-buffer@5.2.1 — indirect
- safer-buffer@2.1.2 — indirect
- balanced-match@1.0.2 — indirect
- concat-map@0.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.
| Code-Review | 1/10 — Found 4/27 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — project is archived |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| License | 9/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 10/10 — security policy file detected |
| Pinned-Dependencies | 2/10 — dependency not pinned by hash detected -- score normalized to 2 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/ipfs-core-types/0.5.0 — retrieved 2026-10-30T02:06:05.915Z
- https://api.deps.dev/v3/projects/github.com%2Fipfs%2Fjs-ipfs — retrieved 2026-10-30T00:43:11.155Z
- https://api.deps.dev/v3/systems/npm/packages/ipfs-core-types/versions/0.5.0 — retrieved 2026-10-30T02:06:06.402Z
- https://api.deps.dev/v3/systems/npm/packages/ipfs-core-types/versions/0.5.0:dependencies — retrieved 2026-10-30T02:06:06.436Z