triaging-findings

What problem does it solve?

Adversarial triage of raw security-scanner output. It verifies each finding, collapses duplicates, re-ranks by derived exploitability, and tags with an owner, producing a concise, actionable triage view.

Core Features & Use Cases

• Verification: validate that each finding is real, actionable, and worth remediation.
• Deduplication: collapse duplicates across scanners to a single canonical finding.
• Ranking by exploitability: prioritize survivors using derived exploitability rather than scanner severity.
• Routing: assign each finding to an appropriate owner for remediation and follow-up.
• Input/output flexibility: accepts VULN-FINDINGS.json, scanner results, or markdown reports and emits TRIAGE.json + TRIAGE.md for downstream workflow.
• Use cases include triaging vulnerability backlog, preparing engineering backlogs, and coordinating across security and development teams.

Quick Start

Feed a findings file or directory to triaging-findings to normalize, deduplicate, verify, and triage the results into TRIAGE.json and TRIAGE.md.