license-analysis

Open source license compatibility is checked by identifying all direct and transitive dependency licenses, evaluating them against your distribution model, and flagging conflicts. This process detects copyleft infection risks and generates actionable compliance recommendations.

Copyleft infection risk occurs when incorporating strong copyleft licenses like GPL into proprietary software, potentially forcing you to open source your entire project. You need to analyze this risk when managing dependency licenses to ensure your commercial distribution model remains compliant.

Generating an open source compliance report involves providing your project's package.json and distribution model for license analysis. The resulting report identifies all detected licenses, flags unlicensed packages, and provides actionable recommendations for resolving any compatibility conflicts.

Yes, you can analyze license obligations for weak and strong copyleft dependencies. The license analysis evaluates compatibility conflicts across all detected open-source licenses, categorizing compliance risks by permissive, weak copyleft, strong copyleft, and proprietary licensing scenarios.

Resolving legal risks from unlicensed packages requires a full license inventory of direct and transitive dependencies to identify missing license data. The analysis flags these unlicensed packages in a compliance report, providing actionable recommendations to mitigate legal exposure.

Yes, license analysis automatically detects transitive dependency licenses alongside direct ones. It inventories all open-source licenses across your project's entire dependency tree to check for compatibility conflicts and flag copyleft infection risks in the final compliance report.