Skip to main content
Code Governance shows where ZeroPath detects AI authorship signals in pull requests. Use it to see which repositories have detectable AI-assisted changes, inspect the evidence behind an attribution, and review how those changes overlap with active security findings. Open Code Governance under Automation. The page is in early access and requires View Custom Reports. Metrics cover the repositories you can view.

Review a repository or period

  1. Select one or more repositories and a date range. All repositories uses the repositories you can view.
  2. Use the trend, AI tools detected, and Confidence of attribution to see where signals appear and how strong they are.
  3. In Recent pull requests, choose Attributed for PRs with signals or All captured for the wider set. Check the Confidence / verdict and Evidence columns, then open the PR in your code host to review the change.

Read the attribution evidence

The confidence reflects the strongest signal ZeroPath recognized. The ≥ prefix marks a lower bound based on observable signals. Inline IDE completions and work committed under a personal account without a marker can be absent from this view. A finding’s attribution identifies where to look for its origin. Review the finding evidence and the code change when deciding how to respond. ZeroPath collects supported pull request events from GitHub, GitLab, Bitbucket, and Azure DevOps. Merged-line volume depends on GitHub diff sizes. Older or missed events can leave gaps in the history. To review security findings before changes merge, see Pull Request Scanning. To see which AI SDKs, models, and tooling your applications include, see AI Inventory.