License Compliance Check
Review package licenses against intended use.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review the licenses of my dependencies against how I will use them. This is an engineering screening aid, not legal advice. Project type and distribution (internal tool, SaaS, distributed app, library): [DISTRIBUTION]. My own license or business model: [MY_LICENSE_OR_MODEL]. Dependency list with versions and licenses: [PASTE_DEPENDENCY_LICENSES]. Tables: 1. License summary: Package | Version | License | Category (permissive, weak copyleft, strong copyleft, network copyleft, source-available, unknown) | Obligations (attribution, notice, source offer, share-alike). 2. Risk by use: Package | My use (linked, modified, bundled, only used internally) | Concern | Severity | Action. 3. Unknown or custom licenses: what I must read in full. 4. Obligations checklist: attribution file, license texts, notices, source availability, and where to put them. 5. Policy proposal: allowed, needs review, and prohibited license categories for my business. State that obligations depend on how software is combined and distributed, which only a qualified lawyer can confirm for [JURISDICTION]. Do not claim a package is safe; mark every conclusion as a question for counsel where it matters.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.