Skip to content

[compiler-threat-spec] Daily compiler threat spec audit (2026-11-13) #77313

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
pelikhan merged 1 commit into from
Nov 13, 2026
Merged

[compiler-threat-spec] Daily compiler threat spec audit (2026-11-13) #77313

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions .changeset/threat-spec-audit-2026-11-13.md
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

12 changes: 12 additions & 0 deletions specs/compiler-threat-detection-changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,18 @@ The unreleased 1.0.81 merge-policy mapping also covers ambiguous check producers

## Mapping Audits

### Mapping Audit (2026-11-13)

Reviewed commits from the last two days touching compiler, parser, bootstrap, and runtime security boundaries.

Findings and disposition:

- Firewall v0.29.12 checksum pin (#77231, #77082): already covered by the independently provisioned release-digest bootstrap controls mapped in security architecture §6.8 and the Section 2 bootstrap note; the checksum entry in `actions/setup/sh/release_integrity.sh` matches `DefaultFirewallVersion`. No rule change.
- Quote-adjacent HTML attribute sanitization (#77007) and the earlier temporary-file, symlink, and step-summary hardening (#76954, #76958, #76974): runtime content-sanitization and filesystem controls that the compiler does not detect in authored workflows. Existing CTR-017 coverage is unchanged. No new `CTR-*` rule.
- `status_changed` issue trigger acceptance (#77179): schema/trigger validation only; it grants no permission and introduces no new threat class.
- Open high-severity code-scanning alerts: none returned (one item was withheld by the secrecy policy). No `threat-detection-suppress` annotations exist in workflow sources, so no suppression SLA action applies.
- Go tests could not be executed in this environment (the required Go 1.27.4 toolchain could not be downloaded); no implementation or normative specification text changed, so no version bump was made.

### Mapping Audit (2026-11-12)

Reviewed commits from the last two days touching compiler, parser, and runtime security boundaries.
Expand Down
Loading