> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/changelog/q2-2026/new-code-audit-pentest-grade-reasoning-on-your-source-code-no-environment-required..md).

# New - Code Audit: Pentest-grade reasoning on your source code, no environment required. 🚀

Code Audit runs pentest-grade security reasoning directly on your source code, searching for logic flaws and other vulnerabilities that pattern-based scanners can't find.

Connect your codebases, confirm the price in credits, and start the audit. No staging URL, crawl, or pentest scope setup required.

<figure><img src="/files/cqqt4g454CQciuwaSmNp" alt=""><figcaption></figcaption></figure>

### Why Teams Use Code Audit

**Reasoning, not pattern matching**

Find hard-to-find bugs like cross-tenant data leakage that classical pattern matching misses.

**10× cheaper than a pentest**

Get pentest-depth reasoning across your codebase in minutes, not hours, and run it on demand.

**Zero setup, just connect a repo**

No staging environment, traffic to replay, or agents to deploy. Point it at your source and start the audit.

**Mythos-ready defense**

Defend against the kind of attacks frontier models now make trivial, with reasoning that matches what attackers can do.

### How Code Audit Fits into Aikido

Code Audit is a sibling to Aikido Pentest. It uses the same agentic engine and issue experience, but stays fully codebase-focused.

Findings include code-based evidence, root cause analysis, remediation guidance, and AI-powered [AutoFix](https://help.aikido.dev/autofix-and-remediation/overview-aikido-autofix) for creating remediation PRs with a few clicks.

Pricing is shown upfront in credits before you start. Cost depends on the size and complexity of the selected codebases.

Use it when you want deep reasoning on source code without setting up a live environment. It works especially well for hard-to-test-by-URL codebases like:<br>

* mobile apps,
* smart contracts,
* desktop apps,
* embedded software, and
* libraries.

→ [Try out Code Audit](https://app.aikido.dev/agentic-review)\ <br>


---

# 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://help.aikido.dev/changelog/q2-2026/new-code-audit-pentest-grade-reasoning-on-your-source-code-no-environment-required..md?ask=<question>&goal=<endgoal>
```

`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.
