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

@kenzot25/why-run

v0.1.3

Published

CLI for why-run - trace function calls to understand why they ran

Readme

@kenzot25/why-run

CLI for why-run - trace function calls to understand why they ran.

Installation

npm install -g @kenzot25/why-run

Or use via npx:

npx @kenzot25/why-run <command>

Commands

install-skill

Install the why-run-debugger Claude Code skill to enable AI-powered trace analysis.

why-run install-skill
# or
npx @kenzot25/why-run install-skill

This copies the skill files to ~/.claude/skills/why-run-debugger/, allowing Claude Code to:

  • Debug call chains: "why did fetchUser run?"
  • Analyze performance: "what's slow?"
  • Explain errors: "why did this error happen?"
  • Help understand code: "help me understand this file"

Usage After Installing Skill

Once the skill is installed, open Claude Code and ask:

| Question | What Claude Will Do | | ------------------------- | --------------------------------------------- | | "why did fetchUser run?" | Show ASCII call tree + causal explanation | | "analyze my traces" | Complete analysis with performance breakdown | | "what's slow in my code?" | Highlight slow functions with recommendations | | "debug this error" | Trace error to root cause |

About why-run

why-run is a function call tracing library that helps you understand the causal chain of function execution. See the main repository for full documentation.

License

MIT