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

@moshi-labs/snitch

v1.0.17

Published

CLI daemon that reports Claude Code activity to a team server

Readme

🐀 Snitch

See what your teammates' Claude Code sessions are working on in real-time.

Dashboard: https://snitch.moshi.ai


Quick Start (5 minutes)

Step 1: Install

npm install -g @moshi-labs/snitch

Step 2: Configure

snitch init

You'll be asked for three things:

| Prompt | What to enter | |--------|---------------| | Server URL | https://snitch.moshi.ai | | API Key | Ask James for the team key | | Your name | Your name (this shows on the dashboard) |

Step 3: Start the daemon

snitch start

That's it! Your Claude Code and Codex activity will now appear on the team dashboard.


Commands

| Command | What it does | |---------|--------------| | snitch start | Start tracking (runs in background) | | snitch stop | Stop tracking | | snitch status | Check if it's running | | snitch logs | View recent logs | | snitch logs -f | Follow logs live |


Troubleshooting

"Is it working?"

snitch status

Should say "Daemon is running". If not, run snitch start.

"I don't see my activity on the dashboard"

  1. Make sure you're working in a moshi repo (moshi-api, moshi-frontend, etc.)
  2. Check logs for errors: snitch logs
  3. Verify your config: cat ~/.snitch/config.json

"I want to reconfigure"

Just run snitch init again. Press Enter to keep existing values.


How It Works

  1. Snitch watches ~/.claude/projects/ (Claude Code) and ~/.codex/sessions/ (Codex) session files
  2. When you use Claude Code or Codex in a moshi repo, it detects tool calls and messages
  3. Activity is sent to the team server
  4. Server uses Claude to categorize your work into tickets
  5. Dashboard shows what everyone's working on

Codex sessions are marked with a codex label in the UI. Claude sessions remain unlabeled (default behavior).


Config File

Stored at ~/.snitch/config.json:

{
  "serverUrl": "https://snitch.moshi.ai",
  "apiKey": "your-team-key",
  "userName": "Your Name",
  "allowedRepos": ["moshi-api", "moshi-frontend", "moshi-e2e", "terraform", "snitch"]
}

You can edit allowedRepos to track additional repositories.


License

MIT