You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent-changes-scoped UK AI Open Code Risk & Resilience review (lookback: 7 days, since 2026-07-29T16:06:00Z). 441 commits reviewed, 184 flagged as security-signal (auth/network/secrets-touching). 5 open code scanning alerts, 0 open secret scanning alerts, 68 open security issues (majority already tracked by existing uk-ai-resilience/container-image-scan issues). One genuinely new, untracked finding was identified: two large prebuilt Go binaries (actionlint, gosec, ~78MB combined) committed directly to git in PR #48979, bypassing the documented go install build path and not excluded by .gitignore. No repository-hiding action is recommended; findings are addressed via targeted remediation and issue tracking.
Two duplicate open issues (#47822, #46277) since 2026-07-17, unresolved >2 weeks
Missing CODEOWNERS
C — Restricted Pending Review (pre-existing)
Blocks enforced review routing repo-wide; tracked by #49167, still open
Control Verification Gaps
Ownership: No .github/CODEOWNERS — confirmed absent on disk. Gap.
SDLC: Build process documents go install for actionlint/gosec (Makefile lines 649-650) yet binaries are committed directly to git and not in .gitignore — reproducibility/review-bypass gap.
Dependency controls: New engine/MCP integrations lack visible pinning evidence in this window's changes reviewed; recommend explicit version pins for open-ontologies MCP server and engine adapter versions.
Secret exposure: SECRET_ fallback pattern for Kiro auth keys appears to follow existing declarative-engine convention (consistent with prior engine additions); no new alert triggered — adequate, but should be confirmed against secret-scanning baseline (0 open alerts, consistent).
Runtime observability: Malicious Code Scanner (daily-malicious-code-scan.lock.yml) and CodeQL both actively surfaced the two new/relevant findings (#653, [Custom Engine Test] Test Issue Created by Custom Engine #654) — detection loop is functioning.
Recovery: Removing the two committed binaries and adding .gitignore entries is low-effort and low-risk; no history rewrite required for forward remediation (existing blobs can be purged separately if desired, but not urgent).
Risk-Scoring Table
Area
Exposure Amplification
Patchability
Detectability
Operational Fragility
Ownership Confidence
Tier
Committed actionlint/gosec binaries
Medium (opaque binary trust)
High (easy remove + gitignore)
High (already flagged by scanner)
Low
Low (no CODEOWNERS)
C
GraphQL injection in project_command.go
Medium
High (parameterize query)
High (Semgrep/CodeQL flagged)
Low
Low (duplicate untriaged issues)
B (pre-existing)
Missing CODEOWNERS
High (systemic)
High (add file)
Medium (self-evident gap)
Medium
Low
C (pre-existing)
New engine adapters (Cursor/Kiro/Crush)
Medium (new trust boundary)
Medium
Medium (relies on manual review)
Medium
Medium
B
Remediation Queue
Item
Action
SLA
Committed actionlint/gosec binaries
Remove from tree, add to .gitignore, confirm CI uses go install
Add explicit version pins + review checklist for engine adapters
Medium
Exception Register
None required this cycle — no temporary hidden-repo or bypass exceptions requested or granted.
Operational Metrics Baseline
MTTR proxy: GraphQL injection findings open since 2026-07-17 (>19 days), still unresolved — indicates slow remediation velocity for known Tier B findings.
Ownership coverage: 0% — no CODEOWNERS file exists.
Unsupported/out-of-context dependency ratio: 2 binaries (actionlint, gosec) out of tracked build tooling — 100% of vendored build binaries are out-of-process.
Exception aging: N/A (no active exceptions).
Exposure without recovery capability: Low — all identified issues have clear, low-effort remediation paths (file removal, query parameterization, CODEOWNERS addition).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Executive Summary
Recent-changes-scoped UK AI Open Code Risk & Resilience review (lookback: 7 days, since 2026-07-29T16:06:00Z). 441 commits reviewed, 184 flagged as security-signal (auth/network/secrets-touching). 5 open code scanning alerts, 0 open secret scanning alerts, 68 open security issues (majority already tracked by existing
uk-ai-resilience/container-image-scanissues). One genuinely new, untracked finding was identified: two large prebuilt Go binaries (actionlint,gosec, ~78MB combined) committed directly to git in PR #48979, bypassing the documentedgo installbuild path and not excluded by.gitignore. No repository-hiding action is recommended; findings are addressed via targeted remediation and issue tracking.Asset Graph Summary (recent-change scoped)
SECRET_fallbacks (#50573), removed Antigravity (#50460), fixed Crush prompt delivery (#50452)actionlint+gosecbinaries committed to git (PR #48979, still present at HEAD).github/CODEOWNERSTier Classification
actionlint/gosecbinariesgo installbuild path; not gitignoredControl Verification Gaps
.github/CODEOWNERS— confirmed absent on disk. Gap.go installfor actionlint/gosec (Makefile lines 649-650) yet binaries are committed directly to git and not in.gitignore— reproducibility/review-bypass gap.SECRET_fallback pattern for Kiro auth keys appears to follow existing declarative-engine convention (consistent with prior engine additions); no new alert triggered — adequate, but should be confirmed against secret-scanning baseline (0 open alerts, consistent).daily-malicious-code-scan.lock.yml) and CodeQL both actively surfaced the two new/relevant findings (#653, [Custom Engine Test] Test Issue Created by Custom Engine #654) — detection loop is functioning..gitignoreentries is low-effort and low-risk; no history rewrite required for forward remediation (existing blobs can be purged separately if desired, but not urgent).Risk-Scoring Table
Remediation Queue
.gitignore, confirm CI usesgo installException Register
None required this cycle — no temporary hidden-repo or bypass exceptions requested or granted.
Operational Metrics Baseline
All reactions