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

clawbacus

v0.1.1

Published

Answer whether local Claude Code usage is likely to exceed your plan's included amount.

Vulnerabilities

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

Links

Maintainers

choltzcholtz

Keywords

Readme

Clawbacus

Small Bun CLI that reads local Claude Code JSONL session logs and answers whether the current period is likely to exceed your plan's included amount.

bunx clawbacus

Or from a local checkout:

bun run src/cli.ts
bun run src/cli.ts --threshold 200
bun run src/cli.ts --since 2026-05-01 --until 2026-05-31
bun run src/cli.ts --json
bun run demo

By default it scans ~/.claude/projects/**/*.jsonl, uses the current calendar month, and compares projected monthly API-equivalent spend against the detected plan limit: $20 for Pro, $100 for Max 5x, $200 for Max 20x, $20/seat for Team Standard, $100/seat for Team Premium, and always safe for API auth.

The default output answers the main question directly:

Would I have to pay more?
⚠️  WARNING
Your Max 20x plan includes $200.00. You have used $194.37 this month and are projected to finish at $478.20, so you would pay about $278.20 extra.

Preview the display states without scanning local Claude logs:

bun run demo          # safe, safe2, warning, and danger
bun run demo:safe
bun run demo:safe2    # on a plan, projected under the included amount
bun run demo:warning
bun run demo:danger

Package smoke test:

bun run smoke:bunx

Publish when ready:

bun pm pack --dry-run
npm publish

Notes:

  • The tool only reads local usage metadata from assistant entries. It does not send prompts or transcripts anywhere.
  • Costs are estimates based on Anthropic API token pricing, including cache reads, 5-minute cache writes, 1-hour cache writes when present in Claude Code logs, Opus fast mode, US inference multipliers for supported models, and web search request charges.
  • It does not estimate subscription-plan limits, credits, negotiated discounts, taxes, or server-side tool runtime charges that are not represented in local token usage.