Skip to content
Community Owned JavaScript Registry
Branch: master
Clone or download
victorb Increase go-ipfs connection manager values
License: MIT
Signed-off-by: Victor Bjelkholm <git@victor.earth>
Latest commit a0a944b May 20, 2019

README.md

Open-Registry Logo

Open-Registry - Open JavaScript Module Registry

Website: https://open-registry.dev

Preliminary npm proxy: https://npm.open-registry.dev

LiberaPay for donations: https://liberapay.com/open-registry-community

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 (npm.open-registry.dev)
  • 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 https://npm.open-registry.dev as the registry config in your preferred client.

# npm
npm config set registry https://npm.open-registry.dev

# yarn
yarn config set registry https://npm.open-registry.dev

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.