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

Feature: Consider go vet a SAST tool #3128

Closed
joycebrum opened this issue Jun 6, 2023 · 1 comment
Closed

Feature: Consider go vet a SAST tool #3128

joycebrum opened this issue Jun 6, 2023 · 1 comment
Labels
check/SAST kind/enhancement New feature or request

Comments

@joycebrum
Copy link
Contributor

Is your feature request related to a problem? Please describe.
It seems that go vet is commonly used by go projects and it claims to statically analysis the code. I'd like to know if it could be considered a SAST tool and perhaps its use be identified by Scorecard tool.

Describe the solution you'd like
Understand whether go vet is indeed a SAST tool and if it can be identified by the Scorecard tool. To run, it seems they just use the go vet command or by running go test with go version >= 1.10.0.

Example:

Describe alternatives you've considered
None.

Additional context
Codeql also covers Go projects, so this go vet would be another option for the maintainers to choose.

@joycebrum joycebrum added the kind/enhancement New feature or request label Jun 6, 2023
@joycebrum joycebrum changed the title ✨ Consider go vet a SAST tool Consider go vet a SAST tool Jun 6, 2023
@joycebrum joycebrum changed the title Consider go vet a SAST tool Feature: Consider go vet a SAST tool Jun 6, 2023
@laurentsimon
Copy link
Contributor

Can you add this to a comment to #2318? I think you can close the issue afterwards, since the other issue consolidates all the SAST tool for every language. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
check/SAST kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants