Copyleft in mainland China: licenses, product boundaries and enforcement

English adaptation of the Chinese research report, with an underlying research cutoff of 19 July 2026. The discussion concerns mainland China. Published court materials are incomplete: the absence of a reported decision is not proof that no such decision exists. This article distinguishes license terms, judicial findings and practical analysis.

Open source is a rights arrangement

Copyleft is often described as a software license that “spreads.” That description is memorable but legally imprecise. In mainland China, copyleft is not a separate statutory intellectual property right. It operates through copyright permissions: a rights holder permits specified acts, subject to conditions governing attribution, source-code availability, downstream licensing and further restrictions.

The commercial question is therefore not simply whether a product contains open-source code. It is which protected material entered the product, under which version of which license, how the components interact, what has been delivered or made available, and whether the recipient has complied with the applicable conditions. Those questions connect legal interpretation with architecture, build records and release operations.

Chinese courts have recognized the contractual and copyright significance of the GNU General Public License. They have also refused to treat every licensing breach as infringement of every economic right. A source-code obligation, an attribution obligation and a prohibition on additional restrictions need to be mapped to their own legal consequences. The leading cases support a fact-sensitive approach, rather than a universal rule that all adjacent software must be disclosed.

The available decisions are concentrated in software, particularly GPL disputes. This research did not identify a reliably verifiable mainland final judgment directly deciding the share-alike obligation in a CC BY-SA artistic work. The license families used in publishing, fonts, databases and hardware therefore need their own analysis; software holdings cannot simply be carried across.

1. Distinguish the license families before assessing risk

Open source, copyleft, public-domain dedication and source availability are different arrangements. MIT, BSD, Apache-2.0 and Mulan PSL v2 are permissive licenses. They do not generally require an entire downstream product to use the same license. GPL is a strong copyleft license; LGPL, MPL, EPL and CDDL use more limited reciprocity structures. AGPL and Mulan PubL v2 address particular network-service situations as well.

CC0 aims to waive rights where possible and supplies a fallback license. It is not copyleft. Its operation in China must also account for limits on disposing of authors’ personal rights. A license with a noncommercial condition, such as CC BY-NC-SA, includes share-alike but should not be described as unrestricted open licensing. Downloadable model weights with acceptable-use or user-category restrictions are likewise not automatically open source.

Four questions provide a useful starting point:

Trigger: is the relevant act distribution, communication to the public, modification, public use of a database, or interaction with a modified program over a network?
Scope: do obligations attach to modified files, a library, an integrated program, adapted material, a database or hardware design documentation?
Beneficiary: must source or other materials be available to recipients, network users or a different defined group?
Consequence: does noncompliance terminate permission automatically, require notice, allow reinstatement, or create a more limited contractual obligation?

A license name without its version is inadequate. GPL-2.0-only and GPL-2.0-or-later, for example, describe different choices. The controlling record is the actual text attached to the relevant release, together with the project’s rights history.

2. Software licenses: similar vocabulary, different boundaries

License family	Main boundary to examine	Practical issue
GPLv2 and GPLv3	Conveying covered software and derivative combinations	Corresponding source, notices, version compatibility and restrictions imposed by distribution channels
AGPLv3	GPLv3 framework plus network interaction with a modified program	A hosted service needs a separate trigger analysis; absence of conventional distribution does not settle the question
LGPL	The library, its modifications and permitted combined works	Replacement or relinking conditions still matter; dynamic linking is not unconditional permission
MPL 2.0	Covered files and modifications to those files	Maintain file-level provenance and examine its secondary-license provisions
EPL and CDDL	Their respective definitions of programs, contributions and covered files	Compatibility cannot be inferred merely because both components are open source
Mulan PubL v2	Its defined derivative works and distribution, including specified network services	Read the Chinese controlling text, linking definitions, termination procedure and source-offer requirements

The primary texts are GPLv2, GPLv3, AGPLv3, LGPLv3, MPL 2.0, EPL 2.0 and CDDL 1.0. These texts, rather than shorthand labels such as “weak” or “strong,” determine obligations.

Mulan requires particular care. Mulan PubL v2 and Mulan PSL v2 are different licenses. PubL contains strong reciprocity and network-service provisions; PSL is permissive. The OSI entry for Mulan PSL v2 does not establish OSI approval for PubL. PubL’s definition expressly addresses static and dynamic linking, while identifying certain interprocess communication and system-call relationships as independent works. That is a textual starting point, not a substitute for examining the actual architecture.

