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

drhank

v1.0.0

Published

Dr. Hank - offline Docker build and docker-compose auditor and fixer

Readme

Hank

Hank is an offline Docker build and docker-compose auditor and fixer.

It builds a ghost Docker image, analyzes your Dockerfile and compose config, detects common issues, and writes:

  • report.txt - build log and analysis
  • patches.diff - suggested fixes
  • .drhank.env.template - discovered env var keys to populate

Requirements

  • python3 available on PATH
  • PyYAML installed in the Python environment used by python3
  • Docker daemon available for audit mode

Install via npm

npm install -g drhank

Then from any project root:

drhank audit .
# or static checks only
drhank doctor .

If you call just:

drhank .

it behaves like:

drhank audit .

Install via pip

pip install drhank
drhank audit .

Typical workflow

  1. Run Hank:

    drhank audit .
  2. Inspect artifacts:

    • report.txt
    • patches.diff
    • .drhank.env.template
  3. Create and populate env file:

    cp .drhank.env.template .drhank.env
    $EDITOR .drhank.env
  4. Apply patches:

    patch -p0 < patches.diff
  5. Rebuild with your normal workflow:

    docker compose up --build

Certificate handling

If Hank detects TLS or certificate problems in the build log, it will add:

volumes:
  - ${HANK_CA_DIR:-./certs}:/usr/local/share/ca-certificates/drhank-ca:ro

Place your corporate CA bundle or PEM files in ${HANK_CA_DIR} (default ./certs).

For build-time trust as well as runtime, extend your Dockerfile:

COPY certs /usr/local/share/ca-certificates/drhank-ca
RUN update-ca-certificates