
GitGuardian catches hardcoded secrets like API keys, tokens, and credentials in our repos quickly and with few false positives. Setup with GitHub was easy, the alerts are clear and actionable, and the historical scan surfaced old leaks we didn't know about. It fits into our workflow without slowing developers down. Review collected by and hosted on G2.com.
The main downside is alert volume at first. The initial scan flagged a lot of old and low-risk findings, so triaging took some time. Tuning ignore rules and reducing noise from test files or placeholder values took some effort. Pricing can also add up as the number of developers grows, and I'd like more flexible remediation workflows. Review collected by and hosted on G2.com.
Great to hear the historical scan caught older leaks your team didn’t know about!
Fair point on the triage effort after the first scan, and I’ll pass that along to the team with your pricing feedback. On more flexible remediation workflows, playbooks might be worth exploring if you haven’t already. They automate parts of the process, like emailing the developer involved a link to the incident so they can resolve it from there (link below).
Thanks for taking the time to lay all this out!
See how GitGuardian improved