Consumer Rights Wiki - User contributions [en]

Creality K2 series GPLv3 violation

2026-06-01T07:35:58Z

181.215.169.214: metadata edit

{{IncidentCargo
|Company=Creality
|StartDate=2025-12-12
|Status=Active
|ProductLine=K2 Series 3D Printers
|Product=Creality K2 SE, K2, K2 Pro, K2 Plus}}

The Creality K2 series 3D printer firmware (encompassing the K2, K2 SE, K2 Pro, and K2 Plus) contains a systemic violation of the GNU General Public License v3 (GPLv3) due to the inclusion of proprietary binary blobs compiled directly into the open-source Klipper host environment. Despite marketing the flagship hardware lineup as a fully open-source ecosystem, Creality has formally refused to share the corresponding source code for multiple critical communication modules, instead utilizing Cython to compile proprietary control logic into CPython shared object files. The ongoing non-compliance has been formally escalated to the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) following a series of admissions by the company's support team.

==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). In December 2025, Creality launched their official GitHub repository for the K2 Series, publicly promoting the flagship line as a fully open-source hardware and software ecosystem <ref name="creality_forum_launch" />. However, community developers quickly discovered that the released codebase was severely outdated, out of sync with active printer configurations, and conspicuously lacked the corresponding source code for critical operational modules <ref name="creality_forum_launch" />.

While Cython is occasionally used for performance optimization, its primary utility in this context was to obfuscate the implementation logic of the printer’s primary hardware integrations <ref name="creality_forum_tracker" />. By placing these binary wrappers directly inside Klipper’s process directory, Creality forced the GPLv3-licensed Klipper host process to dynamically link to and execute opaque binaries at runtime, creating a copyleft compliance conflict <ref name="creality_forum_tracker" />.

