What problem does it solve?
It helps you determine which open-source licenses appear in a dependency set and what obligations or risks they create for your planned deployment, so you can avoid shipping or releasing code that could trigger copyleft duties or non-OSI restrictions.
Core Features & Use Cases
- Dependency license compliance memo: Produces a lawyer-ready memo that classifies dependencies by license family, highlights “needs review” items, and recommends actions like comply, replace, remove, or seek legal review.
- Deployment-aware obligation mapping: Treats the same dependency list differently depending on whether you’re deploying as SaaS, distributing binaries, using internal-only, or embedding/firmware.
- Non-OSI and compatibility checks: Flags license-unknown and non-OSI source-available licenses (e.g., SSPL/BUSL/Commons Clause/Elastic/fair-source) and performs outbound-license compatibility checks when reviewing code you plan to open-source.
- Jurisdiction and contested-issue escalation: Surfaces contested/copyleft triggers (e.g., AGPL network trigger, GPL-3.0 “conveying,” LGPL linking scope) for attorney review with the factors on both sides.
Quick Start
Run /ip-legal:oss-review with a manifest path, SBOM path, a package name, or pasted dependency text, and include the deployment model you intend to use so the memo can map obligations correctly.
