# Compatibility

Source: https://www.testifysec.com/docs/cilock/reference/compatibility/

What CI/lock is built for, tested against, and known to interoperate with.

What CI/lock is built for, tested against, and known to interoperate with.

 

> Sources: [`rookery/cilock/go.mod`](https://github.com/aflock-ai/rookery/blob/main/cilock/go.mod), [`rookery/.github/workflows/release.yml`](https://github.com/aflock-ai/rookery/blob/main/.github/workflows/release.yml), [`rookery/cilock/cmd/cilock/main.go`](https://github.com/aflock-ai/rookery/blob/main/cilock/cmd/cilock/main.go).

 

## Toolchain

 

| Component | Version or configuration |
| --- | --- |
| Go (build) | **1.26.4+** (per `go.mod`) |
| Build flags | `CGO_ENABLED=0`, `GOWORK=off`, `-trimpath` |
| FIPS mode | On by default (`//go:debug fips140=on` in `main.go`) |

 

## Released platforms

 

The official rookery release pipeline produces static binaries for:

 

| OS | Architectures | Notes |
| --- | --- | --- |
| Linux | amd64, arm64 | Full feature set including `--trace` (eBPF where the kernel supports it, else ptrace+seccomp) |
| macOS (Darwin) | amd64, arm64 | All attestors. `--trace` reads the Seatbelt sandbox report: it records the process tree, execs, network activity, and reads inside the working directory, but not `openedFiles` digests or syscalls such as `ptrace` and `mount` |
| Windows | amd64 | Shipped as a `.zip` since v3.2.0. No `omnitrail` attestor (not supported on Windows) and no `--trace` backend: `--trace` fails the run. |

 

macOS and Windows binaries are not OS code-signed (no Apple Developer ID or notarization, no Authenticode); see [Verify the `cilock` binary](https://www.testifysec.com/docs/cilock/getting-started/verify-the-cilock-binary#macos-and-windows-binaries-are-not-os-signed).

 

## Container image

 

The release pipeline publishes binaries only: it builds no container image and creates no GitHub Release (`release.yml`). Earlier versions of this page listed a `ghcr.io/aflock-ai/cilock` image; the current pipeline does not build or update it. To run CI/lock in a container, install the release binary into your own image.

 

## CI platforms

 

Tested integrations from the cilock-action ecosystem:

 

| Platform | Integration | Source |
| --- | --- | --- |
| GitHub Actions | `aflock-ai/cilock-action@d39bb9b17e392520f9e7eef17cf355c027a5c283` (`v1.0.4`; pin the commit, not a tag or `@v1`) | [cilock-action](https://github.com/aflock-ai/cilock-action) |
| GitLab CI | Reusable template at `cilock-action/gitlab/cilock.gitlab-ci.yml` | Same repo |
| Jenkins | Via the `jenkins` attestor + raw `cilock` binary | `rookery/plugins/attestors/jenkins` |
| AWS CodeBuild | Via the `aws-codebuild` attestor | `rookery/plugins/attestors/aws-codebuild` |

 

## Signers

 

The default `cilock` binary blank-imports three signer providers, `file`, `fulcio` and `piv` (verified from `cilock/cmd/cilock/main.go`):

 

| Signer | Module | In default binary? |
| --- | --- | --- |
| Sigstore Fulcio | `plugins/signers/fulcio` | ✅ default |
| File (PEM) | `plugins/signers/file` | ✅ default |
| PIV smart card (YubiKey, slot 9c) | `plugins/signers/piv` | ✅ default |
| KMS (`--signer-kms-ref`: `awskms://`, `gcpkms://`, `azurekms://`, `hashivault://`) | `plugins/signers/kms/{aws,gcp,azure}`, `vault-transit` | builder opt-in |
| debug-signer | `plugins/signers/debug-signer` | builder opt-in |
| SPIFFE/SPIRE | `plugins/signers/spiffe` | builder opt-in |
| HashiCorp Vault | `plugins/signers/vault`, `vault-transit` | builder opt-in |

 

The default binary links no KMS backend, so it registers no `--signer-kms-*` or `--verifier-kms-*` flag; passing one is an unknown-flag error. A build that imports `plugins/signers/kms/{aws,gcp,azure}` or `plugins/signers/vault-transit` registers them, and a ref whose scheme that build does not link errors with `no kms provider found`. The other "builder opt-in" signers likewise exist as Go modules in rookery but aren't blank-imported by default. Add the import to `cilock/cmd/cilock/main.go` (or use `rookery-builder --with …`) and rebuild — see [build a custom CI/lock](https://www.testifysec.com/docs/cilock/guides/build-a-custom-cilock).

 

## Timestamp authorities

 

[RFC 3161](https://datatracker.ietf.org/doc/html/rfc3161) compatible TSAs. Tested against:

 

- **The platform TSA** (derived from `platform-url`; the cilock-action default when `timestamp-servers` is not set)
 - **Sigstore TSA** (Sigstore-operated public TSA)
 - Self-hosted TSAs reachable over HTTPS

 

URL pattern: TSAs are passed via `--timestamp-servers <url>` (repeatable; `-t`). There is no config file: it was [removed](https://www.testifysec.com/docs/cilock/reference/configuration#no-config-file-removed), so flags (or the action's `timestamp-servers` input) are the only way to set them.

 

## Evidence storage

 

| Sink | Notes |
| --- | --- |
| File output | Default; via `--outfile`. |
| OCI registry | Via the `oci` attestor + downstream `cosign`/`oras` push. |
| Archivista | Tested against the [in-toto/archivista](https://github.com/in-toto/archivista) reference server. URL pattern `<platform-url>/archivista`; auth via static `--archivista-headers` or OIDC (`--archivista-oidc` + `--archivista-audience`). |

 

## Witness compatibility

 

CI/lock shares witness's DSSE + in-toto envelope format, but interop is **asymmetric — witness → CI/lock, not fully the reverse**:

 

- CI/lock attestation type URLs use the `https://aflock.ai/attestations/<name>/v0.1` namespace.
 - Legacy witness URLs (`https://witness.dev/attestations/<name>/v0.1`) are accepted via aliases registered in [`attestation/legacy.go`](https://github.com/aflock-ai/rookery/blob/main/attestation/legacy.go), called from `main.go` at startup via `attestation.RegisterLegacyAliases()`.
 - Witness-signed policies (DSSE payload type `https://witness.testifysec.com/policy/v0.1`) work with `cilock verify`.
 - **Witness-produced attestations verify under `cilock verify`.**
 - The reverse holds **only for the shared base attestors**. CI/lock's v0.3 Merkle-tree `product`/`material` attestations (`tree:products` root + inline leaves), standalone inclusion proofs, and trace records use predicates and verification logic witness doesn't implement, so **`witness verify` cannot validate most CI/lock attestations**.

 

## Predicate types in scope

 

| Predicate | Notes |
| --- | --- |
| in-toto Statement v1 (with versioned predicate URLs) | Native format for all CI/lock attestations. |
| DSSE envelope | Wraps every signed attestation. |
| SLSA Provenance v1 | Emitted by the `slsa` attestor. |
| CycloneDX, SPDX | Embedded by the `sbom` attestor when found in products. |
| SARIF | Embedded by the `sarif` attestor when found in products. |
| VEX | Emitted by the `vex` attestor. |

 

## Version pinning recommendations

 

| Dependency | Pin to |
| --- | --- |
| `aflock-ai/cilock-action` in workflows | A commit SHA (not a floating tag like `@v1`), see the [defending-against-supply-chain-attacks](https://www.testifysec.com/docs/cilock/tutorials/defending-against-supply-chain-attacks) tutorial for why. |
| `cilock` binary | A specific release version, not `:latest`, in any production-bound workflow. |
| Custom binaries built via the rookery builder | Pin every plugin module to a path-prefixed tag. |

 

Before moving a pin forward, read the policy changes for the versions you cross. v4.11.0 changes how external verification summaries and policy signer options are judged: see [Changes in v4.11.0](https://www.testifysec.com/docs/cilock/reference/policy-schema#changes-in-v4110).

 

## What's not covered

 

- **Blocking network egress.** With `--trace`, CI/lock records network activity (connections, DNS lookups, TLS SNI hostnames) so a policy can fail the step, but it does not block traffic while the step runs. Pair with [StepSecurity Harden-Runner](https://github.com/step-security/harden-runner) for inline blocking.
 - **Developer laptop or production server protection.** CI/lock operates in CI/CD only.
 - **Windows attestor coverage.** The released Windows binary has no `omnitrail` attestor and no `--trace` backend (`--trace` fails the run), so a Windows runner cannot produce evidence that needs either.

Reference generated from the product documentation. Match commands and support details to your installed release.
