Potential fix for code scanning alert no. 142: Workflow does not contain permissions#1006
Merged
Potential fix for code scanning alert no. 142: Workflow does not contain permissions#1006
Conversation
…ain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
maartenba
approved these changes
Feb 3, 2026
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/DuendeSoftware/docs.duendesoftware.com/security/code-scanning/142
In general, the fix is to add an explicit
permissionsblock to the workflow (either at the top level or per job) that grants only the minimal access needed. For this workflow, the only required permission is read access to repository contents so thatactions/checkoutcan fetch the source code; no write operations are present.The best way to fix this without changing functionality is to add a root-level
permissionssection directly under the workflowname:(or equivalently right after theon:block) specifyingcontents: read. Root-level permissions will apply to all jobs that don’t override them, which suits this simple single-job workflow. Specifically, in.github/workflows/ci.yml, insert:near the top of the file (e.g., after
name: ci). No imports or extra definitions are needed, and no steps or job structure must change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.