Scope dependabot-repair workflow token permissions to least privilege#43411
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update static analysis report for 2026-07-04
Scope Jul 4, 2026
dependabot-repair workflow token permissions to least privilege
Contributor
🤖 PR Triage — Run §28715668077
Minimal low-risk YAML change adding correct token permission scopes. Recommend undraft → fast-track.
|
This was referenced Jul 4, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR narrows the GITHUB_TOKEN permission surface for the dependabot-repair workflow to address a zizmor excessive-permissions signal by replacing read-all with explicit read-only scopes and updating the compiled workflow output accordingly.
Changes:
- Replaced
permissions: read-allwith explicit read-only permissions (actions,contents,issues,pull-requests) in the workflow source. - Recompiled the generated
.lock.ymlso theagentjob now uses the scoped read permissions.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/dependabot-repair.md | Replaces read-all with explicit read-only permission scopes. |
| .github/workflows/dependabot-repair.lock.yml | Updates compiled workflow to apply the narrowed permissions to the agent job. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Low
Comment on lines
+9
to
+13
| permissions: | ||
| actions: read | ||
| contents: read | ||
| issues: read | ||
| pull-requests: read |
Copilot AI
added a commit
that referenced
this pull request
Jul 5, 2026
…ge (#43411) Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
The static-analysis report was flat overall, with one actionable non-FP signal: zizmor
excessive-permissionsondependabot-repair.lock.yml(agentjob). This change narrows default workflow permissions so the compiled job no longer inherits broad token scope.Problem focus
excessive-permissionsfinding independabot-repairwhile leaving accepted FP clusters unchanged.Workflow source change (
.github/workflows/dependabot-repair.md)permissions: read-allwith explicit read-only scopes:actions: readcontents: readissues: readpull-requests: readGenerated workflow impact (
.github/workflows/dependabot-repair.lock.yml)agentjob instead ofread-all.safe_outputs/conclusionjobs remain explicit and unchanged.