Go vulnerability rules in sonarcloud very limited

The SonarSource’s Go analyzer is open-source so you are free to raise PRs to add extra rules. Once merged, they will benefit to all.

I will look into it, digging in the repo for contribution guidelines etc with the team.

So they whole slang library is used by SonarCloud?