Software Development

Golang Security

Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).

Publisher / source

samber/cc-skills-golang (found on skills.sh)

Upstream record

samber/cc-skills-golang

Version

Version 3

Published

2026-11-02

Publication review

Approved for publication

Content fingerprint

8bcc0f7ff7d196aa498e0305b81c28f60c6e50a358626360f526c0cacc760bc4