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

shiphook

v0.3.0

Published

Ship on hook. Webhook-triggered deploy runner: POST → git pull → run your script. Configure via shiphook.yaml or env. Self-hosted for indie devs and micro-SaaS. No vendor lock-in.

Readme

Shiphook

Ship on hook. One webhook, one command. Receive a POST → git pull → run your deploy script. Configure the deployment via YAML or env vars. No SaaS, no containers. Just Node and your repo.

Built for indie devs, micro-SaaS, and open-source projects that want simple, self-hosted deploys.

CI npm version License: MIT TypeScript Node Docs CodeRabbit Reviews


Install

npm install -g shiphook

Run

cd /path/to/your/repo
shiphook

By default Shiphook listens on port 3141. Send a POST to trigger a deploy:

curl -X POST http://localhost:3141/

It runs git pull in the repo, then your script (default: npm run deploy). Response is JSON with pull and run output.

Deploy once (manual)

From your repo root, run:

shiphook deploy

Logs (deploy history)

For every webhook-triggered deploy (and shiphook deploy), Shiphook writes a log file into:

  • .shiphook/logs/<id>.json (machine-readable)
  • .shiphook/logs/<id>.log (human-readable)

The server response includes log: { id, json, log } so you can correlate a request to a file.

Why Shiphook?

  • No vendor lock-in — Your server, your script, your Git. No third-party deploy service.
  • YAML or env — Put shiphook.yaml in your repo (or set env vars). Env overrides file. Run and point your Git webhook at it.
  • Fits your stack — Use npm run deploy, pnpm build, ./deploy.sh, or anything else.
  • Secret-based auth (required) — The server always requires a secret. Set SHIPHOOK_SECRET (or secret: in shiphook.yaml), or omit it and the CLI will auto-generate one and persist it to .shiphook.secret. Send it as X-Shiphook-Secret or Authorization: Bearer <secret>.

Configuration (YAML or env)

Add a shiphook.yaml in your repo (see shiphook.example.yaml) or set env vars. Env overrides the file.

| Option | Default | Description | |--------|---------|-------------| | port / SHIPHOOK_PORT | 3141 | Server port. | | repoPath / SHIPHOOK_REPO_PATH | current dir | Repo path for git pull and script. | | runScript / SHIPHOOK_RUN_SCRIPT | npm run deploy | Command run after pull. | | secret / SHIPHOOK_SECRET | — | Required for auth. If omitted, the CLI auto-generates and persists one in .shiphook.secret. | | path / SHIPHOOK_PATH | / | Webhook path (e.g. /deploy). |

GitHub webhook

  1. Repo → SettingsWebhooksAdd webhook.
  2. Payload URL: https://your-server:3141/ (or your path).
  3. Secret: Same as SHIPHOOK_SECRET / .shiphook.secret.
  4. Events: Push events.
  5. Save. Every push triggers a deploy.

Docs

Full docs (install, config, webhooks, programmatic API): Documentation

Programmatic use

import { createShiphookServer, ensureWebhookSecret, loadConfig } from "shiphook";

const config = loadConfig();
await ensureWebhookSecret(config);
const server = createShiphookServer(config);
await server.start();

License

MIT.