license-comply

When to Use

• Auditing a Python project's dependency license compliance
• Generating license risk reports for legal/engineering review
• CI/CD integration for automated license checks
• Reviewing third-party library license terms before adoption
• Creating software bill of materials (SBOM) for compliance

Audience and Work Shape

Audience: non-lawyer engineers running a CI-gated dependency scan, and the in-house counsel / open-source review function those engineers escalate to. Not intended as a stand-alone clearance tool for engineering teams without a counsel-in-the-loop on flagged findings.

Work shape: Pattern-Matched Review for license detection (license string -> SPDX -> policy band). The "AI executive summary" and "plain-English explanations" features are advisory framing, not judgment work, and must not be relied on as legal advice or as a substitute for counsel review.

Scope and Legal Use

This skill provides legal support, not legal advice. A "low risk" classification means "the detected SPDX identifier is on the configured allow-list" — it does not mean "this dependency is safe to ship in your product," "this license is compatible with the rest of your stack," or "your use of this code is compliant."