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

debugpatch-bridge

v0.1.0

Published

Local bridge for pairing a developer machine with DebugPatch and local Codex workflows.

Readme

DebugPatch Bridge

Local Node bridge for pairing a developer machine with DebugPatch.

Install

npm install -g debugpatch-bridge

Or run without installing:

npx debugpatch-bridge pair --server http://localhost:3000 --code DPB1-2345

How pairing verifies the project

Run the pairing command from inside the repository selected in DebugPatch.

The bridge runs:

git rev-parse --show-toplevel
git remote get-url origin
git branch --show-current

Then it normalizes the GitHub remote to owner/repo and sends a SHA-256 fingerprint of that repository to DebugPatch. The server only accepts the pairing if the fingerprint matches the project repository selected in the web app.

This means VS Code itself is not trusted as the source of truth. The Git repository under the terminal is.

Commands

debugpatch-bridge pair --server http://localhost:3000 --code DPB1-2345
debugpatch-bridge heartbeat
debugpatch-bridge status

Codex integration TODO

The next step is adding a job loop:

debugpatch-bridge run

That loop will poll DebugPatch for local jobs, write DEBUGPATCH_TASK.md, run codex exec, stream logs back, and push the isolated run branch for developer review.