[uk ai resilience] [uk-ai-resilience] Weekly Review - 2026-10-05

[github-actions[bot]]

Executive summary

7-day window (since 2026-09-28): 254 commits (147 Copilot, 46 github-actions[bot], 36 pelikhan, 16 dependabot, 9 other), 88 security-signal commits, 280 open code-scanning alerts, 0 secret-scanning alerts, 35 open security-related issues.

Key findings:

• 259 high-severity "non-deterministic install" alerts (249 npm, 10 uv pip) across .github/workflows/*.lock.yml: 196 opened 2026-09-15, 54 on 2026-10-04. Supply-chain gap (Tier B).
• 6 new insecure-temp-file / file-system-race alerts (2026-10-05) in new .github/scripts/* and scripts/pr-sous-chef.mjs (Tier B).
• Ownership gap persists: no .github/CODEOWNERS ([uk-ai-resilience] Missing .github/CODEOWNERS for security-sensitive compiler/CLI paths (Tier B) #61637); release app-token minting 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, Tier C) still open.
• Container CVE burn-down issues ([container-image-scan] Node CVE burn-down #65791–[container-image-scan] grafana/mcp-grafana CVE burn-down #65797) show active remediation.
• Secret exposure: no open alerts.

Asset graph summary

Asset graph (recent-change scoped)

Segment	Surface	Signal
.github/workflows/*.lock.yml	generated Actions workflows	259 install-pinning alerts
.github/scripts/aw_issue_clustering*.cjs, safe_output_health_cadence.cjs	new automation scripts	temp-file/race alerts
scripts/pr-sous-chef.mjs	maintainer tooling	temp-file alert
pkg/workflow/, pkg/cli/	compiler/CLI (Go)	5 bad-redirect-check, 2 GraphQL sprintf (older)
Dockerfile / container images	MCP gateway, firewall, node, serena, grafana MCP	CVE burn-down issues
Ownership	maintainers	one dominant reviewer (pelikhan), no CODEOWNERS

Tier classification

Tier table

Area	Tier
Compiled workflow dependency installs	B
New .github/scripts temp-file handling	B
Compiler/CLI Go redirect checks	B
Release workflow app-token minting (#60296)	C
Ownership / CODEOWNERS (#61637)	B
Container images (CVE burn-down)	B
Docs/tests/other	A

Control verification gaps

• Ownership: no CODEOWNERS; bus-factor risk.
• SDLC: commits are bot-heavy with human co-author; new scripts merged with CodeQL alerts the same day.
• Dependency: non-lockfile npm install / uv pip install in generated workflows; 1 unpinned Dockerfile base image; curl | sudo sh installer ([setup-security] Unpinned curl | sudo sh root install in sudo_docker_sbx_install.sh (supply-chain risk) #62521).
• Secrets: no open alerts (pass).
• Observability: code scanning, container scans and red-team scans are active; the 2026-10-04 red-team report shows 0 files analyzed plus a threat-detection warning (🚨 [SECURITY] Security Red Team Findings - 2026-10-04 #65681), so coverage is uncertain.
• Recovery: patchability is high (lock files recompile); no per-binary release attestations (Add per-binary attestations to release artifacts #52302).

Risk scoring

Scores (1–5; for exposure/fragility higher is worse, for others higher is better)

Area	Exposure	Patchability	Detectability	Fragility	Ownership	Tier
Workflow install pinning	3	4	5	2	3	B
New script temp files	2	5	5	2	3	B
Go redirect checks	2	5	5	2	3	B
Release app-token minting	4	3	2	3	2	C
CODEOWNERS	2	5	2	2	2	B
Container CVEs	3	4	5	2	3	B

Rationale: install alerts are numerous but deterministic and fixable at compiler level; temp-file alerts are in CI-only scripts with limited exposure.

Remediation queue

#	Action	SLA
1	Make compiler emit lockfile-based installs (npm ci, hash-pinned uv)	High
2	Fix temp-file creation (mkdtemp, exclusive flags) in new scripts	Medium
3	Document sign-off for release app-token minting (#60296)	High
4	Add CODEOWNERS (#61637)	Medium
5	Review bad-redirect-check alerts in pkg/	Medium
6	Verify red-team scan coverage (#65681)	Medium

Human review triggers: any change to release/token workflows; ownership confidence ≤2.

Exception register

No active exceptions. No hidden-repo exceptions recommended.

Operational metrics baseline

• MTTR proxy: oldest alert batch 2026-09-15 (~20 days, 196 alerts); older Go alerts since 2026-07-24 (~73 days).
• Ownership coverage: 0% formal (no CODEOWNERS).
• Unsupported dependency ratio: not measurable from inputs; 1 unpinned image, 259 non-deterministic installs.
• Exception aging: 0 exceptions.
• Exposure without recovery capability: none identified; release attestation gap (Add per-binary attestations to release artifacts #52302).

Note: sub-agents were not dispatched; analysis was done directly from pre-computed data.

Generated by UK AI Operational Resilience · copilot · auto · 27.6 AIC · ⌖ 7.86 AIC · ⊞ 7.9K · ◷

• expires on Oct 8, 2026, 7:41 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 #66213.