LegAudit scans your GitHub repository for compliance violations across GDPR, CCPA, TX TDPSA, IL BIPA and the EU AI Act. Real litigation exposure, quantified in seconds.
Three steps from repository URL to a full compliance exposure report. No account required.
Enter a public GitHub URL or owner/repo slug. LegAudit works with any public repository. No OAuth or setup required.
100+ files analyzed for 13 privacy law signals using pattern matching across data handling, consent flows, biometric logic, and AI pipelines.
Compliance score, dollar exposure estimate, regulation citations and exact code evidence. Ready to share with your legal or engineering team.
LegAudit maps your code to the regulations that govern your users, across every major privacy framework in force today.
Data subject rights, consent mechanisms, retention policies, and breach notification requirements under EU/UK law.
Do-not-sell signals, opt-out rights, consumer access requests, and sensitive personal information handling under California law.
Texas Data Privacy and Security Act requirements including data minimization, purpose limitation, and consumer opt-out controls.
Biometric identifier consent, written release requirements, data retention schedules, and destruction obligations under Illinois law.
High-risk AI system obligations, transparency disclosures, human oversight mechanisms, and prohibited practice detection.
Colorado AI consumer protections including algorithmic decision-making disclosures and developer due diligence obligations.
Begin with a free scan. Scale your compliance programme as your organisation grows.
From engineering teams evaluating the CI/CD integration and legal counsel reviewing coverage.
No. The free scanner runs entirely in your browser and your code never leaves your machine. For the paid CI/CD tier, changed files are transmitted over HTTPS to our scan API, processed by Claude and immediately discarded. Source code is never persisted. Scan results (score, finding titles, line numbers) are stored in your dashboard history.
The GitHub Action runs in parallel with your existing checks and does not block your build unless you explicitly enable the fail-on-critical step. Typical scan time is 15 to 45 seconds depending on the number of changed files. The action caps at 30 files per pull request to keep latency predictable.
JavaScript, TypeScript, Python, Ruby, Go, Java, PHP, HTML, Vue, Svelte and config files (.env, .yml, .json). Minified bundles, node_modules, dist and vendor directories are automatically excluded. If your stack is not listed, contact us and we will add support within one business day.
The model is explicitly instructed not to flag form validation logic, UI library code, test fixtures, generic variable names or minified third-party files. A typical production pull request surfaces zero to three real findings. The detection prompt is tuned continuously based on false-positive reports. Submit examples to our support address and we will resolve them within one business day.
Yes. The GitHub Actions workflow includes a commented-out fail-on-critical step. Uncomment it and configure it as a required status check in your branch protection rules to prevent merges when critical violations are present. We recommend enabling this for repositories that process personal data and leaving it advisory for internal tooling.
EU GDPR, California CCPA/CPRA, Texas TDPSA, Illinois BIPA and the EU AI Act. Each finding is mapped to a specific article or section (for example, GDPR Art. 32 on encryption of personal data) so your legal team can verify citations directly.
One repository equals one GitHub repository with the LegAudit workflow installed. Monorepos count as one. Starter covers one repository, Growth is unlimited and Enterprise includes unlimited repositories with centralised management. You can change which repositories are connected at any time from the dashboard.
Yes. The scanner on this page is free with no account required. Paste any public GitHub repository URL and receive a full compliance report with file paths and line numbers in seconds. Paid plans add CI/CD integration, automated fix suggestions, dashboard history and team management.
LegAudit identifies violations at the code level before they reach production. Privacy counsel reviews policies, contracts and regulatory responses. The two are complementary: LegAudit keeps your codebase clean, while counsel handles DPIAs, data processing agreements and enforcement responses. LegAudit output is not legal advice.
Your card is charged at the start of month two. If you cancel before the trial ends you are never charged. There are no setup fees, no minimum term, and you can cancel from your dashboard at any time. Annual plans are billed upfront at a 25% discount.