Free codebase scan

# Find code\-level privacy risks before merge

Connect GitHub, choose a repository, and get a prioritized view of privacy risks in the code paths your team can fix first\.

[Run a free scan](/dashboard/sign-up)

No credit card • You choose the repository • Free scan

- **Risks and findings detected** — See the privacy issues Inth identifies in your selected repository\.
- **Affected files and lines** — Review the code locations connected to each finding so engineering can inspect the source quickly\.
- **Trackers, SDKs, vendor calls, and data flows** — Understand where third\-party services and data movement appear in the codebase\.
- **Prioritized remediation guidance** — Start with the findings that matter most and use clear next steps for remediation\.
- **Expected scan time** — See what to expect from the scan before reviewing results\.

## How the free scan works

The free experience is built around one clear result: code\-level privacy findings your engineering team can review and act on\.

- **Connect GitHub securely** — Start from GitHub so Inth can scan the repository you select\.
- **Select a repository** — Choose the codebase you want to review for privacy risk\.
- **Inth scans for privacy risks** — Inth checks the selected repository for code\-level signals such as trackers, SDKs, vendor calls, and data flows\.
- **Review your prioritized findings** — Use the result to inspect affected files and lines, understand the issue, and decide what to fix first\.

What you review

## Your free scan creates one report

The report view focuses on one scan result: a single issue record with the affected file, line, vendor signal, and suggested next step\.

**Free scan report**
- **Needs review:** Analytics SDK initialized in checkout — apps/web/checkout\.tsx:42 · vendor call detected

After the first result

## Keep privacy risk visible as the code changes

Once the free scan shows what is in the repository today, Inth can help teams monitor pull requests and website changes so privacy issues are caught closer to the work\.

- **Pull request review** — Review privacy\-relevant changes before they merge, with context for the engineering team\.
- **Website monitoring** — Watch for trackers, SDKs, vendor calls, and data flows that appear after releases\.
- **Remediation workflow** — Turn findings into prioritized work instead of a vague privacy exposure report\.

Expo · Zed · Infisical · Unkey · Cal\.com · Mastra

## Start with the privacy risks in your codebase

Run the free scan, review the concrete findings, and decide what your team should fix first\.

[Run a free scan](/dashboard/sign-up)

No credit card • You choose the repository • Free scan