TigahandGitHub 5972cc9272 fix(report): map sarif level to finding severity (#312) ...

sarif results were hardcoded to level "warning", so a critical finding
and an informational one landed identically in code-scanning ingests.
carry the normalized severity onto report.Result and map it: critical
and high to error, medium to warning, low and info to note. the severity
is derived by flattening each module result and taking the worst rank,
and an absent severity keeps the old "warning" default.

2026-07-22 12:49:59 -07:00

..

markdown.go

feat: live-host probe and sarif/markdown report export

2026-06-10 14:47:17 -07:00

report_test.go

fix(report): map sarif level to finding severity (#312)

2026-07-22 12:49:59 -07:00

report.go

fix(report): map sarif level to finding severity (#312)

2026-07-22 12:49:59 -07:00

sarif.go

fix(report): map sarif level to finding severity (#312)

2026-07-22 12:49:59 -07:00