Files
Betterleaks runs on changed files in the pull request, regardless of file type.Configuration
Betterleaks is configured using thegitleaks key in your .coderabbit.yaml file. The key name is preserved for backward compatibility, existing configurations continue to work without any changes.
betterleaks.tomlgitleaks.toml(backwards compatibility)
When we skip Betterleaks
CodeRabbit will skip running Betterleaks when:- Gitleaks (or a compatible secret scanner) is already running in GitHub workflows.
Notes
- Betterleaks runs on the changed files in the pull request (not just specific file types).
- Betterleaks uses
--no-gitflag, so it scans files directly rather than scanning git history. - The configuration key in
.coderabbit.yamlremainsgitleaksfor backward compatibility. No changes to your existing configuration are required.
What’s next
Trivy
Scan container images and filesystems for known vulnerabilities, misconfigurations, and exposed secrets.
OSV-Scanner
Identify known vulnerabilities in your project’s dependencies using Google’s OSV.dev database.
Linters & security analysis tools
Explore all 40+ tools CodeRabbit integrates with for code quality and security analysis.