NO Golang Vulnerabilities rules in SonarQube

Hello everyone,
first of all I think it’s useful to notify that I’ve read this thread:

nevertheless I think maybe now it’s time to add some vulnerabilities rules related to Go.
It’s true that one can import external scanner results, it’s true that one can define custom rules, but I hope that a best of breed solution such as SonarQube could have its own Go vulnerabilities coverage.
All the best,


I can only agree with you and tell that this is a feature that we are considering for 2022.


did the project to include SAST GoLang coverage in SonarQube have any evolutions?