{"id":58515,"date":"2026-09-21T10:55:46","date_gmt":"2026-09-21T02:55:46","guid":{"rendered":"https:\/\/www.1ai.net\/?p=58515"},"modified":"2026-09-21T10:55:46","modified_gmt":"2026-09-21T02:55:46","slug":"%e8%a2%ab%e8%b4%a8%e7%96%91%e5%81%b7%e4%bc%a0%e4%bb%a3%e7%a0%81%e5%90%8e%e6%99%ba%e8%b0%b1-zcode-%e5%ae%98%e5%ae%a3%e5%bc%80%e6%ba%90%ef%bc%9a%e5%b7%b2%e5%ae%8c%e6%88%90%e6%95%b4","status":"publish","type":"post","link":"https:\/\/www.1ai.net\/en\/58515.html","title":{"rendered":"The ZCode official declared the source after questioning the \"Stealing Code\": completed the overhaul and apologized to all users"},"content":{"rendered":"

The news of September 21stZhipu<\/a> ZCode announced today that the ZCode product safety issue for community feedback is not the only one that has been reported by the governmentOfficially finished the overhaul and apologized to all users<\/strong>.<\/p>\n

\"ebc34765j00tlp1fe00cxd000v90rlp\"<\/p>\n

ZCode Open Source<\/a><\/strong>\u00a0(https:\/\/github.com\/zai-org\/ZCode), handing over the code to community monitoring, making ZCode open and transparent\u3002<\/p>\n

\n
    \n
  • Thanks very much to the community developers who have previously discovered the ZCode problem, we will then establish a normal product safety loophole mechanism, welcome the ongoing inspection and feedback by the developers ' partners, and we will pay back the scale of the problem\u3002<\/li>\n
  • For the code data mentioned in the community, we are committed to not retaining them, nor have they ever been used in model training. Upon completion of the renovation, we invited the China Institute of Information and Communication and the Green League technology to conduct a security audit, the results of which are as follows:<\/li>\n
  • According to a technical assessment conducted by the China Institute of Information and Communication Technology, the zcode-prod Aliyun Oss storage drum is confirmed as cloud zero. ZCode v3.14.0 The ZCode v3.14.0 client has completed a security overhaul, has removed Repo Wiki and has cut off the local warehouse snapshot generation and upload links\u3002<\/li>\n
  • Based on a review of the Green League technology, it has been confirmed that all data objects within the zcode-prod (Ali Cloud Object Storage OSS) and the storage drum itself have been removed. ZCode v3.14.0 The client has been overhauled, the Repo Wiki entrance and the corresponding generation link have been removed, and no functional path has been found to trigger local warehouse snapshots or out-of-files\u3002<\/li>\n
  • Again, I apologize for your continued monitoring\u3002<\/li>\n<\/ul>\n<\/blockquote>\n

    As reported by 1AI on 18 September, in response to community discussions on the uploading of code library data, ZCode, a programming product under the flag of the spectra, apologized to affected users through official spectrograph groups and issued a response that self-checking had been completed at the first time and that the related issues had now been repaired\u3002<\/p>\n

    Officially, the problem stems from ZCode's \u201cCode Bank Index\u201d function, which is designed to help users generate a local repository index to support the recovery of session points, including historical versions, the retreat of historical versions and Repo Wiki (Code Warehouse Knowledge Bank)\u3002<\/p>\n

    Officially known as the Repo Wiki function may trigger the upload of warehouse data when generating the Wiki page (the Knowledge Bank page). The Wiki page will be destroyed and will not be saved as soon as it is generated in the cloud. Some users are affected by the default start-up of the functionality\u3002<\/p>","protected":false},"excerpt":{"rendered":"

    On 21 September, according to the news, ZCode announced today that the official restructuring had been completed in response to community feedback on the safety of ZCode products and apologized to all users. The ZCode Open Source (https:\/\/github.com\/zai-org\/ZCode) has been put under community supervision to make ZCode open and transparent. Thanks very much to the community developers who have previously discovered the ZCode problem, we will then establish a normal product safety loophole mechanism, welcome the ongoing inspection and feedback by the developers ' partners, and we will pay back the scale of the problem. We are committed to keeping the code data mentioned in the community, and have never used them for model training. After the overhaul<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[146],"tags":[8068,219,2680],"collection":[],"class_list":["post-58515","post","type-post","status-publish","format-standard","hentry","category-news","tag-zcode","tag-219","tag-2680"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/posts\/58515","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/comments?post=58515"}],"version-history":[{"count":0,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/posts\/58515\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/media?parent=58515"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/categories?post=58515"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/tags?post=58515"},{"taxonomy":"collection","embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/collection?post=58515"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}