Added 2026/08/2026-08-18-zhejiang-public-information-industry.md

2026/08/2026-08-18-zhejiang-public-information-industry.md

@@ -0,0 +1,241 @@
+Dear GitHub [private] Team,
+
+Thank you for your message dated [private]. Please treat this document as our revised and complete DMCA takedown notice for Ticket 4615624. It replaces and restates our previous submissions in full. We have added a detailed description of the original copyrighted work, the ownership and development chain, the evidence of copying, and the updated status of the former upstream repository.
+
+
+
+1. Copyright owner and authorization
+
+
+
+Copyright owner: Zhejiang Public Information Industry Co., Ltd.
+
+
+
+I, [private], am authorized to act on behalf of the copyright owner and to submit this DMCA takedown notice.
+
+
+
+Authorized representative: [private]
+
+Email: [private]
+
+Telephone: [private]
+
+Physical address: [private]
+
+
+
+The [private] project records contain submissions and development activity associated with Hangzhou Yanlei Network Technology Co., Ltd.. That company was the outsourced development and implementation company. The customer and actual copyright and intellectual-property rights holder for the CPCT system is Zhejiang Public Information Industry Co., Ltd.. The appearance of the outsourced developer's name in commit records does not constitute a public license or permission for any GitHub user to publish or distribute the source code.
+
+
+
+2. Detailed description of the original copyrighted work
+
+
+
+The copyrighted work is the complete source code of the CPCT internal business system, including its source files, original code expression, software architecture, module structure, business logic, configuration files, build files, project-level files, and Git version history.
+
+
+
+The CPCT system includes, without limitation, the following modules and components:
+
+
+
+cpct-cache; cpct-common; cpct-count; cpct-dtts-tasktracker; cpct-dubbo-cpc-ser; cpct-dubbo-cpc; cpct-dubbo-eventApi; cpct-dubbo-label; cpct-dubbo-log; cpct-dubbo-server; cpct-es; cpct-eslog; cpct-label-statistic; cpct-open-api; cpct-service; cpct-shiro; cpct-web; transaction-logs; pom.xml; README.md; and related source files, resources, configuration files, and project history.
+
+
+
+This is proprietary, confidential, non-open-source software developed for the company's internal business use. It has never been released or licensed to the public under an open-source license.
+
+
+
+The software was created and maintained through the company's commissioned development and internal maintenance arrangements. All relevant copyright and intellectual-property rights are owned by Zhejiang Public Information Industry Co., Ltd. under the applicable outsourcing, employment, and intellectual-property arrangements.
+
+
+
+The project was initially established and maintained on the company's [private] repository in approximately 2018. In 2023, the official project codebase was migrated to the company's private [private] platform at [private]. The private [private] repository contains the authoritative source code, complete development history, version iterations, and more than 2,000 internal commit records.
+
+
+
+3. Authoritative source and former upstream repository
+
+
+
+The authoritative version of the CPCT source code is maintained on the company's access-controlled private [private] platform. There is no authorized public source-code release.
+
+
+
+The GitHub fork page currently identifies the former upstream repository as:
+
+
+
+[private]
+
+
+
+This former upstream repository has now been deleted from GitHub. It is not merely closed, archived, or changed to private. The URL currently returns a not-found response.
+
+
+
+Earlier correspondence referred to [private]. The current GitHub fork page identifies the parent as [private]. This difference is noted for the record. The reported public fork is unambiguously:
+
+
+
+https://github.com/suevip1/cpct
+
+
+
+4. Infringing repository and scope of infringement
+
+
+
+The repository at issue is:
+
+
+
+https://github.com/suevip1/cpct
+
+
+
+This repository is publicly accessible and is identified by GitHub as a fork of the former upstream repository.
+
+
+
+I have reviewed the repository and believe that the entire repository is infringing. The infringement is not limited to one isolated file. It includes the publicly accessible source tree, module structure, configuration files, project files, business logic, code expression, and associated Git history.
+
+
+
+At the time of this notice, the public repository displayed approximately 5,505 commits and included the CPCT modules and files described above.
+
+
+
+5. Evidence establishing ownership and copying
+
+
+
+The attached exhibits demonstrate that the public repository contains the company's proprietary CPCT source code:
+
+
+
+a. The [private] commit records for the company's CPCT project correspond in timing, sequence, and operation details with the commits shown in the public GitHub repository.
+
+
+
+b. The company's private [private] repository contains the same project structure, module names, file paths, and development history as the reported repository.
+
+
+
+c. Code structures and code excerpts in the private company repository are identical to the corresponding structures and excerpts in the public repository.
+
+
+
+d. The configuration files contain the same internal database connection information, including database addresses, database names, account information, and other internal configuration details. Sensitive values have been redacted from the attached exhibits.
+
+
+
+e. The company's internal repository shows continuous maintenance and migration of the CPCT project, including more than 2,000 internal commits and the 2023 migration from [private] to the company's private [private] platform.
+
+
+
+These materials establish that the GitHub repository is an unauthorized copy of the company's proprietary CPCT codebase, rather than an independently developed project.
+
+
+
+6. Lack of authorization or license
+
+
+
+The company has never authorized the public release, publication, distribution, copying, or forking of the CPCT source code.
+
+
+
+The former employee who created or uploaded the original GitHub repository has left the company. The original repository was associated with a personal GitHub account, and the company could not access or manage that account because of personal email and device-verification requirements.
+
+
+
+The company has not granted the user suevip1, or any other GitHub user, a license or permission to publish or distribute the CPCT source code.
+
+
+
+The company also attempted to contact the repository owner through GitHub, but no valid response was received.
+
+
+
+7. Updated repository status and requested remedy
+
+
+
+The deletion of the former upstream repository does not resolve the infringement because the public fork remains independently accessible.
+
+
+
+We respectfully request that GitHub:
+
+
+
+1) disable the public repository https://github.com/suevip1/cpct;
+
+2) remove the infringing CPCT source code and associated public repository content from public access;
+
+3) process the entire repository, including its source files, configuration files, project structure, and Git history, because the entire repository is infringing; and
+
+4) confirm that the public fork has been taken down under GitHub's DMCA process.
+
+
+
+The requested remedy is removal or disabling of the reported content. Adding attribution, changing the README, or making limited file changes would not resolve the infringement because the repository as a whole contains the company's proprietary source code.
+
+
+
+8. Access-control and security information
+
+
+
+The original CPCT codebase was maintained in private, access-controlled company repositories. Access was restricted through authentication, repository permissions, and role-based access controls.
+
+
+
+The public GitHub repository was created from a copy made during a limited period when the former upstream repository was unintentionally accessible. After the company restored access controls and the former upstream repository was subsequently deleted, the fork continued to expose the copied proprietary source code publicly.
+
+
+
+The primary basis of this notice is direct copying and unauthorized public distribution of copyrighted source code. The copied repository also contains confidential internal configuration information and creates an information-security risk.
+
+
+
+9. Required statements
+
+
+
+I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, its agent, or the law. I have taken fair use into consideration.
+
+
+
+I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
+
+
+
+I have read and understand GitHub's Guide to Filing a DMCA Notice:
+
+
+
+https://docs.github.com/en/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice
+
+
+
+Please process this document as our complete revised DMCA takedown notice under Ticket 4615624.
+
+
+
+Electronic signature:
+
+
+
+/s/ [private]
+
+
+
+[private]
+
+Authorized representative of Zhejiang Public Information Industry Co., Ltd.