needs-compliance

Name: needs-compliance
Availability: InStock
Author: provenimpact

Analyze dependency licenses and enforce policy compliance from docs/constraints.adoc.

Updated Feb 19, 2026

Search Tags:#dependencies #remediation #compliance #license #governance #policy

Ready to run

npx skills add https://github.com/provenimpact/proven-needs --skill needs-compliance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: needs-compliance
Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-compliance
Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps organizations identify and enforce license and policy compliance across a software project, reducing legal risk and governance gaps.

Core Features & Use Cases

Dependency license analysis for direct and transitive dependencies.
Read constraints from docs/constraints.adoc to enforce licensing rules.
Identify direct, transitive, and unknown license violations.
Propose remediations and orchestrate remediation steps within the proven-needs workflow.
Provide governance-ready compliance audits and reports.

Quick Start

Run the compliance scan to identify license violations and propose remediations for the current project.

Frequently Asked Questions about needs-compliance

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

FAQPage Schema

How do I check software dependency licenses for compliance violations?▼

Dependency license compliance violations are identified by scanning direct and transitive dependencies against rules defined in docs/constraints.adoc. The scan flags direct, transitive, and unknown license conflicts, providing governance-ready audit reports and proposing remediation steps to the orchestrator.

What is transitive dependency license analysis and why does it matter for governance?▼

Transitive dependency license analysis detects policy violations in nested packages within a software project. It matters for governance because it exposes hidden legal risks from indirect dependencies, ensuring comprehensive audits and enabling accurate remediation planning for all unknown or non-compliant licenses.

Can I enforce specific licensing rules from a constraints file across my project?▼

Yes, you can enforce specific licensing rules by defining them in a docs/constraints.adoc file. The compliance enforcement process reads these regulatory and governance constraints, applies them across the software project, and flags any direct or transitive dependencies that violate the specified policies.

How do I plan remediation for unknown or non-compliant dependency licenses?▼

Remediation for unknown or non-compliant dependency licenses is planned by running a compliance scan that identifies violating packages and proposes targeted remediation steps to the orchestrator. This workflow integrates remediation planning directly, ensuring all direct and transitive legal risks are resolved systematically.

Does this compliance scan work for projects with complex regulatory constraints?▼

Yes, the compliance scan works for projects with complex regulatory constraints and governance requirements. It reads rules from docs/constraints.adoc to analyze all dependency licenses, enabling comprehensive audits and ongoing enforcement tailored to your specific legal and regulatory environment.