What's new. 

Latest · MCP 0

Added

• — MCP 0.4: path is optional and defaults to the folder the server was started in. sigship_check returns structured content with a schema: the verdict, counts, accepted risks, findings grouped by check with up to 10 places each and a count of the rest, since (fixed, left, new compared with the last run of the same folder, kept in a small file in the cache folder), and a fix brief worded for the connected client. New tool sigship_badge for the badge code after a GO, and the launch-check prompt. sigship_explain is unchanged. No tool accepts a risk.
• — npx sigship badge <site>: prints the Self-checked badge code for a site with no account and no network call. With SIGSHIP_KEY, registers the site for the Deep self-check badge.
• — npx sigship login and npx sigship logout: sign in to SIGSHIP Cloud with a short code approved in the browser. The token is saved in the cache folder, readable by you only. While signed in, each check reports its verdict, counts, version, date, a repo fingerprint and the folder's name, never code, after the check and without ever failing it. SIGSHIP_NO_REPORT=1 turns it off.
• — A GO in the terminal, Markdown and MCP outputs now ends with Show it with: npx sigship badge <site>.
• — --online: the one free check that uses the network, and only when you ask. It sends the name and version of every package in package.json and your lockfile to OSV (api.osv.dev/v1/querybatch), nothing else, and reports a package with a known vulnerability as SEV-2. If OSV can't be reached, the scan runs without it and says so.
• — Accepted risks: sigship-accept.json in the checked folder, a list of { rule, file?, reason, expires }. A matching finding is listed as an accepted risk and does not count for the verdict, which reads GO with 1 accepted risk in the terminal, JSON, Markdown, SARIF and HTML outputs. Expired or malformed entries are ignored with a warning. There is no flag or command that accepts a risk.
• — --sarif: SARIF 2.1.0 output with one rule per check and a stable fingerprint per result, for GitHub code scanning.
• — --tool lovable|cursor|bolt|claude|replit|windsurf: words the fix prompt for one tool. Without it the prompt is unchanged.
• — npx sigship history [folder]: finds secrets committed in the past, even ones a later commit removed, with the commit and file and never the value. Reads up to 5,000 commits or 50 MB of git log -p.
• — npx sigship init --hook: a pre-commit hook (.git/hooks/pre-commit, or a line in .husky/pre-commit) that runs only the secret checks on the staged files and blocks a commit that adds one. npx sigship hook is what it runs.
• — init adds the definition of done to CLAUDE.md too, when that file exists.
• — --report --brand "Name" --logo file.png: the client report with your name and logo instead of SIGSHIP's. The logo is inlined, so the page still loads nothing from the network.
• — Pack format v2 for the Pro pack: projectLacks (a pattern that must appear somewhere in the project), policy checks (policyFor, policyWhere) that read create policy blocks in SQL, and dep checks (depMatch, depBelow) that compare dependency versions against package.json and the lockfile. Every v1 field still works.

Changed

• — The checks now run in src/engine.js, which takes files already in memory and imports nothing from the file system or the network. src/scan.js only loads a folder from disk and calls it. Output is unchanged.
• — The scanner reads yarn.lock and pnpm-lock.yaml for pinned versions.

`npx sigship ui`

Changed

• — npx sigship ui: the dashboard has the new Night Harbour look, with Plain and Dev wording and a Night and Day switch. It still runs only on your computer and shows findings, never your files.

Requires Node

Changed

• — Requires Node.js 22 or later. Node.js 20 reached end of life in April 2026. CI tests Node.js 22 and 24.
• — A new README, plus a security policy, contribution guide and issue templates.
• — Package details for npm: author, keywords and the changelog in the package.

`npx sigship ui [folder]`

Added

• — npx sigship ui [folder]: a local dashboard in the browser with the verdict, every finding, a button to copy the fix prompt, re-run, and a box to check another folder. It listens on 127.0.0.1 only, needs the private link it prints, and serves findings, never file contents.
• — --no-open, to print the dashboard link without opening a browser.

Licence key support with `SIGSHIP_KEY`, which adds the Pro pack of extra checks

Added

• — Licence key support with SIGSHIP_KEY, which adds the Pro pack of extra checks. Without a key, SIGSHIP still makes no network calls.
• — --report, which writes sigship-report.html, a self-contained report to send to a client. Needs a licence key.
• — --markdown, for pull request comments.
• — npx sigship init --pro, which adds a pull request check that comments its result and a nightly check with an optional Slack alert.
• — The MCP server loads the Pro pack when a key is set.
• — The scanner now reads Firebase .rules and Terraform .tf files.

Changed

• — The Pro pack is data only: patterns and messages. SIGSHIP never runs code from it and rejects a pack it can't validate.
• — A network problem never fails a scan: SIGSHIP falls back to its cached Pro pack, then to the free checks.

Package details for npm and the MCP Registry

Changed

• — Package details for npm and the MCP Registry.

First release

Added

• — First release: 17 checks for how AI-built apps fail, the command line tool with terminal, JSON and fix-prompt output, the pull request check (npx sigship init) and the MCP server.