Potential fix for code scanning alert no. 2: Workflow does not contain permissions #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
elmarburke
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/framer/server-api-examples/security/code-scanning/2
To fix the problem, add an explicit
permissionsblock to restrict theGITHUB_TOKENto only those permissions needed. The best way to implement least privilege, and future-proof the workflow, is to set this at the workflow root, which will then apply to all jobs unless a job-levelpermissionsis provided. For the jobs in this workflow (linting, typechecking), onlycontents: readis required, as the jobs merely check out code and do not need to write to issues, PRs, etc.Therefore, insert the following at the top level of
.github/workflows/pull_request.yml(after thename:or immediately below theon:block):This change should be made after the
nameand before theonblock (or immediately afteron:if you prefer grouping triggers together). Preferably, it is conventional to place it afternameand beforeon.Suggested fixes powered by Copilot Autofix. Review carefully before merging.