dep_audit

Audit and remediate dependency vulnerabilities in Go and Node.js modules.

2.0k|126|Updated Jun 16, 2020
One-click install
npx skills add https://github.com/authgear/authgear-server --skill dep-audit-authgear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dep_audit
Source: https://github.com/authgear/authgear-server/tree/main/.claude/skills/dep_audit
Command: npx skills add https://github.com/authgear/authgear-server --skill dep-audit-authgear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the multi-language dependency vulnerability audit so you can resolve Go and Node security issues without juggling separate procedures or missing critical modules.

Core Features & Use Cases

  • Comprehensive Go Coverage: Runs govulncheck per module, compares versions, defers breaking upgrades, and tidies every module that changes.
  • Structured Node.js Remediation: Audits each package.json directory in sequence, removes stale overrides, gathers breaking-change reports, and applies npm audit fix for patchable issues.
  • Use Case: For authgear-server, follow the instructions to secure both the Go toolchain and every npm-based subproject, then stage and commit the resulting dependency updates.

Quick Start

Start the audit by running govulncheck in every Go module and npm audit across the portal, authui, portalgraphiql, and scripts/npm directories as described in the SKILL.md instructions.

Frequently Asked Questions about dep_audit

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

FAQPage Schema
How do I audit dependency vulnerabilities across both Go and Node.js modules?

Auditing dependency vulnerabilities across Go and Node.js modules requires running govulncheck per Go module and npm audit per package.json directory, then applying fixes that respect semver constraints while deferring major upgrades.

What's the best way to handle breaking changes when upgrading npm dependencies?

Handling breaking changes during npm dependency upgrades involves removing stale overrides, gathering breaking-change reports per directory, and applying npm audit fix only for patchable issues to ensure builds validate before committing.

Does govulncheck work with nested Go modules in a single repository?

Govulncheck works with nested Go modules by running the tool per module, comparing versions, deferring breaking upgrades, and running go mod tidy on every module that changes to maintain consistency.

Can I clean up stale npm overrides while fixing security vulnerabilities?

Cleaning up stale npm overrides during vulnerability remediation involves auditing each package.json directory in sequence, removing outdated overrides, and applying npm audit fix to patch security issues without breaking semver constraints.

How do I validate builds before committing dependency updates?

Validating builds before committing dependency updates requires running govulncheck and npm audit fixes across all Go modules and Node.js directories, then confirming builds pass before staging and committing the resulting changes.

When should I defer major version upgrades during a dependency audit?

Deferring major version upgrades during a dependency audit is necessary when fixes must respect semver constraints, ensuring patchable vulnerabilities are resolved while breaking changes are documented and major upgrades are postponed.