Automated software license analysis

Tuunanen, Timo; Koskinen, Jussi; Kärkkäinen, Tommi

doi:10.1007/s10515-009-0054-z

Cited by 55 publications

(26 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [21] Tuunanen et al compared OSLC, FOSSology and their own implementation, called ASLA (based on the regular expression method). Their evaluation consisted in an empirical study that used 12 FOSS applications.…”

Section: Related Workmentioning

confidence: 99%

A sentence-matching method for automatic license identification of source code files

Germán

Manabe

Inoue

2010

Proceedings of the IEEE/ACM International Conference on Automated Software Engineering

View full text Add to dashboard Cite

The reuse of free and open source software (FOSS) components is becoming more prevalent. One of the major challenges in finding the right component is finding one that has a license that is adequate for its intended use. The license of a FOSS component is determined by the licenses of its source code files. In this paper, we describe the challenges of identifying the license under which source code is made available, and propose a sentence-based matching algorithm to automatically do it. We demonstrate the feasibility of our approach by implementing a tool named Ninka.We performed an evaluation that shows that Ninka outperforms other methods of license identification in precision and speed. We also performed an empirical study on 0.8 million source code files of Debian that highlight interesting facts about the manner in which licenses are used by FOSS.

show abstract

Section: Related Workmentioning

confidence: 99%

A sentence-matching method for automatic license identification of source code files

Germán

Manabe

Inoue

2010

Proceedings of the IEEE/ACM International Conference on Automated Software Engineering

View full text Add to dashboard Cite

show abstract

“…Some approaches for software license identification have been proposed [3,6,8]. Vendome et al investigated the reasons on when and why developers adopt and change licenses by conducting a survey with the relevant developers [10].…”

Section: Introductionmentioning

confidence: 99%

How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects

Manabe

Germán

et al. 2017

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract.A license inconsistency is the presence of two or more source files that evolved from the same original file containing different licenses. In our previous study, we have shown that license inconsistencies do exist in open source projects and may lead to potential license violation problems. In this study, we try to find out whether the issues of license inconsistencies are properly solved by analyzing two versions of a FOSS distribution-Debian-and investigate the evolution patterns of license inconsistencies. Findings are: license inconsistencies occur mostly because the original copyright owner updated the license while the reusers were still using the old version of the source files with the old license; most license inconsistencies would disappear when the reusers synchronize their project from the upstream, while some would exist permanently if reusers decide not to synchronize anymore. Legally suspicious cases have not been found yet in those Debian distributions.

show abstract

“…With the rise of free/libre/open source software (FLOSS) and FLOSS components utilized in software projects the importance of legality concerns has risen. The focus in research has mainly been to license analysis on the software level to either identify the licenses [8] or to check the code against license compatibilities [5,12]. These methods do not support license awareness at the time of development but focus at final source code instead.…”

Section: Introductionmentioning

confidence: 99%

Open Source, Open Innovation and Intellectual Property Rights – A Lightning Talk

Kilamo

Hammouda

Kairamo³

et al. 2012

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract. Open innovation projects are fast paced aiming at producing a quick proof of concept of an innovative software product. This need for speedy results makes the use of open source components as a basis for the work appealing. Open source brings with it an inherent risk of license conflicts that may become an issue when aiming to develope an innovative demo into an actual product. In this study, the first results of investigating the knowledge the participants of innovation projects have on intellectual property are presented. The effect this may have on the project results is also discussed.

show abstract

Automated software license analysis

Cited by 55 publications

References 25 publications

A sentence-matching method for automatic license identification of source code files

A sentence-matching method for automatic license identification of source code files

How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects

Open Source, Open Innovation and Intellectual Property Rights – A Lightning Talk

Contact Info

Product

Resources

About