Exhibit 05 — Developer tooling / release safety← All work
A pre-publish Git scanner for secrets, PII, private files, local paths and risky commit history.
Stack
PythonYear
2026Last updated
Why it exists
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 it’s built
Git Privacy Scanner is a release-safety tool for checking whether a repository is actually safe to publish before pushing it into public view.
- Scan for multiple privacy classes instead of only API-key patterns.
- 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.
Capabilities
Secret-pattern scanningPII checksPrivate-file detectionLocal-path leakage detectionGit history checksPre-publish review workflow
Principles
Assume history matters
Flag before deleting
Privacy is broader than secrets
Make public release a deliberate gate
Questions
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.
Next exhibit — 06
BrowserProof →