supply-chain-onboarding

Automate container image signing and verification in GitHub Actions with Kyverno cosign.

1|Updated Mar 20, 2025
One-click install
npx skills add https://github.com/asanexample/platform --skill supply-chain-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-onboarding
Source: https://github.com/asanexample/platform/tree/main/.claude/skills/supply-chain-onboarding
Command: npx skills add https://github.com/asanexample/platform --skill supply-chain-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, kyverno, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your app's GitHub Actions CI pipeline images pass Kyverno cosign verification, securing your supply chain.

Core Features & Use Cases

  • CI Image Signing: Automates the signing of images in your CI pipeline with cosign.
  • Provenance Tracking: Generates and tracks provenance for your images.
  • Use Case: When setting up or fixing an app repo's deploy.yml / preview.yml, debugging a verify-images / verify-attestations admission failure, or onboarding a product's supply chain.

Quick Start

Run the 'cosign verify' command on your image to ensure it has been signed and attested correctly.

Frequently Asked Questions about supply-chain-onboarding

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

FAQPage Schema
How do I automate container image signing in GitHub Actions CI pipelines?

Automating container image signing in GitHub Actions CI pipelines involves using cosign to sign images during the build process. This Skill generates and tracks provenance for your images to secure your app's supply chain.

What is Kyverno cosign verification for CI pipeline images?

Kyverno cosign verification for CI pipeline images is a process that ensures container images are cryptographically signed and attested before deployment. It secures your supply chain by validating image provenance during admission checks.

Do I need Kyverno and GitHub Actions to verify container images with cosign?

Yes, you need both GitHub Actions and Kyverno to verify container images with cosign using this Skill. GitHub Actions runs the CI pipeline while Kyverno handles the verify-images and verify-attestations admission checks.

Why does my Kyverno verify-images admission check fail for my CI pipeline images?

Your Kyverno verify-images admission check fails when your CI pipeline images have not been signed and attested correctly. You can run the 'cosign verify' command on your image to ensure it has been signed properly.

How do I set up provenance tracking for container images in my deploy.yml workflow?

Setting up provenance tracking for container images in your deploy.yml workflow requires automating image signing with cosign in GitHub Actions. This Skill helps generate and track provenance for your app's deployment workflows.