go-vuln-check

Scan Go module dependencies for known vulnerabilities using govulncheck.

1|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/dennisonbertram/go-agent-harness --skill go-vuln-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-vuln-check
Source: https://github.com/dennisonbertram/go-agent-harness/tree/main/skills/go-vuln-check
Command: npx skills add https://github.com/dennisonbertram/go-agent-harness --skill go-vuln-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and report known Go vulnerabilities in project dependencies using govulncheck and the Go vulnerability database.

Core Features & Use Cases

  • Scans Go modules for known vulnerabilities using govulncheck.
  • Outputs human-readable results and JSON for automation.
  • Supports targeted scans (default path ./...), binary mode for deployed artifacts.

Quick Start

Run govulncheck ./... to scan all module dependencies for known vulnerabilities.

Frequently Asked Questions about go-vuln-check

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

FAQPage Schema
How do I scan Go modules for known vulnerabilities using govulncheck?

To scan Go modules for known vulnerabilities, run govulncheck ./... to analyze all project dependencies against the Go vulnerability database and report identified CVEs. This targets local development paths by default.

Can I output govulncheck results as JSON for CI pipeline automation?

Yes, govulncheck supports JSON output to enable automated processing within CI pipelines. This allows scripts and automation systems to parse vulnerability reports programmatically after dependency scanning completes.

Does govulncheck support scanning deployed binaries for vulnerabilities?

Yes, govulncheck supports binary mode scanning for deployed artifacts. This allows you to identify known CVEs in compiled Go binaries across deployment environments, not just local module source code.

What is the difference between targeted and broad CVE scanning in Go modules?

Targeted scanning uses the default path ./... to check specific module dependencies, while broad scanning can analyze package-level code across local development, CI pipelines, and binary deployments for known CVEs.

Do I need to install govulncheck separately to scan Go dependencies?

Yes, govulncheck must be installed separately as a prerequisite before scanning Go dependencies. Once installed, it queries the Go vulnerability database to identify and report known CVEs in your project modules.

Why use govulncheck instead of general dependency scanners for Go vulnerability detection?

Govulncheck uses the official Go vulnerability database to specifically identify known CVEs affecting Go modules. It provides targeted package-level scanning and binary mode analysis that general dependency scanners lack.