Software development frequently builds on existing code. Businesses use libraries, customize applications, integrate third-party tools, and hire developers to create new features. Those decisions can raise important questions: Does the new software incorporate someone else’s protected work? Who owns the modifications? What does the applicable license require?
Understanding derivative works helps businesses protect their own software while avoiding infringement and licensing problems.
What Does Copyright Protect in Software?
Copyright protects original expression in software, including copyrightable program code. It does not give the owner exclusive rights to every idea or function implemented by the program.
Under 17 U.S.C. § 102(b), copyright does not protect ideas, procedures, processes, systems, or methods of operation. The Copyright Office similarly explains that software copyright does not protect functional aspects such as algorithms, functions, logic, or system design. 17 U.S.C. § 102; Copyright Office Circular 61, p. 1
For example, copyright protection for a scheduling application does not, by itself, prevent another developer from independently creating an application that schedules appointments. Copying protected code or other original expression presents a different issue.
Copyright infringement also does not require malicious intent. A business can face a claim even if its developers did not intend to violate someone else’s rights. 17 U.S.C. § 501(a)
What Is a Derivative Work in Software?
A derivative work recasts, transforms, or adapts a preexisting work. In software, examples may include a modified version of an existing program, a translation of protected code into another programming language, or a customized application that incorporates and adapts existing code.
The copyright owner generally controls the right to prepare derivative works, subject to applicable legal exceptions. 17 U.S.C. §§ 101, 106(2)
The analysis involves more than counting copied lines. It requires identifying what was taken or adapted and whether that material is protected expression. Similar functionality, shared ideas, or common technical requirements do not establish infringement by themselves.
There is also a distinction between modifying software and creating new material that qualifies for its own copyright protection. Minor or purely functional changes may not supply sufficient original authorship. Copyright Office Circular 61, p. 4
Do Libraries, Plug-Ins, and Integrations Create Derivative Works?
There is no reliable blanket rule that linking to a library or using a plug-in always creates, or never creates, a derivative work.
A review should consider:
- Whether protected code or other expression was copied or adapted.
- How the components communicate and operate together.
- Whether the components remain separate or form a combined program.
- The applicable license, including any linking exception.
- Whether the software is distributed, provided to customers, or used through a hosted service.
Technical labels such as “plug-in,” “API,” or “dynamic linking” do not answer every legal question.
Copyright law and license terms also require separate attention. For example, GPL version 3 distinguishes a covered combined work from an aggregate of separate, independent works. That distinction matters when assessing the license’s reach. GPLv3, §§ 1, 5
Who Owns the Modified Software?
Creating modifications does not transfer ownership of the underlying software.
Under 17 U.S.C. § 103(b), copyright in a derivative work extends to the author’s original contributions, rather than the preexisting material. Protection also does not extend to portions in which copyrighted material was used unlawfully. 17 U.S.C. § 103(a)–(b)
A developer may therefore own original additions while still needing permission to use or distribute the underlying program.
Businesses should also avoid assuming that paying a developer automatically transfers copyright. Initial ownership, work-made-for-hire rules, and assignments must be evaluated. Copyright ownership transfers generally require a signed writing, except for transfers by operation of law. 17 U.S.C. §§ 201(a)–(b), 204(a)
As a practical matter, a software development agreement should address ownership of new code, rights to preexisting tools, permitted third-party components, and the licenses needed to use and maintain the finished product.
Can Permission to Create Derivative Works Be Revoked?
That depends on the license and applicable law. A copyright owner should not assume that permission can be withdrawn at any time. A licensee should not assume that an existing modified version can always be used after termination.
Section 203 contains a specific statutory termination framework for certain author-granted rights. Within that framework, a derivative work prepared under an authorized grant before termination may continue to be used under the grant’s terms, but the exception does not authorize creating further derivative works after termination.
That limited rule should not be treated as a universal rule governing cancellation, expiration, or breach of every software license. 17 U.S.C. § 203(a), (b)(1)
Software agreements should expressly address termination, continuing use, existing customer rights, and treatment of modifications.
Does Open-Source Software Require Releasing Your Source Code?
Not necessarily. Open-source licenses impose different conditions, and obligations often depend on how the software is used.
MIT License. This permissive license allows broad use, modification, and distribution, subject to retaining the required copyright and permission notices. It does not impose a general requirement to release proprietary source code. MIT License
GNU GPL version 3. Private modifications generally do not require public release. Conveying covered software to others can trigger licensing, notice, and corresponding-source obligations. Mere network interaction without transferring a copy is not conveying under GPLv3. GPLv3, §§ 0, 2, 4–6
GNU AGPL version 3. If you modify the program and the modified version supports remote network interaction, Section 13 requires an opportunity for those remote users to obtain the corresponding source. This distinction can matter for hosted software. AGPLv3, § 13
Open Software License 3.0. Its external-deployment provision treats specified uses outside the licensee, including certain network uses, as distribution for purposes of the license. OSL 3.0, §§ 1(c), 3, 5
The obligation may be to provide source to specified recipients or users, rather than publish the company’s entire codebase to the world. Review the exact license, version, exceptions, and deployment model before making that determination.
Are There Exceptions for Fair Use or Necessary Adaptations?
Yes, but they are limited and fact-specific.
Section 107 establishes the fair-use framework. Section 117 permits certain copies or adaptations by the owner of a copy of a computer program, including adaptations essential to using the program with a machine, subject to statutory conditions.
Neither provision gives every software customer unrestricted permission to modify, distribute, or commercialize another party’s program. Whether someone owns a copy, rather than merely licenses it, can also matter. 17 U.S.C. §§ 107, 117(a)–(b)
Practical Steps to Protect Your Software Business
We recommend addressing these issues before a product launch, major customer agreement, financing, or sale:
- Document ownership. Review employee and contractor agreements, assignments, and rights to preexisting code.
- Maintain a component inventory. Identify third-party software, versions, licenses, and modifications.
- Review how the product is delivered. Internal use, customer downloads, embedded software, and hosted services can raise different obligations.
- Address modifications in contracts. Specify who may create, use, distribute, sublicense, and maintain customized versions.
- Consider copyright registration early. Registration timing can affect eligibility for statutory damages and attorney’s fees. 17 U.S.C. § 412
- Plan registration deposits carefully. The Copyright Office offers specific deposit options for software containing trade secrets, but those requirements must be followed. Circular 61, pp. 3–4
Legal Guidance for Software Owners and Developers
Brown & Blaier, PC helps businesses address software ownership, intellectual property, and technology agreements. If your company is developing software, licensing a product, or reviewing third-party code obligations, contact our firm to discuss your project.
This article provides general information about U.S. law and does not constitute legal advice. Software copyright and licensing questions depend on the code, agreements, and activities involved.
Updated October 30, 2026