> For the complete documentation index, see [llms.txt](https://kawa-fi.gitbook.io/kawa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kawa-fi.gitbook.io/kawa/audits.md). # Audits At Kawa, we are deeply committed to ensuring the security and stability of our platform. We recognize the importance of thorough and independent audits to maintain the highest level of trust and confidence in our code. While our codebase is still under development, we have not yet conducted any audits. Upon completion of our code, we will engage multiple reputable auditing firms to perform comprehensive security audits. These audits will help to identify and address any potential vulnerabilities, ensuring that our users can confidently interact with our platform. We will regularly update this section with information about the audits performed, the names of the auditing firms, and any findings or improvements made as a result of the audits. Our goal is to be transparent with our community and to continuously enhance the security of the Kawa platform. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kawa-fi.gitbook.io/kawa/audits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.