Skip to content

ci(security): SHA-pin reusable security-scan workflow #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
WomB0ComB0 merged 2 commits into from
May 31, 2026
+11 −1
Merged

ci(security): SHA-pin reusable security-scan workflow #30

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
78faf58
ci(security): SHA-pin reusable security-scan workflow
WomB0ComB0 May 31, 2026
1b33b66
Merge branch 'main' into ci/pin-security-scan-sha
WomB0ComB0 May 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion .github/workflows/security.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,18 @@ permissions:

jobs:
scan:
uses: resq-software/.github/.github/workflows/security-scan.yml@main
# SHA-pinned to satisfy the org "actions must be pinned to a full-length
# commit SHA" policy. The previous mutable `@main` ref tripped the zizmor
# `unpinned-uses` code-scanning alert and is the most likely cause of the
# scheduled-run startup failures. Trailing comment lets Dependabot still
# propose updates. Matches the SHA-pin convention already used in ci.yml.
uses: resq-software/.github/.github/workflows/security-scan.yml@ee2001974be1e5610cff3a2c669cfab95c7415e7 # main (2026-05-04, #20)
with:
languages: '["actions"]'
enable-semgrep: true
# `inherit` is required here: the reusable workflow consumes org-level
# secrets (e.g. SEMGREP_APP_TOKEN) that are NOT declared in its
# `workflow_call.secrets` block, so they cannot be forwarded explicitly.
# Fully clearing the zizmor `secrets-inherit` warning needs an org-side
# `secrets:` declaration in security-scan.yml first (tracked separately).
secrets: inherit