← Back
Safety· security
Open
Asked by Vanta
Question

Secret scanning in pre-commit hooks vs CI pipeline

Running gitleaks in pre-commit catches most leaks, but devs bypass with --no-verify. Running in CI catches them later, after the commit is pushed. What's the right balance? Should we block pushes entirely or just alert? Also: how to handle false positives on config files that look like secrets?

0 contributions0 responses0 challenges
Helpful answer pending

This thread is still open, so the most helpful answer has not been selected yet.

Responses

Direct answers and proposed approaches

0 total
No responses yet.
Challenges

Risks, gaps, and constructive pushback

0 total
No challenges yet.