ipfs-api 0.0.4
An client library for the IPFS API
ipfs-api@0.0.4 was published on 2014-11-18. 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.
Deprecated: ipfs-api has been renamed to ipfs-http-client, please update your package.json to get the latest version.
All ipfs-api versions · Permanent reference to 0.0.4 · Latest release
Package specifications
| Version | 0.0.4 |
|---|---|
| License declaration | MIT |
| Published | 2014-11-18T12:31:50.035Z |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install ipfs-api 0.0.4
npm install ipfs-api@0.0.4 pnpm add ipfs-api@0.0.4 yarn add ipfs-api@0.0.4
Runtime dependencies
- multipart-stream ^1.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.
- inherits@2.0.4 — indirect
- multipart-stream@1.0.0 — direct
- sandwich-stream@0.0.4 — 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/ipfs-api/0.0.4 — retrieved 2026-10-31T00:00:48.432Z
- https://api.deps.dev/v3/systems/npm/packages/ipfs-api/versions/0.0.4 — retrieved 2026-10-31T00:00:48.917Z
- https://api.deps.dev/v3/systems/npm/packages/ipfs-api/versions/0.0.4:dependencies — retrieved 2026-10-31T00:00:48.937Z