Features

Secret scanning Hundreds of kinds of secrets, found offline

scancodebase scans your files and your git history for credentials and shows each one masked, with its type and location.

What it finds

  • Cloud keys for AWS, GCP and Azure
  • CI/CD, GitHub and GitLab tokens
  • Package registry tokens for npm and PyPI
  • Slack, Discord and Telegram tokens, and payment keys such as Stripe
  • Database credentials, private keys and JWTs
  • Generic password and token assignments

What you get

  • The masked secret, its type and its file and line
  • Its context: production, test or example
  • Whether it is on a public list of compromised keys

What makes it different

Secrets are validated without the network and never tested against the provider. Nothing you committed by accident is sent anywhere else.

Which plan includes it

Skipper and above. Compare plans.

FAQ

Questions about this feature

Do you scan the git history?

Yes. A secret removed from the current files can still be in an old commit.

What should I do when a secret is found?

Rotate it at the provider first, then remove it from the code.

More features

Scan yours before the next merge.