license-compliance-scan
Skill13 starsChanged 21 days agoApache-2.0View on GitHub
Check dependency licenses against your project's license and flag conflicts, copyleft obligations, and unknown/unlicensed packages. Reads manifests directly. Advisory, not legal advice. Pure Claude Code, no signup.
In this repository35 other files it gives its agents.
- accessibility-checkSkill
- agentic-app-risk-reviewSkill
- api-security-scanSkill
- broken-link-scanSkill
- cold-load-waterfallSkill
- complexity-hotspotsSkill
- console-error-scanSkill
- cookie-privacy-scanSkill
- core-web-vitalsSkill
- dead-code-scanSkill
- dependency-auditSkill
- diff-risk-reviewSkill
- error-handling-auditSkill
- evidence-code-auditSkill
- exploited-vulnerability-watchSkill
- flaky-selector-scanSkill
- form-validation-scanSkill
- i18n-rtl-auditSkill
- iac-misconfig-scanSkill
- invisible-inkSkill
- mixed-content-scanSkill
- mr-nullSkill
- page-weight-budgetSkill
- railway-exposure-auditSkill
- responsive-screenshotsSkill
- script-quality-reviewSkill
- scunthorpe-checkSkill
- secret-scanSkill
- security-advisory-triageSkill
- security-auditSkill
- security-headers-checkSkill
- seo-checkSkill
- test-quality-reviewSkill
- third-party-bloatSkill
- ui-ux-scanSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read dependency manifests present: package.json, requirements.txt/pyproject.toml, go.mod, Cargo.toml, Gemfile, pom.xml, etc.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
License Compliance Scan
Spot license conflicts in your dependency tree before they become a problem. Read-only and advisory — it flags risks, it doesn't change anything, and it is not legal advice.
Prerequisites
- None. Pure Claude Code — reads dependency manifests and your
LICENSEdirectly, no MCP required.
Trigger
- "Check my dependency licenses"
- "Any license conflicts in this project?"
- "License compliance scan"
Workflow
- Identify the project's own license (from
LICENSE/package.json/pyproject.toml, etc.). - Read dependency manifests present:
package.json,requirements.txt/pyproject.toml,go.mod,Cargo.toml,Gemfile,pom.xml, etc. List declared dependencies and, where stated, their licenses. - Compare each dependency's license against the project's and report
file:line(the manifest entry), severity, and the obligation.
What to flag
| Finding | Why it matters |
| Strong copyleft in a permissive project | GPL/AGPL deps in an MIT/Apache project can impose source-disclosure obligations |
| Network copyleft (AGPL) | Obligations can trigger even for hosted/SaaS use |
| Unknown / missing license | A dependency with no clear license is a legal risk by default |
| License changed across versions | A pinned upgrade may pull in new obligations |
| Project itself missing a LICENSE | Others can't legally reuse it; flag if absent |
| Incompatible combinations | Two dependency licenses that can't be combined for distribution |
- Output an advisory report:
## License Compliance Scan
Project license: Apache-2.0
**1 high, 1 unknown**
### HIGH
- package.json:21 — "some-gpl-lib" is GPL-3.0; combining it with an Apache-2.0
distribution may impose source-disclosure obligations. Review or replace.
### UNKNOWN
- requirements.txt:8 — "obscure-pkg" declares no license. Treat as all-rights-
reserved until clarified.
Note: advisory only, not legal advice — confirm obligations with counsel.Diagnostic only. Want dependency and license checks in your CI gate? See QualityMax — qualitymax.io
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.