All stories
ZCode Industry Developing

ZCode open-sourced after an unauthorized data-upload controversy

The Next Web reports that Z.ai apologized and removed ZCode's repository-upload workflow. Missing development history limits verification, and one company's serious allegation was withdrawn.

Sources (3)

Why now The English report distinguishes the removed upload workflow, the limits of post-fix assessments and an allegation that was retracted. Remediation and verification
GitHub preview for the open-source ZCode repository
GitHub preview for the open-source ZCode repository

What happened

The Next Web reported on September 22 that Z.ai apologized for ZCode uploading local repositories without consent, removed the Repo Wiki feature and disabled the repository-snapshot upload workflow. The company said the fix shipped in version 3.14.0 and published the tool’s source code.

According to the report, the researcher who investigated the behavior confirmed that the upload pipeline was absent from the published code. The same researcher found that the public repository contained only two commits, limiting inspection of the earlier implementation.

What the report establishes

The Next Web distinguishes a large encrypted snapshot that failed to upload from a smaller snapshot of a public repository that reached the server. Those are different outcomes and should not be described as if every captured workspace was successfully transmitted.

The report says outside assessments checked the cloud storage bucket after the fix. Those checks address its later state; they do not reconstruct everything that may have passed through it earlier.

What is verified, and what is not

The Next Web also reports, citing Reuters, that Chengming Technology withdrew its allegation that six coding workspaces had been uploaded, saying it had relied on wrong evidence. That withdrawn allegation must not be presented as an established data leak or used as independent confirmation of the other findings.

The published repository is not a forensic copy of the closed build implicated in the report. It does not, by itself, prove what the older version transmitted or establish that the current version uploads complete source code. This account remains attributed reporting rather than an independent security audit by AITrending.

What remains open

As of the September 22 report, the full assessment report, the duration of the earlier behavior and the number of captured workspaces remained unresolved. Those are the questions to check in subsequent English disclosures. The status remains developing; a post-fix storage check is not a complete historical account of data handling.