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

@yeasy1003/claude-log

v0.2.0

Published

CLI to quickly surface key info from Claude Code conversation history

Readme

claude-log

A small CLI to quickly surface key info from Claude Code conversation history.

Reads Claude Code session logs directly from ~/.claude/projects/*.jsonl (or $CLAUDE_CONFIG_DIR) and gives you three commands: list, show, search. No web UI, no daemon — just stdout.

Install

# install from npm
npm i -g @yeasy1003/claude-log
cc-log --help

Or build from source:

pnpm install
pnpm build
node dist/cli.js --help

Usage

# List recent sessions (default 20 rows)
cc-log list
cc-log list --since 7d --limit 50
cc-log list --project -Users-you-repo-foo
cc-log list --json

# Show a session by id or short prefix (like git short sha)
cc-log show e2a7d418
cc-log show e2a7d418-8305-406a-b072-d38304964866 --json

# Include intermediate tool calls + their results in the output
cc-log show e2a7d418 --with-tool-output
cc-log show e2a7d418 --with-tool-output --tool-output-limit 500
cc-log show e2a7d418 --with-tool-output --tool-output-limit 0   # no truncation

# Search across queries and assistant conclusions
cc-log search "superpower"
cc-log search "migration" --in conclusions --since 30d

Configuration

The Claude data directory is resolved in this order:

  1. --claude-dir <path> (CLI flag, per-command)
  2. $CLAUDE_CONFIG_DIR environment variable
  3. ~/.claude (default)

What counts as "key info"

For each session, claude-log extracts:

  • User queries — your actual messages, stripping <system-reminder> / <command-*> tags and synthetic interrupt markers
  • Assistant conclusions — the final text each turn (tool calls and reasoning are counted separately)
  • Skills invokedSkill tool calls with their names/args
  • Tool calls (opt-in via --with-tool-output on show) — for each turn, the tool_use calls plus their paired tool_result outputs, with per-result truncation (default 2000 chars; --tool-output-limit 0 disables)
  • Tool usage counts — how many times each tool was used
  • Token totals — input / output / cache-read / cache-create
  • Timing — start, end, duration, message count

Sidechain (subagent) entries are excluded by design.

Development

pnpm install
pnpm typecheck
pnpm test
pnpm build

License

MIT