Creality K2 series GPLv3 violation
Background
The Creality K2 series firmware represents a systemic copyleft compliance dispute involving a derivative work based on Klipper, which is licensed under the GNU General Public License v3 (GPLv3). While the hardware can currently be rooted by users, Creality explicitly omits the uncompiled, human-readable source code for multiple proprietary binary blobs linking directly into the Klipper host environment.
Despite these restrictions, Creality has publicly marketed the K2 series ecosystem as entirely open-source. On December 12, 2025, Creality published an official announcement titled "Creality Open-Source 3D Printer Firmware is Here!" claiming to "empower makers and developers" by linking to their K2 Series Klipper GitHub repository. Community audits quickly revealed the repository was missing critical components necessary to build a fully compliant, functional firmware image from source.
This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:
- K2 SE: V2.3.6.49 (`CR4CU220812S11_ota_img_V2.3.6.49.img`)
- K2: V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`)
- K2 Pro: V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`)
- K2 Plus: V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`)
Incident
Creality distributes pre-compiled shared library objects (`.so`) and object files (`.o`) inside Klipper's core directory structures without providing the corresponding source code. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host:
- `serial_485_wrapper.so` (Manages RS-485 serial communication bus)
- `box_wrapper.so`
- `filament_rack_wrapper.so`
- Compiled `.o` object files tied directly to the Color Format System (CFS) multi-material management library.
Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026, a 14-day compliance deadline was established on May 20, 2026. Because compliance was not met, the violation trail was formally logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) on May 27, 2026. Creality continues to distribute the K2 hardware and locked-down firmware images to retail consumers while remaining in active violation of the GPLv3 license terms.
[Company]'s response
On May 24, 2026, Creality sent a written response stating: "Due to the involvement of custom firmware modules, underlying dependencies, and the need to clarify copyrights from multiple parties, the compilation of relevant materials requires a considerable period of time. Currently, we are unable to directly provide the corresponding source code or updated repository links."
On May 29, 2026, Creality issued a follow-up response confirming that they were attempting to clean up a source package "without affecting commercial proprietary code." This statement serves as an admission that proprietary commercial code was actively linked into a distributed GPLv3 copyleft work.
On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination to standard customer service troubleshooting scripts, closed active communication on the ticket, and forwarded the entire case history to their internal legal department and R&D managers without providing a compliance timeline.
Lawsuit
Consumer response
Users immediately flagged that the initial December 2025 release violated the GPLv3 due to the missing source text for the integrated binary blobs, challenging the company's public framing of the ecosystem as a true open-source milestone.
References
- ↑ ref goes here