Repository navigation
Conversation
hrai-nr
approved these changes
Sep 21, 2026
maya-jha
approved these changes
Sep 22, 2026
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.
Summary
Adds explicit
permissionsblocks topull_request.yamlandtrivy_schedule.yaml. CodeQL (ruleMissingActionsPermissions) flagged both workflows for running jobs without a definedGITHUB_TOKENscope, leaving the token at its default, broader access level.Changes
pull_request.yamlpermissions: contents: readas the baseline for all jobs.security(contents: read,security-events: write), since it runsgithub/codeql-action/upload-sarifto publish CFN Nag results, which requires that scope.validate-template-code,trivy-scan, andtest-and-coverageinherit the workflow-level default and need nothing more.test-and-coveragejob stays read-only as it uploads a coverage report viaactions/upload-artifact, which authenticates through the separateACTIONS_RUNTIME_TOKENGitHub injects into every job, notGITHUB_TOKEN. It isn't governed by thepermissions:block at all, so no write scope is needed there.trivy_schedule.yamlpermissions(contents: read,security-events: write) directly on the singletrivyjob, since it also callsupload-sarif.Testing
codeql database create ./codeql-actions-db --language=actions --source-root . --overwrite codeql database analyze ./codeql-actions-db codeql/actions-queries --format=sarif-latest --output=actions-results.sarif --downloadConfirmed the
MissingActionsPermissionsfindings for both files no longer appear inactions-results.sarif