ci: add zizmor GitHub Actions security lint - #471
Conversation
|
Warning Review limit reached
Next review available in: 42 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe changes add workflow security linting, scope release permissions, disable persisted checkout credentials, pass release data through environment variables, and add seven-day Dependabot cooldowns. The Dependabot auto-merge workflow is also removed. ChangesWorkflow security and update controls
Estimated code review effort: 3 (Moderate) | ~20 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/release.yml (1)
15-18: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick winAdd a default-deny workflow permission baseline.
The patch scopes the current jobs, but it removes the workflow-level permission block. Add
permissions: {}at workflow scope so future jobs do not inherit the repository default. GitHub supports an empty permission map for this purpose. (docs.github.com)Proposed hardening
on: push: branches: [main] +permissions: {} + jobs:🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/release.yml around lines 15 - 18, Add a workflow-level permissions baseline in release.yml by setting permissions to an empty map alongside the top-level workflow configuration, while preserving the existing job-level permissions for required access.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/workflows/release.yml:
- Around line 15-18: Add a workflow-level permissions baseline in release.yml by
setting permissions to an empty map alongside the top-level workflow
configuration, while preserving the existing job-level permissions for required
access.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 01a9db8d-57a2-4bcd-9fa6-4adbf76af824
📒 Files selected for processing (3)
.github/dependabot.yml.github/workflows/dependabot.yml.github/workflows/release.yml
💤 Files with no reviewable changes (1)
- .github/workflows/dependabot.yml
Adds zizmor security analysis to the existing lint workflow. The job uses read-only permissions, disables checkout credential persistence, and emits GitHub annotations without uploading SARIF to Advanced Security.
Summary by CodeRabbit