License risk issues

License risk issues identify packages with licensing concerns that may create compliance obligations.

Tag ID	Issue name	Issue description	Severity	Importance	Example
IL0022	License mismatch	Package has a license mismatch between metadata and files	Minimum
IL0050	License	License requires source code distribution	Minimum	Understanding and complying with source code distribution requirements is essential to avoid legal issues and uphold open-source licensing principles. Non-compliance can result in legal disputes or compel the release of proprietary code, potentially undermining commercial business models.	Several licenses require source code distribution. AGPL (Affero General Public License): Software that uses AGPL-licensed code, including software accessed over a network, must be released under the AGPL, making the source code publicly accessible. GPL (General Public License): Requires derivative works to be open sourced under the GPL, enforcing similar distribution obligations. For example, if you include a library released under the GPL in your proprietary application, you would be required to release your application's source code under the GPL, making it publicly accessible and freely redistributable.
.L0005	License	Non-commercial use risk detected	Situation-dependent severity	Using software governed by non-commercial licenses in a commercial environment can lead to serious legal and financial consequences. Organizations should identify and review all software licenses carefully to ensure compliance and reduce the risk of violations.	Non-commercial licenses often include terms that explicitly prohibit using the software for commercial purposes. Creative Commons Attribution-NonCommercial (CC BY-NC): Prohibits using the licensed software for any commercial purpose. For example, if a developer uses a library released under a non-commercial license in a proprietary application, that use violates the license terms and could lead to legal disputes.