Repository navigation
[uk ai resilience] [uk-ai-resilience] Open-code risk report - 2026-10-14 #68741
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by UK AI Operational Resilience. A newer discussion is available at Discussion #69061. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Executive summary
Lookback 7 days (since 2026-10-07): 389 commits (229 security-signal), 21 open security issues, 249 open code-scanning alerts, 0 secret-scanning alerts. Alert mix: 2 critical, 236 high, 6 medium, 5 unrated. 219 high alerts are one pattern (non-deterministic npm install in workflows); 10 more are uv/pip. These are already tracked by #68043. No secret exposure. Note: the sub-agents were not dispatched; this assessment was done directly from pre-computed data, so confidence is moderate.
Asset graph summary
Recent-change scoped asset graph
pkg/workflow(compiler, maintenance workflow YAML)go/unsafe-quoting,go/weak-sensitive-data-hashing,go/bad-redirect-checkpkg/cli.github/workflows/*.lock.yml.github/scripts(JS)Ownership signals: top committers are Copilot (173), Peli de Halleux (163), github-actions[bot] (48).
Tier classification
Tier table
No Tier C/D areas identified.
Control verification gaps
Risk scoring
Scores (1 low risk – 5 high risk)
Remediation queue
go/unsafe-quotingalerts (#1030, #1031); fix or dismiss with justificationHuman-review trigger: any critical alert dismissal.
Exception register
None.
Operational metrics baseline
All reactions