[uk ai resilience] UK AI Open Code Governance Report — 2026-08-19 (7-day recent-change scope)

[github-actions[bot]]

Executive summary

7-day recent-change scoped UK AI open-code governance review of github/gh-aw (385 commits, 88 security-signal commits). Overall posture is resilient: 0 open secret-scanning alerts, active CVE burn-down tracking for container images, and prior UK-AI-governance issues already exist for 2 of the 6 open code-scanning alerts. No critical unaddressed exposure was found in the recent-change window. Two gaps warrant attention: (1) a Go static-analysis alert (go/bad-redirect-check, severity error) in pkg/cli/add_package_manifest.go has no tracking issue yet — investigation shows it is very likely a false positive (the flagged code is a path-traversal/relative-path guard, not a URL redirect), but it remains open and unlabeled; (2) recurring GraphQL string-interpolation warnings in pkg/cli/project_command.go are already tracked (#52749) but unresolved after being flagged by two separate scan categories. Recommend closing the loop on both via low/medium-SLA remediation rather than any restrictive/hiding action.

Asset graph summary (recent-change scoped)

Recent-change scoped asset graph

Segment	Recent activity	Runtime area	Ownership signal
pkg/cli/ (post-agent cache, package manifest, project command)	Heavy churn incl. #53879 "Harden post-agent cache Git commits"	CLI compiler / git operations	Copilot-authored + gh-aw-bot + pelikhan review
scripts/ensure-docs-slide-pdf.js	Docs build tooling	Docs generation pipeline (Node)	No recent commit in window; long-standing warning
.github/workflows/*.lock.yml (daily-semgrep-scan, codeql)	Scanner infra config	CI/CD security tooling	github-actions[bot] generated
Container images: gh-aw-firewall (agent/squid/cli-proxy/api-proxy), gh-aw-mcpg, github-mcp-server, node:lts-alpine	10 open container-image-scan issues, version bump cadence v0.27.x→v0.28.1	Sandboxed execution / firewall / MCP gateway runtime	Automated container-image-scan bot; tracked via dedicated recurring issues
Test suite (pkg/cli batch)	"add t.Parallel() to safe top-level tests" — parallelization hardening	Test/CI reliability	Automated "Daily Go Test Parallelizer" PR bot

Tier classification table

Tier classification

Asset/finding	Tier	Rationale
pkg/cli/add_package_manifest.go redirect check (#655)	B	Likely false positive (path-traversal guard, not redirect); low exposure but no tracking issue exists — open with condition to confirm/dismiss
scripts/ensure-docs-slide-pdf.js untrusted write (#654)	B	Already tracked in #53737 (Tier C per that issue); docs-build-only blast radius, not internet-facing
pkg/cli/project_command.go GraphQL Sprintf x2 (#651/#652)	B	Already tracked in #52749; mitigated by escapeGraphQLString() but string-interpolation pattern remains brittle
Container images (firewall/mcpg/github-mcp-server/node-alpine)	B	Active recurring CVE burn-down process (#52657 "Container CVE burn-down") demonstrates functioning remediation velocity
README.md workflow-security-finding-1 (#564)	A	Documentation-only finding, no runtime exposure
actionlint workflow-out-of-context (#653)	A	CI lint warning, no production exposure

Control verification gaps

• Ownership: Adequate — clear component ownership evidenced by consistent reviewer (pelikhan) across bot-authored hardening PRs (Harden post-agent cache Git commits #53879) and dedicated bots for tests/scans.
• SDLC: Adequate — PR-based workflow, dedicated CI scan workflows (codeql, daily-semgrep-scan), automated test-parallelization hardening in flight.
• Dependency controls: Partial — container CVE tracking is active but the volume of open container-image-scan issues (10+) indicates a backlog; no evidence of an SLA-driven closure cadence.
• Secret exposure: Adequate on current signal (0 open alerts), but this reflects scan-coverage results only, not independent verification — treat as provisional.
• Runtime observability: Adequate — pkg/logger DEBUG namespace tooling supports incident triage.
• Recovery/patch readiness: Partial — two static-analysis findings (redirect check, GraphQL Sprintf) remain open with mitigations only partially verified; no explicit rollback/patch SLA documented for CLI-level findings (as opposed to container images, which have a burn-down issue).

Risk-scoring table and rationale

AI-aware risk scoring

Area	Exposure	Patchability	Detectability	Fragility	Ownership	Tier
add_package_manifest.go redirect check	Low	High	High (CodeQL)	Low	High	B
ensure-docs-slide-pdf.js untrusted write	Low	High	High (CodeQL)	Low	Med (already tracked #53737)	B
project_command.go GraphQL Sprintf	Med	Med (requires refactor to GraphQL variables)	High (CodeQL+Semgrep, 2 scanners)	Med	Med (already tracked #52749)	B
Container image CVEs	Med	Med (upstream dependency on vendors)	High (automated scan)	Med	High (dedicated burn-down issue)	B

Rationale: no Tier C/D candidates identified in this window — all flagged areas have active detection, credible ownership, and existing or newly-recommended remediation paths.

Remediation queue with SLAs

Item	Action	SLA
#655 redirect check finding	Confirm false-positive classification for cleanManifestRelativePath/related redirect check; dismiss with justification or fix if genuinely reachable via untrusted redirect	Medium
#651/#652 GraphQL Sprintf (tracked #52749)	Migrate to GraphQL variables instead of string interpolation in project_command.go	Medium
#654 untrusted file write (tracked #53737)	Validate/sanitize network response before writing in ensure-docs-slide-pdf.js	Medium
Container image CVE backlog (10 open issues)	Establish explicit SLA-driven triage/closure cadence for container-image-scan issues, distinct from ad hoc version bumps	High

Exception register

None required this cycle — no Tier C/D exceptions identified.

Operational metrics baseline

• MTTR proxy: recent hardening PR (Harden post-agent cache Git commits #53879) merged same-day — good baseline signal.
• Ownership coverage: high (single consistent maintainer review across bot PRs).
• Unsupported dependency ratio: not directly measurable this cycle; container CVE backlog volume (10+ open) is the closest proxy and suggests moderate ratio.
• Exception aging: N/A (no exceptions open).
• Exposure without recovery capability: none identified — all flagged areas have active scanners and either existing tracking issues or a newly filed one from this run.

Generated by UK AI Operational Resilience · auto · 43.9 AIC · ⌖ 2.57 AIC · ⊞ 9.3K · ◷

• expires on Aug 22, 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 #54278.