This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:
*'''K2 SE:''' V2.3.6.49 and V2.3.6.66 (`CR4CU220812S11_ota_img_V2.3.6.49.img`) <ref name="email_demand" />
*'''K2:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) <ref name="email_demand" />
*'''K2 Pro:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) <ref name="email_demand" />
*'''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`) <ref name="email_demand" />

==Incident==
Creality distributes Cython-compiled shared library objects (`.so`) inside Klipper's core process directory structures (`/usr/share/klipper/klippy/extras/`) without providing the corresponding source code <ref name="creality_forum_tracker" />. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host:
*`serial_485_wrapper.cpython-39.so` (Manages the custom RS-485 serial communication protocol linking the mainboard to the CFS feeder) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`box_wrapper.cpython-39.so` (Handles logical state routing, filament changes, and multi-material commands) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`filament_rack_wrapper.cpython-39.so` (Controls physical spool selection, drive gears, and filament runout sensors inside the CFS) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`motor_control_wrapper.cpython-39.so` (Governs specialized stepper motor accelerations and hardware-level load balancing) <ref name="creality_forum_tracker" />
*`prtouch_v2_wrapper.cpython-39.so` (Governs strain-gauge-based automatic bed leveling and nozzle probing) <ref name="creality_forum_tracker" />
*`prtouch_v3_wrapper.cpython-39.so` (Handles advanced real-time Z-axis compensation algorithms) <ref name="creality_forum_tracker" />

Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026 <ref name="email_demand" />, a 14-day compliance deadline was established on May 20, 2026 <ref name="email_demand" />. Because compliance was not met, a formal license complaint was logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) on May 28, 2026 <ref name="email_demand" />. 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.

===Creality's Response & Admissions===
Throughout May 2026, the community documented a highly structured deflection loop used by Creality's front-line support staff to handle GPL inquiries, frequently issuing direct denials or stalling templates <ref name="creality_forum_tracker" />.

On May 15, 2026, Creality Customer Service formally acknowledged the initial source code application, stating: *"We have officially forwarded your application for the complete GPLv3 source code for all firmware versions of the K2 series to our R&D team for processing. ... Please stay tuned for further announcements on our official website."* <ref name="email_demand" />

On May 20, 2026, investigator Alex Mercer rejected the indefinite "stay tuned" timeline, establishing a strict 14-day compliance deadline under threat of escalation to the FSF and SFC <ref name="email_demand" />.

On May 24, 2026, Creality sent a written response detailing their inability to provide immediate source code matching the distributed binaries:
<blockquote>"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." <ref name="email_demand" /></blockquote>

On May 29, 2026, Creality issued a follow-up response confirming that *"cleaning up a fully compliant source code package without affecting commercial proprietary code does require an internal process that, for now, does not have a publicly available timeline."* <ref name="email_demand" /> Open-source legal experts note that this statement serves as an explicit corporate admission that proprietary commercial code was actively compiled and dynamically linked into a distributed GPLv3 copyleft work—an architectural contamination directly forbidden under the license guidelines.

On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination, 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 <ref name="email_demand" />.

==Consumer Response & Hardware Bypass==
The release of the K2 series firmware triggered significant backlash across Klipper Discourse, Creality Forums, and Reddit <ref name="creality_forum_launch" />. The community strongly criticized Creality for "malicious compliance"—promoting a printer as open-source while lockboxing its core features behind closed binaries <ref name="creality_forum_tracker" /> <ref name="reddit_k2" />.

These licensing omissions created severe, practical issues for consumers, blocking hardware repair, preventing the use of third-party toolheads, and restricting underlying Linux access <ref name="creality_forum_tracker" /> <ref name="klipper_discourse_k2" />. This backlash was compounded by the fact that Creality had previously repeated the exact same violation when launching the K1 series, only releasing the `prtouch` source code months later after intense public pressure <ref name="k1_github_issue" />. The restriction of root access on subsequent iterations like the K1C 2025 further intensified user distrust <ref name="creality_k1c_forum" />.

Kevin O'Connor, the original creator of Klipper, publicly reiterated: *"Klipper is licensed under the GNU GPLv3. Any redistribution of that code is required to follow the license. I have not dual-licensed the code nor provided any exceptions."* <ref name="klipper_discourse_violation" />

Frustrated by these restrictions, independent developers launched the `fake-name/cfs-reverse-engineering` project to manually map the Co-extrusion Filament System (CFS) feeder bus <ref name="cfs_github" />. Developers discovered that the CFS's GigaDevice GD32F303VET6 microcontroller was binary-compatible with the STM32F106VET6 <ref name="cfs_github" />. By designing a custom hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, developers successfully bypassed Creality's closed-source serial protocol, converting the CFS communication layer into an open CAN bus running standard *candleLight_fw* and native upstream Klipper <ref name="cfs_github" />.

==Industry Context & Legal Precedents==
Creality's ongoing non-compliance occurs amidst a broader industry crackdown on open-source license violations. Creality has a documented history of violations, previously being blacklisted on TH3D Studio LLC's 3D Printer GPL Violation List for withholding source code for Marlin-based printers and the Klipper-based Sonic Pad <ref name="klipper_discourse_violation" />.

Furthermore, on May 18, 2026, the Software Freedom Conservancy (SFC) launched a major compliance initiative against Bambu Lab over violations of the GNU Affero General Public License v3 (AGPLv3) <ref name="sfc_bambu" /> <ref name="toms_hardware_bambu" />. When Bambu Lab attempted to keep their networking library (`libbambu_networking.so`) proprietary and issued a cease-and-desist to an independent developer, the SFC launched Project "baltobu" to reverse-engineer the closed-source libraries and host a fully independent fork of the slicer <ref name="sfc_bambu" /> <ref name="reddit_sfc" />. This underscores a shifting industry landscape where enforcement bodies are taking direct legal and technical action against companies isolating commercial IP within copyleft frameworks.

==References==
<references>
<ref name="creality_forum_launch">[https://forum.creality.com/t/creality-open-source-3d-printer-firmware-is-here/47218 "Creality Open-Source 3D Printer Firmware is Here!"], Official Creality Forum.</ref>
<ref name="creality_forum_tracker">[https://forum.creality.com/t/where-are-the-required-to-be-released-sources-for-crealitys-modifications-to-klipper-the-k2/30019 "Where are the (required to be released) sources for Creality's modifications to Klipper the K2"], Creality Forum Tracker.</ref>
<ref name="email_demand">[https://archive.org/details/creality-k-2-gplv-3-compliance-demand-may-2026 "Creality K2 GPLv3 Compliance Demand Correspondence Logs (May 2026)"], Hosted on the Internet Archive.</ref>
<ref name="reddit_k2">[https://www.reddit.com/r/Creality/comments/1hcer2j/k2_plus_firmware_source_code/ "K2 Plus Firmware Source Code"], r/Creality Community Discussion.</ref>
<ref name="klipper_discourse_k2">[https://klipper.discourse.group/t/creality-k2-plus-and-gpl-violations/22402 "Creality K2 Plus and GPL violations"], Klipper Discourse Group.</ref>
<ref name="k1_github_issue">[https://github.com/CrealityOfficial/K1_Series_Klipper/issues/9 "This repository contains binary-only extensions, violating the Klipper GPLv3 license"], K1 Series GitHub Issue #9.</ref>
<ref name="creality_k1c_forum">[https://forum.creality.com/t/k1c-2025-orcaslicer-workarounds-for-missing-web-interface/47164 "K1C 2025 + OrcaSlicer: Workarounds for Missing Web Interface"], Creality Community Forum.</ref>
<ref name="klipper_discourse_violation">[https://klipper.discourse.group/t/creality-violating-klipper-license/8990 "Creality Violating Klipper License"], Klipper Discourse Group.</ref>
<ref name="cfs_github">[https://github.com/fake-name/cfs-reverse-engineering fake-name/cfs-reverse-engineering], GitHub Repository.</ref>
<ref name="sfc_bambu">[https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ "Comprehensive Response to Bambu's AGPLv3 Violations"], Software Freedom Conservancy.</ref>
<ref name="toms_hardware_bambu">[https://www.tomshardware.com/3d-printing/open-source-non-profit-claims-bambu-lab-violated-license-move-follows-cease-and-desist-demand-on-orcaslicer-fork-that-restored-cloud-printing-features-without-using-bambu-connect "Open-source non-profit claims Bambu Lab violated license"], Tom's Hardware.</ref>
<ref name="reddit_sfc">[https://www.reddit.com/r/BambuLab/comments/1tjku6z/the_software_freedom_conservancy_sfc_just/ "The Software Freedom Conservancy (SFC) launched a counter-offensive against Bambu Lab over AGPL violations"], r/BambuLab - Reddit.</ref>
</references>

Creality K2 series GPLv3 violation

2026-06-01T07:33:45Z

181.215.169.214: editorial change

{{IncidentCargo
|Company=Creality
|StartDate=2025-12-12
|Status=Active
|ProductLine=K2 Series 3D Printers
}}The Creality K2 series 3D printer firmware (encompassing the K2, K2 SE, K2 Pro, and K2 Plus) contains a systemic violation of the GNU General Public License v3 (GPLv3) due to the inclusion of proprietary binary blobs compiled directly into the open-source Klipper host environment. Despite marketing the flagship hardware lineup as a fully open-source ecosystem, Creality has formally refused to share the corresponding source code for multiple critical communication modules, instead utilizing Cython to compile proprietary control logic into CPython shared object files. The ongoing non-compliance has been formally escalated to the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) following a series of admissions by the company's support team.

==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). In December 2025, Creality launched their official GitHub repository for the K2 Series, publicly promoting the flagship line as a fully open-source hardware and software ecosystem <ref name="creality_forum_launch" />. However, community developers quickly discovered that the released codebase was severely outdated, out of sync with active printer configurations, and conspicuously lacked the corresponding source code for critical operational modules <ref name="creality_forum_launch" />.

While Cython is occasionally used for performance optimization, its primary utility in this context was to obfuscate the implementation logic of the printer’s primary hardware integrations <ref name="creality_forum_tracker" />. By placing these binary wrappers directly inside Klipper’s process directory, Creality forced the GPLv3-licensed Klipper host process to dynamically link to and execute opaque binaries at runtime, creating a copyleft compliance conflict <ref name="creality_forum_tracker" />.

This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:
*'''K2 SE:''' V2.3.6.49 and V2.3.6.66 (`CR4CU220812S11_ota_img_V2.3.6.49.img`) <ref name="email_demand" />
*'''K2:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) <ref name="email_demand" />
*'''K2 Pro:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) <ref name="email_demand" />
*'''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`) <ref name="email_demand" />

==Incident==
Creality distributes Cython-compiled shared library objects (`.so`) inside Klipper's core process directory structures (`/usr/share/klipper/klippy/extras/`) without providing the corresponding source code <ref name="creality_forum_tracker" />. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host:
*`serial_485_wrapper.cpython-39.so` (Manages the custom RS-485 serial communication protocol linking the mainboard to the CFS feeder) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`box_wrapper.cpython-39.so` (Handles logical state routing, filament changes, and multi-material commands) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`filament_rack_wrapper.cpython-39.so` (Controls physical spool selection, drive gears, and filament runout sensors inside the CFS) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`motor_control_wrapper.cpython-39.so` (Governs specialized stepper motor accelerations and hardware-level load balancing) <ref name="creality_forum_tracker" />
*`prtouch_v2_wrapper.cpython-39.so` (Governs strain-gauge-based automatic bed leveling and nozzle probing) <ref name="creality_forum_tracker" />
*`prtouch_v3_wrapper.cpython-39.so` (Handles advanced real-time Z-axis compensation algorithms) <ref name="creality_forum_tracker" />

Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026 <ref name="email_demand" />, a 14-day compliance deadline was established on May 20, 2026 <ref name="email_demand" />. Because compliance was not met, a formal license complaint was logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) on May 28, 2026 <ref name="email_demand" />. 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.

===Creality's Response & Admissions===
Throughout May 2026, the community documented a highly structured deflection loop used by Creality's front-line support staff to handle GPL inquiries, frequently issuing direct denials or stalling templates <ref name="creality_forum_tracker" />.

On May 15, 2026, Creality Customer Service formally acknowledged the initial source code application, stating: *"We have officially forwarded your application for the complete GPLv3 source code for all firmware versions of the K2 series to our R&D team for processing. ... Please stay tuned for further announcements on our official website."* <ref name="email_demand" />

On May 20, 2026, investigator Alex Mercer rejected the indefinite "stay tuned" timeline, establishing a strict 14-day compliance deadline under threat of escalation to the FSF and SFC <ref name="email_demand" />.

On May 24, 2026, Creality sent a written response detailing their inability to provide immediate source code matching the distributed binaries:
<blockquote>"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." <ref name="email_demand" /></blockquote>

On May 29, 2026, Creality issued a follow-up response confirming that *"cleaning up a fully compliant source code package without affecting commercial proprietary code does require an internal process that, for now, does not have a publicly available timeline."* <ref name="email_demand" /> Open-source legal experts note that this statement serves as an explicit corporate admission that proprietary commercial code was actively compiled and dynamically linked into a distributed GPLv3 copyleft work—an architectural contamination directly forbidden under the license guidelines.

On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination, 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 <ref name="email_demand" />.

==Consumer Response & Hardware Bypass==
The release of the K2 series firmware triggered significant backlash across Klipper Discourse, Creality Forums, and Reddit <ref name="creality_forum_launch" />. The community strongly criticized Creality for "malicious compliance"—promoting a printer as open-source while lockboxing its core features behind closed binaries <ref name="creality_forum_tracker" /> <ref name="reddit_k2" />.

These licensing omissions created severe, practical issues for consumers, blocking hardware repair, preventing the use of third-party toolheads, and restricting underlying Linux access <ref name="creality_forum_tracker" /> <ref name="klipper_discourse_k2" />. This backlash was compounded by the fact that Creality had previously repeated the exact same violation when launching the K1 series, only releasing the `prtouch` source code months later after intense public pressure <ref name="k1_github_issue" />. The restriction of root access on subsequent iterations like the K1C 2025 further intensified user distrust <ref name="creality_k1c_forum" />.

Kevin O'Connor, the original creator of Klipper, publicly reiterated: *"Klipper is licensed under the GNU GPLv3. Any redistribution of that code is required to follow the license. I have not dual-licensed the code nor provided any exceptions."* <ref name="klipper_discourse_violation" />

Frustrated by these restrictions, independent developers launched the `fake-name/cfs-reverse-engineering` project to manually map the Co-extrusion Filament System (CFS) feeder bus <ref name="cfs_github" />. Developers discovered that the CFS's GigaDevice GD32F303VET6 microcontroller was binary-compatible with the STM32F106VET6 <ref name="cfs_github" />. By designing a custom hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, developers successfully bypassed Creality's closed-source serial protocol, converting the CFS communication layer into an open CAN bus running standard *candleLight_fw* and native upstream Klipper <ref name="cfs_github" />.

==Industry Context & Legal Precedents==
Creality's ongoing non-compliance occurs amidst a broader industry crackdown on open-source license violations. Creality has a documented history of violations, previously being blacklisted on TH3D Studio LLC's 3D Printer GPL Violation List for withholding source code for Marlin-based printers and the Klipper-based Sonic Pad <ref name="klipper_discourse_violation" />.

Furthermore, on May 18, 2026, the Software Freedom Conservancy (SFC) launched a major compliance initiative against Bambu Lab over violations of the GNU Affero General Public License v3 (AGPLv3) <ref name="sfc_bambu" /> <ref name="toms_hardware_bambu" />. When Bambu Lab attempted to keep their networking library (`libbambu_networking.so`) proprietary and issued a cease-and-desist to an independent developer, the SFC launched Project "baltobu" to reverse-engineer the closed-source libraries and host a fully independent fork of the slicer <ref name="sfc_bambu" /> <ref name="reddit_sfc" />. This underscores a shifting industry landscape where enforcement bodies are taking direct legal and technical action against companies isolating commercial IP within copyleft frameworks.

==References==
<references>
<ref name="creality_forum_launch">[https://forum.creality.com/t/creality-open-source-3d-printer-firmware-is-here/47218 "Creality Open-Source 3D Printer Firmware is Here!"], Official Creality Forum.</ref>
<ref name="creality_forum_tracker">[https://forum.creality.com/t/where-are-the-required-to-be-released-sources-for-crealitys-modifications-to-klipper-the-k2/30019 "Where are the (required to be released) sources for Creality's modifications to Klipper the K2"], Creality Forum Tracker.</ref>
<ref name="email_demand">[https://archive.org/details/creality-k-2-gplv-3-compliance-demand-may-2026 "Creality K2 GPLv3 Compliance Demand Correspondence Logs (May 2026)"], Hosted on the Internet Archive.</ref>
<ref name="reddit_k2">[https://www.reddit.com/r/Creality/comments/1hcer2j/k2_plus_firmware_source_code/ "K2 Plus Firmware Source Code"], r/Creality Community Discussion.</ref>
<ref name="klipper_discourse_k2">[https://klipper.discourse.group/t/creality-k2-plus-and-gpl-violations/22402 "Creality K2 Plus and GPL violations"], Klipper Discourse Group.</ref>
<ref name="k1_github_issue">[https://github.com/CrealityOfficial/K1_Series_Klipper/issues/9 "This repository contains binary-only extensions, violating the Klipper GPLv3 license"], K1 Series GitHub Issue #9.</ref>
<ref name="creality_k1c_forum">[https://forum.creality.com/t/k1c-2025-orcaslicer-workarounds-for-missing-web-interface/47164 "K1C 2025 + OrcaSlicer: Workarounds for Missing Web Interface"], Creality Community Forum.</ref>
<ref name="klipper_discourse_violation">[https://klipper.discourse.group/t/creality-violating-klipper-license/8990 "Creality Violating Klipper License"], Klipper Discourse Group.</ref>
<ref name="cfs_github">[https://github.com/fake-name/cfs-reverse-engineering fake-name/cfs-reverse-engineering], GitHub Repository.</ref>
<ref name="sfc_bambu">[https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ "Comprehensive Response to Bambu's AGPLv3 Violations"], Software Freedom Conservancy.</ref>
<ref name="toms_hardware_bambu">[https://www.tomshardware.com/3d-printing/open-source-non-profit-claims-bambu-lab-violated-license-move-follows-cease-and-desist-demand-on-orcaslicer-fork-that-restored-cloud-printing-features-without-using-bambu-connect "Open-source non-profit claims Bambu Lab violated license"], Tom's Hardware.</ref>
<ref name="reddit_sfc">[https://www.reddit.com/r/BambuLab/comments/1tjku6z/the_software_freedom_conservancy_sfc_just/ "The Software Freedom Conservancy (SFC) launched a counter-offensive against Bambu Lab over AGPL violations"], r/BambuLab - Reddit.</ref>
</references>

Creality K2 series GPLv3 violation

2026-06-01T07:33:03Z

181.215.169.214:

{{IncidentCargo
|Company=Creality
|StartDate=2025-12-12
|Status=Active
|ProductLine=K2 Series 3D Printers
}}The Creality K2 series 3D printer firmware (encompassing the K2, K2 SE, K2 Pro, and K2 Plus) contains a systemic violation of the GNU General Public License v3 (GPLv3) due to the inclusion of proprietary binary blobs compiled directly into the open-source Klipper host environment. Despite marketing the flagship hardware lineup as a fully open-source ecosystem, Creality has formally refused to share the corresponding source code for multiple critical communication modules, instead utilizing Cython to compile proprietary control logic into CPython shared object files. The ongoing non-compliance has been formally escalated to the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) following a series of admissions by the company's support team.

==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). In December 2025, Creality launched their official GitHub repository for the K2 Series, publicly promoting the flagship line as a fully open-source hardware and software ecosystem <ref name="creality_forum_launch" />. However, community developers quickly discovered that the released codebase was severely outdated, out of sync with active printer configurations, and conspicuously lacked the corresponding source code for critical operational modules <ref name="creality_forum_launch" />.

While Cython is occasionally used for performance optimization, its primary utility in this context was to obfuscate the implementation logic of the printer’s primary hardware integrations <ref name="creality_forum_tracker" />. By placing these binary wrappers directly inside Klipper’s process directory, Creality forced the GPLv3-licensed Klipper host process to dynamically link to and execute opaque binaries at runtime, creating a copyleft compliance conflict <ref name="creality_forum_tracker" />.

This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:
*'''K2 SE:''' V2.3.6.49 and V2.3.6.66 (`CR4CU220812S11_ota_img_V2.3.6.49.img`) <ref name="email_demand" />
*'''K2:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) <ref name="email_demand" />
*'''K2 Pro:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) <ref name="email_demand" />
*'''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`) <ref name="email_demand" />

