English

AI Code scan

Pentest-grade reasoning on your source code, no environment required.

AI Code scan is the security-focused scan type in AI Scans. It uses pentest-grade reasoning to identify vulnerabilities, logic flaws, and exploit chains in your source code.

You don't need a staging URL, a crawl, or pentest scope setup. Connect a repository, confirm the price in credits, and start the scan.

Create an AI Code scan
Select the scan type, choose repositories, and confirm the credit cost.
Track progress and findings
Status vocabulary, detail tabs, and how to read findings.
What an AI Code scan finds
Vulnerability classes covered, plus what still needs a live target.

#How it works

#Connect repositories

You pick the repositories in the create flow. AI Code scan only needs source code, with no live target, domains, or auth setup. See Aikido Never Stores Your Code for how your source is handled during an analysis.

#Agents reason about your code

Multiple security agents work through the connected codebases together, chaining context across files to surface architectural and logic flaws that traditional static scanners can't see. Commit AGENTS.md in the repository when you want that reasoning to follow your architecture and accepted risks. See Guide Agents with Repository Files.

#Read the findings

Findings land in the Issues tab on the assessment and in the Feed, alongside everything else Aikido detects. Each finding includes a summary, root cause, remediation, and code-based Evidence. See Track Progress and Findings for the full read-out.

#Pricing and credits

AI Code scan is paid for with Aikido credits.

  • The Pricing step shows the exact credit total before you commit.
  • Cost depends on the size and complexity of the codebases you select. Larger or more sprawling selections cost more.
  • Credits are charged when you click Start Audit.

For how these fit with SAST, Deep Review, dynamic application security testing (DAST), and Attack Surface Monitoring, see Which Aikido product should I use?.

#AI Code scan vs Aikido Pentest

Both run the same agentic engine, but they answer different questions. AI Code scan reasons about your source code. Aikido Pentest exercises your running application.

#Use an AI Code scan when:

  • You want deep code reasoning on logic and architectural flaws, including broken access control, privilege escalation, and multi-step exploit chains, without configuring a live environment.
  • You don't have a stable staging or QA target, or auth flows aren't ready for live testing.
  • Your codebase is hard to set up for live testing, such as a mobile app, desktop app, embedded system, or library. For a review focused on on-chain contracts, use AI Smart Contract scan.
  • You need a fast turnaround with minimal setup: connect a repository, confirm credits, start.
  • You want to validate changes in source before they ship to a live deployment.

#Use Aikido Pentest when:

  • You have a live target and want to validate real exploitability with real traffic.
  • You want runtime evidence, including reproduction requests, attack-surface mapping, and live agent activity.
  • Your scope includes domains, authenticated user roles, and crawl-discovered endpoints beyond what's visible in source.
  • You need Exploit Further on validated findings to escalate exploitation against the running app and prove real impact, such as whether sensitive data can actually be reached.
  • You're satisfying compliance frameworks like SOC 2 or ISO 27001 that expect a live pentest.

#AI Code scan vs SAST

Both look at your source code, but they work differently. Static application security testing (SAST) flags patterns, such as a tainted parameter, a risky API call, or a missing check. AI Code scan reasons about intent and context across files, so it can identify issues that need an attacker's perspective. The two are complementary.

#Use an AI Code scan when:

  • You want to catch logic and architectural flaws that pattern-matching can't see, including broken access control, privilege escalation, business logic bypasses, and multi-step exploit chains.
  • You need cross-file reasoning that follows references through services, modules, and helpers.
  • You're analyzing a high-stakes change, release, or codebase and want attacker-style review on top of your continuous scans.
  • You want deeper context on a specific finding, including the root cause, exploit path, and remediation, instead of just a pattern hit.

#Use SAST when:

  • You want fast, every-commit feedback on common vulnerability patterns, including injection sinks, taint flows, hard-coded secrets, dangerous APIs, and infrastructure as code (IaC) misconfigurations.
  • You need broad, continuous coverage across every pull request and branch without spending credits per scan.
  • You're enforcing pull-request gates in CI/CD on known-bad patterns.

#FAQ

#Why doesn't an AI Code scan need a live URL?

AI Code scan reads and reasons about your source code directly. There's no crawl phase, traffic replay, or live exploitation, so there's no environment to point at. For live testing against a deployed target, use Aikido Pentest.

#Can I retest an AI Code scan finding?

Yes. Once you've pushed a fix, use Re-test on the finding to have Aikido re-check it against your latest code. Exploit Further is an Aikido Pentest action. It needs a running app. Retesting for the other scan types is covered in Track Progress and Findings.

Create an AI Code scanSelect AI Code scan, choose repositories, and confirm the credit cost. Guide Agents with Repository FilesCommit markdown in the repository so Aikido agents can follow your architecture, trust boundaries, and accepted risks. AI ScansChoose an AI Code, AI Data Exposure, AI Cloud, or AI Smart Contract scan.