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

@revealyst/agent

v0.2.1

Published

Revealyst Agent — reads Claude Code session logs, summarizes them locally to metric records (never raw prompt content), pushes via device token.

Readme

revealyst-agent

The Revealyst Agent — the sanctioned local-ingest path for Claude Code (product spec §10). Reads your local Claude Code session logs, summarizes them on your machine into daily metric records, and pushes only those records to Revealyst with a device token.

What leaves your machine — and what never does

Transmitted (the full list — enforced by the privacy test suite):

  • daily counts: sessions, prompts, active days
  • daily token totals (input / output / cache read / cache write)
  • per-model request/token counts (model ids only)
  • estimated spend (public list prices; marked as an estimate)
  • a 24-slot hourly activity histogram + peak session concurrency per day
  • your Claude account email — only if you opt in with --consent-identity; otherwise a one-way device hash

Never transmitted: prompt or completion text, tool inputs/outputs, file contents or paths, session titles, working directories, git branches, session ids. The parser structurally cannot carry these fields (src/parse.ts), and tests/privacy.test.ts proves no content survives into an outgoing payload using sentinel-seeded fixtures.

Usage

revealyst-agent login --token rva1.…  [--api <url>] [--consent-identity]
revealyst-agent sync  [--days 30] [--dry-run]
revealyst-agent status

Create the device token in Revealyst → Connections → Revealyst Agent (it is shown once; re-issuing rotates it). sync --dry-run shows exactly what would be pushed without pushing. Schedule sync daily with Task Scheduler (Windows) or cron if you want hands-off updates.

For CI/headless one-shot runs, sync also honors REVEALYST_TOKEN (and optionally REVEALYST_API) without persisting anything — interactive users should prefer login, which keeps the token out of shell history. An env-supplied token is always device-scoped: identity consent applies only to the login that granted it, never to env runs.

sync pins the pushed window to the earliest day your local logs still cover, so a wide --days lookback can never erase previously-synced days whose logs have since been pruned. If no activity falls inside the window, nothing is pushed (and nothing is deleted).

Log locations scanned: %USERPROFILE%\.claude\projects\ (or ~/.claude/projects/), honoring CLAUDE_CONFIG_DIR (multi-path). Local logs retain ~30 days by default, so backfill depth is bounded by that.

Development

Lives in the Revealyst monorepo; tests run from the repo root (npm test) against recorded-shape fixtures in fixtures/vendor-payloads/claude-code-local/. Dev invocation without a build: npm run agent -- sync --dry-run. Build the distributable CLI: npm run build in this directory (emits dist/, CommonJS, revealyst-agent bin).