license-compatibility-analysis
Analyze OSS + third-party licenses for compatibility with the distribution model. Inventory deps, classify licenses, detect incompatibilities, list obligations. Not legal advice.
What this skill does
# License Compatibility Analysis You produce a license compatibility report for a codebase. This is an engineering/compliance artifact fed to legal counsel — not legal advice. ## Core rules - **Evidence-based** — every claim cites the dependency + license file + identifier - **Distribution model drives the answer** — same license, different conclusion for SaaS vs on-prem vs SDK - **Transitive dependencies matter** — copyleft reach travels through deps - **AGPL and SSPL are different from GPL** — treat separately - **Unknown license is a finding** — not a neutral state - **Not legal advice** — explicit disclaimer; hand to counsel - **No fabricated licenses** — work from actual manifests + license files ## Input handling | Dimension | Required | Default | |---|---|---| | **Codebase / project** | Yes | — | | **Distribution model** (SaaS / on-prem / SDK / CLI / mobile app / model weights) | Yes | — | | **Intended project license** | Yes | — | | **Commercial vs non-commercial** | No | Commercial (asked) | | **SBOM or manifest location** | No | Discovered | ## Phase 1 — Setup ``` **Codebase**: [repo] **Distribution model**: [SaaS / on-prem binary / library / SDK / model weights / ...] **Intended project license**: [MIT / Apache-2.0 / BSL / proprietary / ...] **Commercial use**: [yes / no] **Target audience**: [public / partners / internal] **Reach**: [what users receive — source, binary, compiled artifact, network access] **SBOM available**: [yes / no / to be generated] ``` Ask render mode per `diagram-rendering` mixin and output path (default: `/documentation/[case]/license-compatibility/`). > **Disclaimer**: Not legal advice. This report is an engineering artifact; decisions require legal counsel review. ## Phase 2 — Dependency inventory Gather direct + transitive deps via appropriate tool: | Ecosystem | Tool | |---|---| | npm / Node | `npm ls --all` + `license-checker` / `licensee` | | Python | `pip-licenses` / `pip-audit` / SBOM via `cyclonedx-bom` | | Go | `go-licenses` | | Java | `mvn license:aggregate-third-party-report` / Gradle `license` plugin | | Rust | `cargo-deny` / `cargo-license` | | .NET | `nuget-license` / `dotnet list package` | | Container images | Syft / Trivy SBOM | | Multi-ecosystem | Syft (generates CycloneDX or SPDX SBOM) | Table columns: | Package | Version | License | Source | Direct / Transitive | Usage | |---|---|---|---|---|---| | express | 4.19.2 | MIT | npm | direct | runtime | | ... | | | | | | If SBOM supplied: use as authoritative inventory. ## Phase 3 — License classification | Class | Examples | Notes | |---|---|---| | **Permissive** | MIT, BSD-2/3-Clause, Apache-2.0, ISC, Zlib | Minimal obligations (attribution); Apache-2.0 has explicit patent grant | | **Weak copyleft** | LGPL (2.1/3.0), MPL-2.0, EPL-2.0 | File-level or library-level copyleft; dynamic linking often OK | | **Strong copyleft** | GPL (2.0/3.0) | Derivative works must be GPL on distribution | | **Network copyleft** | AGPL-3.0, SSPL | Copyleft triggers on network interaction, not just distribution | | **Source-available (non-OSS)** | BSL 1.1, SSPL, Elastic License v2 | Not OSI-approved; restrictions on production or competitive use | | **Creative Commons** | CC-BY, CC-BY-SA, CC-BY-NC | Not for software generally; NC precludes commercial use | | **Public domain / CC0** | CC0-1.0, Unlicense, WTFPL | Patent grant uncertainty in some jurisdictions | | **Proprietary / Commercial** | Vendor EULAs | Contractual terms; read per-license | | **Dual / Multi** | MIT-or-Apache-2.0, GPL-or-Commercial | Pick the branch that applies | | **Unknown / Missing** | no license file detected | Treat as "all rights reserved"; cannot use without permission | Use SPDX license identifiers (https://spdx.org/licenses/) for unambiguous reference. ## Phase 4 — Compatibility matrix (simplified) Compatibility depends on *your* project's license + distribution model. Simplified: | Dep license | SaaS (no distribution) | On-prem binary | SDK / library | Static link | Dynamic link | |---|---|---|---|---|---| | MIT / BSD / Apache-2.0 | ok | ok | ok | ok | ok | | LGPL | ok | caution — relink obligation | caution — relink | avoid static | ok (dynamic OK) | | GPL-2.0 / 3.0 | ok (SaaS loophole*) | copyleft triggers on distribution | breaks most SDKs | triggers | may trigger | | AGPL-3.0 | **triggers** — SaaS must release source | triggers | breaks most SDKs | triggers | triggers | | SSPL | **triggers** — service offering; legal review | triggers | breaks | triggers | triggers | | BSL 1.1 | depends — competitive use clause | depends | depends | depends | depends | | CC-BY-NC | **no commercial** | no commercial | no commercial | no commercial | no commercial | | Proprietary / EULA | per-terms | per-terms | per-terms | per-terms | per-terms | | Unknown | **block** | block | block | block | block | *GPL "SaaS loophole" is exactly what AGPL closes. This table is simplified — combinations (e.g., GPL-2.0-only vs GPL-2.0+) matter. ## Phase 5 — Per-dependency findings For every flagged dep: ``` **Package**: [email protected] **License**: MIT **Class**: permissive **Compatibility**: ok for all distribution models **Obligations**: include copyright + MIT license text in distributions **Action**: ensure `NOTICE` or `LICENSES/` includes the text **Package**: mongodb@* (driver) **License**: Apache-2.0 **Notes**: patent grant clause; compatible with proprietary **Package**: [email protected] **License**: AGPL-3.0 **Class**: network copyleft **Compatibility**: BLOCKING for proprietary SaaS — network interaction triggers source release **Action**: replace with permissive alternative; or obtain commercial license; or accept AGPL ``` ## Phase 6 — AI model + data license specifics If shipping model weights or datasets: | License | Notes | |---|---| | Apache-2.0 / MIT weights | Freely usable commercially | | Llama 2 / Llama 3 Community License | Use subject to acceptable use policy + monthly-active-user thresholds | | Gemma Terms | Prohibited use policy; commercial allowed within terms | | OpenRAIL-M / BigScience-RAIL | Use restrictions (responsible AI); downstream derivative obligations | | CC-BY datasets | Attribution; no redistribution of dataset itself often OK | | CC-BY-NC datasets | Non-commercial only — blocks commercial use | Model card + data card references required. ## Phase 7 — Attribution + NOTICE obligations Even permissive licenses require attribution: - MIT, BSD: keep copyright + license text with distributions (binary or source) - Apache-2.0: include a `NOTICE` file; propagate on modification - SaaS with no distribution: obligations often only trigger on distribution; but `/licenses` pages are still good hygiene Deliverables for compliance: - `LICENSE` file for the project - `NOTICE` or `THIRD_PARTY_LICENSES` aggregating attributions - In-app "Open Source Licenses" screen / page (mobile + desktop + web apps) - SBOM (CycloneDX / SPDX) for audit ## Phase 8 — Patent grants - Apache-2.0 grants patent rights + includes a retaliation clause - MIT does not explicitly grant patent rights (ambiguous in some jurisdictions) - BSD-3-Clause also silent on patents - GPL-3.0 explicit patent grant; GPL-2.0 weaker - BSL often restricts patent grants Flag patent-relevant dependencies for legal review. ## Phase 9 — Commercial + redistribution restrictions Non-OSS / source-available licenses commonly restrict: - Offering as a competing service (BSL, SSPL, Elastic License v2) - Running in production (BSL has a time-boxed revert to Apache) - Using in combination with non-open projects - Using name / trademark Read each license per-clause. ## Phase 10 — Risk rating | Rating | Meaning | |---|---| | **Block** | Cannot ship without remediation | | **Review** | Legal review required before ship | | **Obligation** | Permitted but obligations apply (attribution, NOTICE, source offer) | | **Clear** | Permitted, minimal obligations | Assign per finding. ## Phase 11 — Remediation options F
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.