Ever wondered if applications really have to be written to target servers or containers? Can they be more flexible so that they run anywhere? I recently had to create a Probot application that worked on VMs, containers, and serverless platforms. And I needed to do that without writing multiple versions of the code.

In this post, we’ll continue the exploration of Gitsign by extracting some of the attestation data from a signed commit and using it to check how the code was built. This will help you understand how you can use the attestation data in your workflows.

Worried about securing your source code supply chain for GitOps and other processes? Learn how to implement automated signing in CI/CD pipelines, verify commit authenticity using transparency logs, and leverage GitHub OIDC tokens with Gitsign for keyless commit signing.