--- title: secret_scan description: Automated scanners found what may be secrets in your code. Kaviris lists them and never blocks the deploy. --- # `secret_scan` **Severity:** note. Automated scanners found what may be secrets in your code. ## What it means Every build is scanned for keys, passwords and credentials in your source and in the built app. Each finding is listed as a warning with its file and line, never the value: [secret_in_source](secret_in_source.md), [secret_in_client_bundle](secret_in_client_bundle.md) or [secret_in_sample](secret_in_sample.md). Each warning starts with a label: *Probably real*, *Probably a test or placeholder value*, or *Unsure*. The labels are a guess to help you sort the list. Kaviris cannot tell which secrets are real and never blocks a deploy for them. ## Your responsibility Your app's secrets are yours to look after. Go through the list, and for any real one: read it from the environment, set it through a secret slot (`kaviris secrets set NAME --from-env NAME --declare`), and rotate it with the provider, since it has been in your source. [All refusal codes](index.md)