sigship

The go/no-go check for AI-built apps.
The postmortem, before the outage.

---

SIGSHIP reads your repo on your own machine and lists what will break in production: leaked keys, open databases, unverified webhooks, AI routes with no spending brake. It exits 0 only when it finds nothing serious, which gives you and your coding agent a real test for done.

npx sigship

No signup, no telemetry, no runtime dependencies. The free tool never touches the network.

Contents

• What you get
• Quick start
• Commands
• Pull requests
• Coding agents (MCP)
• What it checks
• Privacy
• SIGSHIP Cloud and licence keys
• Limits
• Contributing and security

What you get

SIGSHIP read 6 files in 22 ms, ran 17 checks

Postmortem, written before the outage. Worst first.

SEV-1  Your Stripe webhook accepts anything
       src/api/stripe-webhook.ts:3  Handles Stripe events with no signature check in this file.
       Someone posts a fake "payment succeeded" event to your endpoint and
       gets your paid plan for free.

SEV-2  Your AI route has no spending brake
       src/api/chat.ts:2  This route calls a paid AI API and the project has no rate limiter.
       One script loops on this endpoint overnight and you wake up to the invoice.

NO-GO  1 SEV-1, 1 SEV-2, 0 SEV-3. Exit 1.
Paste the fixes into your AI tool: npx sigship --prompt

Exit code	Meaning
0	GO. No SEV-1 or SEV-2 findings.
1	NO-GO. Something blocks launch.
2	SIGSHIP could not run, for example the folder does not exist.

A GO means these checks found nothing that blocks launch. It does not prove the app is safe.

Quick start

Requires Node.js 22 or later.

npx sigship                 # check the current folder
npx sigship path/to/app     # check another folder
npx sigship --prompt        # turn every fix into one prompt for Lovable, Cursor, Bolt or Claude Code
npx sigship ui              # open the same results as a dashboard in your browser

Commands

Command	What it does
npx sigship [folder]	Check a project and print the postmortem.
npx sigship ui [folder]	Open a local dashboard: verdict, findings, a copy-the-fix-prompt button and re-run.
npx sigship init [folder]	Add a pull request check and a definition of done to AGENTS.md.
npx sigship mcp	Start the MCP server for coding agents.

Option	What it does
--prompt	Print the fixes as one prompt for your AI tool.
--json	Print the result as JSON.
--markdown	Print the result as Markdown, for pull request comments.
--strict	Also block on SEV-3 findings.
--report	Also write sigship-report.html for a client. Needs a licence key.
--no-open	With ui, print the dashboard link without opening a browser.
--version, --help	Print the version or the help.

The dashboard listens on 127.0.0.1 only, answers only the private link it prints, and serves findings, never file contents. Press Ctrl+C to stop it.

Pull requests

npx sigship init

Adds .github/workflows/sigship.yml, which fails a pull request that brings back a SEV-1 or SEV-2 problem, and a definition of done in AGENTS.md that tells coding agents to run SIGSHIP before saying they are finished. It never overwrites an existing file.

Coding agents (MCP)

Claude Code:

claude mcp add sigship -- npx -y sigship mcp

Cursor, in .cursor/mcp.json:

{ "mcpServers": { "sigship": { "command": "npx", "args": ["-y", "sigship", "mcp"] } } }

The agent gets two tools, sigship_check and sigship_explain, and one instruction: don't say it's done while the verdict is NO-GO. SIGSHIP is listed in the MCP Registry as io.github.sigship/sigship.

What it checks

17 checks, chosen for how AI-built apps actually fail. Each links to a page with what goes wrong and how to fix it.

SEV-1: blocks launch, exposes data or money Live secret in code · Committed .env · Server secret with a browser-visible name · AI key in the browser · Table with no row level security · Policy that lets anyone write · Unverified Stripe webhook · User input in SQL

SEV-2: blocks launch, abuse is easy AI route with no rate limit · Admin role in localStorage · Unsanitised HTML

SEV-3: reported, blocks only with --strict Wildcard CORS · Secret in logs · No error boundary · No error tracking · No tests · No lockfile

Privacy

• The free tool, dashboard and MCP server run entirely on your machine. They make no network calls and have no telemetry.
• SIGSHIP never prints a secret value, in any output format.
• With a licence key, and only then, SIGSHIP sends the key and a one-way repo fingerprint to api.sigship.dev. It never sends code, file names or findings.

Full details: sigship.dev/privacy.

SIGSHIP Cloud and licence keys

SIGSHIP Cloud is coming: connect a repo from GitHub, Lovable, Bolt, Replit and other AI tools, and SIGSHIP checks every push, watches your live site and tells you what to fix in plain English. Plans are Solo ($19), Team ($59) and Agency ($149) a month. Join the waitlist.

If you already have a licence key, set it to add the Pro pack of extra checks:

SIGSHIP_KEY=your-key npx sigship            # free checks plus the Pro pack
SIGSHIP_KEY=your-key npx sigship --report   # also write a client-ready HTML report
npx sigship init --pro                      # pull request comments and a nightly check

For the nightly check and pull request comments, add the key as the repository secret SIGSHIP_KEY, and optionally SLACK_WEBHOOK_URL for Slack alerts. If the licence server can't be reached, SIGSHIP uses its last download of the Pro pack, or the free checks. A network problem never fails a scan.

Limits

• SIGSHIP uses pattern checks. It can miss real problems and flag safe code.
• It reads your repo, so it can't see settings changed only in a dashboard, such as Supabase policies created in the web console.
• A GO is not a security audit. For a human review, see the pilot review.

Contributing and security

• Found a false positive or a missed problem? Open an issue.
• Want to add a check or fix a bug? See CONTRIBUTING.md.
• Found a security problem in SIGSHIP itself? Please follow SECURITY.md and don't open a public issue.

License

MIT © Zoof04 Inc. · sigship.dev · [email protected]