Scanner-neutral
Reads physical locations from standard SARIF runs and results.
Local-only review tool
Turn scanner output into evidence your team can safely discuss: line-numbered context, an irreversible mask, structural clues, and a signed decision trail.
Scanner in. SARIF or Gitleaks JSON.
Masked evidence out. HTML, Markdown, signed JSON.
01 / Boundary
The CLI resolves scanner paths inside the repository root. Paths that escape it are refused.
The matched span becomes a fixed marker before the report model or renderer can see it.
Review line context, type, length, character classes, and entropy—then sign the resolution.
Important: classification can tell you whether a finding looks deliberate or risky. It cannot prove a credential is valid, revoked, or inactive.
02 / Live workbench
This demo never sends, saves, or logs its inputs. For real findings, use the CLI inside the repository.
generic-api-key
03 / Install
Build from source today. Release binaries are prepared for factory publishing.
$ cargo install --git https://github.com/B-Divyesh/sf-secret-finding-triage
$ sft render --input results.sarif --repo . --output triage.html
Rendered 12 of 12 findings to triage.html.
Reads physical locations from standard SARIF runs and results.
Understands familiar RuleID, File, line, column, Secret, and Fingerprint fields.
Exclude fixtures, vendored trees, generated output, or any project-specific path.
04 / Team workflow
The CLI, safe masking, all export formats, and signed records are free. A one-time Team Workflow Pack adds a reusable policy worksheet, reviewer rubric, and priority product updates.