Skip to content
Test

feat(trivy-to-vuls): get exact LockfilePath #2991

Sign in to view logs

feat(trivy-to-vuls): get exact LockfilePath

feat(trivy-to-vuls): get exact LockfilePath #2991

Triggered via pull request February 11, 2026 22:02
@MaineK00nMaineK00n
opened #2414
MaineK00n/trivy-to-vuls
Status Failure
Total duration 4m 10s
Artifacts –

test.yml

on: pull_request
Build
4m 5s
Build
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Build: contrib/snmp2cpe/pkg/cmd/version/version.go#L1
should have a package comment https://revive.run/r#package-comments
Build: contrib/snmp2cpe/pkg/cmd/convert/convert.go#L1
should have a package comment https://revive.run/r#package-comments
Build: scanner/utils/filepath/windows/windows.go#L1
should have a package comment https://revive.run/r#package-comments
Build: scanner/utils/filepath/unix/unix.go#L1
should have a package comment https://revive.run/r#package-comments
Build: contrib/trivy/parser/parser.go#L2
avoid package names that conflict with Go standard library package names https://revive.run/r#var-naming
Build: errof/errof.go#L1
should have a package comment https://revive.run/r#package-comments
Build: cti/cti.go#L1
should have a package comment https://revive.run/r#package-comments
Build: contrib/snmp2cpe/pkg/cmd/root/root.go#L1
should have a package comment https://revive.run/r#package-comments
Build: constant/constant.go#L1
avoid package names that conflict with Go standard library package names https://revive.run/r#var-naming
Build: constant/constant.go#L1
should have a package comment https://revive.run/r#package-comments