ci(zizmor): enforce high/high GitHub Actions security gate - #6
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
netram-netizen
marked this pull request as ready for review
July 13, 2026 09:54
rmachielse
approved these changes
Jul 14, 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
2 participants
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.
Adds the org-standard
zizmor.ymlworkflow, gating GitHub Actions security findings at high severity / high confidence (perpolicies/zizmor.md).advanced-security: false→ a high/high finding fails the check (fail-closed).permissions.Opened as draft: local offline scans are clean at high/high, but this workflow run also executes the online audits (known-vulnerable-actions, impostor-commit, ref-confusion, stale-action-refs). Will be marked ready once the check passes.
🤖 Generated with Claude Code