Creality K2 series GPLv3 violation - Revision history

Louis: Quotation formatting: use italics for quoted passages in blockquotes and run-in quotes

2026-06-02T02:02:35Z

Quotation formatting: use italics for quoted passages in blockquotes and run-in quotes

Louis: Revise: verify sourcing against primary material; attribute correspondence-log claims; restore sourced CR-10S/Naomi Wu history and K2/K1C forum cites; correct MCU part wording; remove non-citable sources

2026-06-02T01:56:09Z

Revise: verify sourcing against primary material; attribute correspondence-log claims; restore sourced CR-10S/Naomi Wu history and K2/K1C forum cites; correct MCU part wording; remove non-citable sources

Show changes

192.154.196.62: Add Naomi Wu involvement

2026-06-01T21:31:59Z

Add Naomi Wu involvement

← Older revision		Revision as of 21:31, 1 June 2026
Line 48:		Line 48:

	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" />.		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" />.

			Historically, activist and tech community figure Naomi Wu played a critical role in forcing Creality to establish its initial open-source compliance baseline. Wu acted as a direct liaison and public advocate, leveraging significant pressure on Creality management during their past Marlin and early Klipper releases to ensure they published physical source repositories. Her historical intervention established the exact public precedent that community developers have relied upon to demand the release of missing `prtouch` and CFS source text.

	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" />		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" />

181.215.169.214: metadata edit

2026-06-01T07:35:58Z

metadata edit

← Older revision		Revision as of 07:35, 1 June 2026
Line 4:		Line 4:
	\|Status=Active		\|Status=Active
	\|ProductLine=K2 Series 3D Printers		\|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.		\|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==		==Background==

181.215.169.214: editorial change

2026-06-01T07:33:45Z

editorial change

← Older revision		Revision as of 07:33, 1 June 2026
Line 58:		Line 58:
	==References==		==References==
	<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_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="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>
Line 72:		Line 71:
	<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>		<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>		</references>

	~~{{Ph-I-C}}~~

181.215.169.214 at 07:33, 1 June 2026

2026-06-01T07:33:03Z

← Older revision		Revision as of 07:33, 1 June 2026
Line 12:		Line 12:

	This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:		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 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`)		*'''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`)		*'''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`)		*'''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`) <ref name="email_demand" />

	==Incident==		==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:		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" />		*`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" />		*`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" />		*`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" />		*`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_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" />		*`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.		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===		===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" />.		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 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 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:~~		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" />.
	~~<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 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 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~~" />.		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==		==Consumer Response & Hardware Bypass==
Line 56:		Line 58:
	==References==		==References==
	<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_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="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="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="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="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="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>

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

2026-06-01T06:40:10Z

Background update, references pending to be reviewed and cleaned up

Show changes

86.62.28.99: /* Lawsuit */

2026-06-01T06:00:48Z

Lawsuit

← Older revision		Revision as of 06:00, 1 June 2026
Line 33:		Line 33:

	==Lawsuit==		==Lawsuit==
	~~{{Ph-I-L}}~~

86.62.28.99: added summary

2026-06-01T05:59:40Z

added summary

← Older revision		Revision as of 05:59, 1 June 2026
Line 4:		Line 4:
	\|Status=Active		\|Status=Active
	\|ProductLine=K2 Series 3D Printers		\|ProductLine=K2 Series 3D Printers
	}}		}}The Creality K2 series 3D printer firmware 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 an entirely open-source ecosystem, Creality has formally refused to share the corresponding source code for multiple critical communication modules. The ongoing non-compliance has been escalated to the Software Freedom Conservancy and the Free Software Foundation following a series of admissions by the company's support team.
	~~{{Ph~~-I-~~Int}}~~
	==Background==		==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.		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.

86.62.28.99: editorial changes

2026-06-01T05:55:24Z

editorial changes

