Skip to content

Conversation

@teolemon
Copy link
Member

@teolemon teolemon commented Nov 4, 2025

Potential fix for https://github.com/openfoodfacts/openfoodfacts-web/security/code-scanning/7

To fix the problem, explicitly specify a permissions block either at the workflow root (recommended for all jobs) or at the individual job level. Since this workflow does not seem to use the GITHUB_TOKEN at all, we can set permissions: {}
at the root which results in no permissions for the GITHUB_TOKEN. This is the strictest and most secure setting. Adding the permissions block at the top (after name: and before or after on:) is sufficient. No further code or external changes are necessary.


Suggested fixes powered by Copilot Autofix. Review carefully before merging.

…n permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: To Discuss & Validate

Development

Successfully merging this pull request may close these issues.

2 participants