A test suite and interface you can use to implement a IPFS core interface.
Clone or download
olizilla and daviddias Add peers with errors to swarm.peers definition
js-ipfs-api can encounter individual peer info objects that have newer multiaddrs or, in theory, a new format for PeerId that it cannot parse. Allowing for individiual peerInfo validation errors allows us to return a response which has the right number of peers in, and peerId and multiaddr info for all the other peers that could be validated, along with a info about peers that failed to validate.

See: ipfs/js-ipfs-api#887
Latest commit 4b2b7fe Nov 13, 2018



standard-readme compliant

A test suite and interface you can use to implement an IPFS core interface.

Lead Maintainer

Alan Shaw.

Table of Contents


The primary goal of this module is to define and ensure that both IPFS core implementations and their respective HTTP client libraries offer the same interface, so that developers can quickly change between a local and a remote node without having to change their applications. In addition to the definition of the expected interface, this module offers a suite of tests that can be run in order to check if the interface is used as described.

The API is presented with both Node.js and Go primitives. However, there are no actual limitations keeping it from being extended for any other language, pushing forward cross compatibility and interoperability through different stacks.

Modules that implement the interface

Send in a PR if you find or write one!


Include this badge in your readme if you make a new module that implements interface-ipfs-core API.

[![IPFS Core API Compatible](https://cdn.rawgit.com/ipfs/interface-ipfs-core/master/img/badge.svg)](https://github.com/ipfs/interface-ipfs-core)


In JavaScript land:

npm install interface-ipfs-core

In Go land:

# Not available



Install interface-ipfs-core as one of the dependencies of your project and as a test file. Then, using mocha (for Node.js) or a test runner with compatible API, do:

const tests = require('interface-ipfs-core')

// Create common setup and teardown
const createCommon = () => ({
  // Do some setup common to all tests
  setup (cb) {
    // Must call back with an "IPFS factory", an object with a `spawnNode` method
    cb(null, {
      // Use ipfsd-ctl or other to spawn an IPFS node for testing
      spawnNode (cb) { /* ... */ }
  // Dispose of nodes created by the IPFS factory and any other teardown
  teardown (cb) {

// ...etc. (see js/src/index.js)

Running tests by command


Skipping tests

tests.repo.gc(createCommon, { skip: true }) // pass an options object to skip these tests

// OR, at the subsystem level

// skips ALL the repo.gc tests
tests.repo(createCommon, { skip: ['gc'] })
// skips ALL the object.patch.addLink tests
tests.object(createCommon, { skip: ['patch.addLink'] })
Skipping specific tests
tests.repo.gc(createCommon, { skip: ['should do a thing'] }) // named test(s) to skip

// OR, at the subsystem level

tests.repo(createCommon, { skip: ['should do a thing'] })

Running only some tests

tests.repo.gc(createCommon, { only: true }) // pass an options object to run only these tests

// OR, at the subsystem level

// runs only ALL the repo.gc tests
tests.repo(createCommon, { only: ['gc'] })
// runs only ALL the object.patch.addLink tests
tests.object(createCommon, { only: ['patch.addLink'] })
Running only specific tests
tests.repo.gc(createCommon, { only: ['should do a thing'] }) // only run these named test(s)

// OR, at the subsystem level

tests.repo(createCommon, { only: ['should do a thing'] })




In order to be considered "valid", an IPFS core implementation must expose the API described in /SPEC. You can also use this loose spec as documentation for consuming the core APIs. Here is an outline of the contents of that directory:


Feel free to join in. All welcome. Open an issue!

This repository falls under the IPFS Code of Conduct.

Want to hack on IPFS?


Copyright (c) Protocol Labs, Inc. under the MIT License. See LICENSE.md for details.