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
audits: panic-attack reads classifications from audits/ but echidna stores at reports/audits/ (suppressions don't fire) #187
`panic-attack` registry loader (`load_user_classifications` in `panic-attack/src/assail/mod.rs:220`) reads from `/audits/assail-classifications.a2ml` only.
Echidna keeps its registry at `reports/audits/assail-classifications.a2ml`.
Effect: neither the pre-existing nor the §9-11 classifications added in #186 currently suppress panic-attack findings. The only suppressions firing today are kanren structural ones with `suppressed: true`.
Fix shape
Two options:
Symlink `audits → reports/audits` (cheap, preserves current layout)
Move `reports/audits/assail-classifications.a2ml` to `audits/` and update any cross-refs
Option 1 is least disruptive.
Why this matters
The 22 classification entries in `reports/audits/assail-classifications.a2ml` (16 pre-existing + 6 from #186) are inert until this is fixed. Once the symlink lands, the 6 High-FFI findings will actually clear in the next sweep.
Refs
`reports/audits/assail-classifications.a2ml` (the registry that should be canonical)
`audits/audit-ffi-boundary.md` (the human doc; correct location)
Activity