Documentation
Code Audit
Inth Code Audit reads your repository and finds privacy risks that the code shows. It also reviews each pull request for new risks before you merge it.
Code Audit finds risks such as these:
- personal or sensitive data that goes to logs and observability tools
- analytics, advertising, session replay, or identity tools that load before the visitor gives consent
- gaps in retention, deletion, data subject access requests (DSARs), and data export
- personal data that goes to vendors, webhooks, CRMs, or AI services
- privacy risks that a pull request adds
Each finding cites the code that shows it. A finding is evidence for your engineering, privacy, security, or legal team to review. Code Audit does not make legal decisions.
Start here
- Connect GitHub: install the Inth GitHub App, link a repository to a project, and add policy pages.
- Run a full audit: audit the whole repository and unlock the report.
- Read the report: find the risks to fix first.
- Scan pull requests: find new risks before you merge them.
- Read the pull request review: see what Inth posts on GitHub.
- Use comment commands: scan again, and dismiss findings from GitHub.
What you need
- an Inth organization and project
- an owner or admin of the organization to connect GitHub, link projects, start audits, and change repository settings
- an owner of the organization to unlock reports and add Credits
- access to the repository that you want to audit
- Credits to unlock a full report or to run pull request scans
Link a website with policy pages to the project if you can. Code Audit then compares the code with your privacy policy, cookie policy, and other public pages. A scan runs without them.
Free preview
Every organization can run a free Code Audit. It audits the whole repository and shows some of the findings. The preview shows some Medium and Low findings. Critical and High findings stay locked. The report tells you how many findings stay locked. Unlock the full report with Credits to see all of them.
You can have 1 locked preview at a time. To start a new free audit, unlock the last one first.
How Inth handles your code
Inth makes a temporary copy of the repository for each audit. Inth deletes the copy after the audit. If that deletion fails, the copy expires later under Inth retention rules. Inth keeps the report: the findings, the evidence excerpts that they cite, and the repository, branch, commit, and scope of the audit.
Code Audit uses AI models. Inth sends the code and its context to the model provider to make the findings. Inth has zero data retention (ZDR) agreements with its model providers.
Coverage and limits
Inth tests its analysis most for JavaScript and TypeScript. Coverage for Go, Python, Astro, Vue, and Svelte is in preview. For these languages, also review privacy-relevant code yourself.
Code Audit can miss behavior that depends on runtime configuration, external systems, generated code, or languages that it does not support. A clean report is not a compliance certificate. It does not prove that the code has no privacy risks.