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

mytokenuse

v0.1.3

Published

Publish local ccusage snapshots to mytokenuse.dev.

Downloads

25

Readme

mytokenuse

Publish local ccusage snapshots to mytokenuse.dev, then inspect cost and token usage in a private dashboard.

mytokenuse is a small CLI for people who use ccusage and want a shareable, short-lived view of recent LLM usage without wiring up their own storage or dashboard.

Quick Start

npx mytokenuse login
npx mytokenuse publish

The first command opens GitHub sign-in and stores a publish token locally. The second command collects the last 30 days of local ccusage data, sanitizes it, uploads it to mytokenuse.dev, and opens the dashboard.

Commands

npx mytokenuse status
npx mytokenuse login
npx mytokenuse publish
npx mytokenuse publish --dry-run
npx mytokenuse publish --no-open
npx mytokenuse publish --share
npx mytokenuse snapshots
npx mytokenuse share <snapshot-id>
npx mytokenuse unshare <snapshot-id>
npx mytokenuse delete <snapshot-id>
npx mytokenuse delete --all
npx mytokenuse logout

Global Install

For frequent use:

npm install -g mytokenuse
mytokenuse status
mytokenuse publish

What Gets Uploaded

mytokenuse publish runs bundled ccusage reports for the last 30 days:

ccusage daily --json
ccusage session --json

The CLI keeps only the fields needed for the dashboard, gzip-compresses the sanitized reports, and uploads them through short-lived Vercel Blob upload capabilities minted by mytokenuse.dev.

Snapshots are private by default and expire after 7 days.

Privacy Defaults

  • GitHub sign-in is required before upload.
  • Uploads use account-scoped publish tokens.
  • Local filesystem paths are redacted before upload.
  • Snapshot dashboards are private by default.
  • --share publishes a snapshot as visible to anyone with the dashboard URL.
  • delete removes stored snapshot metadata and uploaded usage data.
  • logout revokes the active publish token and removes local config.

Local config is stored at:

~/.config/mytokenuse/config.json

Dry Run

Preview collection and sanitization without uploading:

npx mytokenuse publish --dry-run

Alternate Server

The CLI defaults to:

https://mytokenuse.dev

For local development or a preview deployment:

MYTOKENUSE_CLI_URL=http://localhost:5173 npx mytokenuse status
MYTOKENUSE_CLI_URL=http://localhost:5173 npx mytokenuse publish --dry-run

Requirements

  • Node.js 20 or newer
  • A GitHub account for sign-in
  • Local ccusage data to publish

The npm package depends on ccusage, so you do not need to install ccusage separately for the CLI to collect reports.

Links