Are your Git repositories GDPR compliant?
This tool analyses your Git history for potential European data protection violations. Essential for any EU-based development team or organisation handling European user data.
pip install -e .
gdpr-validator scan /path/to/your/repo
- 🔍 Git History Scanner: Analyses commit logs for personal identifiable information
- 🌐 Fork Tracking: Documents how personal data propagates across repository forks
- 🔐 Hash Analysis: Examines git hashes for permanent data retention issues
- 📊 Branch Inspection: Checks branch metadata for personal data exposure
- ✅ GDPR Compliance Checker: Validates against specific GDPR articles
- 📄 Report Generator: Creates detailed compliance documentation
Every Git repository potentially contains:
- Author names and email addresses in commit history
- Timestamps creating detailed activity patterns
- Personal data that propagates across forks indefinitely
- Cross-border data transfers without explicit consent
- Permanent data retention violating erasure rights
⭐ Star this repo to stay updated
🍴 Fork to contribute improvements
📥 Clone to test your repositories
Every interaction helps us improve GDPR compliance tooling for the community!
git clone https://github.com/DragonDiffusionbyBoyo/EU-GDPR-Git-Validator.git
cd EU-GDPR-Git-Validator
pip install -e .
pip install gdpr-git-validator[full]
pip install gdpr-git-validator[pdf]
pip install gdpr-git-validator[analysis]
git clone https://github.com/yourusername/EU-GDPR-Git-Validator.git
cd EU-GDPR-Git-Validator
pip install -e .[dev]
git clone https://github.com/yourusername/EU-GDPR-Git-Validator.git
cd EU-GDPR-Git-Validator
pip install -e .
gdpr-validator scan /path/to/repository
gdpr-validator scan /path/to/repository --report-format html --output compliance-report.html
gdpr-validator scan /path/to/repository --articles 17,20 --verbose
gdpr-validator analyze-forks https://github.com/user/repo
🔍 GDPR Compliance Scan Results
Repository: /path/to/your/repo
Scan Date: 2025-07-13 18:59:00 UTC
⚠️ VIOLATIONS FOUND:
├── Personal Data Exposure: 47 commits contain email addresses
├── Right to Erasure (Article 17): IMPOSSIBLE - Data exists in 23 forks
├── Data Portability (Article 20): PARTIAL - Git format limits portability
└── Lawful Basis (Article 6): UNCLEAR - No consent mechanism for commit data
📈 Fork Analysis:
├── Your personal data exists in 23 additional repositories
├── Geographic distribution: 12 countries identified
├── Erasure impossibility factor: 100% (distributed across forks)
💡 Recommendations:
├── Implement commit message sanitization
├── Consider using .mailmap for email anonymization
├── Review contributor agreement for data processing consent
└── Document data retention policies in repository
- Git History Analysis: Deep scan of commit logs, author information, and metadata
- Personal Data Detection: Identifies emails, names, and potentially sensitive information
- GDPR Article Compliance: Checks against Articles 6, 13, 14, 17, and 20
- Fork Impact Assessment: Calculates data multiplication across repository network
- Multi-format Reporting: Generate reports in HTML, PDF, JSON, and markdown
- Cross-border Transfer Detection: Identifies international data distribution
- Consent Propagation Analysis: Documents systematic consent failures
- Data Minimization Recommendations: Suggests privacy-preserving alternatives
- Compliance Dashboard: Interactive web interface for ongoing monitoring
Article 6 - Lawful Basis for Processing
- Git commits process personal data (names, emails) - what's your lawful basis?
Article 13/14 - Information to be Provided
- Do contributors know their data will be permanently stored and distributed?
Article 17 - Right to Erasure
- Git's distributed nature makes data erasure technically impossible
Article 20 - Right to Data Portability
-
Git format provides some portability, but with significant limitations
-
⚠️ GitHub CI StatusNote: GitHub Actions is currently failing due to CI workflow quirks. The tool runs perfectly locally and is actively used. CI will be fixed if and when it becomes necessary. For now, focus is on local execution and real-world feedback.
Please clone, test locally, and submit any issues or GDPR scan results via Issues or Pull Requests.
We welcome contributions! This project helps the entire development community understand and address GDPR compliance challenges in version control systems.
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests for new functionality
- Submit a pull request
See CONTRIBUTING.md for detailed guidelines.
This project is licensed under the MIT License - see the LICENSE file for details.
This tool is designed for educational and compliance purposes. It identifies potential GDPR compliance issues but does not constitute legal advice. Consult with qualified legal professionals for specific compliance requirements.
- 📧 Email: [email protected]
- 💬 Discussions: GitHub Discussions
- 🐛 Issues: GitHub Issues
Building privacy-conscious development practices, one repository at a time.