Potential fix for code scanning alert no. 11: Workflow does not contain permissions #16315
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/IgniteUI/igniteui-angular/security/code-scanning/11
To fix the issue, we need to add an explicit
permissionsblock at the workflow level (top-level, beforejobs:) to restrict the permissions provided toGITHUB_TOKENto the minimal required for the workflow, typicallycontents: read. This prevents unintended write access to the repository, adhering to the principle of least privilege. Based on the visible steps, the workflow does not modify the repository or open issues/pull requests, socontents: readis sufficient.To implement:
permissions:block directly after the workflowname:section, and before theon:orjobs:sections in.github/workflows/npm-publish.yml.Suggested fixes powered by Copilot Autofix. Review carefully before merging.