We built Levox, a tool that scans codebases for PII (Personally Identifiable Information) and secrets. The motivation: secrets and sensitive data (emails, API keys, credit cards, etc.) often sneak into repos, and existing scanners are either noisy or slow.
Levox tries to fix that: - 7-stage detection pipeline (Regex → AST → Context → Dataflow → CFG → ML filtering → GDPR checks) - <1s per file, memory efficient - Supports Python, JavaScript/TypeScript, Java - Outputs JSON, SARIF, or terminal tables
Demo: [GitHub link or landing page]
We’re curious: - How do you handle PII leaks today? - Would you see this as a pre-commit/CI step? - What would make it trustworthy enough for production use?
We’d love your feedback!
Easily Install: pip install levox-cli