VOOZH about

URL: https://docs.semgrep.dev/getting-started/scm-support

⇱ Supported source code managers - Semgrep


Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

Skip to main content
PlanUnsupported Semgrep features
Azure DevOps Cloud
  • Query console
Azure DevOps Server
  • Semgrep Multimodal
  • Semgrep Managed Scans
  • Pull request comments
  • Query console
  • Diff-aware scans
  • Sending findings to Semgrep AppSec Platform
  • Default branch identification
  • Generic secrets (requires Semgrep Multimodal)
Bitbucket Cloud Free
  • Semgrep Multimodal†
  • Semgrep Managed Scan†
  • Query console
  • Generic secrets (requires Semgrep Multimodal)
Bitbucket Cloud Standard
  • Semgrep Multimodal†
  • Semgrep Managed Scan†
  • Query console
  • Generic secrets (requires Semgrep Multimodal)
Bitbucket Cloud Premium
  • Query console
Bitbucket Data Center
  • Query console
  • Diff-aware scans and triage through PR comments require Bitbucket Data Center version 8.8 or later.
GitHub Free-
GitHub Pro-
GitHub Team-
GitHub Enterprise Cloud-
GitHub Enterprise Server-
GitLab Free
  • Semgrep Managed Scans*
  • Triage through MR comments*
  • Query console
GitLab Premium
  • Query console
GitLab Ultimate
  • Query console
GitLab Dedicated / Dedicated for Government
  • Query console
GitLab Self-Managed Free
  • Semgrep Managed Scans*
  • Query console
GitLab Self-Managed Premium
  • Query console
GitLab Self-Managed Ultimate
  • Query console
Semgrep Multimodal and Managed Scans require a workspace access token, which is only available to users with Bitbucket Cloud Premium. *Semgrep Managed Scans and triage through MR comments require access to group webhooks, which is unavailable to GitLab Free users. Autofix is supported on all source code managers in the table above. Autofix is not yet available when Semgrep connects to your SCM through the Semgrep Network Broker.

Access limitations

You may need to add Semgrep’s IP addresses to your ingress and egress allowlists, or you can use the Network Broker, if any of the following conditions apply:
  • Your SCM offers security features that limit access to your resources
  • Your SCM is behind a firewall or protected by network restrictions regarding access
  • You are using a virtual private network (VPN)

Was this page helpful?

⌘I
Assistant
Responses are generated using AI and may contain mistakes.