chore(workflow): explicitly set permissions on workflow #128
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/opengovsg/formsg-javascript-sdk/security/code-scanning/6
To fix the problem, we should explicitly set a restrictive
permissionsblock in the workflow configuration. The best approach is to add apermissions:block at the top-level of the workflow configuration (aftername:and beforeon:or afteron:and beforejobs:). This will apply to all jobs unless a job-specific block is set. For typical CI workflows like this,contents: readis sufficient, as the jobs only check out code and interact with packages, not with repository contents in a write capacity. If future jobs require more, they can override at the job level.The only change required is adding the following at the root of
.github/workflows/ci.yml:No additional methods, imports, or definitions are necessary.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.