Skip to content

Commit 2d3beb3

Browse files
fix(ci): repoint codeql-action at a SHA that exists (#36)
`github/codeql-action@29b1f65c1f735799893313399435a59f54045865` is pinned here but **exists in no repository** — the GitHub API returns 422 for it. CodeQL therefore could not start: the run graph fails to build and the job reports `startup_failure`, so this repository has had **no CodeQL scanning at all**. Repointed at `4187e74d05793876e9989daffde9c3e66b4acd07`, which is what the `v3` tag currently resolves to (v3.37.3), verified against the API. Found while auditing the estate: the same non-existent SHA was pinned in **104 repositories**, so CodeQL was dead across nearly all of them. ---- ## Summary by Gitar - **Security and governance:** - Added estate-wide `SECURITY.md` policy and removed duplicate governance documentation - Updated workflow permissions across multiple CI configurations for security compliance <sub>This will update automatically on new commits.</sub> --------- Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
1 parent 34a52b9 commit 2d3beb3

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

SECURITY.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,19 @@
11
# Security Policy
22

3+
TEMPLATE INSTRUCTIONS (delete this block before publishing)
4+
Replace all {{PLACEHOLDER}} values with your information:
5+
Squisher Corpus - Your project name
6+
hyperpolymath - GitHub username or org (e.g., hyperpolymath)
7+
squisher-corpus - Repository name
8+
j.d.a.jewell@open.ac.uk - Security contact email
9+
TBD - Your PGP key fingerprint (40 chars, no spaces)
10+
https://github.com/hyperpolymath.gpg - URL to your public PGP key
11+
github.com/hyperpolymath/squisher-corpus - Your website/domain
12+
2026 - Current year for copyright
13+
14+
Optional: Remove sections that don't apply (e.g., PGP if you don't use it)
15+
-->
16+
317
We take security seriously. We appreciate your efforts to responsibly disclose vulnerabilities and will make every effort to acknowledge your contributions.
418

519
## Table of Contents

0 commit comments

Comments
 (0)