[FEATURE] Go Security Workflow (Fuzzing + SAST)

[tduhamel42]

Use Case

Why is this Go workflow needed?
E.g., automating go test -fuzz, checking vulnerabilities with govulncheck, enforcing golangci-lint, or scanning dependencies.

Proposed Solution

How should this workflow work in FuzzForge?

• Fuzzing: Native Go fuzz tests via go test -fuzz, OSS-Fuzz integration.
• SAST: Run govulncheck, static code analysis with golangci-lint, unsafe pointer usage detection.
• Combined: Unified “Go Security” workflow template.

Alternatives

Other tools like SonarQube, manual CI setup, or external scanners.

Implementation

(Optional) Ideas: GitHub Actions with setup-go, caching modules, running fuzz + SAST in parallel.

Category

• 🛠 Workflow Automation
• 🔗 Fuzzer Integration
• 🔍 SAST / Static Analysis

Additional Context

Links:

• govulncheck
• golangci-lint