[uk ai resilience] [uk-ai-resilience] UK AI open code risk report - 2026-10-06

[github-actions[bot]]

Executive summary

Lookback 7 days (since 2026-09-29): 281 commits (155 Copilot, 50 human, 43 bot, 24 dependabot), 114 security-signal commits, 42 open security issues, 279 open code-scanning alerts (0 secret-scanning). No Tier D candidates. Most risk is supply-chain determinism (non-pinned installs in compiled workflows) and unowned changes to security-sensitive paths. Sub-agents were not dispatched; analysis was performed directly from the pre-computed data (limitation: lower confidence on ownership signals).

Asset graph summary (recent-change scoped)

Asset graph

Segment	Surface	Signals
.github/workflows/*.lock.yml	compiled workflows (CI runtime)	249 npm-lockfile + 10 uv-pip non-deterministic install alerts
.github/scripts/*.cjs, scripts/*.mjs	automation scripts	5 js/insecure-temporary-file alerts (new 2026-10-05)
pkg/workflow, pkg/cli (Go)	compiler/CLI	5 go/bad-redirect-check, 2 GraphQL sprintf alerts (project_command.go:269,272)
Dockerfile	release/compiler image	alpine:3.24 not SHA-pinned (alert #940)
MCP server container images	runtime	CVE burn-down issues #65791–#65797

Ownership: no .github/CODEOWNERS present (see #61637).

Tier classification

Tiers

Area	Tier
Compiled workflow installs	B
Automation scripts temp files	B
Dockerfile base image	B
GraphQL sprintf in project_command.go	B
Go redirect checks (pkg/workflow, pkg/cli)	A (low risk, informational)
Core compiler/CLI code	A
MCP container images (CVEs)	B

Control verification gaps

• Ownership: no CODEOWNERS (open [uk-ai-resilience] Missing .github/CODEOWNERS for security-sensitive compiler/CLI paths (Tier B) #61637).
• SDLC: 259 unpinned/non-deterministic installs; Dockerfile not digest-pinned.
• Dependency: unpinned MCP npm/uvx/container refs ([deep-report] Pin unpinned npm/uvx package versions in agentdb, ruflo, and fabric-rti MCP servers #65971, [deep-report] Pin unpinned container images for kreuzberg and skillz MCP servers #65970).
• Secrets: 0 secret alerts; predictable JUPYTER_TOKEN ([deep-report] Replace predictable JUPYTER_TOKEN (github.run_id) with a generated secret #65969).
• Observability: code scanning active; alert aging visible (oldest open: 2026-07-24).
• Recovery: no explicit rollback/patch runbook evidence found; release token-minting lacked sign-off ([uk-ai-resilience] GitHub App token minting for release workflow added and reverted without documented security sign-off (Tier C [Content truncated #60296).

Risk scoring

Scores (1 low – 5 high risk)

Area	Exposure	Patchability	Detectability	Fragility	Ownership conf.	Priority
Workflow installs	4	2	2	3	3	high
Temp-file scripts	3	2	2	2	3	medium
Dockerfile base image	3	1	3	2	3	medium
GraphQL sprintf	2	1	2	2	3	medium
Container CVEs	3	3	1	3	3	high

Remediation queue

Item	SLA	Tracking
Non-deterministic installs	high	#65894 (existing)
Insecure temp files	high	#65895, #65978 (existing)
CODEOWNERS	high	#61637 (existing)
Dockerfile digest pin	medium	new issue
GraphQL sprintf hardening	medium	new issue
MCP image/package pinning	medium	#65969–#65971

Human-review trigger: any change to release/token-minting workflows or low ownership confidence.

Exception register

None. No hidden-repo exceptions recommended.

Operational metrics baseline

• MTTR proxy: oldest open code-scanning alert 2026-07-24 (~74 days); alerts opened in window: 6.
• Ownership coverage: 0% formal (no CODEOWNERS).
• Unsupported dependency ratio: not measured; 259/279 alerts are install-determinism related.
• Exception aging: 0 exceptions.
• Exposure without recovery capability: release token-minting path ([uk-ai-resilience] GitHub App token minting for release workflow added and reverted without documented security sign-off (Tier C [Content truncated #60296); otherwise none evidenced.

Generated by UK AI Operational Resilience · copilot · auto · 20.2 AIC · ⌖ 7.64 AIC · ⊞ 8K · ◷

• expires on Oct 9, 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 #66613.