Potential fix for code scanning alert no. 3: Workflow does not contain permissions #207
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/openfoodfacts/nutripatrol-frontend/security/code-scanning/3
To address this issue, you should add an explicit
permissionsblock to your workflow to limit theGITHUB_TOKEN's scope. Since none of the deploy steps require write access to repository contents, the principle of least privilege applies, and you should restrict permissions tocontents: read, which means the workflow can only read repository contents, not write or alter them. This block can be added either at the workflow root (recommended when all jobs have the same minimal permissions), or to each individual job. In this case, adding it at the root near the top of the.github/workflows/deploy.ymlfile—prior to thejobs:block—is clear and effective.Implementation steps:
name: ...line, before theon::Suggested fixes powered by Copilot Autofix. Review carefully before merging.