maintainer-license-checklisted
Install: claude install-skill vivekbhange-hub/maintainer-skill
# Dependency license check
Most license trouble in open source is boring and avoidable: a strong-copyleft package pulled
into a permissive project, a dependency with no license at all, or a "source-available" package
that is not open source. This skill finds those early, explains each flag in one line, and
says what the usual options are. It does not give legal advice and says so in every report.
## Steps
1. **Identify the project license.** Look at `LICENSE*`/`COPYING`, then the `license` field in
`package.json`, `pyproject.toml` (`[project]` or `[tool.poetry]`), or `Cargo.toml`. If they
disagree, report the mismatch as a finding and ask which is intended. If there is none, stop
and say the project itself has no license; suggest choosing one first (link
https://choosealicense.com) because nothing else can be judged without it.
2. **Gather license data.** The helper reads manifests directly; lockfiles from npm (v2/v3)
already carry licenses. For other ecosystems, try the local tools that are installed, never
fetching from the network without asking:
- npm/yarn/pnpm: `npx --no-install license-checker --json > maintainer/.cache/npm-licenses.json`
- Python (inside the project's env): `pip-licenses --format=json > maintainer/.cache/py-licenses.json`
- Rust: `cargo metadata --format-version 1 > maintainer/.cache/cargo-meta.json`
- Go: `go-licenses report ./... > maintainer/.cache/go-licenses.csv` (module,url,license; the
helper takes the last