Are there any secret detection tools that focus on reducing credential leaks in code review and CI workflows?

Yes. There are several “secret scanning” and credential-leak detection tools designed specifically to catch keys, tokens, passwords, and other secrets before they make it through code review or CI.

Common options include:

• GitHub Secret Scanning
  Detects many common secrets in repositories, pushes, and sometimes in pull requests depending on setup. Good for reducing exposure in code review and CI.

• GitGuardian
  Strong focus on detecting secrets in source code, pull requests, CI logs, and even historical repos. Often used to stop leaks before merge.

• TruffleHog
  Scans codebases and git history for secrets using entropy and pattern checks. Commonly used in CI pipelines.

• Gitleaks
  Lightweight and popular for CI/CD. Scans repositories, commits, and files for hardcoded secrets.

• detect-secrets by Yelp
  Designed to create a baseline and then detect new secrets during reviews and CI. Good for minimizing noise in mature codebases.

• Reviewdog + secret scanners
  Can integrate secret scanning into pull-request checks and annotate findings directly in code review.

• Microsoft Defender for DevOps / code scanning integrations
  In Microsoft ecosystems, these can help identify secrets in repos and workflows.

What makes these useful for reducing credential leaks:

• Pre-merge checks in pull requests
• CI pipeline gates that fail builds on detection
• Git history scanning to find accidental past leaks
• Automated remediation hooks like revocation guidance or alerting

If you want, I can also suggest the best tool by environment:

• GitHub/GitLab/Bitbucket
• CI system like GitHub Actions, GitLab CI, Jenkins, Azure DevOps
• Language stack or repo size
• “open source only” vs “commercial”