Potential fix for code scanning alert no. 5: Workflow does not contain permissions - #776
Closed
berland wants to merge 1 commit into
Closed
Potential fix for code scanning alert no. 5: Workflow does not contain permissions#776berland wants to merge 1 commit into
berland wants to merge 1 commit into
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Collaborator
Author
|
Superseded by #778 |
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/equinor/semeio/security/code-scanning/5
The best way to fix this problem is to specify the job's permissions so that the GITHUB_TOKEN granted to each job only has the minimal required access, rather than inheriting potentially dangerous repository defaults. Since this workflow does not require write access to the repository or any other special privileges, the optimal fix is to add a
permissions:block to the job definition fortype-checking(line 15), settingcontents: read. This can be done by inserting:immediately after line 15 (under
type-checking:), before any steps. No new packages or imports are required.Suggested fixes powered by Copilot Autofix. Review carefully before merging.