==Incident==
Creality distributes Cython-compiled shared library objects (`.so`) inside Klipper's core process directory structures (`/usr/share/klipper/klippy/extras/`) without providing the corresponding source code <ref name="creality_forum_tracker" />. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host:
*`serial_485_wrapper.cpython-39.so` (Manages the custom RS-485 serial communication protocol linking the mainboard to the CFS feeder) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`box_wrapper.cpython-39.so` (Handles logical state routing, filament changes, and multi-material commands) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`filament_rack_wrapper.cpython-39.so` (Controls physical spool selection, drive gears, and filament runout sensors inside the CFS) <ref name="creality_forum_tracker" /> <ref name="email_demand" />
*`motor_control_wrapper.cpython-39.so` (Governs specialized stepper motor accelerations and hardware-level load balancing) <ref name="creality_forum_tracker" />
*`prtouch_v2_wrapper.cpython-39.so` (Governs strain-gauge-based automatic bed leveling and nozzle probing) <ref name="creality_forum_tracker" />
*`prtouch_v3_wrapper.cpython-39.so` (Handles advanced real-time Z-axis compensation algorithms) <ref name="creality_forum_tracker" />

Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026 <ref name="email_demand" />, a 14-day compliance deadline was established on May 20, 2026 <ref name="email_demand" />. Because compliance was not met, a formal license complaint was logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) on May 28, 2026 <ref name="email_demand" />. 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.

