Open Source License Compliance Verification Checklist
Audit third-party dependencies and licensing obligations before commercial software distribution.
Use this template when preparing a codebase for commercial release, acquisition, or distribution to ensure full compliance with open-source licensing and IP policies. It provides a structured audit checklist to mitigate legal and intellectual property risks.
Role: Principal Compliance Systems Engineer specializing in open-source governance, IP risk mitigation, and automated dependency analysis.
Context
- Project name: {{project_name}}
- Target codebase repository: {{target_codebase}}
- License compliance policy tier: {{license_policy_tier}}
- Dependency inventory list: {{third_party_dependencies}}
- Software distribution model: {{distribution_model}}
- Primary operational jurisdiction: {{target_jurisdiction}}
Task
Produce an actionable, domain-organized verification checklist to audit all third-party software dependencies within {{target_codebase}} against {{license_policy_tier}} standards for safe release under {{distribution_model}}.
Method
- Review {{third_party_dependencies}} against banned and restricted license lists specified in {{license_policy_tier}}.
- Trace transitive dependencies to isolate recursive GPL, AGPL, or reciprocal copyleft obligations.
- Evaluate dynamic versus static linking boundaries across binary artifacts in {{target_codebase}}.
- Check notice, attribution, and third-party copyright inclusion files against {{target_jurisdiction}} legal baselines.
- Audit proprietary dual-licensed components for active commercial licensing entitlements.
- Formulate binary triage rules for modified open-source components requiring source disclosure.
- Structure verification line items into clear sequential phases for release approval.
Constraints
- Every checklist item MUST include a deterministic verification criterion and risk tier (High, Medium, Low).
- MUST NOT include generic advisory statements without direct reference to {{target_codebase}} or {{distribution_model}}.
- Checklists MUST categorize items into Pre-Build Scan, Dependency Audit, and Legal Artifact Generation.
- Keep individual checklist line items concise and actionable for senior engineers.
Output format
- Executive Audit Overview (max 100 words)
- Checklist Section 1: Pre-Build & Ingestion Controls (4-6 items)
- Checklist Section 2: Copyleft & Linking Boundaries (4-6 items)
- Checklist Section 3: Attribution & Artifact Delivery (3-5 items)
- Release Sign-Off Matrix with designated approver roles
Self-review
- Ensure all variables ({{project_name}}, {{target_codebase}}, {{license_policy_tier}}, {{third_party_dependencies}}, {{distribution_model}}, {{target_jurisdiction}}) are actively referenced.
- Confirm every checklist entry contains a markdown checkbox [ ] and a risk classification.
- Verify no placeholder or boilerplate text remains in any section.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.