Sign and attest bottle images (SLSA/sigstore) #339

Open
opened 2026-07-10 00:26:55 -04:00 by didericis · 0 comments
Owner

Why

bot-bottle is self-hosted and open source, which is a structural advantage over closed, cloud-only competitors (Devin, Copilot workspace) — a user can verify what's actually running in their sandbox, those tools' users cannot. We're not capitalizing on that yet: nothing currently lets a user cryptographically confirm that the agent/sidecar images they're running were built from the published source rather than tampered with.

Proposal

  • Adopt sigstore/cosign (keyless signing via OIDC) to sign built agent and sidecar images (Dockerfile.claude, Dockerfile.codex, Dockerfile.sidecars) as part of the release/build pipeline
  • Publish SLSA provenance attestations for each image build (build platform, source commit, build steps)
  • Add a ./cli.py verify (or similar) command that checks a locally built or pulled image's signature/provenance before use, so this is a real, checkable guarantee and not just documentation
  • Document the verification flow prominently — this is a claim that only matters if it's easy for a security-conscious user to actually exercise

Non-goals

  • Not proposing a hosted/paid image registry — this applies to locally built images too
## Why bot-bottle is self-hosted and open source, which is a structural advantage over closed, cloud-only competitors (Devin, Copilot workspace) — a user *can* verify what's actually running in their sandbox, those tools' users cannot. We're not capitalizing on that yet: nothing currently lets a user cryptographically confirm that the agent/sidecar images they're running were built from the published source rather than tampered with. ## Proposal - Adopt sigstore/cosign (keyless signing via OIDC) to sign built agent and sidecar images (`Dockerfile.claude`, `Dockerfile.codex`, `Dockerfile.sidecars`) as part of the release/build pipeline - Publish SLSA provenance attestations for each image build (build platform, source commit, build steps) - Add a `./cli.py verify` (or similar) command that checks a locally built or pulled image's signature/provenance before use, so this is a real, checkable guarantee and not just documentation - Document the verification flow prominently — this is a claim that only matters if it's easy for a security-conscious user to actually exercise ## Non-goals - Not proposing a hosted/paid image registry — this applies to locally built images too
didericis added the Kind/Security label 2026-07-10 00:26:55 -04:00
didericis-codex added the
Priority
Low
4
label 2026-07-18 03:43:01 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#339