Repository navigation
[uk ai resilience] UK AI Open Code Risk & Resilience Governance Report (7-day window) #77186
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by UK AI Operational Resilience. A newer discussion is available at Discussion #77499. |
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: 371 commits (208 security-signal), 26 open security issues, 23 open code-scanning alerts, 0 secret alerts.
Limitations: shell analysis was denied and sub-agents were not dispatched; findings are from grep over alert/issue JSON. Confidence is partial; human review advised.
errorcode-scanning alerts in generated lock files: spec-librarian Enable missing-tool safe output by default when safe-outputs are configured #1085, smoke-copilot Fix JavaScript code formatting issue in push_to_pull_request_branch.test.cjs #1084, jsweep Update mcp inspect command to filter safe-outputs without changing parser #1083, eslint-miner Add support for minimum validation in safe-outputs configurations with refactored base type architecture #1082, daily-doc-updater Add mcp list-tools command for listing MCP server tools #1081.actions/setup/sh/*.sh,actions/setup/js/*.cjs,install-gh-aw.sh,pkg/cli.Tier classification
Tier table
Control verification gaps
Ownership, observability and unsupported-dependency ratio unverified. Secrets control effective (0 alerts). Recovery: workflows regenerable; per-binary release attestations still missing.
Remediation queue
Exception register
None.
Metrics baseline
MTTR proxy, ownership coverage, unsupported-dependency ratio: not computed (tool limits). Exception aging: 0. Exposure without recovery: low.
Issues
None created; top items already tracked by open issues.
All reactions