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

pi-meat

v0.1.1

Published

pi extension + CLI that abridges code diffs into reading diffs — review agent-written code at the concept level, not the line level

Readme

meat

Abridge a code diff into a reading diff.

Humans need to review agent-written code in critical systems. But models are good now. You don't need to review for style or nil-checks or imports. You need to review concepts, algorithm choices, architecture.

So meat uses a model to reduce a diff to the important parts. It shows you the meat.

Install with:

go install meat.dev/cmd/meat@latest

Run with meat to review the latest commit. It takes git-looking parameters to pick commits to review.

It takes a while to process a commit for reading. So I suggest you have an agent build meat into your devtools so that it pre-processes it.

Very large diffs are split at file and hunk boundaries and abridged chunk by chunk (up to a few MB), so one huge commit still produces a single merged reading diff — it just takes proportionally longer.

pi extension

This repo is one of those devtools. It is a pi package: the agent gets a meat tool, and you get a /meat command.

pi install npm:pi-meat

The tool takes a commit, a range, -staged, the working tree, or a diff from the agent's context, and returns the reading diff. /meat [target] (default HEAD) drops the reading diff into the session as context, so the agent works from the meat instead of the raw diff.

If meat is not on your PATH the extension builds it once from the Go source bundled in the package (needs Go installed) and caches the binary in ~/.cache/pi-meat. Set MEAT_BIN to use a specific binary.

Inside pi, meat uses the model currently selected in that session, including its resolved API key or OAuth credentials, custom headers, provider settings, and thinking level. The standalone CLI continues to use OPENAI_API_KEY / ANTHROPIC_API_KEY, MEAT_MODEL, and the matching base-URL variables.