ShipProof

Production evidence gate / v0.10.0

Proof before merge.

ShipProof checks AI-assisted changes for security, correctness, scale, performance, and release risk. It runs locally, deterministically, and with evidence your team can inspect.

Run the gate locally See sample evidence
Read-only by default No source upload No runtime dependency
SAMPLE RUN
shipproof check . LOCAL
GATE RESULTFAIL_WITH_FINDINGS
3 blocking 
$ shipproof check . --format terminal
> FAIL scope: changed-since HEAD (18 files)
> security     2 high · 4 medium · 2 low
> correctness  1 high · 1 medium · 1 low
> scale        1 high · 1 medium · budget exceeded
> release      1 high · artifact check passed
>
> [HIGH] SP105 JWT signature verification disabled
>          src/auth/jwt.ts:61 · 3 blocking
> [HIGH] SP109 SSRF to internal network or metadata
>          src/routes/proxy.ts:44 · remediation attached
> [HIGH] SP110 path traversal in file path
>          src/storage/download.ts:32 · 1 blocking
> [HIGH] SP501 unmetered AI/LLM API route
>          src/api/generate.ts:17 · budget exceeded
> [MED]  SP204 sensitive data or credential logging
>          src/auth/login.ts:88 · review boundary attached
> [MED]  SP406 Express error sent to client
>          src/api/errors.ts:27 · stack trace exposure
>
> findings: 14 · evidence: sp-evidence-7d2c
> exit code: 1
14 findings · 3 blockingexit 1

01Local-firstyour repository stays where it is

02Deterministicsame input, inspectable result

03Automatableterminal, Action, JSON, SARIF, MCP

Interactive sample

See the gate make a decision.

Run a self-contained fixture with the same evidence shape your team can keep in CI.

DEMO REPOSITORYshipproof check ./demo-service --changed-since HEAD
SCAN PIPELINEReady to run
00.00s
  1. 01
    Scope changed files12 files · HEAD..worktree
    Ready
  2. 02
    Evaluate rulessecurity · correctness · scale
    Ready
  3. 03
    Check budgetslatency · memory · artifact size
    Ready
  4. 04
    Write evidenceterminal · JSON · SARIF
    Ready
DECISION RECORDDEMO DATA
RELEASE GATEFAIL WITH FINDINGS
3 blocking
FILES18
FINDINGS14
HIGH5
MEDIUM6
HIGH
SP105 · JWT signature verification disabledsrc/auth/jwt.ts:61 · blocks merge
fix
HIGH
SP109 · SSRF to internal network or metadatasrc/routes/proxy.ts:44 · remediation attached
fix
MED
SP204 · sensitive data or credential loggingsrc/auth/login.ts:88 · review boundary attached
review
HIGH
SP203 · unpinned GitHub Action.github/workflows/ci.yml:29 · supply-chain risk
review
evidence://sp-demo-7d2c14 findings · exit 1

Demo only · no repository data is uploaded or scanned.

The loop

From generated change to mergeable evidence.

A small, repeatable gate that fits the workflow you already have. Start at the terminal; promote the same contract to CI when the change is ready.

  1. 01

    Scope

    Identify the files and evidence that actually changed.

  2. 02

    Scan

    Run security, correctness, scale, performance, and release checks.

  3. 03

    Fix

    Read remediation context and false-positive boundaries beside each finding.

  4. 04

    Verify

    Keep the result as terminal, JSON, SARIF, or CI evidence.

ShipProof workflow: scope, scan, fix, and verify
WORKFLOW MAP One contract across local work and automation.

Evidence, not vibes

Make the decision legible to humans and machines.

Every result has a stable rule ID, severity, control mapping, remediation text, and a boundary for when it may be a false positive. That is what makes a gate reviewable instead of mysterious.

Read the command reference
TERMINAL VIEWsample / no network
Illustrative ShipProof terminal output showing findings and exit code

One contract, several surfaces

Meet developers where the decision happens.

A

CLI

Run a read-only gate from the repository root. Keep feedback close to the code.

shipproof check .
B

GitHub Action

Use the same exit-code and evidence contract in pull requests and release jobs.

uses: kingggg5/shipproof@v0.10.0
C

JSON / SARIF

Export structured results for annotations, archives, and your own review tooling.

--format sarif
D

MCP (optional)

Expose the gate to an AI workflow without making the scanner itself dependent on a model.

shipproof mcp

Claim boundaries

Confidence with a paper trail.

ShipProof can say

“This input produced these deterministic findings under this policy and scope.”

ShipProof does not say

“This code is certified, impenetrable, or free of every possible defect.”

Your team decides

Use the evidence with review, tests, threat modelling, and the context of your system.

Start with one command

Ship the change. Keep the proof.

Read the quick start Browse releases