Picture a planning meeting where someone says, “It’s open source, so we can just use it.” Everyone nods. Before putting it into a product, there are three things to check: what grants the rights, what obligations accompany them, and who will keep the software working.
A public repository is not a permission slip
For software under copyright, the license grants the rights. A repository with no license file usually leaves those rights reserved to the author, even if anyone can read the code. GitHub’s terms allow viewing and forking public repositories; that is not a general permission to use, modify, and redistribute their contents.1
Public-domain code is a different case: it is not subject to copyright, although the meaning and availability of public-domain status vary by jurisdiction.2 An absent license does not establish that status.
Read the terms for software you plan to use or distribute, including the dependencies beneath it. MIT requires preserving copyright and permission notices. Apache 2.0 adds its own redistribution requirements and a patent grant. GPL and AGPL impose different source-sharing obligations, as chapter 2 described.34 Those are conditions of the permission you received.
Courts have taken them seriously. In Jacobsen v. Katzer in 2008, the Federal Circuit treated the conditions of the Artistic License as limits on permission, so acting outside them could be copyright infringement. The ruling depended on that license and those facts; chapter 16 returns to the case.5
SPDX identifiers, such as MIT and Apache-2.0, help identify licenses consistently. A software bill of materials inventories components so you can find the licenses and vulnerabilities that apply.6 Neither replaces reading the relevant terms.
A license is not a maintenance contract
I’ve shipped open-source libraries and left them alone for twelve or thirteen years. A small library that does one job doesn’t always need a roadmap. It does need someone to decide what happens when a user finds a serious bug.
An open-source license tells you what you may do with a project. It does not promise active reviewers, regular releases, a security-reporting process, or a maintainer available next weekend. A proprietary license makes none of those guarantees by itself either. Support commitments have to come from somewhere else.
Look at a dependency the way you’d look at a vendor. Who maintains it? When was the last release? What happens after someone files an issue or security report? Can your team carry a patch if the maintainer cannot? If the answers are quiet, plan for that.
Commercial use still has costs
The right to use software commercially does not supply the staff to integrate, operate, or secure it. Those costs remain even when there is no license fee. Chapter 6 examines who pays for the shared work.
Using open-source software requires no political affiliation. People and organizations with sharply different beliefs can use the same program under the same license. They can still disagree about ownership, corporate influence, and what freedoms the terms should protect. Those disagreements are part of this book.
The next question is what inspection buys you. Chapter 5 looks at the relationship between visible code, security, and trust.
Notes
GitHub, “No License,” Choose a License, https://choosealicense.com/no-permission/. A work “is under exclusive copyright by default,” and software without a license generally means “you have no permission from the creators of the software to use, modify, or share the software,” although GitHub’s terms of service let others view and fork a public repository. ↩
Open Source Initiative, “Frequently Answered Questions,” section “What about software in the public domain? Is that Open Source?,” https://opensource.org/faq. OSI distinguishes public-domain status from a license and explains the jurisdictional limits. ↩
Open Source Initiative, “The MIT License,” https://opensource.org/license/mit: “The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.” ↩
Apache Software Foundation, “Apache License, Version 2.0,” https://www.apache.org/licenses/LICENSE-2.0, section 3 (grant of patent license) and section 4 (redistribution and notice conditions). ↩
Jacobsen v. Katzer, 535 F.3d 1373 (Fed. Cir. 2008), decided 13 August 2008, https://www.cafc.uscourts.gov/opinions-orders/08-1001.pdf. The court held that “the terms of the Artistic License are enforceable copyright conditions” and vacated and remanded the denial of a preliminary injunction. ↩
SPDX, “The System Package Data Exchange (SPDX),” Linux Foundation Projects, https://spdx.dev/, describing SPDX as an open standard for software bills of materials (ISO/IEC 5962:2021); SPDX License List, https://www.spdx.org/licenses. ↩
From But Is It Open? by Timothy O’Brien (Discursive, 2026). © 2026 Timothy O’Brien. All rights reserved.