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-human

v1.0.0

Published

What does your human actually do during a Claude Code session? Pure-autonomous vs interactive, follow-up patterns, engagement split.

Downloads

22

Readme

cc-human

What does your human actually do during a Claude Code session?

Measures human presence in your sessions: how often Claude runs purely autonomously vs. how often the human sends follow-up messages, and what kind of messages they send.

Usage

npx cc-human
npx cc-human --json

Or open index.html in a browser and drag in your .jsonl files.

Metrics

  • Pure-autonomous rate — sessions where the human writes only the initial prompt
  • Interactive rate — sessions with follow-up messages
  • Messages per session — median, mean, max
  • Initial prompt length — how much context the human provides upfront
  • Follow-up types — ack (<30c) / direction (30–149c) / correction (150–599c) / briefing (600+c)

What counts as a "human message"?

Only text content in user-role messages. Tool results (tool_result blocks) are excluded — those are Claude's own output coming back, not human input.

Sample output

cc-human — What does your human actually do?

Sessions analyzed: 183

Human engagement split
  ███████████░░░░░░░░░░░░░░░░░░░ 35.5%  pure-autonomous
  ███████████████████░░░░░░░░░░░ 64.5%  interactive

Human messages per session
  median 2 msg  |  mean 6.1  |  max 87

Follow-up message types  (941 total, median 42 chars)
  ack        ██████░░░░░░░░░░░░░░   26%  ok / yes / done
  direction  ██████████████░░░░░░   69%  brief instructions
  correction  ░░░░░░░░░░░░░░░░░░░░   0%  multi-sentence
  briefing   █░░░░░░░░░░░░░░░░░░░   4%  long task dump

License

MIT