Skip to content
Community Owned JavaScript Registry
Clojure Shell Dockerfile
Branch: master
Clone or download
victorb Remove `ipfs` to start daemon
License: MIT
Signed-off-by: Victor Bjelkholm <>
Latest commit f9fc8c5 May 24, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Add docs about new public dashboard May 8, 2019
infra Remove `ipfs` to start daemon May 24, 2019
logos Add logos + script for generating logos Apr 17, 2019
scripts Add logos + script for generating logos Apr 17, 2019
src/open_registry Handle errors from npm-registry-follow better May 20, 2019
test/open_registry Initial commit Apr 11, 2019
work-logs/2019 Add work-log for week 19 May 15, 2019
.dockerignore Add .dockerignore May 9, 2019
.gitignore Full system in docker-compose Apr 23, 2019 Initial commit Apr 11, 2019
Dockerfile Right layer for cache + correct docker name May 16, 2019
LICENSE Initial commit Apr 11, 2019
docker-compose.yml Run ipfs daemon with `--offline` in development May 20, 2019
mkdocs.yml Fix formatting issues + add to links of docs Apr 26, 2019
project.clj Handle errors from npm-registry-follow better May 20, 2019

Open-Registry Logo

Open-Registry - Open JavaScript Module Registry


Preliminary npm proxy:

LiberaPay for donations:

A user-focused registry of JavaScript libraries used, organized and funded by the community

Features of Open-Registry

  • Serves a mirror of the npm Registry (
  • Community funded
  • Governed by the community
  • Sole focus on providing a library registry

Try it out

Wanna see how it's performing? You can try it out by using as the registry config in your preferred client.

# npm
npm config set registry

# yarn
yarn config set registry

Why Open-Registry?

Rather than relying on private, for-profit companies to host all of our programing libraries (such as npm Inc hosting the npm Registry), we should move towards a different model where the stability and durability of the registry does not depend on a company but the community who is the user of the registry.

If we as a community can come together and fund our own registry, we'll have full control of what the registry should be and how long we can make it last.

The initial idea is to setup a full mirror of npm and serve it to the public.

All the metrics will be public and viewable by anyone, and same with the data in the registry itself.

This will of course need to be paid for, which will also be public. All the payments and bills that will occur because of Open-Registry, will be publicly trackable, and also the income which will be by donations.

So, it's time for developers to put their money where their mouth is, and start prove that a self-organizing community can self-care about it's needs.

Metrics Interface

What would you want to know?

  • Number of instances for hosting
  • How many errors are happening currently?
  • How many packages is the registry serving currently?
  • How many of those are cached?
  • How far back are we from the npm registry?

Some Handy Links

You can’t perform that action at this time.