===Creality's Response & Admissions===
Throughout May 2026, the community documented a highly structured deflection loop used by Creality's front-line support staff to handle GPL inquiries, frequently issuing direct denials or stalling templates <ref name="creality_forum_tracker" />.

On May 15, 2026, Creality Customer Service formally acknowledged the initial source code application, stating: *"We have officially forwarded your application for the complete GPLv3 source code for all firmware versions of the K2 series to our R&D team for processing. ... Please stay tuned for further announcements on our official website."* <ref name="email_demand" />

On May 20, 2026, investigator Alex Mercer rejected the indefinite "stay tuned" timeline, establishing a strict 14-day compliance deadline under threat of escalation to the FSF and SFC <ref name="email_demand" />.

On May 24, 2026, Creality sent a written response detailing their inability to provide immediate source code matching the distributed binaries:
<blockquote>"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." <ref name="email_demand" /></blockquote>

On May 29, 2026, Creality issued a follow-up response confirming that *"cleaning up a fully compliant source code package without affecting commercial proprietary code does require an internal process that, for now, does not have a publicly available timeline."* <ref name="email_demand" /> Open-source legal experts note that this statement serves as an explicit corporate admission that proprietary commercial code was actively compiled and dynamically linked into a distributed GPLv3 copyleft work—an architectural contamination directly forbidden under the license guidelines.

