[check actions] setting GITHUB_TOKEN permissions to read #3983
Conversation
This file contains 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
This change limits the scope of GITHUB_TOKENs to read-only for all contexts for the checker actions. This is a part of adopting security best practices of the OpenSSF based on the ScoreCard tool [1] [1] https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
Setting read-only permission for all scopes for the GITHUB_TOKEN used in all remaining workflows. This is a part of adopting security best practices of the OpenSSF based on the ScoreCard tool [1] [1] https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
bruntib
approved these changes
Aug 24, 2023
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.
This change limits the scope of GITHUB_TOKENs to "read-only" for all contexts for the checker actions.
This is one part of adopting security best practices of the OpenSSF based on the ScoreCard tool [1] as outlined in issue #3977.
Moreover, this PR only updates one workflow. For the other workflows, we need to determine if read-only is feasible or if some actions must be run with write permissions.
[1] https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions