Potential fix for code scanning alert no. 4: Workflow does not contain permissions #39
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/edgee-cloud/segment-component/security/code-scanning/4
In general, to fix this issue you add an explicit
permissions:block either at the workflow root (to cover all jobs) or on the specific job flagged, granting only the minimal scopes required (oftencontents: read). In this workflow, some jobs already have tailored permissions (clippyneedschecks: write,coverageneedscontents: read), so the most targeted and least disruptive fix is to add apermissions:block to thetestjob itself.Concretely, edit
.github/workflows/check.ymlunder thetest:job definition. Right afterruns-on: ubuntu-latest(line 74), insert apermissions:section settingcontents: read. This mirrors the minimal permission used by thecoveragejob and is sufficient for standard operations likeactions/checkoutand running tests, while preventing unnecessary write access. No imports or additional definitions are needed, since this is purely a YAML configuration change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.