Skip to content



Repository files navigation

sinopia2 - a private/caching npm repository server

npm version npm version badge Build Status downloads badge

It allows you to have a local npm registry with zero configuration. You don't have to install and replicate an entire CouchDB database. Sinopia keeps its own small database and, if a package doesn't exist there, it asks for it keeping only those packages you use.

About this fork

First, thanks @rlidwka for this great software.

It is not intended to become the 'official' fork. In fact there are other forks (for example @mathieumg or @ngash) quite active too.

Out fork is internally used at my company, therefore we are going to maintain it in the future.

In this fork I have already merged some relevant PRs:

  • Split travis file in install & script
  • Update README to use fl4re travis badge
  • Travis fix
  • Change to for entries #352
  • Update deps, make compile on Node v4 & 5 #367
  • ADDED intermediate ssl certificate option #379
  • Package search requires 'access' authorization #370

And we have a branch (OAuth_login) that replaces completely the registration/login workflow by Github/Google Oauth instead of plain and open user password. Beside this branch, I plan to maintain the master branch as close as possible to the original sinopia.

If anyone in the community considers our fork a good fork, I will be glad to accept PR.

PRs will be accepted if:

  • fixes some bug
  • fixes random travis failures
  • fixes jslint/jshint styling
  • removes dead code
  • replaces some old library by a newer one
  • refactors
  • add a feature and there is consensus about it (a few +1)

PRs will not be accepted if:

  • modifies the original features
  • adds features only needed by some individual
  • brakes the travis build

Use cases

  1. Use private packages.

    If you want to use all benefits of npm package system in your company without sending all code to the public, and use your private packages just as easy as public ones.

    See using private packages section for details.

  2. Cache registry.

    If you have more than one server you want to install packages on, you might want to use this to decrease latency (presumably "slow" will be connected to only once per package/version) and provide limited failover (if is down, we might still find something useful in the cache).

    See using public packages section for details.

  3. Override public packages.

    If you want to use a modified version of some 3rd-party package (for example, you found a bug, but maintainer didn't accept pull request yet), you can publish your version locally under the same name.

    See override public packages section for details.


# installation and starting (application will create default
# config in config.yaml you can edit later)
$ npm install -g sinopia2
$ sinopia

# npm configuration
$ npm set registry http://localhost:4873/

# if you use HTTPS, add an appropriate CA information
# ("null" means get CA list from OS)
$ npm set ca null

Now you can navigate to http://localhost:4873/ where your local packages will be listed and can be searched.


A Sinopia docker image is available


A Sinopia Chef cookbook is available at Opscode community source:


A Sinopia puppet module is available at puppet forge source:


When you start a server, it auto-creates a config file.

Adding a new user

npm adduser --registry http://localhost:4873/

This will prompt you for user credentials which will be saved on the Sinopia server.

Using private packages

You can add users and manage which users can access which packages.

It is recommended that you define a prefix for your private packages, for example "local", so all your private things will look like this: local-foo. This way you can clearly separate public packages from private ones.

Using public packages from

If some package doesn't exist in the storage, server will try to fetch it from If is down, it serves packages from cache pretending that no other packages exist. Sinopia will download only what's needed (= requested by clients), and this information will be cached, so if client will ask the same thing second time, it can be served without asking for it.

Example: if you successfully request express@3.0.1 from this server once, you'll able to do that again (with all its dependencies) anytime even if is down. But say express@3.0.0 will not be downloaded until it's actually needed by somebody. And if is offline, this server would say that only express@3.0.1 (= only what's in the cache) is published, but nothing else.

Override public packages

If you want to use a modified version of some public package foo, you can just publish it to your local server, so when your type npm install foo, it'll consider installing your version.

There's two options here:

  1. You want to create a separate fork and stop synchronizing with public version.

    If you want to do that, you should modify your configuration file so Sinopia won't make requests regarding this package to npmjs anymore. Add a separate entry for this package to config.yaml and remove npmjs from proxy_access list and restart the server.

    When you publish your package locally, you should probably start with version string higher than existing one, so it won't conflict with existing package in the cache.

  2. You want to temporarily use your version, but return to public one as soon as it's updated.

    In order to avoid version conflicts, you should use a custom pre-release suffix of the next patch version. For example, if a public package has version 0.1.2, you can upload 0.1.3-my-temp-fix. This way your package will be used until its original maintainer updates his public package to 0.1.3.


Sinopia aims to support all features of a standard npm client that make sense to support in private repository. Unfortunately, it isn't always possible.

Basic features:

  • Installing packages (npm install, npm upgrade, etc.) - supported
  • Publishing packages (npm publish) - supported

Advanced package control:

  • Unpublishing packages (npm unpublish) - supported
  • Tagging (npm tag) - not yet supported, should be soon
  • Deprecation (npm deprecate) - not supported

User management:

  • Registering new users (npm adduser {newuser}) - supported
  • Transferring ownership (npm owner add {user} {pkg}) - not supported, sinopia uses its own acl management system

Misc stuff:

  • Searching (npm search) - supported in the browser client but not command line
  • Starring (npm star, npm unstar) - not supported, doesn't make sense in private registry


No CouchDB here. This application is supposed to work with zero configuration, so filesystem is used as a storage.

If you want to use a database instead, ask for it, we'll come up with some kind of a plugin system.

Similar existing things

  • npm + git (I mean, using git+ssh:// dependencies) - most people seem to use this, but it's a terrible idea... npm update doesn't work, can't use git subdirectories this way, etc.
  • reggie - this looks very interesting indeed... I might borrow some code there.
  • shadow-npm, public service - it uses the same code as + service is dead
  • gemfury and others - those are closed-source cloud services, and I'm not in a mood to trust my private code to somebody (security through obscurity yeah!)
  • npm-registry-proxy, npm-delegate, npm-proxy - those are just proxies...
  • Is there something else?


Private npm repository server






No packages published


  • JavaScript 56.7%
  • CSS 41.6%
  • HTML 1.4%
  • Perl 0.3%