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

@blnayan/token-burn

v0.1.15

Published

CLI for syncing Claude Code and Codex usage to Token Burn.

Downloads

1,550

Readme

Token Burn CLI

Sync local Claude Code and Codex usage totals to a Token Burn leaderboard.

Quick Start

Requires Node.js 24 LTS or newer.

npx @blnayan/token-burn@latest setup

setup prints a login approval URL, waits for approval, runs the first sync, and installs automatic sync.

You can still install the CLI globally if you prefer:

npm install -g @blnayan/token-burn
token-burn setup

Commands

Command names are shown as token-burn; use npx @blnayan/token-burn@latest <command> for no-install usage, or run them after a global install.

  • token-burn setup authenticates, syncs once, and installs automatic sync.
  • token-burn login authenticates the CLI with https://tokenburn.nayanbhut.dev.
  • token-burn login --server-url <url> authenticates with another Token Burn server.
  • token-burn sync sends aggregate usage totals.
  • token-burn status shows auth and last sync state.
  • token-burn scheduler install installs automatic sync.
  • token-burn scheduler install --dry-run previews scheduler changes.
  • token-burn scheduler uninstall removes automatic sync.
  • token-burn install-scheduler and token-burn uninstall-scheduler remain available as compatibility aliases.

Output Modes

  • Interactive terminals use rich Clean Operator output by default.
  • Non-TTY output, cron, CI, and NO_COLOR use plain output.
  • Use --plain for log-safe human text.
  • Use --json for machine-readable output where supported.
  • Use --no-color to keep rich layout without ANSI color.

Privacy

Token Burn syncs aggregate daily usage only.

Stored by Token Burn:

  • Daily aggregate token totals
  • Provider name
  • Model names when ccusage reports them
  • Token categories such as input, output, cache creation, and cache read
  • Reasoning output token details when reported
  • Cost estimates when ccusage reports them
  • Device name, OS, CLI version, ccusage version, and sync timestamp

Not stored by Token Burn:

  • Prompts
  • Raw conversation text
  • Project paths or file paths
  • Session IDs
  • Raw ccusage rows
  • GitHub OAuth tokens
  • Raw CLI tokens

Leaderboard periods use UTC boundaries. "Today" means the current UTC date.

If sync reports that the ccusage native binary is not executable after a global npm install, do not run token-burn sync with sudo; root has a separate Token Burn config. Reinstall Node/npm in a user-writable environment such as nvm, or fix the native binary execute bit once.