Go

Go SAST focuses on secure standard library usage and common server patterns

What It Commonly Detects:

Server-Side Request Forgery (SSRF) patterns in HTTP clients
Command execution risks (os/exec)
Insecure TLS settings / skipping verification
Path traversal / unsafe file operations
Randomness misuse where cryptographic randomness is required

Recommended Doc Additions

Go modules and repo layout considerations
Concurrency-related security footguns (where relevant)