Potential fix for code scanning alert no. 5: Workflow does not contain permissions#20
Merged
Potential fix for code scanning alert no. 5: Workflow does not contain permissions#20
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/zen-eth/multiformats-zig/security/code-scanning/5
The best way to fix the problem is to explicitly set a
permissionskey with the minimal required permissions for the workflow or individual jobs. Since this workflow appears to only check out code, cache dependencies, and run tests/builds (it does not interact with the repository beyond reading its contents), the minimal required permission iscontents: read. This key can be added either at the workflow root level (i.e., above thejobsblock, which will apply to all jobs) or at the job level (inside each job). The more concise and maintainable approach is to add it at the workflow root, directly beneath thenameand beforeon. No methods, imports, or additional definitions are required for this change—just this configuration key.Suggested fixes powered by Copilot Autofix. Review carefully before merging.