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

@lets-ship/cli

v0.13.2

Published

Hand work off to the SHIP AI agent team from your terminal.

Readme

ship

Hand work off to the SHIP AI agent team from your terminal.

Two hand-offs:

  • You planned it, SHIP builds it. Write the spec, delegate it, and the platform skips its own planning and builds from what you wrote.
  • You built it, SHIP ships it. Open the pull request, delegate it, and the platform reviews it, tests it, and drives it to merge — recovering CI on the way if it is red.

Install

npm install -g @lets-ship/cli

Authenticate

Create a token in the SHIP console under Settings → API tokens, then:

export SHIP_API_TOKEN=pat_...
export SHIP_PROJECT_ID=proj_...   # optional; saves typing --project

The token carries your own permissions and nothing more, and always expires.

Use

# Hand over a plan
ship delegate plan SHIP-412 --file docs/plan.md
ship delegate plan --title "Rate-limit search" --file docs/plan.md   # creates the issue too

# Hand over a branch (open the PR first; --pr is auto-detected via gh)
ship delegate pr SHIP-412
ship delegate pr SHIP-412 --at qa

# Give one role extra instructions, for this mission only
ship delegate pr SHIP-412 --prompt-file security-review.md
ship delegate pr SHIP-412 --prompt-file security-review.md --prompt-mode extend

# Check on it
ship status SHIP-412
ship status SHIP-412 --json
ship mission list --activity needs_attention

# Control it
ship instruct SHIP-412 -m "Keep the current Node range"
ship mission pause SHIP-412
ship mission resume SHIP-412          # also approves a checkpoint
ship mission merge SHIP-412
ship mission override set SHIP-412 --role reviewer --harness codex
ship mission auto-merge SHIP-412 on

# See what each agent did
ship run list --mission SHIP-412
ship run logs builder-ship-412-3f9c41aa-coding-1 --part system

# Run a mission every week
ship schedule create --name deps --template dependency-upgrades

# Who am I, and what is left
ship whoami
ship credits
ship credits ledger
ship token list

# Teach your local coding agent every command (one skill per capability)
ship init

Exit codes

Distinct per failure class, so a script can branch on them without parsing prose.

| Code | Meaning | |---|---| | 0 | Success | | 1 | Unexpected runtime failure | | 2 | Usage error | | 3 | Not permitted, or no token set | | 4 | Not found, or not visible to this token | | 5 | Precondition not met (e.g. a review hand-off naming no PR, no credits, a merge conflict) | | 6 | Platform not ready (finish onboarding) | | 7 | A sandbox build the command waited on failed | | 8 | Too many requests, or a daily limit reached |

What this is

A pure consumer of the public /v1 API — it can do exactly what your token can do, and nothing more. It never pushes to your repository, never opens a pull request on your behalf, and holds no credential for your code host: the PR auto-detection reads your own gh login, locally.