signed verdicts · v1 · for hugging face spaces

Catch ZeroGPU silent-fails before your users do

SpaceForge verdicts surface the worker-errors, hangs, and quota burn that HF Spaces won't tell you about.

Install the free CLI

See an example verdict— or pip install spaceforge

P95 latency: <30s
False-positive: <0.5%
Signed by: sigstore

spaceforge-report.json

live

{
  "schema": "spaceforge.report/v1",
  "space": "magpiexyz-lab/zerogpu-demo",
  "pr": 142,
  "runtime": "zerogpu",
  "decision": {
    "status": "advisory",
    "runtime_evidence": "worker.silent_fail+quota.burn",
    "warning_codes": [
      "ZEROGPU_WORKER_FAIL",
      "QUOTA_BURN_NO_OUTPUT"
    ]
  },
  "manifest_sha256":
    "e3b0c44298fc1c149afbf4c8996fb924…a495991b7852b855",
  "emitted_at": "2026-05-19T18:42:35Z",
  "latency_ms": 18420
}

sigstore · cert chain ok · tlog #78340912

signed

Substrate evidence · 03

The failure modes HF Spaces won't emit on its own.

Every SpaceForge verdict is a signed JSON bundle pinned to a single PR. No best-effort log scraping — substrate-level telemetry, refusal reasons, and warning codes you can grep.

ZEROGPU_WORKER_FAIL01 / 03
ZeroGPU silent-fails — surfaced
Workers die mid-request. HF returns a 200. Your users see a spinner forever. We watch the runtime substrate HF can see but won't tell you — and stamp a verdict on every PR.
detected at PR time
QUOTA_BURN_NO_OUTPUT02 / 03
Quota burn — measured, not guessed
Every request that consumed compute but produced no output is logged with a refusal reason. Stop billing yourself for hangs you can't see.
detected at PR time
ASYNC_DEADLOCK03 / 03
Async deadlocks — caught at PR time
Pre-merge, before the deadlock ships. The verdict bundle is Sigstore-signed and includes the runtime evidence — not a best-effort log line.
detected at PR time

How it works · 03 steps

From pipx install to signed PR verdict in two coffees.

01step
Install the CLI
One command. Python 3.10+. No agent, no daemon — the binary runs locally and pings a single server only if you opt in.
bash · ~/dev/your-space
```
$ pipx install spaceforge
$ spaceforge --version
spaceforge 0.1.0  ·  python 3.11.8
```

02step

Connect a repo

Sign in with GitHub, install the SpaceForge App on the repo, and commit a 9-line `.spaceforge.yml`. We never touch your branch protection.

.spaceforge.yml

# .spaceforge.yml
space: your-org/your-space
runtime: zerogpu
gate: advisory       # advisory | required
report:
  signed: true
  warning_codes: all
notify:
  pr_comment: true

03step

Read the verdict

On every PR, a signed verdict comment lands in <30s P95 with warning_codes[], runtime evidence, and a manifest hash you can verify locally.

bash · cosign verify

$ cosign verify-blob \
    --bundle verdict.bundle \
    --certificate-identity-regexp '^.+@spaceforge\.dev$' \
    spaceforge-report.json

Verified OK · transparency log entry: 78340912

Why “signed” matters

Every output is either a generated, signed bundle — or an explicit refusal with a reason code.

Sigstore-signed reports. No best-effort claims — every output is either a generated package or an explicit refusal with a reason code.

Sigstore-signed manifest pinned to a single PR commit
Transparency-log entry (Rekor) — verifiable by anyone
Append-only tamper-evident log of every CLI invocation
No telemetry off your machine without --opt-in

bash · cosign verify-blobverified

$ cosign verify-blob \
    --bundle spaceforge-report.bundle \
    --certificate-identity-regexp \
        '^.+@spaceforge\.dev$' \
    --certificate-oidc-issuer \
        'https://accounts.google.com' \
    spaceforge-report.json

Verified OK
                · transparency-log entry: 78340912
  · sha256(report) = e3b0c44298fc1c149afbf4c89…
  · signed by: ci@spaceforge.dev (fulcio-issued)
  · timestamp: 2026-05-19T18:42:35Z

✓ Pegged to OMB M-26-04, §4.2 evidence line item.

Sigstore / RekorOMB M-26-04 ready

Pick your wedge

Two personas. One signed-evidence engine.

HF Spaces devs and federal procurement buyers run the same CLI and read the same signed bundles. Pricing diverges where the work does.

Your wedgeSolo · for HF Spaces devs

$29/ month · per dev

PR-comment bot, verdict history, advisory → required gate per repo. Stays out of your branch protection. Free CLI is included.

Unlimited PR verdicts on personal repos
30 days of signed-verdict history
Slack + email refusal alerts

Upgrade to Solo

Team @ $99/mo also available — same CLI, multi-seat.

OMB Pack · federal procurement

$5K/ year · per organization

Sigstore-signed bundles, append-only audit log, model cards, eval artifacts. Pegged to OMB M-26-04 effective March 2026.

omb-bundle-manifest.json + tamper-evident log
$1–2.5K paid POC creditable toward annual
Procurement-ready PDF rollup of every verdict

Book an OMB Pack demo

Hosted CI add-on: $0.50 / verdict, billed monthly.

See the full pricing grid

ready to emit

One command. Signed verdicts on the next PR you push.

ZeroGPU quota burn compounds every hour you can't see it The free CLI never phones home without consent; the paid PR bot signs every comment with Sigstore.

Install the free CLI

Or with pip

Sign up with GitHubNo credit card. GitHub OAuth only. Free tier installs the CLI and gives you 1 advisory verdict per PR.

Catch ZeroGPU silent-fails before your users do

The failure modes HF Spaces won't emit on its own.

ZeroGPU silent-fails — surfaced

Quota burn — measured, not guessed

Async deadlocks — caught at PR time