← Older revision		Revision as of 05:55, 1 June 2026
Line 12:		Line 12:

	This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line:		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 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:''' 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 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`)		*'''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`)
	~~{{Ph-I-B}}~~

	==Incident==		==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:		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)		*`serial_485_wrapper.so` (Manages RS-485 serial communication bus)
	* `box_wrapper.so`		*`box_wrapper.so`
	* `filament_rack_wrapper.so`		*`filament_rack_wrapper.so`
	* Compiled `.o` object files tied directly to the Color Format System (CFS) multi-material management library.		*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.		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.
	~~{{Ph-I-I}}~~

	===[Company]'s response===		===[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 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."''
Line 34:		Line 30:

	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.		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.
	~~{{Ph-I-ComR}}~~

← Older revision		Revision as of 02:02, 2 June 2026
Line 10:		Line 10:
	}}		}}

	The Creality K2 series 3D printer firmware (covering the K2 SE, K2, K2 Pro, & K2 Plus) ships proprietary modules compiled with Cython into the GPLv3-licensed Klipper host environment without releasing the corresponding source code.<ref name="creality_forum_tracker" /><ref name="cfs_github" /> Klipper's community developers & the independent reverse-engineering project fake-name/cfs-reverse-engineering have documented these closed binaries as a violation of the GNU General Public License v3 (GPLv3), the license under which Klipper is distributed.<ref name="creality_forum_tracker" /><ref name="cfs_github" /> [[Creality]] opened a public GitHub repository for the K2 line in December 2025 & markets it as open source, but the published code lacks the source for several hardware communication modules.<ref name="creality_forum_launch" /> A correspondence log uploaded to the Internet Archive in May 2026 records Creality support telling a requester it was ''"unable to directly provide the corresponding source code,"'' & shows the requester copying the [[Software Freedom Conservancy]] (SFC) & the Free Software Foundation (FSF) on the demand.<ref name="email_demand" />		The Creality K2 series 3D printer firmware (covering the K2 SE, K2, K2 Pro, & K2 Plus) ships proprietary modules compiled with Cython into the GPLv3-licensed Klipper host environment without releasing the corresponding source code.<ref name="creality_forum_tracker" /><ref name="cfs_github" /> Klipper's community developers & the independent reverse-engineering project fake-name/cfs-reverse-engineering have documented these closed binaries as a violation of the GNU General Public License v3 (GPLv3), the license under which Klipper is distributed.<ref name="creality_forum_tracker" /><ref name="cfs_github" /> [[Creality]] opened a public GitHub repository for the K2 line in December 2025 & markets it as open source, but the published code lacks the source for several hardware communication modules.<ref name="creality_forum_launch" /> A correspondence log uploaded to the Internet Archive in May 2026 records Creality support telling a requester it was ''unable to directly provide the corresponding source code,'' & shows the requester copying the [[Software Freedom Conservancy]] (SFC) & the Free Software Foundation (FSF) on the demand.<ref name="email_demand" />

	==Background==		==Background==
	The K2 series firmware is built on Klipper, the open-source 3D-printer host software that its creator Kevin O'Connor distributes under the GPLv3.<ref name="klipper_discourse_violation" /> In December 2025, Creality opened a public GitHub repository for the K2 series & promoted the line as open source.<ref name="creality_forum_launch" /> Community developers found that the published code was outdated, out of sync with shipping printer configurations, & missing the source for several hardware communication modules.<ref name="creality_forum_launch" /><ref name="creality_forum_tracker" /> The dispute predates that repository: a Creality-forum thread asking where the required K2 Klipper sources were had been open since February 2025.<ref name="creality_forum_tracker" />		The K2 series firmware is built on Klipper, the open-source 3D-printer host software that its creator Kevin O'Connor distributes under the GPLv3.<ref name="klipper_discourse_violation" /> In December 2025, Creality opened a public GitHub repository for the K2 series & promoted the line as open source.<ref name="creality_forum_launch" /> Community developers found that the published code was outdated, out of sync with shipping printer configurations, & missing the source for several hardware communication modules.<ref name="creality_forum_launch" /><ref name="creality_forum_tracker" /> The dispute predates that repository: a Creality-forum thread asking where the required K2 Klipper sources were had been open since February 2025.<ref name="creality_forum_tracker" />

	The missing modules ship as Cython-compiled shared objects. The reverse-engineering project fake-name/cfs-reverse-engineering describes these files as compiled with Cython ''"to make them opaque."''<ref name="cfs_github" /> Because the wrappers sit inside Klipper's own process directory, the GPLv3-licensed Klipper host loads & executes the closed binaries at runtime.<ref name="creality_forum_tracker" /><ref name="cfs_github" />		The missing modules ship as Cython-compiled shared objects. The reverse-engineering project fake-name/cfs-reverse-engineering describes these files as compiled with Cython ''to make them opaque.''<ref name="cfs_github" /> Because the wrappers sit inside Klipper's own process directory, the GPLv3-licensed Klipper host loads & executes the closed binaries at runtime.<ref name="creality_forum_tracker" /><ref name="cfs_github" />

	The missing source affects the firmware images shipped across the K2 line:		The missing source affects the firmware images shipped across the K2 line:
Line 33:		Line 33:
	A Klipper community thread on the K2 Plus documents that these compiled modules implement the printer's automatic filament-changing feature & ship only as shared-object files, & a moderator there describes Creality as in violation of the GPLv3.<ref name="klipper_discourse_k2" />		A Klipper community thread on the K2 Plus documents that these compiled modules implement the printer's automatic filament-changing feature & ship only as shared-object files, & a moderator there describes Creality as in violation of the GPLv3.<ref name="klipper_discourse_k2" />

	According to a correspondence log uploaded to the Internet Archive in May 2026, a requester pressed Creality for the complete GPLv3 source code, & Creality support acknowledged the request on May 15, 2026.<ref name="email_demand" /> The log's outgoing letters, signed by a sender identifying himself as Alex Mercer, were copied to the [[Software Freedom Conservancy]] (compliance@sfconservancy.org) & the Free Software Foundation (license-violation@gnu.org) on May 27 & May 29, 2026, & state that the violation is ''"logged with the Software Freedom Conservancy and the Free Software Foundation."''<ref name="email_demand" /> The log records a single recurring demand, that Creality either release the source or stop shipping the firmware. The May 29, 2026 letter reads:		According to a correspondence log uploaded to the Internet Archive in May 2026, a requester pressed Creality for the complete GPLv3 source code, & Creality support acknowledged the request on May 15, 2026.<ref name="email_demand" /> The log's outgoing letters, signed by a sender identifying himself as Alex Mercer, were copied to the [[Software Freedom Conservancy]] (compliance@sfconservancy.org) & the Free Software Foundation (license-violation@gnu.org) on May 27 & May 29, 2026, & state that the violation is ''logged with the Software Freedom Conservancy and the Free Software Foundation.''<ref name="email_demand" /> The log records a single recurring demand, that Creality either release the source or stop shipping the firmware. The May 29, 2026 letter reads:
	<blockquote>''"I reiterate my demand: immediately provide the complete corresponding source code or halt all distribution of the K2 series firmware until compliance is achieved."''</blockquote><ref name="email_demand" />		<blockquote>''I reiterate my demand: immediately provide the complete corresponding source code or halt all distribution of the K2 series firmware until compliance is achieved.''</blockquote><ref name="email_demand" />
	Creality continues to distribute the same firmware images while the source remains unreleased.<ref name="creality_forum_tracker" />		Creality continues to distribute the same firmware images while the source remains unreleased.<ref name="creality_forum_tracker" />

Line 41:		Line 41:

	In the correspondence log, a May 15, 2026 reply from Creality Customer Service reads:		In the correspondence log, a May 15, 2026 reply from Creality Customer Service reads:
	<blockquote>''"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."''</blockquote><ref name="email_demand" />		<blockquote>''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.''</blockquote><ref name="email_demand" />

	A May 24, 2026 reply in the same log, attributed to Creality Service, reads:		A May 24, 2026 reply in the same log, attributed to Creality Service, reads:
	<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."''</blockquote><ref name="email_demand" />		<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.''</blockquote><ref name="email_demand" />

	A May 29, 2026 follow-up in the log states:		A May 29, 2026 follow-up in the log states:
	<blockquote>''"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."''</blockquote><ref name="email_demand" />		<blockquote>''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.''</blockquote><ref name="email_demand" />

	The log records no substantive reply after May 29, 2026; per the log, Creality forwarded the case to its internal legal department & R&D manager without giving a compliance timeline.<ref name="email_demand" />		The log records no substantive reply after May 29, 2026; per the log, Creality forwarded the case to its internal legal department & R&D manager without giving a compliance timeline.<ref name="email_demand" />

	==Consumer response & hardware bypass==		==Consumer response & hardware bypass==
	The K2 firmware drew criticism on the Creality forums, where the cfs project author argued that withholding the source for the parts that matter moved Creality from incompetent to ''"actively malicious"'': promoting a printer as open source while keeping its core features behind closed binaries.<ref name="creality_forum_tracker" />		The K2 firmware drew criticism on the Creality forums, where the cfs project author argued that withholding the source for the parts that matter moved Creality from incompetent to ''actively malicious'': promoting a printer as open source while keeping its core features behind closed binaries.<ref name="creality_forum_tracker" />

	The closed binaries created practical problems for owners: blocked hardware repair, no support for third-party toolheads, & restricted access to the printer's underlying Linux system.<ref name="creality_forum_tracker" />		The closed binaries created practical problems for owners: blocked hardware repair, no support for third-party toolheads, & restricted access to the printer's underlying Linux system.<ref name="creality_forum_tracker" />
Line 58:		Line 58:
	Creality had faced the same complaint over the earlier K1 series. Issue #9 on its K1_Series_Klipper GitHub repository flagged binary-only extensions as a GPLv3 violation & demanded the corresponding source; the issue remained open as of March 2025.<ref name="k1_github_issue" /> On the later K1C, Creality removed root access; owners on the Creality forum note that the printer's own documentation describes the removal as intentional.<ref name="creality_k1c_forum" />		Creality had faced the same complaint over the earlier K1 series. Issue #9 on its K1_Series_Klipper GitHub repository flagged binary-only extensions as a GPLv3 violation & demanded the corresponding source; the issue remained open as of March 2025.<ref name="k1_github_issue" /> On the later K1C, Creality removed root access; owners on the Creality forum note that the printer's own documentation describes the removal as intentional.<ref name="creality_k1c_forum" />

	Independent developers started the fake-name/cfs-reverse-engineering project to map the Creality Filament System (CFS) feeder bus.<ref name="cfs_github" /> The project documents that the CFS uses a GigaDevice GD32F303VET6 microcontroller, which its firmware notes describe as binary-compatible with an ''"STM32F106VET6"''.<ref name="cfs_github" /> By building a hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, the developers converted the CFS link into a standard CAN bus running candleLight_fw & upstream Klipper, bypassing Creality's closed serial protocol.<ref name="cfs_github" />		Independent developers started the fake-name/cfs-reverse-engineering project to map the Creality Filament System (CFS) feeder bus.<ref name="cfs_github" /> The project documents that the CFS uses a GigaDevice GD32F303VET6 microcontroller, which its firmware notes describe as binary-compatible with an ''STM32F106VET6''.<ref name="cfs_github" /> By building a hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, the developers converted the CFS link into a standard CAN bus running candleLight_fw & upstream Klipper, bypassing Creality's closed serial protocol.<ref name="cfs_github" />

	Kevin O'Connor, the creator of Klipper, restated the license terms on the Klipper Discourse forum:		Kevin O'Connor, the creator of Klipper, restated the license terms on the Klipper Discourse forum:
	<blockquote>''"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."''</blockquote><ref name="klipper_discourse_violation" />		<blockquote>''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.''</blockquote><ref name="klipper_discourse_violation" />

	==Prior violations & the Bambu Lab AGPLv3 case==		==Prior violations & the Bambu Lab AGPLv3 case==
Line 68:		Line 68:
	Creality's open-source disputes go back to 2018. After it shipped its CR-10 line with Marlin, a GPLv3-licensed firmware, without releasing complete corresponding source, US distributor Printed Solid stopped selling Creality printers over the non-compliance.<ref name="hackaday_marlin" /> Community pressure followed, & technology figure Naomi Wu was credited, alongside that pressure, with getting Creality to release the Marlin source for the CR-10S, including its filament-sensor & power-loss-recovery code, in April 2018.<ref name="3dprintingnerd_nw" />		Creality's open-source disputes go back to 2018. After it shipped its CR-10 line with Marlin, a GPLv3-licensed firmware, without releasing complete corresponding source, US distributor Printed Solid stopped selling Creality printers over the non-compliance.<ref name="hackaday_marlin" /> Community pressure followed, & technology figure Naomi Wu was credited, alongside that pressure, with getting Creality to release the Marlin source for the CR-10S, including its filament-sensor & power-loss-recovery code, in April 2018.<ref name="3dprintingnerd_nw" />

	On May 18, 2026, the Software Freedom Conservancy published a response to violations of the GNU Affero General Public License v3 (AGPLv3) by [[Bambu Lab]] over its proprietary networking library <code>libbambu_networking.so</code>.<ref name="sfc_bambu" /><ref name="toms_hardware_bambu" /> After Bambu issued a cease-and-desist to Pawel Jarczak, the developer of an OrcaSlicer fork, the SFC announced Project baltobu (''"Bringing Affero Licensed Things (On)to Bambu Users"'') to reverse-engineer the closed library & host an independent slicer fork.<ref name="sfc_bambu" />		On May 18, 2026, the Software Freedom Conservancy published a response to violations of the GNU Affero General Public License v3 (AGPLv3) by [[Bambu Lab]] over its proprietary networking library <code>libbambu_networking.so</code>.<ref name="sfc_bambu" /><ref name="toms_hardware_bambu" /> After Bambu issued a cease-and-desist to Pawel Jarczak, the developer of an OrcaSlicer fork, the SFC announced Project baltobu (''Bringing Affero Licensed Things (On)to Bambu Users'') to reverse-engineer the closed library & host an independent slicer fork.<ref name="sfc_bambu" />

	==References==		==References==