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

debughub

v1.2.0

Published

Cross-platform CLI tool for agent-agnostic deterministic debug logging

Downloads

300

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

sebherrerabesebherrerabe

Keywords

debuggingagentscursorcli

Readme

DebugHub

A cross-platform CLI tool providing a Cursor-like "Debug Mode" loop for any coding agent (Codex, Claude, etc.), without requiring MCP or complex remote execution setups.

Features

  • Runtime Setup Guide: See docs/RUNTIME_PREREQS.md for installing Java/Go/Python/Rust/PHP/.NET required by helper E2E tests.
  • Agent-Agnostic: Works with any coding assistant capable of modifying files and running basic OS commands.
  • Vendored Runtime Helpers: Small, standalone helpers for TypeScript/Node, Browser TS/JS, Java, Python, Rust, PHP, Go, and C# are installed in .debughub/vendor.
  • Shared HTTP Contract: All helpers follow one event contract (.debughub/vendor/<version>/http/EVENT_CONTRACT.md after debughub install) and submit best-effort HTTP events to the local collector.
  • Deterministic: A MANIFEST.json and strict integrity verification ensures files are not tampered with.
  • Safe and Local: By default, the collector server only binds to 127.0.0.1.

Quick Start

  1. Install inside any repository:
npx debughub install
  1. Start the local collector:
npx debughub start

  1. Read the given sessionId and endpoint. Follow the instructions to configure your environment variables:

    • DEBUGHUB_ENABLED=1
    • DEBUGHUB_SESSION=<sessionId>
    • DEBUGHUB_ENDPOINT=http://127.0.0.1:<port>

  2. Use the helper inside your app code (see .debughub/vendor/<version>).

  3. Run your app and reproduce the issue.

  4. Check logs:

npx debughub tail --n 50

Security Model

  • No network traffic leaves your local machine.
  • No remote code is downloaded at runtime.
  • No eval or shell spawning in helpers.
  • The debughub verify command validates the helper code matches the official SHA-256 signatures.

Commands

  • debughub install: Installs support files to .debughub/.
  • debughub start: Starts the collector server in the background.
  • debughub stop: Stops the background collector.
  • debughub tail: Print the latest recorded events.
  • debughub search "<query>": Search events by text or label.
  • debughub clear: Clears the output log file.
  • debughub verify: Verifies integrity of the vendor code in .debughub/.
  • debughub doctor: Checks installation and system status.