license-analysis

Analyze open-source license compatibility and compliance risks across project dependencies.

147|32|Updated Feb 11, 2026

Search Tags:#spdx #dependency scanning #copyleft #legal risk #license analysis #open source compliance

Ready to run

npx skills add https://github.com/seb1n/awesome-ai-agent-skills --skill license-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: license-analysis
Source: https://github.com/seb1n/awesome-ai-agent-skills/tree/main/legal-and-compliance/license-analysis
Command: npx skills add https://github.com/seb1n/awesome-ai-agent-skills --skill license-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and resolve potential legal risks and compliance issues arising from the mix of open-source licenses used in a software project's dependencies.

Core Features & Use Cases

License Inventory: Automatically detects all licenses across direct and transitive dependencies.
Compatibility Checks: Evaluates license compatibility against your project's distribution model.
Risk Assessment: Flags copyleft infection risks and unlicensed packages.
Compliance Reporting: Generates a report with actionable recommendations for resolving conflicts.
Use Case: Ensure your commercial software doesn't inadvertently violate the terms of GPL-licensed libraries it depends on.

Quick Start

Analyze the licenses in my Node.js project, providing the package.json and my project's distribution model.

Frequently Asked Questions about license-analysis

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

FAQPage Schema

How do I check open source license compatibility for my project dependencies?▼

Open source license compatibility is checked by identifying all direct and transitive dependency licenses, evaluating them against your distribution model, and flagging conflicts. This process detects copyleft infection risks and generates actionable compliance recommendations.

What is copyleft infection risk and when do I need to analyze it?▼

Copyleft infection risk occurs when incorporating strong copyleft licenses like GPL into proprietary software, potentially forcing you to open source your entire project. You need to analyze this risk when managing dependency licenses to ensure your commercial distribution model remains compliant.

How do I generate an open source compliance report for my Node.js project?▼

Generating an open source compliance report involves providing your project's package.json and distribution model for license analysis. The resulting report identifies all detected licenses, flags unlicensed packages, and provides actionable recommendations for resolving any compatibility conflicts.

Can I analyze license obligations for both weak and strong copyleft dependencies?▼

Yes, you can analyze license obligations for weak and strong copyleft dependencies. The license analysis evaluates compatibility conflicts across all detected open-source licenses, categorizing compliance risks by permissive, weak copyleft, strong copyleft, and proprietary licensing scenarios.

What is the best way to resolve legal risks from unlicensed packages in my software?▼

Resolving legal risks from unlicensed packages requires a full license inventory of direct and transitive dependencies to identify missing license data. The analysis flags these unlicensed packages in a compliance report, providing actionable recommendations to mitigate legal exposure.

Does license analysis detect transitive dependency licenses automatically?▼

Yes, license analysis automatically detects transitive dependency licenses alongside direct ones. It inventories all open-source licenses across your project's entire dependency tree to check for compatibility conflicts and flag copyleft infection risks in the final compliance report.