Security testing starts with understanding vulnerabilities. The CVE website lists known software flaws. The OWASP Top Ten highlights common weaknesses. With this knowledge, we can improve our Go development. This article shows how to put in place robust practices. They are to: fuzz inputs, verify dependencies, and use static analysis tools (SAST).

Using systemd to avoid having to write some risky code

Comparison between types of API tokens.

Rust and Node aren't bad for encouraging dependency use -- your favorite language's tools just suck.