Add Sentinel CI workflow for workflow security scanning#66
Conversation
5f1136e to
5e9149f
Compare
|
Force-pushed with SHA-pinned actions to satisfy zizmor's unpinned-uses rule. Per the org-wide sentinel rollout, the floating-tag-for-easy-updates model is being replaced with SHA-pin + dependabot. Spec updated. Rest of the PR unchanged. |
|
Promoted to blocking mode — this repo had zero sentinel findings on the warn-only scan, so we're skipping the 7-day warn-only observation period. fail-on-findings is now true; future PRs that introduce critical/high findings will block merge. |
5e9149f to
33712dd
Compare
|
Promoted to blocking mode — this repo had zero sentinel findings on the warn-only scan, so we're skipping the 7-day warn-only observation period. fail-on-findings is now true; future PRs that introduce critical/high findings will block merge. |
1 similar comment
|
Promoted to blocking mode — this repo had zero sentinel findings on the warn-only scan, so we're skipping the 7-day warn-only observation period. fail-on-findings is now true; future PRs that introduce critical/high findings will block merge. |
Part of org-wide sentinel rollout. Warn-only mode (fail-on-findings: false). Spec: https://www.notion.so/copilotkit/3683aa381852818bacd8e14eb7233c22
33712dd to
d0a4de6
Compare
Summary
.github/workflows/sentinel.ymlfor automated workflow security scanning via Sentinelmainfail-on-findings: false) — surfaces findings without blocking mergesDetails
Sentinel scans GitHub Actions workflows for security issues (credential exposure, injection risks, overly broad permissions, unpinned actions, etc.). This initial rollout uses
severity: highto focus on the most impactful findings.Test plan