security.yml: run gitleaks and trivy as GitHub-hosted actions so consumers can restrict allowed actions (K22-REPO-32) #35

Open
opened 2026-10-11 13:30:23 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-11 13:30:23 +00:00 (Migrated from github.com)

The shared security workflow runs gitleaks and trivy as docker:// container steps. GitHub's 'Allow select actions' policy cannot allow docker:// references, so any consumer that applies K22-REPO-32 (allowed actions = GitHub-authored + verified + listed) gets a startup_failure on the security workflow. Seen on KofTwentyTwo/gclo on 2026-10-11 (KofTwentyTwo/gclo#66).

Proposal: replace the docker:// steps with pinned GitHub-hosted actions (gitleaks/gitleaks-action, aquasecurity/trivy-action), or document in repository.md that REPO-32 is not applicable while the shared workflow uses container steps.

The shared security workflow runs gitleaks and trivy as docker:// container steps. GitHub's 'Allow select actions' policy cannot allow docker:// references, so any consumer that applies K22-REPO-32 (allowed actions = GitHub-authored + verified + listed) gets a startup_failure on the security workflow. Seen on KofTwentyTwo/gclo on 2026-10-11 (KofTwentyTwo/gclo#66). Proposal: replace the docker:// steps with pinned GitHub-hosted actions (gitleaks/gitleaks-action, aquasecurity/trivy-action), or document in repository.md that REPO-32 is not applicable while the shared workflow uses container steps.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/standards#35