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

kensaku

v0.3.1

Published

CLI to pin GitHub Actions uses references to commit SHAs.

Readme

kensaku

日本語版はこちら

kensaku is a CLI that scans GitHub Actions uses: entries and shows or applies updates that pin action references to commit SHAs.

Installation

npm install -g kensaku
pnpm add -g kensaku
bun add -g kensaku

Usage

kensaku check
kensaku fix
kensaku -v / --version

By default, it scans .github/workflows/**/*.yml and .github/workflows/**/*.yaml under the current directory.

kensaku check --path ".github/workflows/release.yml"
kensaku fix --path ".github/workflows/*.yml"

help command

kensaku -h
Usage: node --experimental-strip-types ./src/cli.ts <check|fix> [options]

Options:
  --path <glob>       Workflow glob to scan
  --root <dir>        Root directory to scan
  --repo <owner/name> Reserved for future use
  --major-only        Only update major tags like v4 (default)
  --no-major-only     Allow non-major refs such as v4.2.1

For local development:

npm run build
node ./dist/cli.js check

Behavior

  • Detects owner/repo@ref entries such as actions/checkout@v4
  • Ignores docker://... and ./...
  • If an action is already pinned like @sha # v4, it uses the comment as the source ref for refreshes
  • --major-only is enabled by default, so only major tags like v4 are updated automatically

check command

kensaku check

.github\workflows\ci.yml:17
  action: actions/checkout
  target: v5
  current: v5
  latest: 93cb6efe18208431cddfb8368fd83d5badbf9bfd
  replace: uses: actions/checkout@v5
  with:    uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5

.github\workflows\ci.yml:51
  action: oven-sh/setup-bun
  target: v2
  current: v2
  latest: 0c5077e51419868618aeaa5fe8019c62421857d6
  replace: uses: oven-sh/setup-bun@v2
  with:    uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # v2

fix command

before

steps:
  - name: Checkout code
    uses: actions/checkout@v5
    with:
      fetch-depth: 0

  - name: Setup Bun
    uses: oven-sh/setup-bun@v2
    with:
      bun-version: latest
kensaku fix

after

steps:
      - name: Checkout code
        uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5
        with:
          fetch-depth: 0

      - name: Setup Bun
        uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # v2
        with:
          bun-version: latest

Authentication

GitHub API resolution uses GITHUB_TOKEN or GH_TOKEN when available. It can run without a token, but you are more likely to hit rate limits.

Adjust name and version in package.json before publishing.