Start a run

Your first audit

Sign in, connect GitHub, choose a source, and launch either a full audit or a diff review.

V12 supports two starting points for a run: a GitHub repository or an uploaded archive (.zip, .tar, .tar.gz, or .tgz). For most teams, GitHub is the best path because it unlocks repository sync, pull request selection, and Autopilot.

Before you start

You need:

  • a V12 account,
  • enough credits for the scan you want to run, and
  • GitHub access to the repositories you want V12 to inspect.

1. Connect GitHub

If this is your first run:

  1. Sign in to V12.
  2. Open Settings and connect your GitHub account.
  3. Install the V12 GitHub app on the repositories or organizations you want V12 to analyze.
  4. Return to Create run and sync repositories if the repo list hasn’t refreshed yet.

GitHub-backed runs depend on both pieces:

  • OAuth lets V12 identify you and list accessible repositories.
  • The GitHub app grants repository access for analysis and ongoing automation.

2. Open Create run

Go to Create run. The first screen asks for a code source:

  • GitHub repository: choose from connected repositories.
  • Upload archive: upload a .zip, .tar, .tar.gz, or .tgz file.

If you upload an archive, include the full project and build system when possible. Proof-of-concept execution and remediation validation work best when the uploaded project is complete.

3. Choose the audit type

When you pick a GitHub repository, V12 offers two audit modes:

Full audit

Use this for a broad review of a branch, tag, commit, or selected file set.

Diff review

Use this to review only the code changes from a GitHub pull request, a commit range, or a patch file.

If your team wants a diff review on every change, Autopilot is the next step.

4. Name the run

Every run needs a Run name. Pick something your team can recognize later, especially if you’ll compare multiple scans of the same repository:

  • payments-service main before release
  • router PR #184 diff review
  • staking-contract archive upload

5. Select scope

Full audit scope

Browse the repository tree and select the files or directories to analyze. Use scope control to exclude vendor code, skip generated artifacts, drop tests that aren’t useful audit targets, and stay within the file cap shown by the UI.

Diff review scope

V12 shows the changed files for the selected diff. You can narrow the billable review to the files you care about while still letting the system read surrounding code for context.

6. Confirm cost and submit

On the last step, review the selected repository or archive, the audit mode, the final scope, and the estimated price.

When everything looks right, click Run audit.

After submission

Once queued, the run appears in Runs. From there you can watch status changes, open the findings view when analysis finishes, and share specific findings with teammates.

Next: Reading findings

Type to search.