npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

np-solo

v0.3.3

Published

Another private node package manager

Readme

np-solo

This is a simple private npm registry. No service dependencies. User registration will be through a config file and now command line. It was designed to work as a scoped private registry so it will not cache public npm service.

To install execute

npm install np-solo -g

To start the registry execute in the directory of your configuration (npsolo.json) file. All paths will be relative to this location.

np-solo

np-solo.json will store all of your configuration settings. Below is a description of the possible settings.

{
  // Which port for the server to bind
  port: 9000,
  // A specifc hostname or ip address to bind
  hostname: undefined,
  // The maximum allowed size of the request body 
  maxRequestSize: '1mb',
  // Allow unauthenticated users, this can also be an object that will have specify 
  // options for read or write.
  // { read: true, write: false }
  allowAnonymous: false,
  // Specifies if there should be a prefix in the express routes.
  // Helpful for reverse proxy instances. It should not end in / unless you know why.
  // ie /npm
  urlPrefix: '',
  // Configure how the registry will store the json and tar files. This can be a plain object
  // that will require default providers (currently only local is supported). You can also require your
  // own class that confirms to the storage contract for specific implementations.
  storageProvider: {
		type: 'local',
		options: {
			dir: './storage'
		}
	},
	// Configure how the registry will authenticate users. Users will typically be stored in the config file.
	authProvider: {
		type: 'simple',
		options: {
			// Which hash algorithm to use when authenticating users. [See Node Docs](https://nodejs.org/api/crypto.html#crypto_crypto_createhash_algorithm)
			hashAlgorithm: 'sha512',
			users: {}
		}
	}
}

Example npsolo.json file:

{
	"authProvider": {
		"options": {
			"users": {
				"test": {
					"password": "ee26b0dd4af7e749aa1a8ee3c10ae9923f618980772e473f8819a5d4940e0db27ac185f8a0e1d5f84f88bc887fd67b143732c304cc5fa9ad8e6f57f50028a8ff",
					"email": "[email protected]",
					"token": "6c84fb90-12c4-11e1-840d-7b25c5ee775a",
					"can": {
						"write": true,
						"read": true
					}
				}
			}
		}
	}
}