On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination, 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 <ref name="email_demand" />.

==Consumer Response & Hardware Bypass==
The release of the K2 series firmware triggered significant backlash across Klipper Discourse, Creality Forums, and Reddit <ref name="creality_forum_launch" />. The community strongly criticized Creality for "malicious compliance"—promoting a printer as open-source while lockboxing its core features behind closed binaries <ref name="creality_forum_tracker" /> <ref name="reddit_k2" />.

These licensing omissions created severe, practical issues for consumers, blocking hardware repair, preventing the use of third-party toolheads, and restricting underlying Linux access <ref name="creality_forum_tracker" /> <ref name="klipper_discourse_k2" />. This backlash was compounded by the fact that Creality had previously repeated the exact same violation when launching the K1 series, only releasing the `prtouch` source code months later after intense public pressure <ref name="k1_github_issue" />. The restriction of root access on subsequent iterations like the K1C 2025 further intensified user distrust <ref name="creality_k1c_forum" />.

Kevin O'Connor, the original creator of Klipper, publicly reiterated: *"Klipper is licensed under the GNU GPLv3. Any redistribution of that code is required to follow the license. I have not dual-licensed the code nor provided any exceptions."* <ref name="klipper_discourse_violation" />

Frustrated by these restrictions, independent developers launched the `fake-name/cfs-reverse-engineering` project to manually map the Co-extrusion Filament System (CFS) feeder bus <ref name="cfs_github" />. Developers discovered that the CFS's GigaDevice GD32F303VET6 microcontroller was binary-compatible with the STM32F106VET6 <ref name="cfs_github" />. By designing a custom hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, developers successfully bypassed Creality's closed-source serial protocol, converting the CFS communication layer into an open CAN bus running standard *candleLight_fw* and native upstream Klipper <ref name="cfs_github" />.

