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

tokenbroke

v0.1.12

Published

Are you tokenbroke? Prove it. Reads your local Codex CLI / Claude Code usage and ranks you on the leaderboard of the most rate-limited developers alive.

Readme

tokenbroke

Are you tokenbroke? Prove it.

npx tokenbroke

Five seconds. No signup. It reads the usage / rate-limit state your AI coding tools already keep on your machine, files it — signed, under a name like starving-crab-42 — and prints your rank among the most rate-limited developers alive, plus the state of the nation.

The board: tokenbroke.lol

Before you run a stranger's CLI (good instinct)

This package is MIT open source: github.com/SnehanChakravarthi/tokenbroke

  • Every filesystem access goes through one allowlist-enforcing layer (src/readers/access.ts). Paths not on the allowlist cannot be opened; symlinks and hardlinks are rejected before reading.
  • It never reads your code, prompts, conversations, or credentials. Credential files (~/.codex/auth.json, ~/.claude/.credentials.json) are never opened. Where a mixed file must be read (~/.claude.json), only allowlisted usage fields are extracted; the rest is discarded.
  • Zero runtime dependencies. What you installed is one bundled file — read it right here in the tarball (dist/index.js), it's the exact code npx executes.
  • It submits only when you run it. The keep-fresh hook is opt-in (the CLI asks first); uninstalling it is deleting two lines from your tool's config.

What it does

  1. Detects Claude Code and/or Codex CLI and reads their local usage / rate-limit state. One tool missing or partial data is normal, not an error.
  2. Submits one signed snapshot. Re-running updates your row — re-running is the ritual.
  3. Prints the receipt: your rank, your roast, the collective misery, and a claim URL. Claiming (GitHub OAuth, optional) puts your name and face on your row. You never have to.

Stance

tokenbroke is an unaffiliated parody and community tool — not endorsed by, associated with, or speaking for OpenAI or Anthropic. The bit is affectionate. The data is serious.