license-check
Inventory the licenses of a project's dependency graph and enforce a policy over them using postmortem - denied licenses, unknown licenses, dual-licensing. Use when the user asks about license compliance, what licenses their dependencies carry, whether GPL/AGPL is present, or wants a license gate for CI.
- License 许可
- MIT
- 最近更新
- 2026-10-22
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- license-check
- description
- Inventory the licenses of a project's dependency graph and enforce a policy over them using postmortem - denied licenses, unknown licenses, dual-licensing. Use when the user asks about license compliance, what licenses their dependencies carry, whether GPL/AGPL is present, or wants a license gate for CI.
03 SKILL.md 正文
License Compliance Check
CLI details and preflight:
${CLAUDE_PLUGIN_ROOT}/docs/postmortem-reference.md.
Workflow
1. Preflight
postmortem --version. Ask for the policy if none is stated and none exists in postmortem.conf (auto-loaded [license] section): which SPDX ids are forbidden (typical: AGPL-3.0-only and copyleft for proprietary SaaS), and does unknown fail?
2. Inventory
postmortem licenses <path> --online --packages --json -o -
--online is usually needed: only npm and composer declare licenses offline. --unknown-only for a focused pass on the unresolved set.
3. Enforce
Either via flags: --deny <SPDX> (repeatable), --allow <SPDX> (allowlist mode), --fail-on-unknown (pair with --online); or via the project's postmortem.conf. Key semantics to relay: a dual-licensed package fails only when EVERY alternative it offers is denied - report the alternative that saves it.
4. Report
## License inventory: <project> - <compliant | violations | unknowns to resolve>
| License | Packages | Policy |
|---|---|---|
### Violations
<package, license, why denied, the dependency path that pulls it in (postmortem why <pkg> <path>)>
### Unknown licenses
<the actionable set: package + where to check>
### CI gate
<the exact licenses command with policy flags, or the postmortem.conf [license] block to commit>
Rules
- You report what the graph declares; whether a license is acceptable for the user's product is their counsel's call - state findings, not legal advice.
- Unknown is not a violation; it is unresolved. Keep the two lists separate.
- Dev-only dependencies often deserve a softer policy: mention
--omit devwhen a violation sits in the dev tree.
04 同仓库更多 Skills
threat-watch
Generate a threat landscape digest from mlab.sh - recent critical/KEV CVEs filtered to a declared technology stack, with actor attribution. Use when the user asks what is new in vulnerabilities, wants a daily/weekly threat brief, asks about recent CVEs for a product, or sets up a recurring watch on their stack.
supply-chain-audit
Full supply-chain audit of a project - postmortem detects malicious code, install hooks and risky dependencies locally, then mlab.sh enriches what it finds (hashes, endpoints, actors, CVEs). Use when the user asks to audit a project's dependencies or supply chain, check a repo for malicious packages, or vet a codebase before adoption or deployment.
smishing-campaign
Analyze a batch of reported SMS/text messages through mlab.sh - score each for smishing, cluster them into campaigns, and extract the shared infrastructure (URLs, callback numbers, sender patterns). Use when the user has multiple reported SMS from users/employees, or investigates an SMS phishing wave. For a single message, phishing-triage does the job.
script-triage
Statically analyze a suspicious shell script through mlab.sh - install.sh, cron payloads, CI steps, curl-pipe-sh one-liners. Flags dangerous constructs (download-piped-to-shell, base64 decoding, reverse shells, persistence, anti-forensics, destructive deletes), extracts every IOC and enriches them. Use when the user pastes shell code and asks if it is safe/malicious, or provides a .sh file to vet before running it.
sbom-export
Generate a CycloneDX SBOM locally with postmortem and push it through mlab.sh vulnerability scanning - for projects or container images where no single lockfile can be pasted. Use when the user asks for an SBOM, needs vuln scanning of a container image or a multi-ecosystem repo, or when sbom-audit lacks a usable lockfile.
sbom-audit
Audit a dependency lockfile or SBOM for known vulnerabilities via mlab.sh, prioritize findings by KEV status and EPSS, and attribute actively exploited CVEs to threat actors. Use when the user provides a lockfile (package-lock.json, yarn.lock, pnpm-lock.yaml, Cargo.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, go.sum, composer.lock, Gemfile.lock, pom.xml, gradle.lockfile, packages.lock.json, pubspec.lock, mix.lock) or a CycloneDX / SPDX SBOM, or asks to check dependencies for vulnerabilities.