Repository navigation
ci(instant-sync): block egress except the GitHub API (Hypatia RE002) - #127
hyperpolymath wants to merge 1 commit into
Conversation
The dispatch job holds FARM_DISPATCH_TOKEN and ran harden-runner in
egress-policy: audit. Audit mode records traffic but never blocks it, so
on this push-to-main trigger it was not containment. Hypatia RE002 rates
that high, and it fails the blocking Hypatia gate on every PR.
The job now runs egress-policy: block with one allowed endpoint,
api.github.com:443. peter-evans/repository-dispatch (pinned 28959ce)
makes a single call, POST /repos/{owner}/{repo}/dispatches, to
GITHUB_API_URL, which defaults to https://api.github.com. The action is
downloaded during job set-up, before harden-runner starts.
#107 planned to derive the allowlist from an audit run on main. No such
run exists: every instant-sync run since June ended in startup_failure.
So the allowlist comes from the action's source, not from observed
traffic. Action pins are unchanged, so actions.lock is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDgHt5BLAJ1gNWrw1wz
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
|
|
#117 already fixes both scripts, and its Generated by Claude Code |
Fork governance
Scope: the three lanes below are static checks at the named commit. A K9-DEED conformance🟡 advisory · commit
K9 live corpus (L0–L2): 8 finding(s) / scope notes
Scope: K9 components L0–L2 against contract v1.0.0 at the named standards commit. L3 signature verification and routed coordination-dialect files are not certified. Green is limited to this scope. Orange is missing evidence; yellow is grandfathered debt or warnings; grey is an explicit scope exclusion. report.json, badge.json and the validator logs are in the k9-grid artifact on the linked run. Hypatia verdict grid🟢 clean · commit Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change. Unique graded findings across gating and advisory rows: 18 (18 reporter observations; 18 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Hypatia scan: 12 finding(s)
panic-attack assail: 3 finding(s)
echidnabot: not_applicable — proofs here are gated by their own toolchains (proofs.yml: Idris2, Lean, Agda); no ECHIDNA engine is configured, so this adapter could only ever report not_run
rhodibot (RSR compliance): 11 finding(s)
panicbot: not_applicable — panic-attack already reports directly as its own row in the Hypatia verdict grid; enrolling panicbot would count the same findings twice
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet README)
glambot (presentation quality): 82 finding(s)
seambot: not_applicable — no seam register is declared (spec/seams/seam-register.json)
finishingbot (release readiness): 127 finding(s)
cipherbot: not_applicable — no cryptography is implemented in this repository; the hashes present are checksum/integrity pins, which cipherbot would report as cryptographic findings
accessibilitybot: not_applicable — no served HTML surface; this is a checker library/CLI with AsciiDoc documentation
Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run. |



Summary
Hypatia's one high finding on this repo, RE002, is in
.github/workflows/instant-sync.yml. The job holdsFARM_DISPATCH_TOKENbut runs harden-runner withegress-policy: audit, which records traffic and never blocks it. The finding is onmainat0dceab6, so it fails the blocking Hypatia gate on every PR, including #121, which only adds a doc. #107 added audit mode as step one of "audit, then tighten to block". This PR is step two.Changes
egress-policy: audit→egress-policy: block, withallowed-endpoints: api.github.com:443.actions.lockis unchanged.The allowlist comes from the action's source, not from observed traffic. #107 planned an audit run on
mainto collect the traffic, but none exists: every instant-sync run since June ended instartup_failure.peter-evans/repository-dispatchat the pinned28959cemakes one request,POST /repos/{owner}/{repo}/dispatches, toGITHUB_API_URL. That defaults tohttps://api.github.com(dist/index.js, lines 1973 and 2119). The action is downloaded during job set-up, before harden-runner starts.RSR Quality Checklist
Required
mainor on release, so CI on this PR cannot run it.with:was checked with a parser.workflow-linter.ymlruns actionlint and zizmor on this PR.unsafeblocks without// SAFETY:comments.envfiles includedTesting
python3 -c 'yaml.safe_load(...)': the step now readsegress-policy: block,allowed-endpoints: api.github.com:443.mainafter merge, and only ifFARM_DISPATCH_TOKENis set. If the dispatch then fails with a harden-runner blocked-egress annotation, add exactly the host it names.main, the Hypatia gate's single error-level SARIF result is gone. The other 12 results are warnings and do not gate.Generated by Claude Code