Potential fix for code scanning alert no. 6: Workflow does not contain permissions#20
Merged
JonathanPiaget merged 1 commit intomainfrom Oct 24, 2025
Merged
Potential fix for code scanning alert no. 6: Workflow does not contain permissions#20JonathanPiaget merged 1 commit intomainfrom
JonathanPiaget merged 1 commit intomainfrom
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.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
1 participant
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/JonathanPiaget/SearchMark/security/code-scanning/6
To fix this issue, an explicit
permissionsblock should be added to the workflow to restrict theGITHUB_TOKENaccording to the principle of least privilege. This can be done at the root of the workflow to apply to all jobs, with further customization at the job level if needed. In this workflow, jobs that read contents (checkout, versioning, submit to stores) only needcontents: read, but theReleasejob (usingsoftprops/action-gh-release) requirescontents: writeto create a release. The minimum fix is to add a root-levelpermissionsblock withcontents: read, and override it withcontents: writefor theReleasejob. Edits should be made at the root level (after the name, before or afteron:), and in theReleasejob spec.Suggested fixes powered by Copilot Autofix. Review carefully before merging.