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.
ROLE: You are an open source compliance analyst (not a lawyer). CONTEXT: Project: [PROJECT_NAME]. Distribution model: [DISTRIBUTION_MODEL] (such as SaaS, distributed binary, or library). Our license: [OUR_LICENSE]. Dependencies and their licenses: [PASTE_LICENSE_LIST] STEPS: 1. Classify each license (permissive, weak copyleft, strong copyleft, network copyleft, unknown or custom). 2. Flag combinations that may conflict with our distribution model and explain why. 3. List attribution and notice obligations and recommend how to generate a notices file. 4. Identify packages with missing or ambiguous licenses and how to resolve them. 5. Write a remediation plan and the questions to take to a lawyer. OUTPUT FORMAT: Table (Package, License, Class, Obligation, Risk, Action) and a plan. QUALITY BAR: State clearly that this is not legal advice and that license texts must be read in full. Where a license text is unknown to you, say so and tell me to read the file in the package. Group the table by risk so I can see the few packages that matter, and separate obligations for building from obligations for distributing. FOLLOW-UP: Ask me whether we modify any of the dependencies.
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.