You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
governance / Validate Hypatia Baseline is red on main: 28 findings not covered by the baseline #80
governance / Validate Hypatia Baseline is red on main. It was measured at 2cc3088 in run 37864612160 (job 113608485491). The scan found 31 findings. Three are acknowledged by .hypatia-baseline.json. The remaining 28 are not covered by the baseline, so the gate fails: Gate failed: 28 unfiltered finding(s) at or above 'info'.
Every pull request inherits this red. It is not a required check here; the only required context on main is scan / gitleaks. #79 removes the two findings in release.yml, which leaves 26 on its head (job 113764445362).
Severity
Count
Rule module
Files
critical
6
structural_drift (SD004, "descriptile in retired location")
The full list, with the reason for each finding, is printed by the "Run Hypatia scan (Baseline validation)" step of the run named above.
Acceptance criteria
Every finding is either fixed or given a .hypatia-baseline.json entry. Each entry needs a reason, an expiry and a tracking issue, in the format in hyperpolymath/standardsdocs/HYPATIA-BASELINE-FORMAT.adoc.
The six .machine_readable/6a2/*.a2ml findings and the three Justfile SD024 findings are resolved by the estate's descriptile migration (A2ML is retired), not by a baseline entry with no expiry.
The instant-sync.yml dispatch step skips cleanly when FARM_DISPATCH_TOKEN is absent.
governance / Validate Hypatia Baseline passes on main.
🤖 Filed with Claude Code as the deferral for the red check on #79.
Activity
fix(ci): replace the scaffold release workflow with a working one (#79)