Repository navigation
finding-bridge: a hitlog consumer that seals hits for triage #2116
MohdSaifHussain
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I wrote a CLI that ingests garak hitlogs and normalizes each hit into a sealed, hash-chained finding for triage.
Why: after a run you've got a hitlog.jsonl full of successful attacks and no good way to hand them off. Pasting raw outputs into tickets means every reviewer re-reads the harmful content, and nothing proves the evidence wasn't edited later.
What it does:
Tested against a real 0.16.0 run (llama3.2:1b via Ollama, dan + promptinject, 699 hits) — that run is a worked example in the repo, raw data kept out of the tree: https://github.com/MohdSaifHussain/finding-bridge/tree/master/examples/04-real-data
Repo: https://github.com/MohdSaifHussain/finding-bridge
Disclosure: the code is AI-written under my direction; the test suite (357 tests, mutation-audited) and the decision record in the repo are what I'd point at before you trust it. If the hitlog format changes again I'd like to track it — the parser found out the hard way that my fixtures mimicked a shape 0.16.0 no longer writes, so shape reports are welcome.
All reactions