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

docker-registry-server

v2.2.0

Published

docker registry server implemented in node

Readme

docker-registry-server

Docker registry implemented in Node.

npm install -g docker-registry-server

You can also pull the docker image

docker pull mafintosh/docker-registry-server

Usage

To start it run

docker-registry-server

Currently data will be stored in ./layers and ./db. For more info run docker-registry-server --help

Authentication

Per default there is no authentication (meaning everyone can push/pull images). You can use the --user command line option to limit registry access.

docker-registry-server --user mafintosh:secret --user another:hunter2

Hooks

Similar to a git repository you can specify hooks that are executed when certain events happen. Currently the following hooks are supported

  • tag (id, tag) Triggered when an image is tagged (happens when you push a tagged image)
  • image (id) Triggered when an image metadata is uploaded
  • layer (id) Triggered when an image layer is uploaded
  • verify (id) Triggered when an image layer+metadata has been verified
  • index (id) Triggered when an image file system data has been indexed

The tag hook is especially useful as it allows you to set up a push->deploy flow.

To add a hook specify it as a command line argument prefixed with --on-{name} {bash-script}

docker-registry-server --on-tag "echo image \$1 was tagged with \$2 - please deploy"

Or add them in a ./hooks/{name} file

APIs

The registry should support all of the APIs specified in the docker docs. In addition, the following APIs are available

GET /v1/images/{id}/tree/{directory}

Returns a JSON array containing the files/folders in {directory} in the image {id}. Fx if you have an image, 4a21b50675ba611ab0e9236c4f9430348d932ea3bf6e9b2af86b47eca9088320 and you want to list the files in /root do

curl localhost:8000/v1/images/4a21b50675ba611ab0e9236c4f9430348d932ea3bf6e9b2af86b47eca9088320/tree/root

GET /v1/images/{id}/blobs/{filename}

Get the file content of {filename} in the image {id}. Fx if you have the same image as above and want to read /root/package.json do

curl localhost:8000/v1/images/4a21b50675ba611ab0e9236c4f9430348d932ea3bf6e9b2af86b47eca9088320/tree/root/package.json

GET /v1/events

Get a newline delimited JSON stream on events from the registry. Use type={name} to limit the events you get.

curl localhost:8000/v1/events?type=tag

License

MIT