Potential fix for code scanning alert no. 2: Workflow does not contain permissions#85
Merged
robertodauria merged 1 commit intomainfrom Jan 13, 2026
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Collaborator
Pull Request Test Coverage Report for Build 20940884726Details
💛 - Coveralls |
bassosimone
approved these changes
Jan 13, 2026
Collaborator
bassosimone
left a comment
There was a problem hiding this comment.
Surprising that the default is write, BTW 😅
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/m-lab/autojoin/security/code-scanning/2
To fix the problem, we must explicitly set
permissionsfor the workflow or individual jobs, restricting theGITHUB_TOKENto the minimal scopes required. This workflow checks out code, runsgo test, and sends coverage viashogo82148/actions-goveralls@v1. These operations only require read access to repository contents; they do not create or modify issues, PRs, or repository data. Therefore, settingpermissions: contents: readat the workflow (top) level is an appropriate least‑privilege configuration and will apply to bothcoverageandfinishjobs.The best fix without changing functionality is to add a root-level
permissionsblock directly under thename: coverageline in.github/workflows/coverage.yml. This will ensure that, unless a job overrides permissions, both jobs run withcontents: readand no write scopes. No other code, steps, or actions need modification, and no imports or additional methods are involved, as this is a pure YAML configuration change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.
This change is