ci(live-ebsi): pin least-privilege GITHUB_TOKEN permissions#138
Merged
Conversation
CodeQL alert #1 (actions/missing-workflow-permissions): live-ebsi.yml was the only workflow without an explicit permissions block, so its token inherited the repository-wide default. Practical exposure was already low — the repo default is read-only, there is no pull_request trigger, and the job only checks out, installs and runs pytest against the live registries without touching the GitHub API. Pinned anyway because this is the one unattended, scheduled workflow: an explicit block keeps it read-only regardless of a later change to the default. CI-only, the published artifact is unchanged: no CHANGELOG entry and no release (same as #126 / PR #132). Closes #137
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
1 participant
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.
ci(live-ebsi): pin least-privilege GITHUB_TOKEN permissions
CodeQL alert #1 (actions/missing-workflow-permissions): live-ebsi.yml was
the only workflow without an explicit permissions block, so its token
inherited the repository-wide default.
Practical exposure was already low — the repo default is read-only, there
is no pull_request trigger, and the job only checks out, installs and runs
pytest against the live registries without touching the GitHub API. Pinned
anyway because this is the one unattended, scheduled workflow: an explicit
block keeps it read-only regardless of a later change to the default.
CI-only, the published artifact is unchanged: no CHANGELOG entry and no
release (same as #126 / PR #132).
Closes #137