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

codewhy

v0.1.1

Published

Git-native AI coding history: explain why code exists, what changed it, and which tests protect it

Readme

What it does

CodeWhy records redacted AI coding-session evidence so you can trace a file, line, feature, or commit back to the agent session that changed it—including intent, checks, risks, and later interactions.

  • Works with Codex, Claude Code, Gemini CLI, OpenCode, and Cursor
  • Keeps private runtime data under .git; shareable records live under .codewhy
  • Answers locally by default, with optional BYOK synthesis

Install

npm install -g codewhy
cd your-git-repository
codewhy init
codewhy setup all

Example

codewhy file src/auth/session.ts
codewhy why src/auth/session.ts:42
codewhy ask src/auth/session.ts "What changed, why, and which tests passed?" --local

Answers cite their evidence with session, commit, check, and risk references instead of inferring intent from code alone.

Use codewhy --json <command> for automation. Run codewhy --help for the complete command list.

Learn more

GitHub · Operations and privacy · Issues · Core library

MIT © CodeWhy contributors