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

harness-analyzer

v0.4.0

Published

Local AI harness usage analytics and secure aggregate profile sync

Readme

Harness Analyzer CLI

Collect Claude Code, Codex and other local AI harness usage without uploading raw sessions, prompts, files or project paths.

Install

npm install -g harness-analyzer

Sync the hosted profile

  1. Open https://harness-analyzer.marketmaker.cc/profile.
  2. In "CLI sync", create and copy a token.
  3. Connect this computer and upload an aggregate snapshot:
harness-analyzer login
harness-analyzer sync

The token is stored in ~/.config/harness-analyzer/credentials.json with mode 0600. For automation, provide it through HARNESS_ANALYZER_TOKEN instead. harness-analyzer logout removes the local token; revoke the server token from Profile.

Each installation also keeps a random device ID and label in ~/.config/harness-analyzer/device.json with mode 0600. The ID survives logout so repeated uploads replace that device's latest snapshot instead of creating duplicates. By default the private label is the local hostname. Set a persistent alias with --device-name:

harness-analyzer login --device-name build-worker-01
# or update it during the next upload
harness-analyzer sync --device-name build-worker-01

HARNESS_ANALYZER_DEVICE_NAME overrides the saved label for one process without changing device.json. When both are present, the explicit --device-name value wins and is saved. Device labels, platform and architecture are sent only to the private owner analytics used for the device breakdown; they are never included in the public profile.

Sync a server fleet

Connect every server to the same account token. Each installation retains its own ID, and the service aggregates the latest snapshot from every device:

# Run on worker-01 through worker-10 with the matching number.
export HARNESS_ANALYZER_TOKEN='ha_sync_...'
harness-analyzer sync --device-name worker-01

For scheduled jobs that should not persist an infrastructure hostname, use a temporary alias instead:

HARNESS_ANALYZER_DEVICE_NAME=worker-01 harness-analyzer sync --quiet

Use harness-analyzer sync --dry-run to inspect totals without making a network request. Existing offline commands remain available: summary, today, week, month, projects, and sessions.