[uk ai resilience] UK AI Open Code Risk & Resilience Governance — 2026-08-28

[github-actions[bot]]

Executive summary

Recent-changes-focused UK AI Open Code Risk & Resilience Governance review (7-day lookback, since 2026-08-21). Of 500 commits in window, 158 carried security signals and 8 code-scanning alerts remain open. No open secret-scanning alerts. 37 open security-labelled issues exist repo-wide; 3 already track prior governance findings from earlier runs. Two new code-scanning alerts (#664, #665) match a previously-triaged false-positive pattern (go/bad-redirect-check on a path-traversal guard) and lack tracking issues — these are the highest-priority actionable gaps this cycle. One alert (#663) has since been mitigated in code (content-type/size/signature validation added) but the CodeQL alert itself remains open pending dismissal. No new systemic control failures were found; resilience posture (patchability, ownership) remains strong across findings.

Asset graph summary (recent-change scoped)

Changed surfaces and dependency signals (7-day window)

Surface	Files/Areas	Signal source
Manifest/include path validation	pkg/cli/add_package_manifest_includes.go, pkg/cli/add_package_manifest.go	CodeQL go/bad-redirect-check (#656 fixed pattern site, #664/#665 new)
Operational-value grader config	pkg/workflow/graders_config.go	CodeQL go/bad-redirect-check (#664, #665)
Docs build tooling	scripts/ensure-docs-slide-pdf.js	CodeQL js/http-to-file-access (#663) — mitigated in code, alert open
GraphQL query construction	pkg/cli/project_command.go	CodeQL workflow-go-graphql-injection-sprintf (#651/#652) — tracked in issue #52749
CI/workflow tooling provenance	actionlint/gosec binaries (historical, since removed from tree; .gitignore now excludes /actionlint, /gosec)	Sighthound finding (#653) — historical, already mitigated by .gitignore
Repo README	README.md	Smoke-test dummy finding (#564) — not a real signal

Ownership signal: all flagged files are core CLI/workflow-engine Go and JS build tooling with active recent commit history, indicating clear maintainer ownership rather than orphaned code.

Tier classification table

Tier assignments

Finding	Alert(s)	Tier	Rationale
Path-traversal guard flagged as redirect check (graders_config.go:441,448)	#664, #665	B — Open With Conditions	Same confirmed-false-positive pattern as previously closed #655/#656 analysis; no redirect sink involved
Path-traversal guard flagged as redirect check (add_package_manifest_includes.go:146)	#656	B — Open With Conditions	Duplicate of the same validated pattern as #655 (already tracked in issue #54037 for the sibling function in add_package_manifest.go); this new instance lacks its own tracker
Docs PDF fetch write	#663	A — Open Safe (code) / Alert open	Code already validates content-type, size, and PDF signature before write; alert stale, needs dismissal not code change
GraphQL query string construction	#651, #652	B — Open With Conditions	Already tracked (issue #52749), no new action needed
actionlint/gosec binaries in git history	#653	D — Decommission Candidate (historical)	Binaries no longer in tree; .gitignore prevents recurrence; residual risk is git-history bloat only
README smoke-test dummy	#564	A — Open Safe	Not a real finding

Control verification gaps

• SDLC controls: CodeQL alerts for a repeatedly-recurring false-positive pattern (bad-redirect-check on path-traversal guards) are not being dismissed with a documented reason, causing the same pattern to resurface as "new" alerts across files (Fix multi commit PRs #655→[Custom Engine Test] Test Issue Created by Custom Engine #656→Codex fails to start github MCP #664/#665). Recommend a codeql-suppressions/dismissal-with-rationale process for confirmed false positives to reduce alert-fatigue and keep the open-alert count meaningful.
• Dependency/runtime controls: No gaps identified in this window; no open secret-scanning alerts.
• Recovery controls: All flagged files have low patchability risk (simple, local fixes or dismissals); no rollback-readiness concerns.

Risk-scoring table and rationale

AI-aware risk scoring (Tier B items)

Finding	Exposure amplification	Patchability	Detectability	Operational fragility	Ownership confidence
#664/#665 (graders_config.go)	Low	High	High (CodeQL)	Low	High
#656 (add_package_manifest_includes.go)	Low	High	High (CodeQL)	Low	High

Rationale: all three are the identical validated pattern — a strings.HasPrefix(x, "/") check inside a path-cleaning/traversal-guard function, not a value that reaches an http.Redirect/Location header. CodeQL's go/bad-redirect-check heuristic over-matches on the leading-slash check. Low exposure and high patchability keep these at Tier B pending a documented CodeQL dismissal or an equivalent guard-comment fix.

Remediation queue with SLAs

Item	Action	SLA urgency
#664, #665	Confirm no HTTP redirect sink is reachable from graders_config.go; dismiss both alerts as false positive with rationale, or add clarifying guard	Medium
#656	Same as above for add_package_manifest_includes.go:146	Medium
#663	Dismiss alert referencing the existing in-code validation (content-type/size/signature checks already present)	Low
#653	No code action required; confirm CI Makefile paths use go install (already the case) — optionally purge historical blobs from git history if repo size is a concern	Low

Exception register

None required this cycle — all findings are either already mitigated in code or have low-risk, high-patchability fixes available; no temporary risk-acceptance exceptions are being requested.

Operational metrics baseline

Metric	Value
MTTR proxy (time from alert open to same-run triage)	Same-day (this run)
Ownership coverage	100% of flagged files map to actively maintained core packages
Unsupported dependency ratio	0% (no dependency-alert findings this window)
Exception aging	N/A (no open exceptions)
Exposure without recovery capability	None identified — all findings have a clear, low-effort remediation path

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• github.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "github.com"

See Network Configuration for more information.

Generated by UK AI Operational Resilience · copilot · auto · 37.3 AIC · ⌖ 11.5 AIC · ⊞ 8.1K · ◷

• expires on Aug 31, 2026, 11:36 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 #57471.