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

pr-run

v0.1.28

Published

Run and inspect pull request branches locally with worktrees, env files, Docker, scripts, terminals, and diffs.

Readme

PR-run (Work in progress)

The app made for people who review multiple Pull Requests every day. Think Github PRs + Worktrees integrated into one place.

Publish npm package Version Bump

How to run

PR-run requires Bun.

bunx pr-run@latest

This starts the local backend, serves the browser UI.

Why?

When reading diffs on github isn't enough, you may need to run a PR in your local machine. So you have to:

  • Manually create a worktree.
  • Manually set up a .env
  • Manually start/stop docker containers. And when testing PRs e2e (like a web app pointing to an API) you have to make sure everything is working right.

I don't know if someone already solved this problem, but I lost so much time doing this manually that I decided to create my own solution.

Dependencies

GitHub CLI (gh), Docker, and editor CLIs are optional and are only needed for the workflows that use them.

This project copies a lot of things from t3code Feel free to open PRs, issues or suggest features. This is my first serious open source project :)

Documentation