What problem does it solve? Legal and engineering teams need to know what licenses are in their dependency tree, what obligations those licenses trigger given how the software is deployed, and what to do about each one before shipping or open-sourcing code. ## Core Features & Use Cases - License Classification: Classifies every dependency into permissive, weak copyleft, strong copyleft, public domain, non-OSI source-available, or unknown buckets by reading actual license text rather than package metadata. - Deployment-Aware Obligation Mapping: Maps obligations to the deployment model (SaaS, distributed binary, internal only, embedded) since the same dependency triggers different obligations in each context. - Risk-Flagged Memo Output: Produces a structured memo with severity ratings, top-of-memo flags for license-unknown and non-OSI packages, outbound license compatibility checks, and attorney approval routing. - Use Case: Point it at a package.json or SBOM before a release to learn that a transitive AGPL dependency in your SaaS product requires attorney review before shipping. ## Quick Start Ask the assistant to run an OSS license review on your project's package.json file and tell it how the software will be deployed.
