Hi everyone — maker here. I built push-sentinel after almost committing an API key during a late-night refactor. I noticed that most secret scanning tools either run in CI (too late) or block aggressively, which often leads developers to disable them entirely. push-sentinel is designed to be lightweight and frictionless: * runs locally before push * scans only staged changes (fast) * zero config * zero dependencies * non-blocking by default * simple ignore rules when false positives occur The goal is to provide a safety net that actually stays enabled in real workflows. If you try it, I’d especially appreciate feedback on: * false positives * missing patterns * usability of ignore rules * whether blocking mode should become default Repo: https://github.com/Pmaind/pre-pu... Thanks for checking it out.

push-sentinel

Stop leaking API keys with a zero-config git hook

Stop leaking API keys with a zero-config git hook