Code security audits by an independent oversight committee
In the AI era, code transparency no longer has to mean publishing the source. 开途 Kaitu has set up an independent oversight committee whose members rigorously audit the core code and publish their conclusions — a more responsible way to protect every user.
April 14, 2026
The committee is made up of independent security experts who aren't driven by commercial interests. Its conclusions are traceable and verifiable — more authoritative than simply putting code online.
In the AI era, fully public source code means certain governments can quickly find and exploit vulnerabilities. Committee audits strike the best balance between transparency and security.
The committee's audit reports are published for all users. No need to read source code — anyone can see the security findings and the fixes made.
Every major release triggers a committee re-review, creating a continuous loop rather than a one-time code dump that nobody maintains afterwards.
Audit requests start only after 开途 Kaitu verifies the requester's credentials, and the requester's identity must be disclosed publicly on this website. The following three types of parties may initiate a formal audit:
A standing body of independent security experts. It can initiate audits on its own authority without a separate request, and its conclusions must be made public.
Operators and enterprise customers with a partnership agreement with 开途 Kaitu can submit audit requests through the partner channel; conclusions are shared within the scope of the agreement.
Third-party organizations holding internationally recognized security certifications (such as ISO 27001, CREST or OWASP-certified bodies) can initiate targeted audits after credential verification.