Developers' Perspectives on Software Licensing: Current Practices, Challenges, and Tools
Nathan Wintersgill, Trevor Stalnaker, Daniel Otten, Laura A. Heymann, Oscar Chaparro, Massimiliano Di Penta, Daniel M. German, Denys Poshyvanyk
TL;DR
The paper investigates how software developers approach OSS license compliance, addressing a gap where licensing tasks are known to be challenging yet poorly understood in practice. Through a mixed-method study of 58 developers and seven interviews, it maps task frequency, difficulty, decision factors, roles, problem-resolution processes, and tool usage. Key contributions include a nuanced view of where licensing tasks are hardest (notably verification), how decisions are influenced by legal and organizational factors, and the current limitations and desired enhancements of licensing tools and workflows, including integration into existing platforms and cautious consideration of AI assistance. The findings offer practical recommendations for tool designers and future research on developer–legal collaboration to improve license compliance in real-world software projects.
Abstract
Most modern software products incorporate open-source components, requiring development teams to maintain compliance with each component's licenses. Noncompliance can lead to significant financial, legal, and reputational repercussions. While some organizations may seek advice from legal practitioners to assist with licensing tasks, developers still play a key role in such a process. To this end, it is essential to understand how developers approach license compliance tasks, the challenges they encounter, and the tools that they use. This work studies these aspects of software licensing practices through a study - conducted by a joint team of software engineering and legal researchers - consisting of a survey with 58 software developers and seven follow-up interviews. The study resulted in 15 key findings regarding the current state of practice. We discuss the implications of our findings and offer directions for future research as well as actionable recommendations for licensing tools.