Skip to main content

Understanding default branches for agent-based scan projects

The default branch for your Veracode Software Composition Analysis agent-based scan projects determines which data to display in the Veracode Platform. It also specifies the branch in which Veracode automatically creates issues for newly released vulnerabilities.

The Veracode Platform only displays issues, vulnerabilities, libraries, and licenses from the default branch. All list views only show the items from the default branch and all of the counts across your organization only include findings from the default branch, unless you view another branch.

When Veracode releases or updates a vulnerability that impacts any of your projects, it automatically creates a new issue or updates an existing issue in the default branch.

For new projects, Veracode automatically sets the default branch to Use Last Scanned, which means the default branch always updates to the most recently scanned branch or tag. In your Veracode SCA project settings, you can set the default branch that works with your Git workflow.