What Is Open Source Software, and How Do Licenses Work?
What makes software open source under the OSI definition, how permissive licenses like MIT differ from copyleft like GPL and AGPL, and well-known examples.
Short answer
Open source software is software whose source code is published under a license that lets anyone use, study, change and redistribute it, as set out in the Open Source Initiative's 10-point Open Source Definition. Licenses fall into two broad groups: permissive ones like MIT and Apache-2.0, and copyleft ones like GPL-3.0 and AGPL-3.0 that require shared changes to stay open.
Key takeaways
- Publishing source code is not enough; the license must grant the freedoms in the OSI's Open Source Definition, including free redistribution and no discrimination against users or fields of use.
- Permissive licenses (MIT, Apache-2.0) let others reuse code in closed products; copyleft licenses (GPL, AGPL) require derivative works to be shared under the same terms.
- Open source does not automatically mean free of cost, more secure or community-run, though it makes independent review possible.
Open source code runs most of the internet, every Android phone and a large share of the apps on your laptop. The term has a precise meaning, though, and the license attached to a project decides what you can do with it. This post covers the official definition, the main license families and how to read them.
What makes software open source?
Software is open source when its license meets the Open Source Initiative's Open Source Definition, which has 10 criteria covering redistribution, source access and fair treatment of users.
The Open Source Initiative (OSI) maintains the definition and reviews licenses against it. Its 10 criteria are:
- Free redistribution
- Source code must be available
- Derived works must be allowed
- Integrity of the author's source code
- No discrimination against persons or groups
- No discrimination against fields of endeavor
- Distribution of license (rights apply to everyone who receives the program)
- License must not be specific to a product
- License must not restrict other software
- License must be technology-neutral
A project that posts its code on GitHub with no license, or with terms like "non-commercial use only," is not open source under this definition. Without a license, copyright law reserves all rights to the author by default.
What is the difference between permissive and copyleft licenses?
Permissive licenses let anyone reuse the code, including in closed-source products, while copyleft licenses require modified versions to be released under the same license.
| License | Type | Main obligation | Notable detail |
|---|---|---|---|
| MIT | Permissive | Keep the copyright and license notice | Very short; widely used for libraries |
| Apache-2.0 | Permissive | Keep notices, state significant changes | Includes an explicit patent grant |
| GPL-3.0 | Strong copyleft | Share source of distributed derivative works under GPL | Adds anti-tivoization and patent terms |
| AGPL-3.0 | Network copyleft | Same as GPL, plus share source with users of a network service | Closes the "run it as a web service" gap |
Permissive licenses are popular for libraries and frameworks because companies can adopt them with minimal paperwork. Copyleft licenses keep improvements in the commons: if you ship a modified GPL program to others, you must provide your source changes too.
The AGPL exists because the regular GPL's obligations are triggered by distribution. A company can modify GPL software and run it on its own servers without distributing anything. The AGPL extends the obligation to users who interact with the software over a network.
There are also "weak copyleft" licenses, such as the Mozilla Public License 2.0 and the LGPL, which apply copyleft to the licensed files or library but allow linking from proprietary code.
What are some well-known open source projects?
Much everyday software is open source or built on it, from operating systems to browsers and media players.
- The Linux kernel, licensed under GPL-2.0, which also sits under Android and many web servers.
- Firefox and LibreOffice, both under the Mozilla Public License 2.0.
- VLC media player, built on GPL and LGPL code.
- Kubernetes, under Apache-2.0.
- React, under MIT.
- The Android Open Source Project, mostly under Apache-2.0.
Many commercial products combine open source parts with proprietary ones. Google Chrome, for instance, is built on the open source Chromium project but adds closed components. Open source apps need patching like any other software, and most update through the same channels covered in our guide on how to keep your devices updated.
Does open source mean free and safe?
Open source licenses guarantee freedoms over the code, not a zero price or automatic security.
Companies can charge for open source software, sell support, or offer paid hosted versions. The license only guarantees that the source and the rights travel with it.
Security works similarly. Public code makes independent audits possible, and serious flaws in popular projects are often found and fixed quickly. But small projects maintained by one volunteer can go unreviewed for years, and attackers have targeted open source package repositories with malicious lookalike packages. The practical test is the same as for any software: is it actively maintained, does it publish security fixes, and do you install it from the official source? The same thinking applies to browser extensions, many of which are open source and some of which are not trustworthy.
How do you check a project's license?
Look for a LICENSE file in the source repository and an SPDX identifier, then compare it with the OSI's list of approved licenses.
Most projects include a file named LICENSE or COPYING in the top folder, and many state an SPDX short identifier such as MIT, Apache-2.0 or GPL-3.0-or-later in their package metadata. The SPDX License List gives each license a standard ID, and the OSI publishes which licenses it has approved. If you plan to bundle open source code in a product you sell, read the full license text and keep a record of the licenses you use, because attribution notices are a requirement under nearly all of them. For personal use, such as installing a Linux distribution or using open source apps, you can simply use the software; the obligations apply when you redistribute it.
Frequently asked questions
Is open source the same as free software?
They overlap almost completely in practice. 'Free software' is the Free Software Foundation's term and stresses user freedom, while 'open source' is the OSI's term and stresses the development model; most licenses are approved by both.
Is 'source available' software open source?
No. Some projects publish code but restrict commercial use or competing services, which breaks the OSI criteria against discriminating by field of endeavor. Those licenses are called source available.
Can I sell software that uses open source code?
Usually yes. Permissive licenses allow it with attribution, and even the GPL allows selling copies, provided you pass on the source code and the same license to recipients.
Is open source software safer?
Open code can be audited by anyone, which helps, but it only matters if people actually review it and maintainers ship fixes. A well-maintained project is safer than an abandoned one regardless of license.
Sources
- The Open Source Definition (Open Source Initiative)
- OSI Approved Licenses (Open Source Initiative)
- What is Free Software? (GNU Project)
- SPDX License List
Research-based: Technorat does not claim hands-on testing. See how we research. Spotted an error? contact@technorat.com