ipfs-api 3.0.0
A client library for the IPFS API
ipfs-api@3.0.0 was published on 2016-04-08. Its manifest declares 8 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.2.2.
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 3.0.0 · Latest release
Package specifications
| Version | 3.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2016-04-08T03:33:50.582Z |
| Node.js requirement | >=4.2.2 |
| Type declarations | Not declared |
| Runtime dependency count | 8 |
| 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 | src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 64 |
| Repository stars | 1041 |
| Repository forks | 289 |
Install ipfs-api 3.0.0
npm install ipfs-api@3.0.0 pnpm add ipfs-api@3.0.0 yarn add ipfs-api@3.0.0
Runtime dependencies
- detect-node ^2.0.3
- flatmap 0.0.3
- glob ^7.0.3
- multiaddr ^1.0.0
- multipart-stream ^2.0.1
- ndjson ^1.4.3
- qs ^6.0.0
- wreck ^7.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.
- async-function@1.0.0 — indirect
- async-generator-function@1.0.0 — indirect
- babel-runtime@6.26.0 — indirect
- balanced-match@1.0.2 — indirect
- base-x@1.1.0 — indirect
- boom@3.2.2 — indirect
- brace-expansion@1.1.21 — indirect
- bs58@3.1.0 — indirect
- call-bind-apply-helpers@1.0.2 — indirect
- call-bound@1.0.4 — indirect
- concat-map@0.0.1 — indirect
- core-js@2.6.12 — indirect
- core-util-is@1.0.3 — indirect
- detect-node@2.1.0 — direct
- dunder-proto@1.0.1 — indirect
- es-define-property@1.0.1 — indirect
- es-errors@1.3.0 — indirect
- es-object-atoms@1.1.2 — indirect
- flatmap@0.0.3 — direct
- fs.realpath@1.0.0 — indirect
- function-bind@1.1.2 — indirect
- generator-function@2.0.1 — indirect
- get-intrinsic@1.3.1 — indirect
- get-proto@1.0.1 — indirect
- glob@7.2.3 — direct
- gopd@1.2.0 — indirect
- has-symbols@1.1.0 — indirect
- hasown@2.0.4 — indirect
- hoek@4.3.1 — indirect
- inflight@1.0.6 — indirect
- inherits@2.0.4 — indirect
- ip@1.1.9 — indirect
- is-stream@1.1.0 — indirect
- isarray@1.0.0 — indirect
- json-stringify-safe@5.0.1 — indirect
- lodash.filter@4.6.0 — indirect
- lodash.map@4.6.0 — indirect
- math-intrinsics@1.1.0 — indirect
- minimatch@3.1.5 — indirect
- minimist@1.2.8 — indirect
- multiaddr@1.4.1 — direct
- multipart-stream@2.0.1 — direct
- ndjson@1.5.0 — direct
- object-inspect@1.13.4 — indirect
- once@1.4.0 — indirect
- path-is-absolute@1.0.1 — indirect
- process-nextick-args@2.0.1 — indirect
- qs@6.17.1 — direct
- readable-stream@2.3.8 — indirect
- regenerator-runtime@0.11.1 — indirect
- safe-buffer@5.1.2 — indirect
- sandwich-stream@1.0.0 — indirect
- side-channel@1.1.1 — indirect
- side-channel-list@1.0.1 — indirect
- side-channel-map@1.0.1 — indirect
- side-channel-weakmap@1.0.2 — indirect
- split2@2.2.0 — indirect
- string_decoder@1.1.1 — indirect
- through2@2.0.5 — indirect
- util-deprecate@1.0.2 — indirect
- varint@4.0.1 — indirect
- wrappy@1.0.2 — indirect
- wreck@7.2.1 — direct
- xtend@4.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.
| Maintained | 0/10 — project is archived |
|---|---|
| Code-Review | 3/10 — Found 9/30 approved changesets -- score normalized to 3 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/ipfs-api/3.0.0 — retrieved 2026-10-30T22:28:33.411Z
- https://api.deps.dev/v3/systems/npm/packages/ipfs-api/versions/3.0.0 — retrieved 2026-10-30T22:28:33.796Z
- https://api.deps.dev/v3/systems/npm/packages/ipfs-api/versions/3.0.0:dependencies — retrieved 2026-10-30T22:28:33.829Z
- https://api.deps.dev/v3/projects/github.com%2Fipfs%2Fjs-ipfs-api — retrieved 2026-10-30T22:28:34.150Z