Version control systems

Start where
your code lives.

Bring the intended repository into TraceMint. Choose the connection and permissions that fit your source-control environment, then scope the security work.

TraceMint manual Azure DevOps connection form with empty credential fields and an illustrative GitHub connection below. No provider account is connected by this example.
TraceMint interfaceIllustrative demo dataView full size — opens image in a new tab↗
Provider support

Your repositories.
Your connection model.

All five providers have repository connection, discovery and import paths. Authentication, event triggers and result feedback are provider-specific—not a single blanket integration promise.

Connection directoryChoose your provider

GitHub

App or token

Connect & import

GitHub App or supported token connection.

Repository discovery, selection and import. Scope access to the repositories used for the evaluation.

Delivery workflow

Configured push / pull-request webhooks and GitHub Actions workflows.

Explore delivery workflows

GitLab

Cloud or self-managed

Connect & import

GitLab.com or a configured self-managed URL.

Repository discovery, selection and import using the configured authentication method.

Delivery workflow

Configured push / merge-request webhooks and GitLab CI workflows.

Explore delivery workflows

Bitbucket

Choose your edition

Connect & import

Cloud or a separate Server / Data Center setup.

Repository access depends on the selected edition and connection. Cloud and self-managed paths are not interchangeable.

Delivery workflow

Edition-specific webhook configuration; Bitbucket Pipelines for Cloud.

Explore delivery workflows

Azure DevOps

Manual connection

Connect & import

Personal access token and organization / collection URL.

Discover and import repositories through a manual connection configured for your Azure DevOps environment.

Delivery workflow

Azure Pipelines configuration. A native Azure SCM webhook receiver is not currently provided.

Explore delivery workflows

Gitea

Your Gitea instance

Connect & import

Personal access token and Gitea server URL.

Discover and import repositories through a manual connection to your Gitea instance.

Delivery workflow

Configured signed push / pull-request webhooks, with commit-status and pull-request feedback paths.

Explore delivery workflows
Before connecting

Configure least-privilege credentials, allowed server URLs and the exact provider edition. Webhooks and external feedback require their own permissions and setup; a saved connection does not enable them automatically.

A practical onboarding path

The right repository.
The right access.

01

Identify the connection

Review your provider, hosted or self-managed setup, network access and supported authentication method.

02

Limit the permissions

Grant the access needed for the selected workflow. Keep credentials scoped and follow your organization’s rotation process.

03

Choose what to analyze

Select the intended repository and scan configuration. Review the project and revision behind each result.

Connection checklist

Verify the parts
your team will rely on.

In focus

Repository access

Confirm provider edition, authentication method, repository visibility, branch selection and network reachability.

Automation triggers

A working repository connection does not imply every PR, webhook or scheduled-scan combination. Test the exact event flow you intend to use.

Result destination

Agree whether reviewers use the TraceMint workspace, a supported integration or exported evidence. Do not assume automatic write-back is enabled.

Plan your evaluation

Connect a representative
repository first.

Tell us what you want to evaluate. Our team will review your request and contact you to agree the scope and arrange a time.

Request a demo