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

claude-burn-rate

v1.2.0

Published

Privacy-first CLI dashboard for Claude Code usage analytics

Readme

Quick Start

npx claude-burn-rate

A browser dashboard opens at localhost:3456 with your full usage analytics. No API keys, no config, no setup.

To install globally:

npm install -g claude-burn-rate

Features

Overview

Summary cards for total cost, sessions, messages, and tool calls. Daily activity charts, token composition breakdown, cost by model, and key insights — all at a glance.

Usage Analytics

Sessions — Searchable, sortable table of every session with date, project, summary, message count, estimated cost, and duration.

Projects — Per-project cost and usage breakdown with bar charts, a leaderboard, and branch-level cost analysis.

Patterns — Usage heatmap by hour of day, peak hours chart, and week-over-week comparisons. See when you're most productive (or most expensive).

Tool Usage — Breakdown of every tool Claude invoked across your sessions.

Insights & Gamification

Efficiency Score — A composite score based on cache hit rates, model selection, and cost concentration.

Achievements — Unlock badges as you hit milestones: First $100, Cache Master, Night Owl, and more.

Streaks — Track consecutive days of Claude Code usage.

Expensive Prompts — Find your costliest individual prompts across all sessions with per-prompt token breakdowns and optimization tips.

Contributions — Lines written, lines edited, files touched, and co-authored git commits. See which files Claude edits most.

Security Audit

A complete audit of everything Claude accessed during your sessions:

  • Risk Posture Score — Overall security rating based on sensitive file access, dangerous commands, and out-of-scope activity
  • Secret Detection — Flags bearer tokens, API keys (OpenAI, AWS, GitHub, Atlassian), passwords, and credentials found in commands
  • Dangerous Sessions — Sessions with the highest concentration of risky operations
  • MCP Risk Analysis — Identifies high-risk Model Context Protocol server activity
  • File Access Log — Every file read, written, or edited, with sensitive path highlighting
  • Bash Command Log — Commands categorized as destructive, permission changes, network, package managers, or safe
  • Directory Scope Map — In-project vs out-of-project access, with flags on out-of-scope paths

Light & Dark Theme

Toggle between light and dark mode from the header. Your preference is saved across sessions.


CLI Reference

claude-burn-rate              # Open browser dashboard (default)
claude-burn-rate --summary    # Quick terminal summary
claude-burn-rate --export csv # Export data (json|csv|markdown)

| Flag | Short | Description | |------|-------|-------------| | --port <port> | -p | Server port (default: 3456) | | --summary | -s | Print terminal summary and exit | | --export <fmt> | -e | Export as json, csv, or markdown | | --watch | -w | Watch mode with live updates | | --help | -h | Show help |

Terminal Summary

$ claude-burn-rate --summary

──────────────────────────────────────────────────
  claude-burn-rate — Usage Summary
──────────────────────────────────────────────────

  Total Estimated Cost:  $142.58
  Active Days:           12
  Avg Cost/Day:          $11.88

  Sessions:              34
  Messages:              4,210
  Tool Calls:            891

──────────────────────────────────────────────────

Exports

# JSON — pipe into jq, scripts, or other tools
claude-burn-rate --export json > usage.json

# CSV — open in Excel, Google Sheets, etc.
claude-burn-rate --export csv > sessions.csv

# Markdown — paste into docs, PRs, or Notion
claude-burn-rate --export markdown > report.md

Filtering

All dashboard tabs support filtering by date range and project.


How It Works

claude-burn-rate reads the JSONL session files from ~/.claude/projects/ that Claude Code already creates on your machine. It parses token usage, tool calls, timestamps, and model identifiers, then computes costs using Anthropic's published pricing.

Supported models: Opus 4.5/4.6, Sonnet 4.5/4.6, Haiku 4.5 — with automatic fallback pricing for unknown models.

Requirements: Node.js 18+. No dependencies beyond one small package (open).


Privacy

claude-burn-rate is designed to be fully offline:

  • No network requests — the dashboard is served locally and reads only local files
  • No telemetry — no usage tracking, analytics, or crash reporting
  • No data collection — nothing is sent anywhere, ever
  • No API keys required — everything is computed from files already on your machine

Your data never leaves your machine. You can verify this — the package has a single dependency (open, for launching the browser) and makes zero HTTP calls.


License

MIT