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

@stax.sh/cli

v0.1.0

Published

Audit this project for your AI coding agent.

Readme

@stax.sh/cli

Audit this project for your AI coding agent.

npx @stax.sh/cli                    # one-shot
curl -fsSL stax.sh/install | sh     # install the standalone binary

The CLI inspects your project locally (file system, git history, knowledge files), scores it against the Stax rule set, and uploads a redacted snapshot to stax.sh. The qualitative read is handed to your own agent via stax review.

Commands

| Command | What it does | | --- | --- | | stax | inspect + score + upload + show the result in your terminal | | stax review | print the follow-up prompt for your agent | | stax review --copy | copy the follow-up prompt to the clipboard | | stax login | sign in via device-code flow | | stax logout | forget the saved token | | stax doctor | diagnose Node version, network, git availability |

Privacy

Stax never sends snapshots to any LLM provider. Scoring is deterministic and runs on Stax's own servers; the qualitative read happens inside your own coding agent (Claude Code, Cursor, Codex CLI), using the subscription you already pay for.

Secrets, emails, and absolute home paths are redacted before upload.