container-signing

Sign and verify container images with keyless Cosign and SLSA attestations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cameronsjo/dev-toolkit --skill container-signing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-signing
Source: https://github.com/cameronsjo/dev-toolkit/tree/main/skills/container-signing
Command: npx skills add https://github.com/cameronsjo/dev-toolkit --skill container-signing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Securing container builds by enabling cryptographic signing and provenance to prevent tampered images from being deployed.

Core Features & Use Cases

  • Cosign-based signing of container images with keyless verification and optional attestations.
  • SLSA provenance generation to prove build provenance and reproducibility for container artifacts.
  • Verification & governance: validate signatures and attestations in CI/CD, GHCR publishing, and runtime environments.

Quick Start

Set up Cosign signing and SLSA provenance for your container builds and GHCR publishing in CI/CD pipelines.

Frequently Asked Questions about container-signing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sign container images in GitHub Actions using Cosign?

To sign container images in GitHub Actions using Cosign, you apply keyless signing and SLSA attestations directly within your CI/CD workflows. This process cryptographically verifies image integrity and prevents tampered artifacts from being deployed.

What is SLSA provenance and why do I need it for container artifacts?

SLSA provenance for container artifacts is a record that proves build origin and reproducibility. You need it to enforce supply chain security, prevent tampered images from being deployed, and validate artifact integrity in CI/CD pipelines.

How can I verify container signatures and attestations in GHCR publishing scenarios?

You verify container signatures and attestations in GHCR publishing scenarios by applying Cosign verification commands within your CI/CD pipelines. This governance step validates the cryptographic signatures and SLSA provenance of your container artifacts.

Does Cosign support keyless signing for CI/CD pipelines?

Yes, Cosign supports keyless signing for CI/CD pipelines. It enables you to cryptographically sign container images and generate SLSA attestations without managing static keys, ensuring end-to-end supply chain security for your GitHub Actions workflows.

What is the best way to enforce supply chain security for container builds?

The best way to enforce supply chain security for container builds is applying end-to-end cryptographic signing and verification. Using Cosign for keyless signing and SLSA for provenance generation prevents tampered images from being deployed across CI/CD pipelines.