Security & Supply Chain

Release Signing

Every release is signed at multiple levels:

LayerMethodVerification
CI buildsSigstore cosign (keyless, OIDC)cosign verify-blob
Local buildsApple Developer ID (YubiKey)codesign -dvvv
ProvenanceGitHub Attestations (SLSA)gh attestation verify

Verify a Release

# Cosign (CI-signed releases)
cosign verify-blob omegon-*.tar.gz \
  --signature omegon-*.tar.gz.sig \
  --certificate omegon-*.tar.gz.pem \
  --certificate-identity-regexp '.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# GitHub Attestations
gh attestation verify omegon-*.tar.gz --repo styrene-lab/omegon

SBOM

Every release includes a CycloneDX Software Bill of Materials (omegon-sbom.cdx.json) listing all Rust crate dependencies with versions. The SBOM is itself signed with cosign.

Credential Storage

API keys and OAuth tokens are stored in the system keychain:

OAuth tokens are refreshed automatically. JWT claims are extracted for account identity (used by the Codex client for account ID routing).

HashiCorp Vault Integration

/vault status       # Check Vault connectivity
/vault login        # Authenticate to Vault
/vault configure    # Set Vault address and auth method
/vault init-policy  # Create a least-privilege policy for omegon

For teams that manage secrets through Vault, Omegon can read credentials directly from Vault paths instead of environment variables or the local keychain.

Process Safety

License

Omegon is licensed under the Business Source License 1.1. The BSL converts to MIT on 2031-03-19. Non-production use is permitted; production use requires a separate license from Black Meridian, LLC (until the change date).