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

@rjmunhoz/docker-registry-explorer

v0.1.3

Published

Simple docker registry explorer

Readme

docker-registry-explorer

Enormously simple blessed based cli tool to show repositories and tags available on a given docker registry server

Usage

  • install from npm (or yarn, or pnpm etc)
npm i -g @rjmunhoz/docker-registry-explorer
  • run
drxplore
  • use the up and down arrow keys to change repositories, hit enter (or return) to select a repositry and load its tags

Environment variables

Don't add the /v2/ suffix to the URL address. You MUST add http or https to the regisry URL

If you don't want to fill the registry's login, password and url every time you open this application, you can set the enviroment variables described in the sample .envrc.sample. They're all strings and their names are pretty self explanatory.

If you insert anything wrong in the prompts or environment variables, the app will crash and you'll have to kill the terminal session. I'll fix that soon (or, see I think something should be different)

If you don't know how to set an environment variable, check this link

Running from source

  • clone this
git clone https://github.com/rjmunhoz/docker-registry-explorer.git
  • go into the newly created folder
cd docker-registry-explorer
  • build it
npm run build
  • Run it
node dist/index.js

I think something should be different

Well, isn't open source beautiful? PRs are totally welcome and desired :)

PS: If it's a bug and you think it's my fault, issue me and I'll try to solve it ASAP