SCA scanner
Last updated: Oct 28, 2026
For the common configuration file keys of all the scanners, read Use a configuration file.
Specific configuration file keys
The SCA scanner has this key. Use it to do an SCA analysis of a repository.
sca
This key has two configuration options:
include(optional; if you do not use it, the scanner scans the fullworking_dir): The paths to the files or directories to analyzeexclude(optional): The files or directories to exclude from the analysis
For example:
sca:
include:
- relative/path/to/file
- relative/path/to/directory/
# Optional keys
exclude:
- test/To know how to specify paths in the include and exclude subsections,
read Use a configuration file.
Configuration file example
This is an example of a configuration file with many optional keys:
namespace: my_app
working_dir: ./
commit: e59607b9de3ef4c13d292705fg3da1ff0c67eb38
language: EN
output:
file_path: /fluid-attacks-results.csv
format: CSV
checks:
- F052
sca:
include:
- src/front/package-lock.json
- "*.json"
exclude:
- src/**/test/package.jsonAnalyze Docker images
Fluid Attacks will deprecate this function in a short time. To scan Docker containers, use the Container scanner of Fluid Attacks.
The SCA image can also analyze Docker images.
To do this,
use the sbom key.
sbom
This key has these basic options:
source_type(mandatory): Sets the type of source to analyze. The correct values are:docker: A Docker image from a container registrydocker-daemon: A local image through the Docker daemon (available only on Linux systems)ecr: An image hosted on Amazon ECRecr-with-credentials: An ECR image with explicit AWS credentialsdir: A local directory
image_uri(mandatory for Docker sources): The unique identifier of the image that you want to analyze.docker_credentials(optional): The credentials to authenticate to a container registry:username(optional): The username that owns the Docker image in the container registry that you select.password(optional): The password or token with read access rights to the image.use_docker_daemon(optional): When you set it totrue, the scan connects to your Docker daemon to analyze images. This option helps you scan local images. It is available only on Linux systems.
aws_credentials(optional): The AWS credentials for images on ECR:region(optional): The AWS region for images on ECR. The default value isus-east-1.access_key_id,secret_access_key,session_token(optional): AWS credentials with read access to the ECR image.
Configuration file example for Docker image analysis
Fluid Attacks will deprecate this function in a short time. To scan Docker containers, use the Container scanner of Fluid Attacks.
This is an example of a configuration file to analyze a Docker image on GHCR:
language: EN
output:
file_path: /working-dir/fluid-attacks-results.csv
format: CSV
sbom:
source_type: docker
image_uri: docker://ghcr.io/myuser/my-img:latest
docker_credentials:
username: myuser
password: ghp_my_secret_tokenThis is an example of a configuration file to analyze a local image (available only on Linux systems):
language: EN
output:
file_path: /working-dir/fluid-attacks-results.csv
format: CSV
sbom:
source_type: docker-daemon
image_uri: alpine:3.17Do you have a question about the scanner, or did you find a problem? Read "Scanner FAQ".
Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' pentesting team, complete this contact form.