This CLI tool can help integrate Aikido Security scans into any custom CI pipeline such as Jenkins, CircleCI,... If you are looking to add checks to a Github, Azure Repos,.. pull request, you do not need this package and you can use our native plugins.
The quickest way to get started is to install the cli tool as a global package.
# npm users
$ npm install -g @aikidosec/ci-api-client
# yarn users
$ yarn global add @aikidosec/ci-api-clientAfter installation, you'll need to setup your Aikido API key. You can add your key by requesting a token on the Continuous Integrations page in the Integrations section of the Aikido web platform. Click the "Start integrating" link and setup your key globally by executing
$ aikido-api-client apikey <your-api-key-here>~/.config/configstore/aikido-api-client.json. If you don't want this behaviour (e.g. for security related issues), you can also provide your API key to aikido-api-client by adding --apikey <your-api-key-here> to every command. However, for the examples below, we'll assume you've used aikido-api-client apikey <your-api-key-here> to save your API key. If --apikey is provided while a key is set in the configuration file on disk, the key that was provided with --apikey will be used.
The example below shows how to use the scan-release command. The use case here is to block a new build or a new release as long as issues are still open.
$ aikido-api-client scan-release <repository_id or repository_name> <commit_id>Usage: Aikido API Client scan-release [options] <repository_id> <commit_id>
Run a release scan of an Aikido repo.
Arguments:
repository_id The internal GitHub/Gitlab/Bitbucket/.. repository id you want to scan.
commit_id The commit you want to scan
Options:
--no-fail-on-dependency-scan Don't fail when scanning depedencies. Default is to fail on new CVE
--fail-on-sast-scan Let Aikido fail when new static code analysis issues have been detected
--fail-on-iac-scan Let Aikido fail when new infrastructure as code issues have been detected
--fail-on-secrets-scan Let Aikido fail when new exposed secrets have been detected
--minimum-severity-level <level> Set the minimum severity level. Accepted options are: LOW, MEDIUM, HIGH and CRITICAL. (choices: "LOW", "MEDIUM",
"HIGH", "CRITICAL")
--poll-interval [interval] The poll interval when checking for an updated scan result (preset: 10)
--sla-mode Let Aikido only fail only on open issues that have gone out of SLA.
--json Output the scan result as JSON (gate_passed and issue_breakdown)
-h, --help display help for command
The example below shows how to use the upload-coverage command. The use case here is to upload LCOV or Cobertura coverage reports from your CI pipeline so Aikido can track coverage per commit and branch. --file-paths accepts one or more literal paths or glob patterns (for example coverage/**/lcov.info). Absolute paths and .. segments are not allowed.
$ aikido-api-client upload-coverage \
--commit-sha <commit_sha> \
--branch-name <branch_name> \
--repository-id <repository_id> \
--file-paths coverage/lcov.info
# Or match multiple reports with a glob:
$ aikido-api-client upload-coverage \
--commit-sha <commit_sha> \
--branch-name <branch_name> \
--repository-id <repository_id> \
--file-paths 'coverage/**/*.info' 'coverage/**/cobertura.xml'Usage: Aikido API Client upload-coverage [options]
Upload LCOV or Cobertura coverage reports to Aikido (with repository_source_paths and EOF metadata).
Options:
-c, --commit-sha <commitsha> The commit SHA for this CI run
-b, --branch-name <branchname> The branch name for this CI run
-f, --file-paths <paths...> Path(s) or glob pattern(s) to LCOV or Cobertura coverage report(s). Format is detected from each filename.
-ri, --repository-id <repositoryid> The scm repository id
-h, --help display help for command
The CLI will spawn a cloud-based scan and then report scan progress. It will exit with exitCode 0 if the scan was successfull (gate_passed: true). The process will exit with exitCode 10 if the scan was unsuccesfull (gate_passed: false). If anything else goes wrong (e.g. API unavailable, scanning unavailable, other unexpected issue) the process will exit with exitCode 1.
If you want the scan to run quietly (without output), you can add the --quiet option to the command. If you want machine-readable output instead, add --json to scan-release. That prints a JSON object with gate_passed and issue_breakdown and skips spinners and other extra info.
Please note that the repository_id which you need to provide to the CLI is the unique ID of the Git provider you are using, not the ID of the repository in Aikido. You can also find this ID in Aikido, by going to the repository's detail page and clicking on the Git provider's icon in the header. Alternatively, you can pass the repository name as it is defined in Aikido.
# For more options and combinations, check the help output
$ aikido-api-client help scan
$ aikido-api-client help scan-releaseUploading custom test results (supported by the scan command only):
$ aikido-api-client upload --repository-id <repository_id> --type checkov --file <path_to_payload_file>
# For more options and combinations, check the help output
$ aikido-api-client help uploadFor more information about these parameters, please refer to aikido-api-client help, aikido-api-client help scan, aikido-api-client help scan-release or aikido-api-client help upload, or the public ci api page.
For more information about all available commands and options, execute:
$ aikido-api-client help$ aikido-api-client help <command>If you are missing functionality in this cli tool, please feel free to add it. If you've detected a bug, please submit a PR. Check out CONTRIBUTING.md for more information.