agentleFS
Sign inStart free
kasimmjkasimmj/claude-skills-mega/skills/license-check/SKILL.md

license-check

Skill1 starsChanged 6 months agoMITView on GitHub

Inventory all dependency licenses across package.json, requirements.txt, go.mod, Cargo.toml, pubspec.yaml and flag incompatible or unknown licenses.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. usk6666/yorishiro-proxy★ 19same name
    2. Vulnetix/pix-ai-coding-assistant★ 9same name
    3. manastalukdar/ai-devstudio★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look for and parse:

    line 20
  2. Distinctive:

    Read from lockfile if license metadata is there

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

License Check Skill

You are performing a dependency license audit. Output is a table — make it readable and actionable.

Step 1 — Find all manifests

Look for and parse:

  • package.json + package-lock.json / yarn.lock / pnpm-lock.yaml
  • requirements.txt, Pipfile.lock, poetry.lock, pyproject.toml
  • go.mod / go.sum
  • Cargo.toml / Cargo.lock
  • pubspec.yaml / pubspec.lock
  • Gemfile.lock
  • composer.lock

Step 2 — Resolve license for each dep

For each direct + transitive dependency:

  • Read from lockfile if license metadata is there
  • Otherwise: hit the registry (npm, PyPI, crates.io, pub.dev)
  • Fall back to "UNKNOWN" — don't guess

Step 3 — Classify

ClassExamplesOK for proprietary?
🟢 PermissiveMIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, Unlicense✅ Yes
🟡 Weak copyleftLGPL-2.1, LGPL-3.0, MPL-2.0⚠️ With caveats (dynamic linking, file-level)
🔴 Strong copyleftGPL-2.0, GPL-3.0, AGPL-3.0❌ No — would force open-sourcing
⚪ Source-availableBSL, SSPL, Elastic v2⚠️ Often forbidden for SaaS
❓ Unknown / Missing—⚠️ Must resolve before shipping

Step 4 — Output

LICENSE AUDIT REPORT
─────────────────────
Total dependencies: 1,247 (direct: 38, transitive: 1,209)

🔴 BLOCKERS (must remove or replace)
  - <package@version> — <license> — <reason>

⚠️ WARNINGS (review with legal)
  - <package@version> — <license> — <reason>

❓ UNKNOWN (resolve before release)
  - <package@version> — <repo URL to investigate>

🟢 CLEAN (1,239 packages)
  ✓ MIT       : 894
  ✓ Apache-2.0 : 218
  ✓ BSD-3-Clause: 71
  ✓ ISC        : 56

Step 5 — Suggest fixes

For each blocker, suggest a permissive replacement if you know one:

  • mariadb (GPL) → mysql2 (MIT)
  • readline (GPL) → linenoise (BSD)

When NOT to use

  • The project is OSS itself with a GPL license — copyleft deps are fine then
  • You only need a security audit (use security-audit skill)

Failure modes

  • ⚠️ License strings in metadata are not always accurate. Always cross-check with the actual LICENSE file in the upstream repo for anything critical.
  • ⚠️ Dual-licensed projects (e.g., MPL + GPL) need careful handling — note the dual nature and recommend the permissive option.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free