We often talk about securing the software supply chain in terms of application dependencies. For instance, pinning package versions, maintaining lockfiles, and auditing third-party libraries.

But what about the code that runs our CI/CD pipelines?

GitHub Actions workflows can execute third-party actions, and the security of those dependencies matters just as much when building and deploying software.

The introduction of workflow dependency lockfiles is an interesting step towards making CI/CD workflows more reproducible and secure.

I wrote about this recently, exploring why workflow lockfiles matter and how they fit into the broader software supply-chain security picture.

Read the article: https://amitmerchant.com/ci-pipeline-lockfile/

Curious how others are approaching dependency security in their CI/CD pipelines. Are you already pinning your actions and enforcing similar controls?