Create a Code Security Audit
Connect repositories, confirm the credit cost, and start an AI Code Analysis.
The create flow is two steps: pick the repositories you want analyzed, then confirm the credit cost and start.
Prerequisites
Before you start, make sure:
You have the Manage Pentests and AI Code Analysis permission. Without it, you can't create analyses or open existing ones.
At least one repository is connected. Self-scanned repositories aren't eligible and are excluded from the picker. You can pick up to 6 repositories per analysis.
Your wallet has enough credits to cover the quoted cost. You can top up from inside the create flow if needed. See Wallet & Credits for purchase details.
Set up the analysis
To launch the wizard, click AI Code Analysis in the main navigation, then click Create Audit in the page header.
Connect Repositories
Open the Repositories picker and select up to 6 connected repositories.
To keep a monorepo audit focused, click Exclude Paths next to a selected repository and add the directories you don't want analyzed. For example, exclude unrelated applications or services that aren't part of this audit.
Click Continue to move to pricing.

Exclude unrelated applications or services, not documentation, READMEs, or other non-code assets. Aikido can use those files as architectural context to investigate security risks more accurately.
Continue stays disabled until at least one repository is selected. Clicking Cancel on this step takes you to your repositories list, which is useful if you still need to connect repos before continuing.
Pricing
Aikido calculates the credit cost for your selection. When the estimate is ready, the price shows next to Full AI Code Analysis, and your balance shows in the footer. If you're short on credits, click Add Credits to top up.
Click Start Audit to launch.
After Start Audit, Aikido takes you to the assessment detail page, where you can follow progress and read findings as they land. See Track Progress and Findings.
FAQ
Why is there a 6-repo cap?
AI Code Analysis focuses agent attention on a coherent set of codebases. Beyond 6 repositories, the analysis tends to lose focus and quality drops. If you genuinely need more in a single analysis, contact support. The tooltip on the Repositories field links to the same path.
Need help?
Open the Intercom chat in the bottom right corner if the credit estimate looks off or the picker doesn't show a repository you expect.
Last updated
Was this helpful?