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

doxray-app

v0.2.3

Published

X-ray for your Claude Code sessions — open a readable report (conversation, tokens, estimated cost, tools) in your browser. 100% local.

Readme

doxray

X-ray for your Claude Code sessions. Open a readable report — conversation, tokens, estimated cost and tool usage — straight from your .jsonl session files. Everything is parsed locally: your data never leaves your machine.

Two ways to use it

1. Web (no install)

Go to doxray.app and drag a session file (~/.claude/projects/<project>/*.jsonl) onto the page.

2. CLI

Run it inside any project you've used with Claude Code:

npx doxray-app

(Install it globally with npm i -g doxray-app and the command becomes just doxray.)

It finds that project's sessions, lets you pick one, and opens the report in your browser (served locally on 127.0.0.1, nothing uploaded).

doxray            # interactive list of the project's sessions
doxray --latest   # open the most recent session
doxray <id|n>     # open a specific session (by id or list number)

Requires Node 18+.

How it finds your sessions

Claude Code stores sessions under ~/.claude/projects/<slug>/, where <slug> is the working directory with non-alphanumeric characters replaced by -. doxray derives the slug from your current directory and reads the matching folder.

"Estimated cost"

On a flat-rate Pro/Max plan you never see what a session is worth. doxray multiplies the tokens in your log by Anthropic's public API list prices to estimate it. It's a reference figure, not a bill.

Development

npm install
npm run dev      # hot-reload dev server
npm run build    # production build into dist/

The CLI (bin/doxray.mjs) serves the built dist/ plus the chosen session over a tiny local server, then opens the browser at /?local=1 (the app auto-loads the session).

Privacy

100% local. The web app reads files with the browser File API; the CLI serves them from 127.0.0.1. No uploads, no account.