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

dockeridoo

v0.0.10

Published

![Dockeridoo Mascot](https://raw.githubusercontent.com/FalkZ/dockeridoo/main/dockeridoo.png)

Readme

Dockeridoo

Dockeridoo Mascot

The "easiest" way to run docker images as cli tools.

Motivation

I wanted to create an simple tool to run as a cli tool. The main problem was, that I ran my tool on ARM architecture and wanted to run it on x86 as well. The cross compilation was quite straight forward, with the docker cli:

docker buildx build --platform linux/amd64,linux/arm64 ...

The main problem was, that I wanted other people to use my tool and the default way to run a docker image requires the following steps:

  1. Start Docker Deamon
  2. Pull a current Image
  3. Run the Image and attach the current working directory as a volume

This is quite a lot of steps for a simple cli tool. Thats why I created this tool to run docker images with as little friction as possible.

Usage

  1. Prerequirements
    • Docker
    • NodeJS
  2. Install Dockeridoo:
    # npm
    npm i -g dockeridoo 
  3. Run an docker image as cli tool:
    dodoo [image name]
    # for example
    dodoo fa7k/create-cards

How it works

  1. It detects if docker is already running on your system. If not, it starts the docker deamon.
  2. It pulls the latest image specified in the command.
  3. It runs the image with the current working directory as a volume. And any command line arguments will also be passed to the image.

Create your own Dockeridoo compatible CLI Tool

Dockerfile:

FROM alpine:3.19 # choose a base image (preferably small)

# do whatever you want here

# These 2 lines are important to make the image work with Dockeridoo.
# The directory you started Dockeridoo will be supplied as the volume /workdir 
# This way files from the host system can be accessed inside the container
VOLUME /workdir
WORKDIR /workdir

ENTRYPOINT ["your_cli_tool.sh"]

If you want your cli tool to be compatible across achitectures, you can use the following command to build your image:

docker buildx build --platform linux/amd64,linux/arm64 -t your_image_name .

Hint: make sure your base image was also built for multiple architectures 😉