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

@telemetry-dev/stats

v0.1.5

Published

Local web dashboard for token usage across AI coding agents

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aikinslaryeaaikinslaryeaephraimduncanephraimduncan

Keywords

Readme

@telemetry-dev/stats

Local web dashboard for token usage across AI coding agents. One command scans the agent logs on your machine, stores normalized usage in a local SQLite database, and opens a dashboard in your browser. Nothing leaves your machine.

The Telemetry Stats dashboard

Usage

npx @telemetry-dev/stats            # sync, start the dashboard, open browser
npx @telemetry-dev/stats --json     # sync and print stats as JSON
npx @telemetry-dev/stats --sync     # sync and print a summary

Options: --port <n> (default 3847), --host <addr> (default 127.0.0.1), --no-open, --help. A port held by another Telemetry Stats dashboard is reused; a port held by anything else is skipped for the next free one.

Supported agents

Claude Code, Codex CLI (incl. Sakana Fugu), Gemini CLI, OpenCode, Amp, Droid, Pi, Oh My Pi, Qwen CLI, Kimi, Mux, Grok Build, OpenClaw, Prime Agent, Senpi, Kimchi, Reasonix, Gajae-Code, Jcode, Junie, Augment Code, OpenCodeReview, CodeBuddy, WorkBuddy, Cherry Studio, Command Code, DeepSeek Harness, Codebuff, Freebuff, Hermes, Kilo CLI, Goose, Zed, Kiro, Antigravity CLI, MiMo Code, ZCode, Devin CLI, Devin Desktop, Octofriend (incl. Synthetic), Crush, Cline, GitHub Copilot CLI, Roo Code, Kilo, and — via local usage caches — Cursor, Google Antigravity, Trae, Warp/Oz, and MiniMax Code.

Data and privacy

  • Only usage metadata is stored: agent, model, provider, session id, project path, timestamps, token counts, and costs. Never prompts, completions, tool arguments, or credentials.
  • Data lives in the platform data directory (~/Library/Application Support/telemetry-stats on macOS, $XDG_DATA_HOME/telemetry-stats on Linux, %LOCALAPPDATA%\telemetry-stats on Windows).
  • Costs recorded by an agent are kept as reported. Other events are priced from a locally cached models.dev catalog and marked "estimated": exact provider+model first, then an unambiguous model id, then the rate tuple a strict plurality of providers agree on for that model id (aggregators republish delisted first-party models). Unresolved models stay "unpriced" and are never folded into a total silently.

Development

npm install
npm run dev        # vite dev server
npm test           # vitest
npm run typecheck
npm run build      # nitro server + client + headless CLI to .output/
node bin/telemetry-stats.mjs --no-open