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

@plainworkdigital/pinfix

v0.1.0

Published

Pin GitHub Actions to full commit SHAs and container images to sha256 digests, keeping the version as a comment. Offline check for CI, zero dependencies.

Readme

Pinfix: pin GitHub Actions and Docker images in one step

A tag is a moving label. uses: actions/checkout@v4 and FROM node:22 run whatever their owner points the label at today, and in March 2025 a popular action's tags were moved to malicious code. A full commit SHA or an image digest cannot be moved. GitHub can now require SHA pinning for a whole organisation, so unpinned lines fail the workflow.

Pinfix finds those lines and rewrites them, keeping the version readable:

Dockerfile
  line 1
  - node:22-alpine
  + node:22-alpine@sha256:0a7108bf6c7bf5de370ffb1a3ed6be93d405b43ff159f681a8d18c0e2bc2e402
  line 4
  - ghcr.io/astral-sh/uv:latest
  + ghcr.io/astral-sh/uv:latest@sha256:4a1f3666816dafadd20ceb71eac9a7d56d7ef30279f7d64048519ab901ada336
  line 5
  - mcr.microsoft.com/dotnet/runtime:8.0
  + mcr.microsoft.com/dotnet/runtime:8.0@sha256:60d11c2be381e7f90b8bd984472dd2432933858aba55087d5936980cf2071d5a
3 references would change. Run again with --write to save.

That is real output from running pinfix pin on a three-line Dockerfile (digests are what the registries returned when it was made; tags move, which is the point). For actions the result looks like this:

- uses: actions/checkout@v4
+ uses: actions/checkout@<full 40-character commit SHA>  # v4.4.0

On the command line

npx @plainworkdigital/pinfix check
npx @plainworkdigital/pinfix pin .github/workflows/ci.yml
npx @plainworkdigital/pinfix pin .github/workflows/ci.yml --write

check needs no network and exits 1 when something is unpinned, so it works as a CI step. pin prints what it would change and writes only with --write. If any reference cannot be resolved, --write saves nothing (add --partial to save the ones that did resolve); files are replaced atomically. Set GITHUB_TOKEN to raise GitHub's rate limit.

Options: --actions or --images (only that kind), --json. Outside workflow files only image: is read (a container: main key or image: logo.png in a Jekyll or mkdocs file is ignored).

What it handles

| Where | What gets pinned | |---|---| | .github/workflows/*.yml, action.yml | uses: owner/repo@ref, owner/repo/path@ref, reusable workflows, docker://image | | Dockerfile, Containerfile | FROM image[:tag] (not scratch, earlier stages or $VARIABLES) | | Compose, Kubernetes, workflow services: / container: | image: name[:tag] |

How it resolves: a tag or branch becomes a commit through GitHub's "Get a commit" API (annotated tags resolve to their commit); the version comment is the most specific tag on that commit (v4.4.0 over v4). An image tag becomes the digest the registry reports for that tag; for multi-architecture images that is the index digest, so every platform still works. Registries are asked anonymously.

Pro ($9, one-time key)

Pinning one reference or one file is free and stays free. Pro is for whole repositories and teams:

  • Pin a folder. pinfix pin . --write, or Pin every reference in the workspace in VS Code.
  • Verify. pinfix verify checks that each version comment still resolves to the pinned SHA (a stale comment or a moved tag shows up as drift) and that each pinned image digest is still what its tag points at.
  • Update. pinfix update --write moves pins to the newest release, staying in the same major version unless you pass --major; image digests are refreshed for the same tag.
  • Policy and SARIF. A policy file lists trusted owners and ignore patterns (--policy file.json, or the pinfix.policyFile setting); --format sarif writes SARIF 2.1.0 for code scanning.

Get a key at https://plainworkdigital.com/d20261016a4/ , then run pinfix activate <key> or Pinfix: Enter Pro key in VS Code. The key is checked with one request to Plainwork's licence server and remembered for 10 minutes; offline, the free features keep working.

Privacy

No telemetry. File contents are never sent anywhere: only owner/repo and a tag, or an image name and tag, go to api.github.com or the image's own registry, when you ask for a pin. A repository cannot make Pinfix contact a server on its own: nothing is looked up until you act.

What it cannot do

  • Private repositories and private images (no credentials are used for registries; GitHub uses your token if you provide one).
  • GitHub Enterprise Server, and registries that need a login.
  • References built from variables (FROM $BASE, uses: ${{ ... }}), Helm or Terraform templates: these are skipped and counted, not guessed.
  • A pin proves you run the same bytes tomorrow, not that those bytes are safe. Pinning does not review the action's code.
  • A tag that is moved before you pin it is pinned as moved. Pin from a tag you have already reviewed.