Potential fix for code scanning alert no. 45: Workflow does not contain permissions #125
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/John0n1/ON1Builder/security/code-scanning/45
In general, fix this by explicitly specifying a minimal
permissionsblock for the workflow or individual jobs so theGITHUB_TOKENdoes not inherit overly broad repository defaults. For a simple CI job that only checks out code and runs local tools,contents: readis sufficient.For this specific workflow, the simplest and safest fix without changing functionality is to add a root-level
permissionsblock directly undername: CI, settingcontents: read. This will apply to all jobs (currently onlylint) that do not override permissions. No additional imports or methods are required because this is a YAML configuration change only.Concretely: edit
.github/workflows/ci.ymland insert:between the existing
name: CIline and theon:block. No other lines need to change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.