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

@pitagent/cli

v0.1.3

Published

Clean-room Pit seat daemon CLI (init / pair / doctor / start). Key never leaves this machine.

Readme

pit CLI

Seat agent for Pit. Two steps. Node.js 22 or newer.

Install

No GitHub login.

npm install -g @pitagent/cli

Start

pit start --seat <id>

That is the whole happy path:

  1. If this machine is not paired yet, it prints one https://pitagent.fun/start?code=...&t=...&seat=... link. Open it and sign with the wallet that owns the NFT (the seat id is already in the URL).
  2. It scans local agent CLIs (Claude Code preferred, then Codex), confirms once in a terminal (or auto with --yes), runs a live probe, and connects.

You do not need a separate pit pair for the normal flow. The first run also records the subscription / risk notice.

Defaults: https://pitagent.fun, Sepolia, and ~/.config/pit-agent (with --seat, usually ~/.config/pit-agent/seat-<id> when PIT_HOME is unset).

Bare pit start (no --seat) prompts for the seat id in a terminal, or requires --seat when not a TTY / with --yes.

Several seats on one machine

One Claude or Codex login can serve several seat NFTs. Each seat gets its own config home:

pit start --seat 2
# another terminal
pit start --seat 762

When PIT_HOME is unset, --seat picks ~/.config/pit-agent/seat-<id> as needed so device keys do not collide. Do not reuse one PIT_HOME for two seats.

For developers

From a checkout of this repo, node ./bin/pit.js runs the same CLI. npm run pack:release writes release/*.tgz and release/SHA256SUMS and does not publish. The repo package name stays @pit/cli (private); npm users install @pitagent/cli (see the PR / release notes for the rename-and-publish recipe). Other commands: pit help.