Project history illustrates the importance of versions. OceanBase’s initial repository license used Mulan PubL v2. A March 2026 commit changed the license to Apache-2.0. Saying simply that “OceanBase is licensed under X” loses the distinction between earlier copies, later versions and the rights necessary for relicensing.

3. Copyright and contract operate together in China

The PRC Copyright Law identifies protected categories and the exclusive rights that a license may permit, including reproduction, distribution, adaptation and communication through information networks. The Computer Software Protection Regulations provide the software-specific framework. A public license ordinarily grants nonexclusive permission; it does not place the work outside copyright. See the Copyright Law and Software Protection Regulations.

The contractual analysis does not depend on a conventional signed agreement. The Civil Code recognizes manifestations of intention through conduct and treats retrievable electronic records as a form of writing. In the Luohe cases, publication under an open-source license was analyzed as an offer, with relevant user conduct constituting acceptance. Nor does a zero price invalidate the arrangement: PRC contract law does not use common-law consideration as a general formation requirement.

Teams should nevertheless make the offer intelligible. Repository licenses, source headers, packaged notices, website descriptions and commercial-license messages should not contradict one another. Save the version visible at acquisition and release. A separate commercial or exclusive license needs its own rights and documentation; a public license should not be presented as evidence of exclusivity.

Standard-term rules also matter. A widely offered license may be scrutinized under the Civil Code’s rules on standard terms, notice, explanation and interpretation. “As is” language does not automatically displace mandatory limits on exclusions of liability. Authors’ attribution and integrity interests also cannot simply be treated as transferable economic rights. Foreign-drafted language about waiving or not asserting such interests operates only within applicable law.

Cross-border documents add another layer. Under Articles 48–50 of the PRC Law on the Application of Laws to Foreign-Related Civil Relations, ownership and content of intellectual property, licensing contracts and infringement are not necessarily governed by the same connecting rule. A foreign license does not by itself remove Chinese copyright and mandatory-law questions from litigation over conduct in China.

4. Termination must be matched to the actual breach

The core sequence in the GPL cases is permission, breach of a relevant condition, termination under the applicable arrangement, and subsequent unauthorized acts. It is not “a term was breached, therefore every use was always infringing.” Distinguish a condition on authorization from an independent promise and identify the copyright act affected.

The cure mechanisms differ. GPLv3 section 8 contains provisional and permanent reinstatement routes, including provisions connected with cessation, notice and correction. CC 4.0 has its own reinstatement mechanism tied to correction within 30 days of discovery. Mulan PubL v2 uses a contributor-notice structure with conditions that can prevent termination. GPLv2 should not be assumed to contain GPLv3’s mechanism. The relevant texts include CC BY-SA 4.0 and Mulan PubL v2.

In MetInfo, the Supreme People’s Court considered a bespoke website-software EULA, not a standard copyleft license. Removing the required attribution could breach the agreement and the attribution right without turning already permitted downloading, copying and necessary modification into infringement of every economic right. The award was RMB 11,000, with additional relief. The lesson is to match the violated obligation to the permission and right at issue. Judgment (2021) Zui Gao Fa Zhi Min Zhong No. 1547.

5. Architecture is evidence, not a legal shortcut

Neither PRC legislation nor the reported cases supply an automatic equation between dynamic linking and a derivative work, or between an API call and independence. Moving code into a separate directory is not a reliable cure. Conversely, two components appearing in one product does not necessarily make them a single covered work.

The analysis should document several dimensions:

Code: copied expression, modified files, incorporated headers and interface definitions.
Build: linking, processes, plugins, build scripts and replaceability.
Function: whether modules can operate, be packaged, deployed and updated independently.
Delivery: whether the customer receives an integrated program or distinct products, and how licensing and interfaces describe them.
Proof: repositories, reproducible builds, diagrams, technical comparisons and expert evidence.

Three case patterns show why the details matter. The HBuilder plugin dispute turned in part on how license statements appeared in the relevant directories and release. The Buluanmai dispute distinguished a website’s front-end GPL code from independently structured back-end PHP code. The Luohe/Wanyou dispute reached a broader result where the defendant did not establish the independence of the sandbox component. These are different evidentiary records, not competing one-line rules about folders or interfaces.

6. What the main mainland decisions establish

HBuilder plugins

