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

stagecoach-ai

v0.1.16

Published

Thin npm wrapper that downloads and runs the stagecoach native binary — a snapshot-based AI commit-message generator that uses YOUR local CLI agent.

Downloads

1,047

Readme

stagecoach-ai

stagecoach-ai is a thin npm wrapper that downloads the stagecoach native binary at install time (via a postinstall script) and execs it on every stagecoach invocation. stagecoach is a snapshot-based AI commit-message generator that uses YOUR local CLI agent. If the postinstall download was blocked (for example by running npm install --ignore-scripts or a corporate npm mirror that disables scripts), the stagecoach command prints a message pointing at https://github.com/dabstractor/stagecoach#install — install directly or use a package manager that allows postinstall.

Install

npm install -g stagecoach-ai
stagecoach

See the main repository for features, configuration, and the full CLI reference.

Publishing (for maintainers)

This package is published automatically when a v* tag is pushed (the same tag that fires goreleaser). goreleaser has no native npm pipe, so an npm-publish job (in release.yml) runs after the goreleaser job:

  1. Syncs package.json version to the tag (v1.2.01.2.0; the committed version stays 0.0.0, a dev placeholder).
  2. npm install --ignore-scripts --no-package-lock — validates the tar / extract-zip deps resolve WITHOUT running postinstall (the native binary is fetched at user install time, not publish time) and WITHOUT writing a lockfile into the tarball.
  3. npm publish — the package is unscoped (stagecoach-ai), so it is public by default; no --access flag is needed (that flag is scoped-packages-only).

Required secret: NPM_TOKEN — an npm automation token (npmjs.com → Access Tokens → "Automation"), which bypasses publish 2FA for non-interactive CI. Add it under the repo's Settings → Secrets → Actions. (A "Publish" token will fail in CI if the account has publish 2FA on.)

The wrapper's smoke tests (the shim + the installer) run on every PR in ci.yml (npm-smoke job) to catch regressions before a release. See the main repo's distribution notes for all install channels.

Optional future enhancement: add a files field to package.json to slim the tarball (the test/* files currently ship, ~9KB extra, which is harmless) and/or use npm publish --tag next for prerelease tags so npm install does not resolve an RC as latest. Both require a package.json change and are intentionally out of scope for the initial publish wiring.