Make a commit; gitsign will open a browser-based OIDC flow (or use the ambient OIDC token in CI) to obtain a Fulcio certificate and record the signature in Rekor
Verify a commit with gitsign verify --certificate-identity <expected-identity> --certificate-oidc-issuer <expected-issuer> HEAD
For CI environments, set GITSIGN_CONNECTOR_ID and ensure the OIDC token is available as an environment variable so gitsign authenticates non-interactively
Known gotchas
Use gitsign verify rather than git verify-commit because the native git command does not pass signer identity expectations to the signing tool; it only confirms cryptographic integrity without validating who signed
gitsign requires network access to Fulcio and Rekor at commit time; air-gapped environments must configure gitsign to use private Fulcio and Rekor instances via GITSIGN_FULCIO_URL and GITSIGN_REKOR_URL
Signed commits reference a short-lived Fulcio certificate; the signature remains verifiable via Rekor even after the certificate expires, because Rekor stores the certificate at the time of signing
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp