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.

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

General

Account Creation for Local ScanningPR and Release Gating for Code Using Local ScannerPerforming Nightly Scans Using Local ScannerCLI Options for Local Scanner

CI/CD Integrations

Azure DevOps Server Setup for Local Code ScanningBitbucket Pipeline Setup for Local Code ScanningBamboo Setup for Local Code ScanningCircleCI Setup for Local Code ScanningGitHub Action Setup for Local On-Prem Code ScanningGitLab Self Managed Setup for Local Code ScanningJenkins Setup for Local Code ScanningTeamCity Pipeline Setup for Local Code Scanning

Operating Systems

Linux Setup for Local Code ScanningMac Setup for Local Code ScanningWindows Setup for Local Code Scanning

Other

Local Scanning in Existing SCM-Integrated Workspaces