security: workflow hardening (CODEOWNERS + lint)#82
Open
J0ET0M wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for docs-qubic-org ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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.
What
Adds two files as part of the post-2026-07-13 workflow-hardening rollout:
.github/CODEOWNERS— mandates workflow-security review on.github/workflows/,.github/actions/,.github/CODEOWNERS, and.github/dependabot.yml..github/workflows/lint-workflows.yml— runsactionlint+zizmoron any PR that touches workflow files.Why
Preventive actions #2 and #5 from the 2026-07-13 post-mortem. Together they gate malicious workflow-file additions behind competent security review and catch a large class of insecure workflow patterns automatically.
Follow-up
Preventive action #3 — adding a least-privilege
permissions:block to every existing workflow file in this repo — is a per-workflow manual task. See the repo maintainer guide. Once merged,actionlint/zizmorwill flag workflows missing that block.Branch protection
Branch protection on the default branch will be updated separately (via
rollout.sh protect) to require Code Owner review. Nothing to do in this PR for that.🤖 Rolled out by
incidents/rollout/rollout.sh.