Overview

What V12 does and where to start: runs, the findings inbox, Autopilot and the API.

V12 is a security agent for mission-critical code. A run reviews the code in your GitHub repositories, or a change to it. A full review goes through Compile, Scan, Triage, Prove and fix and Report; a review of a change goes through Compile, Review changes and Triage. What a run finds lands in your workspace's Findings inbox, with the Evidence in your code. Where the run produced them, a finding also shows a proof of concept (PoC) and a proposed Fix.

Where to start

Quickstart

Connect GitHub, add a repository and start your first run.

Start and follow a run

Choose what to review, check the price and follow the run.

Findings inbox

Read the findings of the organization or of one repository.

Autopilot

Review every push to a branch, or each new pull request, automatically.

Organizations and members

Invite people to an organization and give each one a role.

API overview

Read findings and start runs from scripts, AI assistants and the terminal.

What you work with

The sidebar holds Findings, Runs, Focuses and Autopilot. A focus is a short document that tells runs what to look for; attach it to runs and Autopilot rules.
The repository switcher above them shows All repositories or one repository workspace, and the four pages follow it.
Runs are paid for from your workspace's Credit balance; see Credits and billing.
The REST API, the MCP server and the v12 CLI reach the same findings and runs; see the API overview.

Sign in with Continue with GitHub, Continue with Google or Continue with email, which uses a password. New to V12? Choose Create an account on the same page.

Signing in with GitHub is not the same as installing the V12 GitHub App, which gives V12 access to your private repositories. Connect GitHub shows how to install it.