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

existentialburn

v0.1.2

Published

Extract your Claude Code usage stats. Runs 100% locally — your prompts never leave your machine.

Readme

existentialburn

Extract your Claude Code usage stats. Runs 100% locally — your prompts and code never leave your machine. Only token counts, tool calls, timestamps, and model names are extracted.

Quick start

npx existentialburn > upload.json

Then upload at existentialburn.com/upload.

What it extracts

The extractor reads ~/.claude/projects/ JSONL conversation files and outputs structured JSON:

  • Daily aggregates — tokens, cost, messages, sessions, tool calls, model breakdowns, hourly activity
  • Session details — duration, token counts, models used, tool calls, git branch names, subagent spawns
  • Totals — lifetime token/cost/session/message/day counts
  • Metadata — streaks, longest session, tool call breakdown, project count, date range

Note: Git branch names (e.g. fix-acme-billing-bug) are included in session data. If your branch names contain sensitive information, review the output before uploading.

What it does NOT extract

  • Prompt content or conversation text
  • Code snippets or file contents
  • Tool call arguments or parameters
  • Images or binary data
  • Any personally identifiable information beyond usage patterns

Programmatic usage

import { extract } from "existentialburn";

const data = extract();
console.log(`$${data.totals.totalCost.toFixed(2)} across ${data.totals.totalSessions} sessions`);

Custom directory

const data = extract({ claudeDir: "/path/to/claude/projects" });

Output format

{
  "version": 1,
  "extractedAt": "2026-03-15T...",
  "daily": [{ "date": "2026-03-14", "totalCost": 12.50, ... }],
  "sessions": [{ "id": "...", "durationMs": 3600000, ... }],
  "totals": { "totalCost": 450.00, "totalSessions": 200, ... },
  "meta": { "longestStreak": 14, "subagentSpawns": 42, ... }
}

Requirements

  • Node.js 18+
  • Claude Code installed (~/.claude/projects/ must exist)

Platform support

  • macOS / Linux — fully supported
  • Windows — should work (uses os.homedir() and path.join() for cross-platform paths), but Claude Code on Windows may store data in a different location. If extraction fails, try passing a custom directory: extract({ claudeDir: "C:\\Users\\you\\.claude\\projects" })

License

MIT