Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add govulncheck linter #32

Closed
malt3 opened this issue Aug 18, 2023 · 1 comment
Closed

Add govulncheck linter #32

malt3 opened this issue Aug 18, 2023 · 1 comment

Comments

@malt3
Copy link

malt3 commented Aug 18, 2023

This is a feature idea / request.
First of all: thank you so much for working on this!
Having cached / incremental linters for Bazel / Go would greatly improve the velocity of my team.
Especially if this can be done in CI.

I wonder if govulncheck could be adapted to be a nogo-analyzer.
Since govulncheck is very resource intensive, it would greatly benefit from nogo support.
I don't currently understand nogo or govulncheck well enough to understand fully if they could work together, so feel free to close this if it is not feasible.

@sluongng
Copy link
Owner

govulncheck is a complicated tool. It does not use the typical Analyzer framework and requires a constantly updated db of known vulnerabilities.

I have commented in golang/go#61494 (comment) wrt how it could be supported in the Bazel ecosystem. But if that ever happens, we would want a separate rule for it and not in nogo-analyzer.git repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants