- with readers working within the Retail & Leisure industries
- within Consumer Protection and Real Estate and Construction topic(s)
A California court recently issued two important rulings in a lawsuit between a nonprofit organization and TV manufacturer Vizio over open source software. These decisions may affect how companies manage open source software compliance obligations and whether everyday consumers have standing to sue to enforce those obligations.
What Is This Case About?
Many electronic devices—from smartphones to smart TVs—run on “open source” software. Open source software is free to use, but it comes with conditions. Those conditions vary, but a common requirement of so-called “copyleft” open source licenses is that if you use the software in your product, you must share the underlying code with anyone who asks for it. This allows others to study, modify, and improve the software.
In 2018, a nonprofit called the Software Freedom Conservancy (“SFC”) bought a Vizio smart TV.1 It found the TV contained open source software, including software licensed under a copyleft open source license called the GNU General Public License version 2 (“GPLv2”).2 SFC asked Vizio to share the source code as required, but the nonprofit claims Vizio’s responses were inadequate.3 In 2021, SFC sued.4
What makes this case unusual is that SFC is not suing as the creator of the software. It is suing as a consumer who bought a product. If SFC wins, it could open the door for other consumers to bring similar lawsuits.
The February 2026 Ruling: Can Consumers Sue?
In February 2026, the judge ruled that the case must proceed to trial because factual disputes remain for a jury to resolve.5
SFC is pursuing two main arguments. First, it claims that anyone who buys a product with open source software has the right to demand the source code, even though the consumer didn’t write the software.6 The court found this issue to be unsettled, turning in part on disputed evidence regarding the intent and scope of the license.7
Second, SFC argues that Vizio made a direct promise to provide source code.8 SFC alleges that Vizio’s TVs include a menu offering to provide source code upon request, and that one of SFC’s employees accepted that offer through Vizio’s customer support.9 However, the court found there are factual disputes about when this happened and who made the request.10
The trial is scheduled for August 2026.11 To win, SFC will need to prove that a contract existed, that Vizio breached it, and that SFC was harmed as a result.
Even if SFC establishes a breach of contract, demonstrating actual harm may prove difficult. The nonprofit’s interest is promoting open source principles, not recovering money. This could make traditional damages hard to calculate, though the court could order specific performance (i.e., requiring Vizio to provide the code).
The December 2025 Ruling: What Companies Don’t Have to Do
In a separate ruling from December 2025, the judge sided with Vizio on a narrower question. SFC argued that companies using open source software must not only share the code, but also provide instructions so consumers can modify the software and reinstall it on their devices.12
The judge rejected this argument. The court found that the language of the open source license requires companies to share code so others can use and modify it, but it does not require companies to permit reinstallation of modified code or to ensure devices remain operable after such modifications.13
This matters because many companies use “locked-down” devices. For example, a smart TV might use open source software but prevent consumers from making changes to how the TV operates. The court ruled that this practice may be allowed under the particular open source license at issue here.14
Notably, GPL version 3 (GPLv3) does require companies to provide installation information sufficient to run modified code,15 but that version did not apply to this case. The distinction between the two license versions is becoming increasingly important.
What This Means for Businesses
For companies that make electronic devices, these rulings provide helpful guidance.
- Source code obligations remain a real risk.
GPLv2 raises at least a triable issue as to whether companies must provide corresponding source code upon request.
- No obligation to ensure device functionality after modification (under GPLv2).
Companies are not required to allow users to reinstall modified code or ensure devices function after modification.
- Consumer standing could expand exposure.
If SFC prevails, ordinary consumers, not just copyright holders, may be able to enforce open source obligations.
- Scope of required disclosures may be clarified.
The upcoming trial could provide guidance on what qualifies as “corresponding source code” required to be shared under GPLv2, including the extent to which proprietary code in adjacent or linked software modules must be disclosed.
- Public-facing offers can create liability.
Offers to provide source code (e.g., in menus, documentation, or support interactions) may form independent contractual obligations.
- Compliance processes should be proactive.
Companies should keep track of their open source usage and implement reliable, repeatable processes for distinguishing proprietary code and fulfilling source code requests.
Footnotes
1 Complaint, Software Freedom Conservancy, Inc. v. Vizio, Inc., No. 30-2021-01226723-CU-BC-CJC, at ¶ 55 (Cal. Super. Ct. Orange Cnty. Oct. 19, 2021).
2 Id. at ¶¶ 34, 37, 40-41, 52, 55; the Complaint also alleges similar claims under the GNU Lesser General Public License version 2.1 (“LGPLv2.1”), which are not addressed directly by this article.
3 Id. at ¶¶ 56-64.
4 Id. at ¶ 1.
5 Minute Order, Software Freedom Conservancy, Inc. v. Vizio, Inc., No. 30-2021-01226723-CU-BC-CJC, at 1-5 (Cal. Super. Ct. Orange Cnty. Feb. 17, 2026)
6 Id. at 3.
7 Id. at 4-5.
8 Id. at 2.
9 Id.
10 Id. at 2-3.
11 Software Freedom Conservancy v. Vizio Inc., SOFTWARE FREEDOM CONSERVANCY, https://sfconservancy.org/copyleft-compliance/vizio.html (last visited Apr. 16, 2026).
12 Minute Order, Software Freedom Conservancy, Inc. v. Vizio, Inc., No. 30-2021-01226723-CU-BC-CJC, at 3 (Cal. Super. Ct. Orange Cnty. Dec. 23, 2025) (“December 23 Minute Order”).
13 Id. at 4-5. SFC states that it never advanced the position that the GPLv2 requires ensuring that devices remain functional after user-modification and therefore contends that the December 2025 ruling is “irrelevant.” Judge in Vizio Case Rules on Issue Irrelevant to Rights Under Copyleft, SOFTWARE FREEDOM CONSERVANCY (Dec. 24, 2025), https://sfconservancy.org/news/2025/dec/24/vizio-msa-irrelevant-ruling/.
14 December 23 Minute Order at 5.
15 GNU General Public License Version 3 § 6, GNU (June 29, 2007), https://www.gnu.org/licenses/gpl-3.0.html.
The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.
[View Source]