Potential fix for code scanning alert no. 18: Workflow does not contain permissions#19
Merged
Dhruvacube merged 1 commit intomasterfrom Jun 15, 2025
Merged
Potential fix for code scanning alert no. 18: Workflow does not contain permissions#19Dhruvacube merged 1 commit intomasterfrom
Dhruvacube merged 1 commit intomasterfrom
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Dhruva Shaw <dhruvashaw@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/Creatrix-Net/creatrix-net.github.io/security/code-scanning/18
To fix the issue, add a
permissionsblock to the workflow. Since the workflow primarily interacts with repository contents and pushes Docker images, the permissions can be limited tocontents: read. This ensures the workflow has only the necessary access to repository contents while preventing unintended write access.The
permissionsblock should be added at the root level of the workflow file to apply to all jobs. Alternatively, it can be added to the specific job (build) if different jobs require different permissions.Suggested fixes powered by Copilot Autofix. Review carefully before merging.