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

@svenroth-ai/shipwright

v0.27.0

Published

One command to install AND update Shipwright — the /shipwright-* SDLC plugins and the Command Center. Run `npx @svenroth-ai/shipwright@latest`.

Readme

@svenroth-ai/shipwright

One command to install and update Shipwright — the /shipwright-* SDLC plugins and the Command Center, first run and every run after.

npx @svenroth-ai/shipwright@latest

Always include @latest. A bare npx @svenroth-ai/shipwright can silently reuse a cached older copy; the tool also self-checks the registry and warns you when you are behind.

What it does

Running the command, in order:

  1. Self-version check — warns (never fails) if a newer version is published.
  2. Preflight — verifies the prerequisites the plugins actually need: the claude CLI, uv, a working Python (test-run, not the Microsoft-Store python3 stub), Node >= 20.12.0, and git. A missing one is a loud, actionable failure — not a dead install that looks fine.
  3. Pluginsclaude plugin marketplace add/update svenroth-ai/shipwright, then installs/updates every plugin read from the marketplace manifest (never a hardcoded list), then syncs the plugin cache so each plugin's hooks (uv run "${CLAUDE_PLUGIN_ROOT}/../../shared/…") actually resolve — the step claude plugin install alone skips, which otherwise leaves every hook dead at session start.
  4. Command Center — probes :3847. Free → starts the packaged server; already running the same version → opens it (no second server); an older version → swaps it (via a detached swapper, so it is safe to run from inside the Command Center's own terminal); a foreign process → fails loud and leaves it running (PORT=<n> to pick another port).
  5. Summary — reports exactly what happened. When plugins changed, it prints the one thing it cannot do for you: restart Claude Code so the freshly installed plugins activate in a new session.

Options

| Flag | Effect | | --- | --- | | --no-open | do not open the browser (CI / headless) | | --plugins-only | install/update plugins, skip the Command Center | | --webui-only | boot/attach the Command Center, skip the plugin phase | | --port <n> | Command Center port (default 3847, or PORT env) | | --version, -v | print this package's version | | --help, -h | help |

Notes

  • The bundled server + client are built — re-running the command is the update. Only @lydell/node-pty resolves a native binary at install time.
  • Publishing is a manual step performed by the maintainer.

MIT © svenroth.ai