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

tokenwise-cli

v0.3.1

Published

The efficiency layer for AI coding spend. Rank yourself by value shipped per dollar — not tokens burned. Open-source CLI; only anonymized aggregates ever leave your machine.

Readme

tokenwise

The efficiency layer for AI coding spend. Stop flexing how much you burned — flex how much you shipped per dollar.

Every AI-coding tracker ranks you by tokens torched, so the "winner" is whoever wasted the most. Tokenwise flips it: one honest score for value shipped per dollar, across Claude Code and Codex.

npx tokenwise-cli

Published as tokenwise-cli on npm; the installed binary is tokenwise (npm i -g tokenwise-cli, then tokenwise).

  tokenwise · efficiency, not waste

  EFFICIENCY SCORE  (local estimate · last 30 days)
  92/100  ████████████████████████

  Cost / commit    $0.41
  Cache hit rate   73%
  Spent            $128.40  (1,204 turns)
  Shipped          312 commits  +18420/-6310 lines

Commands

| Command | What it does | |---|---| | npx tokenwise-cli | Show your spend + efficiency score (default report) | | tokenwise score | Print just your efficiency score | | tokenwise share | Write a shareable card to ./tokenwise-card.svg | | tokenwise submit --handle @you | Preview the exact anonymized aggregate, then post it to the leaderboard |

Options: --days <n> (default 30), --all, --all-projects, --handle <@you>, --json, --dry-run.

Scope: by default the score is for the current repo — usage is scoped (by each session's working directory) to the repo you run it in, so "cost per commit" lines up with that repo's commits. Add --all-projects for your global spend across everything.

submit posts your anonymized aggregate straight to the leaderboard (Supabase PostgREST, anon key bundled). The official score is computed in the database, so nobody can fake it. Use --dry-run to preview without uploading. Self-host by overriding TOKENWISE_SUPABASE_URL / TOKENWISE_SUPABASE_ANON_KEY.

Privacy — this is the whole point

This CLI is open source (MIT) precisely because it touches your most sensitive data: prompts, code, file paths. So you can read it and verify the promise:

Only anonymized numeric aggregates ever leave your machine. Never prompts, never code, never file paths or branch names.

Run tokenwise submit to print the exact JSON that would be uploaded before anything is sent. Project paths appear only as a one-way SHA-256 hash. Cost is computed locally. The leaderboard and card are opt-in.

How it works

  1. Reads local logs from Claude Code (~/.claude/projects/**/*.jsonl), Codex (~/.codex/sessions/**/*.jsonl) and Copilot CLI (~/.copilot/, experimental).
  2. Computes real cost from a bundled pricing table (Claude Code leaves cost out, so we calculate it — including cache-read/creation rates).
  3. Pairs spend with your local git activity (commits, lines kept) to estimate efficiency: cost per merged PR, per kept line, cache reuse.
  4. The official ranked score on the leaderboard is computed server-side from these aggregates (anti-gaming) — the CLI shows a local estimate.

Sources

| Tool | Support | Notes | |---|---|---| | Claude Code | ✅ full | the anchor — local JSONL with token usage | | Codex CLI | ✅ experimental | token tracking only in recent builds | | Copilot CLI | ⚠️ experimental | best-effort local-log parsing; format varies | | Cursor | ❌ not supported | billing is server-side; local data has no token/cost. (Teams: a Cursor Admin-API path is on the roadmap.) |

Copilot/Codex sessions don't record a working directory, so they only count under --all-projects (the per-repo score needs a cwd).

MIT © Bluu — part of tokenwise.dev