Overall Satisfaction with GitGuardian Internal Monitoring
It's very difficult to manage secrets leaks when you're building in public (Open Source). We use GitGuardian regularly and it's part of our commit/push hooks and GitHub actions. With GitGuardian setup on our repositories, we can totally rely on their awesome service and know immediately if a secret has been leaked/exposed. I've personally used GitGuardian for other open-source projects and they've saved me from a lot of trouble 😮💨. One of the must-have tools in your Git setup.
- Secret scanning for secrets like Github OAuth Secrets
- Git commit/push hooks, so there's a check before you even try to push to a VCS
- Automatic rollback on accidentally pushed secerts
- Awesome dashboard and amazing options to resolve any false-positives
- I quite honestly don't know. I faced a lot of the issues and I searched a lot for the right tools. Nothing but GitGuardian had everything I needed
- Secret scanning (like API Keys, OAuth Keys, etc)
- Github action
- Discord Integration, absolutely love it
- The place where I use this the most is an open-source project where we're still pre-revenue. But GitGuardian definitely has saved us from some major breaches
I've evaluated quite a few other tools, like git-secrets, Git-leaks, scan, and maybe a few more. They're all great but quite surprisingly none of them detected Github OAuth Secrets for us. A lot of the FOSS tools out there focus on much simpler, generic secrets, which is good in itself but with GitGuardian, it was dead simple from day one. I just connected our Github Account and set up the gg-shield cli and that was all.
Do you think GitGuardian Internal Monitoring delivers good value for the price?
Yes
Are you happy with GitGuardian Internal Monitoring's feature set?
Yes
Did GitGuardian Internal Monitoring live up to sales and marketing promises?
Yes
Did implementation of GitGuardian Internal Monitoring go as expected?
Yes
Would you buy GitGuardian Internal Monitoring again?
Yes