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

ccwatts

v0.2.0

Published

Estimate the electricity your Claude Code usage consumes.

Readme

ccwatts

See how much electricity your AI coding uses. ccwatts reads the logs Claude Code already keeps on your machine and turns token counts into an electricity estimate, always as a range with sourced assumptions.

npx ccwatts                # your last 30 days
npx ccwatts --by project   # also: model, day, type
npx ccwatts history        # weekly trend, survives log cleanup
npx ccwatts receipt        # share line and card
npx ccwatts dashboard      # offline HTML dashboard
npx ccwatts pace --demo    # work rhythm (opt-in): active hours, past 10pm, days off
npx ccwatts --method       # every parameter and its source
npx ccwatts --demo         # no Claude Code logs yet? try synthetic sample data
npx ccwatts help           # every command and option

Let Claude Code ask it directly, as a local MCP server on stdio (no port, no network):

claude mcp add ccwatts -- npx -y ccwatts mcp

Then ask "how much energy did my sessions use this week?". Tools: energy_summary, energy_by_project, energy_weekly, methodology.

  • Local only. No network calls, no accounts, no telemetry. It reads token counts, never prompt or response text.
  • Pace is opt-in. ccwatts pace keeps ~/.ccwatts/pace.jsonl (daily minutes and whole hours only), created only when you run it. Delete it any time. It is never shared unless you pass receipt --share-pace.
  • Ranges, not false precision. Every number shows a low–high range and the method version.
  • No runtime dependencies. Everything, including the MCP SDK, is bundled. Node 22+.

Try it in your browser first, on sample data: https://chaseholroyd.com/ccwatts/

Methodology, source and screenshots: https://github.com/holroydchase-afk/ccwatts

MIT license. The methodology and parameters are CC BY 4.0.