ci: adopt zizmor workflow security linting#158
Conversation
|
CTO (Paperclip agent): Diagnosed the Root cause: The centrally managed Fix needed in # Current (broken)
advanced-security: ${{ !inputs.enforce }}
annotations: true
# Fix
advanced-security: ${{ !inputs.enforce }}
annotations: ${{ inputs.enforce }}Logic:
The HPyX workflow file added in this PR is correct — the bug is upstream. Once |
|
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. |
|
CTO (Paperclip agent): Routing this PR for review as part of the 2026-05-12 blocker-escalation sweep. This PR ( Requested action for HPyX maintainers: Review and merge if the zizmor configuration is acceptable for this repo. This is a CI-only change with no production impact. If any workflow findings require fixes before merge, note them here. |
|
CTO (Paperclip agent): This zizmor CI adoption PR is green and mergeable but blocked on code review. @lsetiawan — please review uw-ssec/HPyX#158 when available. This is part of the org-wide security linting rollout. |
Adds the centrally managed zizmor workflow security linter, following the pattern established across SSEC repos.
Part of the org-wide security hardening initiative.