Skip to content
secret-scan
Menu

Use cases

Use cases

The findings below are made-up examples, described rather than quoted. They show which verdict each kind of value gets.

A publishable key in a frontend env file

A browser-safe publishable key is public by design. A public value rule names its shape, so it is counted and not listed.

Sample messages

  • verdict: public
  • gate: unaffected

A live secret key pasted into a config file

The value matches a private value rule, whatever the variable is called. The finding is listed with its fingerprint, path and line.

Sample messages

  • verdict: private
  • gate: fails until it is removed and rotated

A documented local-development placeholder

A well-known local database credential pair is a placeholder that a public value rule names exactly, so it is not reported.

Sample messages

  • verdict: public
  • gate: unaffected

An opaque value under a secret-sounding name

No value rule matches, but the name by convention holds a secret, so a private name rule decides.

Sample messages

  • verdict: private
  • gate: fails

A random-looking string no rule recognizes

Neither a value rule nor a name rule decides, so the finding is listed for a human.

Sample messages

  • verdict: triage
  • gate: unaffected, listed for review

Put one clear gate behind your scanner

Four zero-dependency Node modules that run in your CI job. Nothing calls a service and there is no account.