# Build a Baseline / Detect Only New Secrets There are situations where a repository already contains checked‑in secrets, but you want to ensure no **new** secrets are introduced. A baseline file lets you document the known findings so future scans only report anything that is not already in that list. The easiest way to create a baseline is to run a normal scan with the `--manage-baseline` flag (typically at a low confidence level to capture all potential matches): ```bash kingfisher scan /path/to/code \ --confidence low \ --manage-baseline \ --baseline-file ./baseline-file.yml ``` This generates a YAML file named `baseline-file.yml` in the current directory. The file tracks each finding under an `ExactFindings` section: ```yaml ExactFindings: matches: - filepath: ruby_vulnerable.rb/ fingerprint: 056876f00ffd0622 linenum: 52 lastupdated: Mon, 14 Jul 2025 10:17:56 -0700 - filepath: ruby_vulnerable.rb/ fingerprint: ce41d19b83b2b1b0 linenum: 53 lastupdated: Mon, 14 Jul 2025 10:17:56 -0700 - filepath: ruby_vulnerable.rb/ fingerprint: e8644d91fa6654f5 linenum: 40 lastupdated: Mon, 14 Jul 2025 10:17:56 -0700 ``` `fingerprint` reuses Kingfisher's 64-bit *finding fingerprint* algorithm with offsets set to zero. It hashes the secret value together with the normalized filepath, so moving a secret around does not create a new entry. Use the same YAML file with the `--baseline-file` option on future scans to hide all recorded findings: ```bash kingfisher scan /path/to/code \ --baseline-file /path/to/baseline-file.yaml ``` If you intentionally add a new secret that should be ignored later, rerun the scan with both `--manage-baseline` and `--baseline-file` to append new matches to the file without removing existing entries: ```bash kingfisher scan /path/to/code \ --manage-baseline \ --baseline-file /path/to/baseline-file.yml ``` If you want to know which files are being skipped, enable verbose debugging (-v) when scanning, which will report any files being skipped by the baseline file (or via `--exclude`): ```bash kingfisher scan /path/to/project -v ```