[uk ai resilience] [uk-ai-resilience] UK AI Governance report - 2026-10-02

[github-actions[bot]]

Executive summary

Lookback 7 days (since 2026-09-25): 133 commits (43 security-signal), 277 open code-scanning alerts, 0 secret-scanning alerts, 68 open security issues. Risk is dominated by CI supply-chain non-determinism and a recurring set of CodeQL Go findings. Nearly every high-priority finding already has an open [uk-ai-resilience] tracking issue, so no new issues were created (duplicate avoidance). Note: the sub-agents were not dispatched; this report was synthesized directly from the pre-computed data, so confidence is moderate.

Asset graph summary (recent-change scoped)

Asset graph

Surface	Evidence	Alerts
Workflow compiler (pkg/workflow)	create_code_scanning_alert.go, mcp_github_config.go, mcp_setup_generator.go, mcp_cli_mount.go, compiler_yaml_ai_execution.go, graders_config.go, github_app_requirements.go	9 allocation-size-overflow, several bad-redirect-check
CLI (pkg/cli)	experiments_command.go, project_command.go, add_package_manifest_*.go	allocation overflow, GraphQL sprintf, bad-redirect-check
CI workflows (.github/workflows)	244 npm-install non-determinism, 10 uv pip-install, 1 inline pip, 1 setup-node unpinned	256 high
Container build	root Dockerfile unpinned base image (#940)	1 high
Scripts	ensure-docs-slide-pdf.js http-to-file	1 medium

Ownership signal: an open issue notes missing CODEOWNERS for security-sensitive paths.

Tier classification

Tiers

Area	Tier	Tracking issue
CI npm/uv install non-determinism (256 alerts)	B	#61636
Dockerfile base image not SHA-pinned (#940)	B	#61166
go/bad-redirect-check (path guards)	B	#57472, #64044
Missing CODEOWNERS	B	#61637
go/allocation-size-overflow (9 alerts)	C	#64043, #63466, #63465, #60876, #60875
GraphQL sprintf in project_command.go (#651/#652)	C	#64527, #52749
ensure-docs-slide-pdf.js http-to-file	C	#53737, #62692
Unpinned pip in daily-geo-optimizer (#768)	C	#61379
GitHub App token minting added/reverted w/o sign-off	C	#60296
`curl	sudo sh` docker sbx install	C

Control verification gaps

• Ownership: no CODEOWNERS for compiler/CLI paths.
• SDLC: CodeQL alerts recur (same files re-flagged, alert numbering drift) — triage is slower than alert creation.
• Dependency: 256 alerts of unpinned/non-locked installs; unpinned Docker image.
• Secrets: no open secret-scanning alerts (control healthy).
• Runtime observability: not independently verified.
• Recovery: App-token release workflow was reverted without documented sign-off.

Risk scoring

Scores (1 low risk – 5 high risk)

Area	Exposure	Patchability	Detectability	Fragility	Ownership conf.	Priority
CI install non-determinism	4	2 (mechanical)	2	3	2	high
Allocation overflow in compiler	3	2	2	3	2	medium
GraphQL sprintf	3	2	2	2	2	medium
curl|sudo sh install	4	2	3	3	2	high
Dockerfile unpinned	3	1	2	2	2	medium

Remediation queue

Item	SLA
Pin/lock CI installs (#61636), sudo installer (#62521)	high
Resolve allocation-overflow and GraphQL sprintf alerts (fix or documented dismissal)	medium
Add CODEOWNERS (#61637)	medium
Pin Dockerfile digest (#61166)	medium
Human review triggers: App-token minting (#60296), any Tier C with low ownership confidence	high

Exception register

None recorded. Any dismissal of recurring CodeQL false positives must carry threat hypothesis, expiry date and mitigation plan.

Operational metrics baseline

• MTTR proxy: many alerts open across multiple runs; recurring tracking issues suggest long remediation time (not precisely measured).
• Ownership coverage: low (no CODEOWNERS for sensitive paths).
• Unsupported dependency ratio: not measured; 256/277 alerts are unpinned install patterns.
• Exception aging: 0 formal exceptions.
• Exposure without recovery capability: 1 known ([uk-ai-resilience] GitHub App token minting for release workflow added and reverted without documented security sign-off (Tier C [Content truncated #60296).

Generated by UK AI Operational Resilience · copilot · auto · 15.7 AIC · ⌖ 6.52 AIC · ⊞ 7.8K · ◷

• expires on Oct 5, 2026, 7:38 AM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by UK AI Operational Resilience.

A newer discussion is available at Discussion #65893.