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

tokenmaxing

v0.1.0

Published

Terminal AI usage wrapped summary for Claude Code and Codex.

Readme

tokenmaxing

tokenmaxing is a local-only, read-only terminal summary for Claude Code and Codex usage — your AI usage, wrapped.

It scans:

  • Claude Code: ~/.claude (or $CLAUDE_CONFIG_DIR) for usage stats and transcripts, plus project .claude directories under your home directory.
  • Codex: ~/.codex (or $CODEX_HOME).

It renders, one section at a time:

  1. Total messages by source
  2. Per-month token usage
  3. Burn — local spend cache when present, otherwise a clearly marked list-price estimate
  4. All-time token usage
  5. Token usage summary
  6. Input/output token comparison
  7. Model token comparison
  8. Model standing by input + output tokens
  9. Most active time of day (messages per hour)
  10. Daily activity matrix (contribution-graph style)

Every count and token figure comes from locally recorded data. The only estimated values are in the burn panel, marked with ≈.

Run

npx tokenmaxing

Or from a clone:

npm start

In a terminal the report reveals one section at a time, with a [NN/total] progress counter. Each section decodes in with a brief scramble-resolve animation.

  • enter / space / — next section
  • / b — replay the previous section
  • a — show all remaining sections
  • q / ctrl-c — quit

Provider colors are categorical: Claude is orange, Codex is cyan, the combined total is amber — so any bar, model row, or table line maps to its source at a glance.

Piped or redirected output prints everything at once without colors or animation.

Privacy

The CLI reads local metadata and transcripts to compute usage, but the report does not print prompt text, model responses, tool outputs, credentials, or file contents. Nothing leaves your machine — there is no network call anywhere in the tool.