ci(security): install the Strix worm-guard gate - #192
Open
stayawakebot[bot] wants to merge 1 commit into
Open
Conversation
Pin Ndevu12/strix@93fe465d7b02. Opened by `saw guard setup`.
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.
Installs the Strix worm-guard CI gate — opened by
saw guard setup..github/workflows/worm-guard.ymlNdevu12/strix@93fe465d7b02…(93fe465d7b0266c6010778999b73b591ae082f3e)worm-guard): scans PRs/pushes and, on an infected verdict, opens ONE rollingsecurity/auto-cleanfix PR (needscontents: write+pull-requests: write, granted at the job level). The gate stays red until that fix PR is merged — remediation opens the fix, it does not make the check pass.pin-drift): weekly (+ manual) it files ONE self-closing issue if the pinned Strix release falls behind (issues: writeonly).Please finish the hardening (a PR can't set these):
.github/**(andconfig/security.yml, if used).GH_SECURITY_TOKENsecret (a PAT with repo + PR scope) so the fix PR itself gets scanned — a PR opened with the built-in token does not re-trigger this gate.A PR opened by a bot token may not trigger the new workflow on this PR — push an empty commit to run the gate on itself. This is a single rolling PR; re-runs update it.