License Declared
Question: What are the declared software package licenses?
Overview
License Declared measures the total number and specific licenses declared in a software package which include both software and documentation source files. Data points consist of a list of unique licenses and the corresponding number of files associated with each license. For Example: 
To understand the declared licenses is critical for several reasons:
- Software packages often contain multiple licenses. Knowing the declared licenses is vital for compliance purposes during software acquisition.
- Licenses can create conflicts such that not all obligations can be fulfilled across all licenses in a software package. Licenses Declared can provide transparency on potential license conflicts present in software packages.
Understanding license conflicts is crucial to avoid legal issues and ensure smooth integration of software components.
Want to Know More?
Filters
- Time: Licenses declared in a repository can change over time as the dependencies of the repository change. One of the principle motivations for tracking license presence, aside from basic awareness, is to draw attention to any unexpected new license introduction.
- Declared and Undeclared: Separate enumeration of files that have license declarations and files that do not.
References
Additional Information
To edit this metric please submit a Change Request here
To reference this metric in software or publications please use this stable URL: https://chaoss.community/?p=3963
The usage and dissemination of health metrics may lead to privacy violations. Organizations may be exposed to risks. These risks may flow from compliance with the GDPR in the EU, with state law in the US, or with other laws. There may also be contractual risks flowing from terms of service for data providers such as GitHub and GitLab. The usage of metrics must be examined for risk and potential data ethics problems. Please see CHAOSS Data Ethics document for additional guidance.