You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: