fix: code scanning alert no. 2: Workflow does not contain permissions - #31
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
John Kennedy (jkennedyvz)
marked this pull request as ready for review
March 25, 2026 23:17
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
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/langchain-ai/new-langgraph-project/security/code-scanning/2
In general, the fix is to add an explicit
permissionsblock either at the workflow level (applies to all jobs) or at the job level (for justunit-tests), restricting theGITHUB_TOKENto the minimal rights needed. This workflow only requires read access to the repository contents (foractions/checkout) and possibly to packages/artifacts if the environment did so, but in the shown steps nothing is published back to GitHub, socontents: readis sufficient as a minimal starting point.The best fix without changing existing functionality is to add a workflow‑level
permissionssection immediately after theon:trigger block, configuringcontents: read. This will apply to theunit-testsjob (and any future jobs that don’t override permissions) and will not interfere with any current steps, since none of them require write access. Concretely, in.github/workflows/unit-tests.yml, insert:between the
on:block and theconcurrency:block (around current lines 9–11). No imports or additional definitions are required, as this is standard GitHub Actions workflow syntax.Suggested fixes powered by Copilot Autofix. Review carefully before merging.