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 🙏

© 2026 – Pkg Stats / Ryan Hefner

dockerctl

v0.0.0

Published

A controller for a project's docker containers

Downloads

4

Readme

Docker Controller

This is a small CLI app to make using Docker inside of projects a little easier. I hacked it together in a few spare hours on a Sunday so it's very rough around the edges.

The idea is you install this as a global npm module and then have a docker.json file inside of your project root which describes your images and containers like this:

{
  "directory": "docker/",
  "images": {
    "mgarratt/data": "data/",
    "mgarratt/nginx": "nginx/",
    "mgarratt/php-fpm": "php-fpm/"
  },
  "containers": {
    "data": {
      "name": "data",
      "image": "mgarratt/data",
      "volume": {
        ".": "/data/www:rw",
        "./docker/logs": "/data/logs:rw"
      },
      "detach": true,
      "privileged": true
    },
    "php-fpm": {
      "name": "php-fpm",
      "image": "mgarratt/php-fpm",
      "volumes-from": "data",
      "detach": true,
      "privileged": true
    },
    "nginx": {
      "name": "nginx",
      "image": "mgarratt/nginx",
      "volumes-from": "data",
      "link": "php-fpm:php-fpm",
      "publish": "80:80",
      "detach": true,
      "privileged": true
    }
  }
}

Images are simply named and given a path inside of the main directory, these relative paths are made absolute for use by Docker. Containers are given a name and the options to pass to them when running, things like volumes are converted to absolute paths relative to the cwd, not the directory set in the json file.

The following commands are available:

  • build - create all the images
  • run - run all the containers
  • stop - stop all the containers
  • rm - remove all the containers
  • rmi - remove all the images

Future ideas

In future I will add support for more Docker commands along with being able to enact the command on a single image or container.

Other ideas include things like getting the status of containers and varying useful information such as IP address and ports.