Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Dependency Auditor

  • 618 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

dependency-auditor is a Claude Code skill that scans Go module dependencies in go.mod for known vulnerabilities and outdated packages for developers who need supply-chain checks before merging or deploying Go services.

About

dependency-auditor is a security-focused agent skill for Go projects that reads module manifests and evaluates require directives against vulnerability and freshness criteria before code ships. The skill is built around standard Go module files—go directives, direct requires such as gin, redis, jwt, gorilla/mux, zap, gorm, and indirect dependency trees—and helps surface risky or stale versions during PR review or pre-deploy checks. Developers reach for dependency-auditor when maintaining microservices or APIs written in Go and want automated dependency hygiene without leaving the IDE workflow. The skill pairs naturally with CI merge gates and complements broader security suites by narrowing specifically on Go mod supply-chain risk. It assumes a go.mod-backed codebase and familiarity with Go module versioning semantics.

  • Scans go.mod and go.sum files for vulnerable or outdated dependencies
  • Outputs severity levels with remediation recommendations
  • Integrates directly into Claude, Cursor, and local workflows
  • Supports both direct and indirect dependency analysis
  • Hard-gate: blocks merge on critical vulnerabilities

Dependency Auditor by the numbers

  • 618 all-time installs (skills.sh)
  • Ranked #474 of 2,203 Security skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill dependency-auditor

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs618
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you audit Go module CVEs before deploy?

Automatically scan Go module dependencies for known vulnerabilities and outdated packages before merging or deploying.

Who is it for?

Go backend developers who maintain go.mod-based services and need fast supply-chain checks before merge or release.

Skip if: Teams on npm, pip, or Maven-only stacks where Go module scanning does not apply.

When should I use this skill?

A developer asks to check Go dependencies, scan go.mod for CVEs, or validate packages before merging or deploying.

What you get

Vulnerability report, outdated dependency list, and remediation guidance for go.mod packages.

  • vulnerability report
  • outdated dependency list

Files

SKILL.mdMarkdownGitHub ↗

Dependency Auditor

Skill Type: POWERFUL · Category: Engineering · Domain: Dependency Management & Security

Offline, deterministic dependency auditing across 8+ package ecosystems. The three scripts are pattern-matchers over manifests/lockfiles — they do not call live advisory APIs; pair their findings with npm audit / pip-audit / cargo audit for current CVE coverage.

Quick Start

# 1. Scan for vulnerabilities (built-in offline CVE pattern set; exit non-zero on high severity)
python3 scripts/dep_scanner.py /path/to/project --format json --fail-on-high -o scan.json

# 2. Check license compliance and conflicts
python3 scripts/license_checker.py /path/to/project --policy strict --format json -o licenses.json

# 3. Plan upgrades from the scanner's inventory
python3 scripts/upgrade_planner.py scan.json --risk-threshold medium --timeline 90 --format json -o plan.json

Consume the outputs: scan.json findings drive which packages to pin/patch now; licenses.json conflicts go to the user as a legal-risk list; plan.json orders upgrades by risk with rollback notes. --quick-scan skips transitive deps; --security-only limits the plan to security fixes.

Verification loop: after applying upgrades, re-run step 1 and assert 0 high-severity findings before closing the audit.

Supported Ecosystems

LanguageManifests parsed
JavaScript/Nodepackage.json, package-lock.json, yarn.lock
Pythonrequirements.txt, pyproject.toml, Pipfile.lock, poetry.lock
Gogo.mod, go.sum
RustCargo.toml, Cargo.lock
RubyGemfile, Gemfile.lock
Javapom.xml, gradle.lockfile
PHPcomposer.json, composer.lock
C#/.NETpackages.config, project.assets.json

License Classification

  • Permissive: MIT, Apache 2.0, BSD (2/3-clause), ISC
  • Copyleft (strong): GPL v2/v3, AGPL v3 — flags contamination risk in permissive projects
  • Copyleft (weak): LGPL v2.1/v3, MPL 2.0
  • Proprietary / Dual / Unknown — unknown licenses are surfaced for manual review

The checker analyzes license inheritance through dependency chains and emits conflict pairs with remediation suggestions.

Upgrade Risk Matrix

RiskUpdate typeHandling
LowPatch, security fixesApply immediately
MediumMinor with new featuresBatch into scheduled update
HighMajor version, API changesDedicated migration task + tests
CriticalKnown breaking changesPlanned migration with rollback procedure

Prioritization: security patches > bug fixes > feature updates > major rewrites; deprecated features get immediate attention.

Scripts (accurate capability claims)

  • `scripts/dep_scanner.py` — multi-format parser; built-in offline vulnerability pattern set (~16 CVE patterns — a smoke layer, not a replacement for live advisories); transitive resolution from lockfiles; JSON + text output.
  • `scripts/license_checker.py` — license detection from package metadata; compatibility matrix across 20+ license types; --policy permissive|strict; conflict detection with remediation.
  • `scripts/upgrade_planner.py` — semver-based breaking-change prediction; risk-ordered migration plan with testing checklist and timeline estimation.

Sample fixtures: test-project/ and test-inventory.json in this folder; expected shapes in expected_outputs/.

CI Integration

# Security gate in CI
python3 scripts/dep_scanner.py . --format json --fail-on-high
python3 scripts/license_checker.py . --policy strict --format json

Best Practices

1. Prioritize security: address high/critical findings immediately; license compliance before functionality. 2. Gradual updates: incremental upgrades with thorough testing; feature flags for risky bumps. 3. Cadence: security scans per commit; license audits monthly; full audit quarterly. 4. False positives: whitelist with documentation; contact maintainers for license ambiguity.

See README.md for detailed usage and references/ for the vulnerability/license knowledge bases.

Related skills

How it compares

Pick dependency-auditor over generic security suites when the codebase is Go-only and the goal is focused go.mod CVE and freshness checks.

FAQ

What does dependency-auditor scan in a Go project?

dependency-auditor reads the project's go.mod file, including direct require blocks and indirect dependencies, to surface known vulnerabilities and outdated package versions before merge or deployment.

When should developers run dependency-auditor?

dependency-auditor fits pre-merge PR review and pre-deploy checks for Go services, giving developers a fast supply-chain snapshot without switching to a separate security console.

Is Dependency Auditor safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Securitybackendintegrationstesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.