platformchangelog.dev
44 tools
feedpost

PlatformEngineering.org: Beyond SHA pinning: Why immutability isn't provenance in GitHub Actions

Chainguard's DevRel engineer Erika Heidi argued in a Platform Engineering webinar that pinning GitHub Actions to a commit SHA verifies immutability but not authorship or project membership. She cited a timeline of CI/CD supply chain incidents from March 2025 to March 2026, including the tj-actions/changed-files and Trivy compromises, and demonstrated an imposter commit in a fork of actions/checkout that a SHA pin would accept. She presented immutable releases, workflow lock files, vendoring and a curated action catalog as ways to close the gap, and the vendor's own catalog as one option.

What changes for platform teams

Platform teams that enforce SHA pinning should also review what each pinned SHA points to, since org-level SHA policies do not check commit authorship or project membership. Lock files that require commits on a source repository branch can help against fork-only imposter commits, but they are in public preview and must be maintained with the GitHub CLI.

Read the original at PlatformEngineering.org Blog ↗

written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Report a mistake

context
PlatformEngineering.org: Beyond SHA pinning: Why immutability isn't provenance in GitHub Actions | Platform Changelog