dependency-audit

Scan Go module dependencies for vulnerabilities, outdated packages, and license issues.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/srnichols/plan-forge --skill dependency-audit-srnichols
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-audit
Source: https://github.com/srnichols/plan-forge/tree/main/presets/go/.github/skills/dependency-audit
Command: npx skills add https://github.com/srnichols/plan-forge --skill dependency-audit-srnichols

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires govulncheck, go-licenses, forge_sweep, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Dependency Audit Skill identifies potential security vulnerabilities, outdated packages, and license issues in Go modules, ensuring your project is secure and compliant before code merges.

Core Features & Use Cases

  • Vulnerability Scanning: Checks for known vulnerabilities in Go module dependencies.
  • Outdated Modules: Identifies outdated packages that may pose security risks.
  • License Verification: Checks for license conflicts that could impact your project's licensing.
  • Use Case: Before pushing code to a repository, use this skill to scan dependencies for any potential issues.

Quick Start

Run 'dependency-audit' to automatically scan for vulnerabilities in your Go module dependencies.

Frequently Asked Questions about dependency-audit

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

FAQPage Schema
How do I scan Go modules for security vulnerabilities and license issues?

Scanning Go modules for vulnerabilities and license issues requires automating dependency checks using tools like govulncheck and go-licenses. This process identifies known security flaws, outdated packages, and license conflicts to ensure compliance before merging code.

Can I run Go dependency vulnerability scanning automatically in a CI/CD pipeline?

Yes, Go dependency vulnerability scanning can be automated within CI/CD pipelines and pre-commit hooks. Integrating these checks ensures that dependency validation and security compliance occur automatically before code is pushed or merged.

What is dependency auditing in Go and when do I need it?

Dependency auditing in Go is the process of validating modules for known vulnerabilities, outdated packages, and license conflicts. You need it before pushing code to a repository to ensure project security and licensing compliance.

What's the best way to check for outdated Go packages that pose security risks?

Checking for outdated Go packages that pose security risks is best handled by automated dependency scanning. This process identifies outdated modules and highlights potential security vulnerabilities, ensuring your project remains secure before code merges.

Do I need govulncheck and go-licenses to verify Go module compliance?

Yes, you need govulncheck and go-licenses along with forge_sweep to verify Go module compliance. These tools are required to automate the dependency scanning process for known vulnerabilities and license conflicts within your modules.