==Industry Context & Legal Precedents==
Creality's ongoing non-compliance occurs amidst a broader industry crackdown on open-source license violations. Creality has a documented history of violations, previously being blacklisted on TH3D Studio LLC's 3D Printer GPL Violation List for withholding source code for Marlin-based printers and the Klipper-based Sonic Pad <ref name="klipper_discourse_violation" />.

Furthermore, on May 18, 2026, the Software Freedom Conservancy (SFC) launched a major compliance initiative against Bambu Lab over violations of the GNU Affero General Public License v3 (AGPLv3) <ref name="sfc_bambu" /> <ref name="toms_hardware_bambu" />. When Bambu Lab attempted to keep their networking library (`libbambu_networking.so`) proprietary and issued a cease-and-desist to an independent developer, the SFC launched Project "baltobu" to reverse-engineer the closed-source libraries and host a fully independent fork of the slicer <ref name="sfc_bambu" /> <ref name="reddit_sfc" />. This underscores a shifting industry landscape where enforcement bodies are taking direct legal and technical action against companies isolating commercial IP within copyleft frameworks.

==References==
<references>
| refs =
<ref name="creality_forum_launch">[https://forum.creality.com/t/creality-open-source-3d-printer-firmware-is-here/47218 "Creality Open-Source 3D Printer Firmware is Here!"], Official Creality Forum.</ref>
<ref name="creality_forum_tracker">[https://forum.creality.com/t/where-are-the-required-to-be-released-sources-for-crealitys-modifications-to-klipper-the-k2/30019 "Where are the (required to be released) sources for Creality's modifications to Klipper the K2"], Creality Forum Tracker.</ref>
<ref name="email_demand">[https://archive.org/details/creality-k-2-gplv-3-compliance-demand-may-2026 "Creality K2 GPLv3 Compliance Demand Correspondence Logs (May 2026)"], Hosted on the Internet Archive.</ref>
<ref name="reddit_k2">[https://www.reddit.com/r/Creality/comments/1hcer2j/k2_plus_firmware_source_code/ "K2 Plus Firmware Source Code"], r/Creality Community Discussion.</ref>
<ref name="klipper_discourse_k2">[https://klipper.discourse.group/t/creality-k2-plus-and-gpl-violations/22402 "Creality K2 Plus and GPL violations"], Klipper Discourse Group.</ref>
<ref name="k1_github_issue">[https://github.com/CrealityOfficial/K1_Series_Klipper/issues/9 "This repository contains binary-only extensions, violating the Klipper GPLv3 license"], K1 Series GitHub Issue #9.</ref>
<ref name="creality_k1c_forum">[https://forum.creality.com/t/k1c-2025-orcaslicer-workarounds-for-missing-web-interface/47164 "K1C 2025 + OrcaSlicer: Workarounds for Missing Web Interface"], Creality Community Forum.</ref>
<ref name="klipper_discourse_violation">[https://klipper.discourse.group/t/creality-violating-klipper-license/8990 "Creality Violating Klipper License"], Klipper Discourse Group.</ref>
<ref name="cfs_github">[https://github.com/fake-name/cfs-reverse-engineering fake-name/cfs-reverse-engineering], GitHub Repository.</ref>
<ref name="sfc_bambu">[https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ "Comprehensive Response to Bambu's AGPLv3 Violations"], Software Freedom Conservancy.</ref>
<ref name="toms_hardware_bambu">[https://www.tomshardware.com/3d-printing/open-source-non-profit-claims-bambu-lab-violated-license-move-follows-cease-and-desist-demand-on-orcaslicer-fork-that-restored-cloud-printing-features-without-using-bambu-connect "Open-source non-profit claims Bambu Lab violated license"], Tom's Hardware.</ref>
<ref name="reddit_sfc">[https://www.reddit.com/r/BambuLab/comments/1tjku6z/the_software_freedom_conservancy_sfc_just/ "The Software Freedom Conservancy (SFC) launched a counter-offensive against Bambu Lab over AGPL violations"], r/BambuLab - Reddit.</ref>
</references>

{{Ph-I-C}}

Creality K2 series GPLv3 violation

2026-06-01T06:40:10Z

181.215.169.214: Background update, references pending to be reviewed and cleaned up

{{IncidentCargo
|Company=Creality
|StartDate=2025-12-12
|Status=Active
|ProductLine=K2 Series 3D Printers
}}The Creality K2 series 3D printer firmware (encompassing the K2, K2 SE, K2 Pro, and K2 Plus) contains a systemic violation of the GNU General Public License v3 (GPLv3) due to the inclusion of proprietary binary blobs compiled directly into the open-source Klipper host environment. Despite marketing the flagship hardware lineup as a fully open-source ecosystem, Creality has formally refused to share the corresponding source code for multiple critical communication modules, instead utilizing Cython to compile proprietary control logic into CPython shared object files. The ongoing non-compliance has been formally escalated to the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) following a series of admissions by the company's support team.

==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). In December 2025, Creality launched their official GitHub repository for the K2 Series, publicly promoting the flagship line as a fully open-source hardware and software ecosystem <ref name="creality_forum_launch" />. However, community developers quickly discovered that the released codebase was severely outdated, out of sync with active printer configurations, and conspicuously lacked the corresponding source code for critical operational modules <ref name="creality_forum_launch" />.

While Cython is occasionally used for performance optimization, its primary utility in this context was to obfuscate the implementation logic of the printer’s primary hardware integrations <ref name="creality_forum_tracker" />. By placing these binary wrappers directly inside Klipper’s process directory, Creality forced the GPLv3-licensed Klipper host process to dynamically link to and execute opaque binaries at runtime, creating a copyleft compliance conflict <ref name="creality_forum_tracker" />.

This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:
*'''K2 SE:''' V2.3.6.49 and V2.3.6.66 (`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 Cython-compiled shared library objects (`.so`) inside Klipper's core process directory structures (`/usr/share/klipper/klippy/extras/`) without providing the corresponding source code <ref name="creality_forum_tracker" />. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host:
*`serial_485_wrapper.cpython-39.so` (Manages the custom RS-485 serial communication protocol linking the mainboard to the CFS feeder) <ref name="creality_forum_tracker" />
*`box_wrapper.cpython-39.so` (Handles logical state routing, filament changes, and multi-material commands) <ref name="creality_forum_tracker" />
*`filament_rack_wrapper.cpython-39.so` (Controls physical spool selection, drive gears, and filament runout sensors inside the CFS) <ref name="creality_forum_tracker" />
*`motor_control_wrapper.cpython-39.so` (Governs specialized stepper motor accelerations and hardware-level load balancing) <ref name="creality_forum_tracker" />
*`prtouch_v2_wrapper.cpython-39.so` (Governs strain-gauge-based automatic bed leveling and nozzle probing) <ref name="creality_forum_tracker" />
*`prtouch_v3_wrapper.cpython-39.so` (Handles advanced real-time Z-axis compensation algorithms) <ref name="creality_forum_tracker" />

Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026 <ref name="ticket_ack_may15" />, a 14-day compliance deadline was established on May 20, 2026 <ref name="mercer_demand_may20" />. Because compliance was not met, a formal license complaint was logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF). 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.

===Creality's Response & Admissions===
Throughout May 2026, the community documented a highly structured deflection loop used by Creality's front-line support staff to handle GPL inquiries, frequently issuing direct denials or stalling templates <ref name="creality_forum_tracker" />.

On May 15, 2026, Creality Customer Service formally acknowledged the initial source code application, stating: *"We have officially forwarded your application for the complete GPLv3 source code for all firmware versions of the K2 series to our R&D team for processing. ... Please stay tuned for further announcements on our official website."* <ref name="ticket_ack_may15" />

On May 24, 2026, following a warning that the ticketing system would close automatically, Creality sent a written response detailing their inability to provide immediate source code matching the distributed binaries:
<blockquote>"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." <ref name="creality_refusal_may24" /></blockquote>

On May 29, 2026, Creality issued a follow-up response confirming that *"cleaning up a fully compliant source code package without affecting commercial proprietary code does require an internal process that, for now, does not have a publicly available timeline."* <ref name="creality_confession_may29" /> Open-source legal experts note that this statement serves as an explicit corporate admission that proprietary commercial code was actively compiled and dynamically linked into a distributed GPLv3 copyleft work—an architectural contamination directly forbidden under the license guidelines.

On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination, 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 <ref name="ticket_closure_may31" />.

==Consumer Response & Hardware Bypass==
The release of the K2 series firmware triggered significant backlash across Klipper Discourse, Creality Forums, and Reddit <ref name="creality_forum_launch" />. The community strongly criticized Creality for "malicious compliance"—promoting a printer as open-source while lockboxing its core features behind closed binaries <ref name="creality_forum_tracker" /> <ref name="reddit_k2" />.

These licensing omissions created severe, practical issues for consumers, blocking hardware repair, preventing the use of third-party toolheads, and restricting underlying Linux access <ref name="creality_forum_tracker" /> <ref name="klipper_discourse_k2" />. This backlash was compounded by the fact that Creality had previously repeated the exact same violation when launching the K1 series, only releasing the `prtouch` source code months later after intense public pressure <ref name="k1_github_issue" />. The restriction of root access on subsequent iterations like the K1C 2025 further intensified user distrust <ref name="creality_k1c_forum" />.

Kevin O'Connor, the original creator of Klipper, publicly reiterated: *"Klipper is licensed under the GNU GPLv3. Any redistribution of that code is required to follow the license. I have not dual-licensed the code nor provided any exceptions."* <ref name="klipper_discourse_violation" />

Frustrated by these restrictions, independent developers launched the `fake-name/cfs-reverse-engineering` project to manually map the Co-extrusion Filament System (CFS) feeder bus <ref name="cfs_github" />. Developers discovered that the CFS's GigaDevice GD32F303VET6 microcontroller was binary-compatible with the STM32F106VET6 <ref name="cfs_github" />. By designing a custom hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, developers successfully bypassed Creality's closed-source serial protocol, converting the CFS communication layer into an open CAN bus running standard *candleLight_fw* and native upstream Klipper <ref name="cfs_github" />.

==Industry Context & Legal Precedents==
Creality's ongoing non-compliance occurs amidst a broader industry crackdown on open-source license violations. Creality has a documented history of violations, previously being blacklisted on TH3D Studio LLC's 3D Printer GPL Violation List for withholding source code for Marlin-based printers and the Klipper-based Sonic Pad <ref name="klipper_discourse_violation" />.

Furthermore, on May 18, 2026, the Software Freedom Conservancy (SFC) launched a major compliance initiative against Bambu Lab over violations of the GNU Affero General Public License v3 (AGPLv3) <ref name="sfc_bambu" /> <ref name="toms_hardware_bambu" />. When Bambu Lab attempted to keep their networking library (`libbambu_networking.so`) proprietary and issued a cease-and-desist to an independent developer, the SFC launched Project "baltobu" to reverse-engineer the closed-source libraries and host a fully independent fork of the slicer <ref name="sfc_bambu" /> <ref name="reddit_sfc" />. This underscores a shifting industry landscape where enforcement bodies are taking direct legal and technical action against companies isolating commercial IP within copyleft frameworks.

==References==
<references>
<ref name="creality_forum_launch">[https://forum.creality.com/t/creality-open-source-3d-printer-firmware-is-here/47218 "Creality Open-Source 3D Printer Firmware is Here!"], Official Creality Forum.</ref>
<ref name="creality_forum_tracker">[https://forum.creality.com/t/where-are-the-required-to-be-released-sources-for-crealitys-modifications-to-klipper-the-k2/30019 "Where are the (required to be released) sources for Creality's modifications to Klipper the K2"], Creality Forum Tracker.</ref>
<ref name="ticket_ack_may15">Creality Support Ticket #20260515750685, Official Email Correspondence from cs@creality.com, 15 May 2026.</ref>
<ref name="mercer_demand_may20">Alex Mercer Email Communication to Creality Support, Ticket #20260515750685, 20 May 2026.</ref>
<ref name="creality_refusal_may24">Creality Support Team Response, Ticket #20260515750685, 24 May 2026.</ref>
<ref name="creality_confession_may29">Creality Support Team Response, Ticket #20260515750685, 29 May 2026.</ref>
<ref name="ticket_closure_may31">Creality Support Case Closure Notification, Ticket #20260515750685, 31 May 2026.</ref>
<ref name="reddit_k2">[https://www.reddit.com/r/Creality/comments/1hcer2j/k2_plus_firmware_source_code/ "K2 Plus Firmware Source Code"], r/Creality Community Discussion.</ref>
<ref name="klipper_discourse_k2">[https://klipper.discourse.group/t/creality-k2-plus-and-gpl-violations/22402 "Creality K2 Plus and GPL violations"], Klipper Discourse Group.</ref>
<ref name="k1_github_issue">[https://github.com/CrealityOfficial/K1_Series_Klipper/issues/9 "This repository contains binary-only extensions, violating the Klipper GPLv3 license"], K1 Series GitHub Issue #9.</ref>
<ref name="creality_k1c_forum">[https://forum.creality.com/t/k1c-2025-orcaslicer-workarounds-for-missing-web-interface/47164 "K1C 2025 + OrcaSlicer: Workarounds for Missing Web Interface"], Creality Community Forum.</ref>
<ref name="klipper_discourse_violation">[https://klipper.discourse.group/t/creality-violating-klipper-license/8990 "Creality Violating Klipper License"], Klipper Discourse Group.</ref>
<ref name="cfs_github">[https://github.com/fake-name/cfs-reverse-engineering fake-name/cfs-reverse-engineering], GitHub Repository.</ref>
<ref name="sfc_bambu">[https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ "Comprehensive Response to Bambu's AGPLv3 Violations"], Software Freedom Conservancy.</ref>
<ref name="toms_hardware_bambu">[https://www.tomshardware.com/3d-printing/open-source-non-profit-claims-bambu-lab-violated-license-move-follows-cease-and-desist-demand-on-orcaslicer-fork-that-restored-cloud-printing-features-without-using-bambu-connect "Open-source non-profit claims Bambu Lab violated license"], Tom's Hardware.</ref>
<ref name="reddit_sfc">[https://www.reddit.com/r/BambuLab/comments/1tjku6z/the_software_freedom_conservancy_sfc_just/ "The Software Freedom Conservancy (SFC) launched a counter-offensive against Bambu Lab over AGPL violations"], r/BambuLab - Reddit.</ref>
</references>

{{Ph-I-C}}