> For the complete documentation index, see [llms.txt](https://canary-1.gitbook.io/canary/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canary-1.gitbook.io/canary/trust-and-transparency/audits.md).

# Audits

Independent review of the Canary DVN code.

The DVN code was audited with zero security findings, and the latest version of the code is audited on an ongoing basis, deliberately using different audit firms.

## How auditing fits the standard

* **Rolling review.** The latest version of the code is reviewed on a rolling basis rather than once, so the audited code and the running code do not drift apart.
* **Different firms.** Using different firms brings different methods and different blind spots to each review.
* **Attested code.** Auditing matters most when you can prove the audited code is the code that runs. Every verification produces a hardware attestation of exactly which code executed, as described on [Trusted execution](/canary/how-it-works/trusted-execution.md).
* **Small surface.** The client is compact by design, small enough to fit inside an enclave without unnecessary dependencies, which keeps the audit surface small.