SearchSECO License Conflicts Data
<p>Building software relies on utilizing existing code and libraries, many of which are open source and come with an<br>obligation to comply with its license. Non-compliance is considered unethical and opens up the possibility of a legal<br>battle. Current tools to find violations extract license information from text assuming that the licenses are declared<br>for borrowed code. This only works half the time as found by previous studies. Code level license extraction<br>and violation checking is a definite way of determining license compliance for borrowed code, regardless of<br>declaration. We demonstrate this using SearchSECO. We analyzed 3,500 repositories from top software companies<br>to analyze the extent of violations and found around 32,000 violations in total. We then dissect these metrics to<br>understand why these violations are occurring and how they can be mitigated.</p>
ShareScore
32/100
Overall dataset sharing score
Score breakdown
These five areas show where the dataset supports — or may limit — practical reuse.
- Stewardship
- 4
- Harmonization
- 4
- Access
- 16
- Reuse readiness
- 8
- Engagement
- 0