In Digital Heaven v Youzi, Beijing High People’s Court examined three plugins claimed by the plaintiff. GPL text elsewhere in HBuilder did not, on the court’s assessment of the release, establish that the claimed plugins were GPL-licensed. The appeal resulted in RMB 500,000 damages and RMB 210,000 reasonable expenses. The case should not be read as holding that every license applies only to its own directory, or that the plugins necessarily ran independently. The available text is a judgment mirror for (2018) Jing Min Zhong No. 471.

Front-end and back-end separation

In Buluanmai v Shanliang Fashion, the Supreme People’s Court distinguished the GPL front end from the PHP back end that the plaintiff asserted. Technical structure, function, presentation and independent deployment supported separation; interaction alone did not establish derivation. Copying the back end remained infringing. The relevant lesson is to prove independence, not merely name two parts of an application differently. Judgment mirror, (2019) Zui Gao Fa Zhi Min Zhong No. 663.

VirtualApp and commercial distribution

Luohe v Wanyou addressed GPLv3’s legal effect, a later attempt to restrict commercial use, source-code noncompliance and whether the defendant’s application was an integrated whole. Charging money was not itself inconsistent with GPL. The court treated the absence of required source and the failure to establish component independence as significant, awarded RMB 500,000 and ordered infringement to cease. The reasoning about source availability must be distinguished from the operative remedies: it was not an order to publish all source code to the world. Guangzhou IP Court, (2019) Yue 73 Zhi Min Chu No. 207.

In Luohe v Fengling, the Supreme People’s Court upheld infringement and RMB 500,000 damages. The small asserted proportion of copied files did not itself defeat liability. On the particular contribution and management record, the project manager could sue without a blanket conclusion that administrators own all contributions. The judgment also rejected the argument that GPLv3 necessarily required a pre-litigation notice-and-cure process. These holdings should remain tied to the facts and license terms. Judgment (2021) Zui Gao Fa Zhi Min Zhong No. 2063.

A claimant’s upstream breach is not a general copying license

The OfficeTen/OpenWrt dispute concerned GPLv2-based software. The Supreme People’s Court distinguished a developer’s possible noncompliance toward upstream rights holders from copyright in that developer’s own original contributions. The upstream holders were not parties. The defendant could not treat the claimant’s possible breach as a general entitlement to copy its code. The result did not invalidate GPL or eliminate a separate upstream claim. Court account of (2021) Zui Gao Fa Zhi Min Zhong No. 51.

Across these cases, commercially valuable software does not become damage-free because its source was accessible. Download volumes, functional contribution, commercial-license evidence, monetization and duration may matter. Equally, a license’s source obligation and a court’s chosen remedy are different questions.

7. Creative works, documents and fonts require their own analysis

CC BY-SA governs licensed material and shared adaptations, not necessarily every independent work collected alongside it. Attribution should identify the author as required, link to the license, retain relevant notices and identify changes. “Source: internet” is ordinarily an inadequate record of permission.

A translation or substantial adaptation may engage share-alike; an anthology of independent articles raises a different question. Charging access is not the same as imposing prohibited restrictions on the recipient’s licensed rights. Platform terms and digital restrictions must be checked separately. CC BY-NC-SA adds another issue: the noncommercial condition cannot be assumed satisfied merely because no individual download fee is charged. Commercial websites, advertising, paid courses and brand marketing require a fact-specific assessment or a separate permission.

The GNU Free Documentation License and Free Art License use different structures. Compatibility with Creative Commons is version- and condition-specific. These licenses should not be treated as substitutes for software licenses, which address source, object code, linking and related engineering issues. See GNU FDL 1.3 and the Free Art License.

Fonts are another frequent source of confusion. The font software, individual glyph designs, font names and a document typeset using the font are not the same subject matter. The SIL Open Font License addresses font software and reserved names. Its conditions do not ordinarily convert every document created with an OFL font into an openly licensed document. Keep the actual font license with embedded or distributed font files and assess modifications separately.

GNU’s translation notice also matters in Chinese disputes: unofficial translations should not replace the English license text. Preserve the original, a reliable translation and the version obtained. Creative Commons’ official Chinese legal texts have a different translation status.

8. Data and hardware do not fit the software analogy perfectly

For a dataset, begin with the protected interest: copyright in individual entries, originality in selection or arrangement, confidential information, contractual rights or a competition-law interest. Mainland China does not simply replicate the EU’s general sui generis database right. A license cannot create a statutory copyright in material that does not qualify, although contractual and competition-law questions may remain.

