English

Local Code Scanning

Local code scanning lets you analyze your source code directly on your own machines without sending any code to Aikido. It is useful when you want to test changes during development, work in isolated environments, or keep sensitive repositories fully local.

For most workflows we still recommend using the standard Aikido integrations as they give faster results and better coverage.

Before you start, make sure you have an Aikido account/workspace that supports local scanning. Follow Account Creation for Local Scanning.

To send Aikido a zip of a repository instead, follow Upload a Repository as a Zip. That upload sends the archive to Aikido, and Aikido stores it. Local scanning keeps the code on your machines.

If you are looking to scan container images instead, check the container image scanning docs.

General

Account Creation for Local Scanning PR Gating for Code Using Local Scanner Release Gating for Code Using Local Scanner Performing Nightly Scans Using Local Scanner CLI Options for local code scanning

CI/CD Integrations

Azure DevOps Server Setup for Local Code Scanning Bitbucket Pipeline Setup for Local Code Scanning Bamboo Setup for Local Code Scanning CircleCI Setup for Local Code Scanning GitHub Action Setup for Local On-Prem Code Scanning GitLab Self Managed Setup for Local Code Scanning Jenkins Setup for Local Code Scanning TeamCity Pipeline Setup for Local Code Scanning

Operating Systems

Linux Setup for Local Code Scanning Mac Setup for Local Code Scanning Windows Setup for Local Code Scanning

Other

Local Scanning in Existing SCM-Integrated Workspaces