Secrets scanner
Last updated: Oct 22, 2026
Quick scan vs. configuration file
The secrets scanner supports two modes of operation.
Quick scan — scan a file or directory directly from the command line, without a configuration file. Only verified rules are applied:
ss scan /path/to/repositoryThis outputs findings to the console by default.
Use --strict to exit with a non-zero status code when secrets are found,
which is useful for CI/CD pipelines:
ss scan /path/to/repository --strictConfiguration file — use a YAML configuration file for more advanced scenarios: including or excluding specific paths, enabling preview rules, or writing results to a file:
ss scan --config config.yamlThe rest of this page describes the configuration file options in detail.
For common configuration file keys that apply to all scanners, see Use a configuration file.
Specific configuration file keys
The following key is available for the secrets scanner, and it can be used to configure secret detection over a repository.
ss
This key configures which files are scanned and how detection is tuned. All options are optional:
include: Paths to files or directories to scan, relative toworking_dir. If omitted, the entireworking_diris scanned.exclude: Gitignore-style patterns for files or directories to exclude. The.git/directory is always excluded automatically.feature_preview: When set totrue, enables detection rules that are still in beta and pending approval. Defaults tofalse.
For example:
ss:
include:
- src/
- config/
exclude:
- vendor/
- "**/*.lock"
feature_preview: falseOutput configuration
Use the top-level output key to write results to a file:
file_path(optional): Path where the report will be written. The format is inferred from the file extension: use.sariffor a SARIF 2.1.0 report, or.csvfor a CSV report. If omitted, findings are printed to the console only.
output:
file_path: /results/fluid-attacks-results.sarifConfiguration file examples
Scanning a repository
language: EN
working_dir: /path/to/repository
output:
file_path: /results/fluid-attacks-results.sarif
ss:
include:
- src/Excluding paths
language: EN
working_dir: .
output:
file_path: /results/fluid-attacks-results.sarif
ss:
include:
- src/
- config/
exclude:
- vendor/
- "**/*.lock"
- "**/node_modules/"Enabling preview rules
language: EN
working_dir: .
output:
file_path: /results/fluid-attacks-results.sarif
ss:
feature_preview: trueFailing the pipeline on findings
language: EN
strict: true
working_dir: .
output:
file_path: /results/fluid-attacks-results.sarif
ss:
include:
- src/Exporting results as CSV
language: EN
working_dir: .
output:
file_path: /results/fluid-attacks-results.csv
ss:
include:
- src/Have a question about the scanner or encountered 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.