Skip to content

chore(governance): stop declaring repository identity in settings.yml #119

chore(governance): stop declaring repository identity in settings.yml

chore(governance): stop declaring repository identity in settings.yml #119

Triggered via pull request September 19, 2026 19:34
Status Failure
Total duration 20m 11s
Artifacts 4

static-analysis-gate.yml

on: pull_request
panic-attack assail
5s
panic-attack assail
Hypatia neurosymbolic scan
34s
Hypatia neurosymbolic scan
Patch Bridge CVE triage
8s
Patch Bridge CVE triage
Deposit findings for gitbot-fleet
7s
Deposit findings for gitbot-fleet
Fit to window
Zoom out
Zoom in

Annotations

12 errors, 10 warnings, and 6 notices
Hypatia neurosymbolic scan
Process completed with exit code 1.
Hypatia neurosymbolic scan
Hypatia found 7 critical security issue(s) — blocking merge
Hypatia neurosymbolic scan: Justfile#L55
[hypatia] CI policy requires a retired descriptile path; align the check with .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .github/workflows/openssf-compliance.yml#L73
[hypatia] CI policy requires a retired descriptile path; align the check with .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .machine_readable/6a2/PLAYBOOK.a2ml#L1
[hypatia] Descriptile in retired location -- must be in .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .machine_readable/6a2/NEUROSYM.a2ml#L1
[hypatia] Descriptile in retired location -- must be in .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .machine_readable/6a2/AGENTIC.a2ml#L1
[hypatia] Descriptile in retired location -- must be in .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .machine_readable/6a2/ECOSYSTEM.a2ml#L1
[hypatia] Descriptile in retired location -- must be in .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .machine_readable/6a2/META.a2ml#L1
[hypatia] Descriptile in retired location -- must be in .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .machine_readable/6a2/STATE.a2ml#L1
[hypatia] Descriptile in retired location -- must be in .machine_readable/descriptiles/
Hypatia neurosymbolic scan: .github/workflows/dependabot-automerge.yml#L1
[hypatia] workflow .github/workflows/dependabot-automerge.yml performs a write (push/commit/release/PR) but grants no `contents: write` at the workflow level or any job level — the write will be denied at run time.
Hypatia neurosymbolic scan: .github/workflows/dependabot-automerge.yml#L51
[hypatia] workflow .github/workflows/dependabot-automerge.yml:51 gates on `github.actor == 'dependabot[bot]'` — `github.actor` is the run-triggering user, which an attacker controls on `pull_request_target` from a fork
Hypatia neurosymbolic scan: .github/workflows/sonarqube.yml#L32
[hypatia] job in .github/workflows/sonarqube.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/instant-sync.yml#L22
[hypatia] job in .github/workflows/instant-sync.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/labels.yml#L38
[hypatia] job in .github/workflows/labels.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/label-triage.yml#L52
[hypatia] job in .github/workflows/label-triage.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/dependabot-automerge.yml#L59
[hypatia] job in .github/workflows/dependabot-automerge.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/boj-build.yml#L27
[hypatia] job in .github/workflows/boj-build.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/release.yml#L145
[hypatia] job in .github/workflows/release.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: .github/workflows/push-email-notify.yml#L44
[hypatia] job in .github/workflows/push-email-notify.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring
Hypatia neurosymbolic scan: labels.yml#L1
[hypatia] Job `sync` in labels.yml has no `timeout-minutes:` declaration. Default is 6 hours — a stuck codeload fetch or runner hang can burn budget. Add `timeout-minutes: 10` (or proportional).
Hypatia neurosymbolic scan: label-triage.yml#L1
[hypatia] Job `triage` in label-triage.yml has no `timeout-minutes:` declaration. Default is 6 hours — a stuck codeload fetch or runner hang can burn budget. Add `timeout-minutes: 10` (or proportional).
panic-attack assail
panic-attack binary not available — skipping assail
panic-attack assail
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Patch Bridge CVE triage
panic-attack binary not available — skipping Patch Bridge
Patch Bridge CVE triage
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Hypatia neurosymbolic scan
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Deposit findings for gitbot-fleet
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
bridge-report
218 Bytes
sha256:a8c9854ea7a34338934dbf30cbce55092f75aa48f947acc43d1dd848b9742fea
hypatia-findings
2.04 KB
sha256:d061c38be2cef60c9cba8a79be848243285642dd9aeab24a6acab5982a1f3472
panic-attack-findings
171 Bytes
sha256:2ee5270d1d3d48e7ed221846550b7061273b54b8838428e8571b62d934dbcf00
unified-findings
2.29 KB
sha256:7b127de8b013de9009a8d081717c4b8981127831cfb0df4f8aa8b5a0ea326d4f