Action Receipts

Open receipt format · v0.1.0

Record and verify automated changes.

For teams using agents, scripts, or CI to change repositories and services.

Try it with sample dataInstall the CLI

See a signed deployment receipt. Nothing is saved.

  • Local files
  • No account
  • No telemetry
Evidence cards linked by a black chain, ending in a sealed artifact envelope.
Stated approval → recorded command → file hash → signature
01Approved scope
02Recorded command
03File hash
04Signature

Offline verifier

Verify a signed receipt.

The verifier checks every recorded event and the receipt signature on your device.

or paste JSON

Unchecked

No receipt loaded

Choose a receipt JSON or try the sample. Selected files stay in this browser tab.

How it works

Create, record, sign, and verify.

  1. 01

    Record the approved scope.

    Start with the actor, approval reference, scope, redaction rules, and retention window.

  2. 02

    Record a command or tool result.

    Capture command output, tool data, and file hashes. Sensitive values are redacted first.

  3. 03

    Sign and export the receipt.

    Export JSON or a self-contained HTML report. Technical details use Ed25519.

Integrity is not identity.

A valid receipt shows signed contents have not changed. It does not prove approval was legitimate or an action was correct.

Command-line quick start

Run the sample or use your own change.

TERMINAL / QUICK START
# Run a complete sample in a new temporary directory
$ action-receipts demo

# Or create and sign your own receipt
$ action-receipts new --out deploy.receipt.json --actor "release-bot@ci" --authorization "change-482 approved" --summary "Publish docs" --scope "repo:docs/**"
$ action-receipts run --receipt deploy.receipt.json -- npm run build
$ action-receipts seal --receipt deploy.receipt.json --html deploy.receipt.html
$ action-receipts verify deploy.receipt.json --json
Download Linux x64Read the source (GitHub)

Export formats

Export each receipt as JSON or HTML.

Install the CLI