Commit cd67367
ci(supervised-fleet-scan): pass GITHUB_TOKEN + lower threshold to surface Dependabot findings
Fixes two silent-drop defects in the scheduled fleet scan workflow:
1. GITHUB_TOKEN was not passed to the fleet-coordinator env, so the
Hypatia DependabotAlerts rule (DA001-DA004) always returned
`{:error, "GITHUB_TOKEN not set"}` and no alerts were ever
surfaced. Three low-severity CVEs on hyperpolymath/007 sat
open for weeks partly for this reason.
Token resolution order: secrets.FLEET_SCAN_PAT (preferred,
needs `security_events` scope on every target repo) ->
secrets.GITHUB_TOKEN (fallback — only scopes this repo).
For a real estate-wide scan the PAT is required; otherwise
the workflow only ever queries alerts on gitbot-fleet itself.
2. HYPATIA_SEVERITY defaulted to "medium", which filtered out every
low-severity finding from every rule (not just Dependabot). Now
set to "low" so the scan surfaces the full picture; downstream
dispatch/review still gates behaviour per severity.
Pairs with:
- verification-ecosystem/hypatia@75a36ce (exported-severity floor
so fresh-low Dependabot alerts reach default threshold)
- 007-lang@769fed0 + rsr-template-repo@80a66ae (per-repo
hypatia-scan.yml now passes its own built-in token through and
declares security-events: read)
See 007-lang/audits/audit-dependabot-automation-gap-2026-04-17.md
for the full chain audit.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 93daf05 commit cd67367
1 file changed
Lines changed: 16 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
43 | 43 | | |
44 | 44 | | |
45 | 45 | | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
46 | 62 | | |
47 | 63 | | |
48 | 64 | | |
| |||
0 commit comments