Restrict links workflow to contents: read - #1679
Conversation
zizmor flags the linkChecker job for excessive-permissions: with no permissions block it inherits the default broad token. The workflow only checks out the repo and runs a link checker, so contents: read is sufficient. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesWorkflow Token Permissions
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
zizmor reports an
excessive-permissionsfinding for thelinkCheckerjob inlinks.yml: with nopermissions:block it inherits the default broad token. The workflow only checks out the repo and runs a link checker, so this grants it the minimalcontents: readat the workflow level (matching the style ofprecious.yml).🤖 Generated with Claude Code
Summary by CodeRabbit