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

cc-error

v1.0.0

Published

Which Claude Code tools fail most often? 54% of sessions hit at least one error. WebFetch fails 25% of the time. Track tool failure rates across all your sessions.

Downloads

26

Readme

cc-error

npm version npm downloads

Which Claude Code tools fail most often? Tracks is_error across all tool results to find failure patterns.

npx cc-error

Zero dependencies. Reads ~/.claude/projects/ directly.

Output

cc-error — Tool Failure Rates in Claude Code
====================================================
Sessions: 1,977 | 54.5% hit ≥1 error
Total calls: 143,714 | Errors: 6,444 (4.5% overall)

Error rate by tool (top 10, ≥10 calls):
  WebFetch                 ████████░░░░░░░░░░░░   24.8%  (378/1,523)
  KillShell                ██░░░░░░░░░░░░░░░░░░    8.0%  (2/25)
  Bash                     ██░░░░░░░░░░░░░░░░░░    6.1%  (3330/54,519)
  TaskOutput               ██░░░░░░░░░░░░░░░░░░    5.3%  (44/825)
  Read                     █░░░░░░░░░░░░░░░░░░░    4.2%  (1544/36,664)
  Glob                     █░░░░░░░░░░░░░░░░░░░    3.9%  (109/2,785)
  Edit                     █░░░░░░░░░░░░░░░░░░░    3.5%  (605/17,310)

What it tells you

  • 54% of sessions hit at least one error — errors are the norm, not the exception
  • WebFetch fails 25% of the time — blocked URLs, auth walls, timeouts. 1 in 4 web fetches fails
  • Bash has 6% error rate — across 54K calls, that's 3,300 failed commands
  • Read fails 4% — usually reading a file that doesn't exist yet
  • Edit fails 3.5% — old_string not found in file
  • 4.5% overall error rate means Claude handles ~1 error per 22 tool calls

Flags

npx cc-error          # tool failure rankings
npx cc-error --json   # raw JSON output

Browser version

yurukusa.github.io/cc-error — drag and drop your projects folder.

Part of cc-toolkit — tools for understanding your Claude Code sessions.


Source: yurukusa/cc-error