Potential fix for code scanning alert no. 1: Workflow does not contain permissions #37
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/DataScience-GT/query/security/code-scanning/1
In general, fix this by explicitly declaring minimal
GITHUB_TOKENpermissions for the workflow or for each job. For a pure build job that only checks out code and runs local commands,contents: readis usually sufficient. Add apermissionsblock either at the root level (applies to all jobs) or under thebuildjob (applies only to that job).The best minimal change here is to add a job-level
permissionsblock underjobs.build, just aboveruns-on. This avoids affecting any other jobs that might be added later and keeps the change clearly scoped. No other functionality changes are required, and no imports or dependencies are involved because this is a YAML configuration file.Concretely, in
.github/workflows/pnpm-build.yml, modify thebuildjob definition so that:This explicitly restricts the
GITHUB_TOKENfor this job to read-only access to repository contents.Suggested fixes powered by Copilot Autofix. Review carefully before merging.