A publicly reported Mandarin speech-dataset dispute illustrates the distinction. The reported dataset was not protected as a compilation or trade secret, but its commercial interests received competition-law protection. A Creative Commons noncommercial condition helped inform the assessment of conduct. Because the report did not disclose a complete case number or full license designation, it should not be recast as a definitive CC BY-SA copyright precedent. The limitation is part of the finding.

ODbL distinguishes a database from certain products made from it; CDLA-Sharing uses its own data and enhancement concepts. Neither should be presumed to cover all model parameters or analytical outputs. Personal-information, data-security and cross-border requirements remain independent: public availability or a copyright permission is not a lawful basis for every processing activity.

OpenStreetMap illustrates the overlap. License compliance does not resolve Chinese surveying, mapping, geographic-information or publication requirements. Likewise, CERN OHL and TAPR OHL concern design materials and related obligations. They do not automatically clear patents, chip-layout rights, third-party firmware, trademarks, product certification or safety liability.

9. Turn the legal analysis into a release process

Intake

Record the component, upstream URL, version, commit, hash, SPDX identifier and acquisition date. Review LICENSE, COPYING, NOTICE, headers, README statements and download-page terms together. An unlicensed public repository is not presumed available for unrestricted reuse. Resolve contradictory commercial-use notices before relying on them.

Contributor provenance also matters. A project’s ability to offer a commercial license depends on its rights, not merely repository control. Assignments, contributor agreements, declarations and individual permissions serve different purposes. A Developer Certificate of Origin can support provenance without itself transferring every copyright. Keep evidence appropriate to the actual licensing model.

Design and development

Map processes, interfaces, containers, links and deployment units for reciprocity-sensitive dependencies. Where independence matters, implement real independent build, replacement and deployment capability. A diagram unsupported by the actual product offers little protection. Maintain a software bill of materials and keep unreviewed dependencies out of release branches.

Compatibility should be assessed on the exact licenses. GPLv2-only and Apache-2.0 present a different combination from GPLv3 and Apache-2.0. MPL secondary-license mechanisms and Mulan PubL’s particular AGPL exception have conditions; neither creates universal compatibility. Copyright-license compatibility also leaves patent, trademark and export-control analysis outstanding.

Delivery

Corresponding source must match what was delivered. A link to an unmodified upstream repository may omit the distributor’s modifications, necessary scripts or other required materials. Map each binary to its source package, notices, offer and required installation or relinking information. Keep required offers and download locations operational for the relevant period.

Customer appliances, mobile packages, container images, firmware and private deployments can all deliver software to another person. Different group entities, contractors and customers should not automatically be classified as “internal.” For network-triggered licenses, include the deployed service version and the user-facing source route in release controls.

Finally, inspect channel terms. App stores, cloud marketplaces, end-user agreements and DRM can impose restrictions inconsistent with upstream permissions. Separate rights in the public version, proprietary additions, support service and trademark. Before publishing source, remove credentials, personal information, confidential configuration and unrelated third-party materials without omitting source that the license actually requires.

Response to noncompliance

Preserve the shipped binaries, source, pages, downloads, contracts and logs. Identify the actual rights holder and provision; do not assume every demand has the same legal basis. Assess cessation, correction, replacement, a new release or a commercial permission against the specific cure mechanism. Notify affected downstream recipients where appropriate without purporting to revoke rights already obtained by compliant recipients.

For a dispute, prepare the rights chain, repository history, code comparison, reproducible build and technical explanation together. An argument that the claimant breached somebody else’s upstream license is not a substitute for showing your own permission or independent development.

10. The limits of the present evidence

The published mainland case record is strongest on software GPL decisions. Other license families may be widely used without a comparably developed published mainland case record. Judicial commentary is not a judgment; a first-instance decision is not a universal Supreme People’s Court rule; and reasoning that a program should be open-sourced is not necessarily an operative order compelling disclosure.

Those distinctions determine the appropriate confidence of an assessment. The practical task is to connect each conclusion to the license text, the applicable PRC rule, the actual product and the evidence available. A release-time LICENSE file is useful, but it cannot replace that chain of work.

References and license texts

The links below collect the principal statutes, license texts and judicial materials discussed above. The two expressly identified judgment mirrors in section 6 are secondary hosts; they should be checked against a court-issued judgment before use in proceedings.