go-security

Apply structured review checklists to identify security risks in Go codebases.

1|Updated Feb 19, 2026

Search Tags:#dependencies #golang #risk-assessment #threat-modeling #code-review #security-review #go-security

Ready to run

npx skills add https://github.com/juburr/mad-skills --skill go-security-juburr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-security
Source: https://github.com/juburr/mad-skills/tree/main/go-security
Command: npx skills add https://github.com/juburr/mad-skills --skill go-security-juburr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides secure Go coding practices and security reviews to help developers detect and remediate vulnerabilities early in the software lifecycle, reducing risk and hard-to-trace bugs.

Core Features & Use Cases

Structured review workflow: triage danger signals, assess HTTP hardening, and verify authentication/authorization controls.
Comprehensive guidance: data handling, supply chain awareness, and cryptographic best practices, with references for deeper dives.
Use Case: teams auditing a Go service against common CVEs and misconfigurations during code reviews and security audits.

Quick Start

Follow the triage workflow in the guide to begin a security review of a Go codebase.

Frequently Asked Questions about go-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform a security review on a Go codebase?▼

Perform a security review on a Go codebase by applying structured checklists to assess HTTP hardening, verify authentication controls, and check dependency management. This process identifies danger signals and provides actionable remediation guidance.

What should I look for when auditing Go code for common vulnerabilities and CVEs?▼

When auditing Go code for vulnerabilities and CVEs, look for misconfigurations in input handling, data handling controls, and cryptographic practices. A structured threat-modeling checklist helps detect and remediate these risks early in the software lifecycle.

Can I use this approach to review pull requests for Go services?▼

Yes, you can use this approach to review pull requests for Go services. The structured workflow applies to design reviews and code changes by enforcing triage signals, supply-chain checks, and HTTP hardening tailored for Go authentication and input handling scenarios.

Does the checklist cover dependency management and supply-chain risks in Golang?▼

The checklist covers dependency management and supply-chain risks in Golang by enforcing supply-chain checks during security reviews. It guides developers through verifying data handling controls and assessing dependency vulnerabilities to reduce hard-to-trace bugs.

What is the best way to mitigate authentication and HTTP hardening risks in Go?▼

The best way to mitigate authentication and HTTP hardening risks in Go is to apply a structured review checklist that verifies authorization controls and enforces data handling protocols. This provides actionable code examples to correct misconfigurations.