Software licensing and open source sit at the foundation of modern technology, quietly shaping how software is built, shared, monetized, and scaled across the digital economy. From proprietary enterprise platforms to collaborative open-source projects powering the internet, licensing terms define who can use code, modify it, distribute it, and profit from it. This section of Legal Streets explores how Technology, Media & Innovation Law governs software ownership, usage rights, compliance obligations, and risk management in an increasingly code-driven world. You’ll gain insight into the legal differences between commercial licenses and open-source models, the responsibilities developers and businesses face when integrating third-party code, and the consequences of noncompliance. As innovation accelerates and software becomes embedded in nearly every industry, understanding licensing frameworks becomes essential for protecting intellectual property while encouraging collaboration. Whether you’re a developer, startup founder, legal professional, or technology decision-maker, these articles provide clarity on the legal structures that support innovation, reduce risk, and keep modern software ecosystems running smoothly.
A: Yes—if you follow the license terms (notices, attribution, and any source-sharing obligations).
A: MIT is permissive (few obligations); GPL is copyleft and can require sharing source when distributing covered works.
A: It can—AGPL may require offering source to users who interact with the software over a network.
A: Often less likely than linking code, but it’s fact-specific—architecture and integration method matter.
A: Not always—typically only the covered work and corresponding source, but scope depends on how components combine.
A: It’s a place to collect required attributions; some licenses (and many company policies) use it for compliance.
A: Scan dependencies, track versions, generate SBOMs, and gate releases on compliance.
A: Usually no—most licenses require keeping notices and attribution intact.
A: Generally no—code may be licensed, but names/logos are often separately protected.
A: Before shipping copyleft code, doing SaaS with AGPL components, or signing enterprise OSS audit obligations.
