Skip to content
govulncheck

govulncheck #172

Sign in to view logs

govulncheck

govulncheck #172

Triggered via schedule April 1, 2024 00:48
@evansimsevansims
⁠ b4b1b5f
master
Status Failure
Total duration 1m 26s
Artifacts –

govulncheck.yml

on: schedule
scan
1m 17s
scan
Fit to window
Zoom out
Zoom in

Annotations

1 error
scan
Process completed with exit code 2.