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

rungrep

v0.3.0

Published

Find GitHub workflow runs by partial name

Readme

rungrep

grep for GitHub Actions runs. Find workflow runs by partial name from your terminal.

Ever scrolled through pages of workflow runs looking for that one build? rungrep lets you search by partial name, filter by branch/status/workflow, and get a direct link to open in your browser.

$ rungrep "deploy api" -r myorg/backend -l
NAME                          DATE                   URL
──────────────────────────────────────────────────────────
deploy api to production v3   2/15/2026, 8:22:45 PM  https://github.com/myorg/backend/actions/runs/22041593851

Install

npm install -g rungrep

Quick start

# Find runs matching "deploy" in a repo
rungrep "deploy" -r org/repo

# Get the latest matching run on main
rungrep "deploy" -r org/repo -b main -l

# Filter by workflow and status
rungrep "deploy" -r org/repo -a "CI" -s success

# Top 5 matching runs
rungrep "deploy" -r org/repo -t 5

# Search runs from last 30 days (default: 7d)
rungrep "deploy" -r org/repo --since 30d

# Open latest matching run in browser
rungrep "deploy" -r org/repo -l --open

# JSON output — pipe to jq, use in scripts
rungrep "deploy" -r org/repo -l --json

Auth

Uses GITHUB_TOKEN env var. Falls back to the GitHub CLI (gh auth token) if installed.

Options

rungrep <name> --repo <org/repo> [options]

| Option | Description | |---|---| | <name> | Partial run name to match (required) | | -r, --repo <org/repo> | GitHub repository (required) | | -b, --branch <branch> | Filter by branch | | -a, --action <workflow> | Filter by workflow name | | -s, --status <status> | Filter by run status (see below) | | -t, --top <n> | Return top N matching runs | | -l, --last | Return only the latest match | | --since <duration\|date> | Only search runs newer than duration (7d, 24h, 2w) or date (2026-02-01). Default: 7d | | --open | Open the run in browser (requires exactly one match, or combine with -l) | | --json | Output as JSON | | --debug | Show diagnostic info on stderr |

completed action_required cancelled failure neutral skipped stale success timed_out in_progress queued requested waiting pending

License

MIT