Scan for multiple privacy classes instead of only API-key patterns.
PROJECT / 05 · Developer tooling / release safety
Git Privacy Scanner
Git Privacy Scanner is a release-safety tool for checking whether a repository is actually safe to publish before pushing it into public view.
PRE-PUBLISH / CLEAR
A repository can look clean in its current files while still leaking secrets, personal data, machine paths or sensitive content in ignored files and commit history.
HOW I BUILT AROUND IT01 02 03 04
Check repository history and local-path leakage as part of the publish decision.
Make findings reviewable before release rather than silently deleting evidence.
Keep the tool small enough to run as a routine pre-publication check.
CAPABILITIESWhat it does,
What it does,
without the theatre.
01Secret-pattern scanning02PII checks03Private-file detection04Local-path leakage detection05Git history checks06Pre-publish review workflow
ARCHITECTURE
What the system is meant to preserve.
- 01Assume history matters
- 02Flag before deleting
- 03Privacy is broader than secrets
- 04Make public release a deliberate gate
Is it only a secret scanner?+
No. It also targets PII, private files, machine-specific local paths and risky Git history.
When is it intended to run?+
Before publishing or sharing a Git repository, especially when a project started as private local work.
Can it guarantee a repository is safe?+
No automated scanner can guarantee that. It is a review aid and release gate, not a substitute for judgement on sensitive content.