-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distinguishing immutable from mutable actions as a consumer #216
Comments
My suggestion is using OCI image name syntax like
|
With the current syntax it's not possible to determine if it's an action is immutable or not from only the YAML. However, we can query the GitHub Container Registry to see if an OCI artifact with the action's name exists. If yes, it's an immutable action. If no, it's a classic/traditional/mutable action. For example: ghcr.io/docker/build-push-action
Specifically, we'd be looking to see that the |
The README shows the following example for consuming an immutable action:
This is indistinguishable from the existing syntax for mutable actions, which I assume is for backwards compatibility reasons.
Is there anyway for a consumer or analysis tool to know what security guarantees to expect from an action (e.g. if pinning to a SHA is necessary for immutability)?
The text was updated successfully, but these errors were encountered: