Potential fix for code scanning alert no. 1813: Workflow does not contain permissions #4923
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/codeharborhub/codeharborhub.github.io/security/code-scanning/1813
To fix the problem, explicitly define a least-privilege
permissionsblock for thebuildjob (or at the workflow root) so it does not inherit broad repository defaults. Thebuildjob checks out the code, installs dependencies, builds, and uploads a Pages artifact; this only requires read access to repository contents and the ability to upload the artifact. The upload-pages-artifact action does not require extra repo write permissions; current GitHub docs recommendcontents: readfor the build job.The best minimal fix without changing functionality is:
permissions: contents: readto thebuildjob.permissionsblock on thedeployjob unchanged, since it is already least-privilege for Pages deployment (pages: write,id-token: write).Concretely:
.github/workflows/deploy.yml, underjobs: build:, insert apermissions:section beforeruns-on: ubuntu-latest:No other imports or definitions are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.