Actions lockfiles prevent this. They won't allow you to lock an impostor commit, which is the right default.
(The previous way to provide general actions immutability, i.e. hash-pinning, had this issue and thus required additional checks.)
One could write an action that executes a shell script that does docker pull abc:latest.
As the consumer of an action that becomes really hard to find out unless I take the whole codebase apart.
Re:Lock Your GitHub Actions
by embedding-shape on Thursday November 12, 2026 @09:37AM
(#50468001)
> As the consumer of an action that becomes really hard to find out unless I take the whole codebase apart.
Maybe it's just me, but I only use (public) Actions I'm able to review in an hour or less, meaning less than 5K LOC or so. Not sure how people are able to just "consume" 3rd party GitHub Actions and not even review what exactly they do, how are people comfortable with the risks this opens up? It's literally supply-chain wild west, but seemingly people continue like it's 2010.
Re:Lock Your GitHub Actions
by chrisweekly on Wednesday November 11, 2026 @06:31PM
(#50460502)
I almost forgot about that completely outrageous treatment of forks -- just bonkers.
That’s exactly what lockfiles are intended to avoid!
IMO Github should make Immutable tags mandatory to publish on https://github.com/marketplace