General Tech
Lock Your GitHub Actions
GitHub Actions can be vulnerable to supply-chain attacks if not properly configured, but GitHub recommends using lockfiles to mitigate this risk. To use lockfiles, update to GitHub Actions version 1.32.0 or higher, and use the `gh actions-lock` command to relock after modifying workflow files. Additionally, use a security linter like zizmor to scan for vulnerabilities. Lockfiles can be verified using a CI workflow, such as the `verify-lockfile.yml` example provided. It is recommended to pin the version of zizmor to avoid future vulnerabilities.
Read the full article at hugovk.dev →