CtrlK
BlogDocsLog inGet started
Tessl Logo

endor-license

Analyze dependency license compliance and identify license risks. Use when the user says "check licenses", "license compliance", "any GPL dependencies", "copyleft risk", "endor license", or wants to know if dependencies are compatible with their project license. Flags copyleft (GPL, AGPL), unknown, and no-license packages. Do NOT use for vulnerability scanning (/endor-sca) or policy enforcement (/endor-policy).

83

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/endor-license/SKILL.md
SKILL.md
Quality
Evals
Security

Endor Labs License Compliance

Analyze dependency licenses for compliance risks and compatibility.

License Categories

CategoryLicensesRisk
PermissiveMIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, Unlicense, CC0-1.0Low
Weak CopyleftLGPL-2.1, LGPL-3.0, MPL-2.0, EPL-2.0, CDDL-1.0Medium
Strong CopyleftGPL-2.0, GPL-3.0, AGPL-3.0, SSPL, OSL-3.0High
Unknown/NoneNo license, custom, proprietary, UNLICENSEDHigh

Workflow

Step 1: Get License Findings

Use scan MCP tool with scan_types: ["dependencies"], scan_options: { "quick_scan": true }. Retrieve details via get_resource (resource_type: Finding).

CLI fallback:

npx -y endorctl api list --resource Finding -n $ENDOR_NAMESPACE --filter "spec.finding_categories contains FINDING_CATEGORY_LICENSE_RISK" 2>/dev/null

For CLI field paths and parsing gotchas, read references/cli-parsing.md.

Step 2: Analyze Manifest Files

Read project manifests (package.json, go.mod, etc.) to build a complete license inventory.

Step 3: Present Results

## License Compliance Report

**Project:** {name} | **Dependencies Analyzed:** {count}

### License Summary

| Category | Count | Risk |
|----------|-------|------|
| Permissive (MIT, Apache, BSD) | {n} | Low |
| Weak Copyleft (LGPL, MPL) | {n} | Medium |
| Strong Copyleft (GPL, AGPL) | {n} | High |
| Unknown/No License | {n} | High |

### License Risks

| # | Package | License | Risk | Issue |
|---|---------|---------|------|-------|
| 1 | {pkg} | GPL-3.0 | High | Copyleft - may require open-sourcing |
| 2 | {pkg} | AGPL-3.0 | Critical | Network copyleft - affects SaaS |

For each high-risk finding, provide:
- Implications for proprietary vs. open-source projects
- Permissive-licensed alternatives
- Options: replace, isolate, accept copyleft, request exception

### Full License Inventory

| Package | License | Category | Risk |
|---------|---------|----------|------|

### Next Steps

1. `/endor-policy` — Enforce license rules
2. `/endor-scan` — Full security analysis
3. `/endor-cicd` — Add license checks to CI/CD

Compatibility Matrix

Commercial/Proprietary Projects

LicenseCompatibleAction
MIT, Apache, BSDYesAllow
LGPLReviewCheck linking method
GPL, AGPLNoBlock or replace
UnknownNoBlock until resolved

Open Source (MIT/Apache) Projects

LicenseCompatibleAction
MIT, Apache, BSD, LGPLYesAllow
GPLPartialMay affect project license
AGPLNoBlock or replace

For data source policy, read references/data-sources.md.

Error Handling

ErrorAction
No license findingsNo scan run — suggest /endor-scan
Auth errorSuggest /endor-setup
Repository
endorlabs/skills-ideas
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.