Potential fix for code scanning alert no. 2: Workflow does not contain permissions#18
Merged
ialejandro merged 2 commits intofix/security-improvesfrom Feb 15, 2026
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Iván Alejandro Marugán <hello@ialejandro.rocks>
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
2 participants
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/devops-ia/self-learning-platform/security/code-scanning/2
To fix the problem, define an explicit
permissions:block that restrictsGITHUB_TOKENto the least privilege needed. Since this workflow only reads the code (viaactions/checkout) and uploads artifacts, and does not write to the repository or modify issues/PRs, we can setcontents: readat the top (root) level of the workflow. That setting applies to all jobs that do not overridepermissions. No job in the shown snippet needs elevated permissions, so a single root-level block is enough.Concretely, in
.github/workflows/lint-test.yml, add:between the
name:andon:keys (for example after line 1 or before line 3). This documents the intended permissions and ensures that even if org/repo defaults are broad (read-write) or change in the future, these jobs will only have read access to repository contents. No additional imports, methods, or other definitions are required.Suggested fixes powered by Copilot Autofix. Review carefully before merging.