dependency-governance

Enforce dependency policies and audit package changes in repositories.

3|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pax-k/pax-fullstack-harness --skill dependency-governance-pax-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-governance
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/dependency-governance
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill dependency-governance-pax-k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Dependency Governance helps manage the sprawl of dependencies in repositories, ensuring changes are intentional, justified, and reviewable.

Core Features & Use Cases

  • Policy Definition: Establish rules for adding, replacing, or removing dependencies.
  • Dependency Checks: Utilize tools for audit and unused-dependency checks.
  • Documentation: Update and record decisions in docs/quality/dependencies.md.
  • Security Coordination: Use security-baseline for vulnerability checks.
  • Validation: Run checks and confirm rationale for new dependencies.
  • Use Case: Before deploying a new package, use Dependency Governance to validate the decision, ensuring it adheres to the project's standards.

Quick Start

Use the dependency-governance skill to validate the addition of a new package in your project.

Frequently Asked Questions about dependency-governance

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

FAQPage Schema
How do I enforce policies for adding new dependencies to a repository?

You can enforce dependency policies by defining rules for package additions, utilizing audit tools for unused-dependency checks, and validating that rationale exists for new packages before deployment.

What is dependency governance and when do I need it for my project?

Dependency governance manages dependency sprawl by ensuring changes are intentional, justified, and reviewable. You need it when agent-edited repositories require strict policy enforcement, security auditing, and documentation for package modifications.

How do I document dependency changes and security audits in my codebase?

Document dependency changes by updating and recording decisions in `docs/quality/dependencies.md`. Coordinate vulnerability checks using a security baseline to ensure all package modifications and audits are properly archived.

Can I audit unused dependencies and check for vulnerabilities before deploying packages?

Yes, you can run dependency checks using ecosystem tools to audit unused packages and coordinate vulnerability checks against a security baseline to validate package decisions before deployment.

Does dependency governance work for package removal as well as dependency addition?

Yes, dependency governance applies to dependency addition, removal, and security auditing. It requires policy definition, ecosystem tools, and documentation updates to ensure all package changes are justified and reviewable.

What's the best way to manage dependency sprawl in agent-edited repositories?

The best way to manage dependency sprawl is establishing policy rules for package changes, running automated dependency audits, validating new package rationale, and updating decision records in your project documentation.