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

cru-teams

v1.2.0

Published

◫ Manage terminal layouts for Claude Code agent teams

Readme

◫ cru

Layout for Claude Code agent teams, fixed.

Agent teams let multiple Claude Code instances work together in parallel — cru handles the terminal layout so you don't have to.

╭──────────────────┬────────────────┬────────────────╮
│                  │                │                │
│                  │  ⚡ worker-1    │  ⚡ worker-2    │
│                  │                │                │
│       lead       ├────────────────┼────────────────┤
│                  │                │                │
│                  │  ⚡ worker-3    │  ⚡ worker-4    │
│                  │                │                │
╰──────────────────┴────────────────┴────────────────╯

demo

Terminal setup

  • Already using tmux? You're good.
  • iTerm2? Use tmux -CC for native pane integration.
  • Ghostty? Workers still run in tmux (that's how Claude Code spawns agents), but cru mirrors them into native Ghostty splits via AppleScript — so you get Ghostty's UI instead of working inside tmux yourself. Requires Ghostty v1.3.0+.
  • cmux? Native support — cru mirrors workers into cmux splits via the cmux CLI socket. Tabs get labeled with ◫ (lead) and ⚡ (workers) for quick identification. Auto-detected when running inside cmux.

Install

npm install -g cru-teams
pnpm add -g cru-teams
bun add -g cru-teams

Quick start

  1. Set up cru in your project:
cru init
  1. In Claude Code, spawn a team:
/cru split the auth module into subtasks and parallelize across workers

That's it — cru creates the panes, applies the grid layout, and your workers are ready to go.

Use cases

Parallel feature work — split subtasks across workers, merge when done

/cru break down the checkout flow into vertical slices, one worker per slice

Review crew — workers build, one reviews

/cru 3 review PR #142 — one on security, one on performance, one on test coverage

Competing hypotheses — debug faster with multiple theories at once

/cru users report the app crashes on login — each worker investigates a different theory

Research spike — explore different approaches simultaneously

/cru 3 evaluate auth libraries — one on passport, one on lucia, one on arctic

Documentation