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

@jaobrown/clog

v0.4.0

Published

Track and share your Claude Code usage

Readme

 ██████╗██╗      ██████╗  ██████╗
██╔════╝██║     ██╔═══██╗██╔════╝
██║     ██║     ██║   ██║██║  ███╗
██║     ██║     ██║   ██║██║   ██║
╚██████╗███████╗╚██████╔╝╚██████╔╝
 ╚═════╝╚══════╝ ╚═════╝  ╚═════╝

Track and share your Claude Code usage.

Clog parses your local Claude Code sessions and gives you stats on sessions, duration, tokens, and projects. Optionally sync to a public GitHub repo to share your coding activity.

Requirements

Usage

View local stats

npx @jaobrown/clog
# or
npx @jaobrown/clog stats

Shows a summary of your Claude Code usage:

  • Total sessions, duration, and tokens
  • Project count and current streak
  • Top 5 projects by time spent
  • Recent sessions

Initialize GitHub sync

npx @jaobrown/clog init

Creates a public GitHub repository to sync your stats. You'll be prompted for:

  • GitHub username
  • Repository name (default: clog)
  • Local repo path (default: ~/.clog/repo)

Sync to GitHub

npx @jaobrown/clog sync

Parses your sessions and pushes updated stats to your GitHub repo. The repo includes:

  • data/latest.json - Public profile payload (summary, activity, project/session metadata used by clog.sh)
  • README.md - Formatted stats display

Redact sensitive projects

npx @jaobrown/clog redact [path]

# Examples: `npx @jaobrown/clog redact my-app` or `npx @jaobrown/clog redact /Users/you/code/my-app`

Marks a directory as redacted (defaults to the current directory). Redacted projects still count toward totals, but their project name and session titles are hidden everywhere clog syncs data:

  • Project name: top secret
  • Session title: **********

Tip: Redaction matches by full path, project name, or basename. If you used a path under ~/.claude/projects/, use the real project directory (for example /Users/you/code/my-app) or just the project name (npx @jaobrown redact my-app).

How it works

clog reads Claude Code session files from ~/.claude/projects/. Each session includes:

  • Session title and timestamp
  • Duration
  • Token usage (input, output, cache)
  • Git branch and model used
  • Subagent activity

When syncing to GitHub, clog publishes only profile/leaderboard data:

  • Summary totals and daily activity
  • Project names and session titles/timestamps/durations
  • Aggregated token usage, tool usage, and model breakdown

It does not publish local project paths, per-session git branches/model IDs, message counts, or conversation content.

Data storage

  • Claude Code sessions: ~/.claude/projects/
  • clog config: ~/.claude/clog.json
  • Sync repo (default): ~/.clog/repo/

FAQ

Can I redact sensitive data?
Yes. Use npx @jaobrown/clog redact [path] to hide a project’s name and session titles in clog stats, the README, and latest.json. You can redact as many projects as you need.

License

MIT