Answer: Vulnerability Remediation supports Origin, GitHub, GitLab, and Bitbucket Cloud. Bitbucket Data Center and Azure DevOps Services are not supported. Status: Check failed Entry: tool/cursor/integrations/vulnerability-remediation-source-control-support Revision: 1 Digest: sha256:83b15fb422eb3066 (changes whenever the content changes) Timeline: Created: 2026-11-15T02:11:29Z Last changed: 2026-11-15T02:11:29Z Last verified: 2026-11-16T12:26:21Z Last attempt: 2026-11-20T12:41:04Z (failed) Next check: 2026-11-20T13:41:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Supported providers | Origin, GitHub, GitLab, and Bitbucket Cloud | [1] | 2026-11-16 Origin | Supported | [1] | 2026-11-16 GitHub | Supported | [1] | 2026-11-16 GitLab | Supported | [1] | 2026-11-16 Bitbucket Cloud | Supported | [1] | 2026-11-16 Bitbucket Data Center | Not supported | [1] | 2026-11-16 Azure DevOps Services | Not supported | [1] | 2026-11-16 Sources: [1] Anysphere. "cursor.com/docs/vulnerability-remediation.md". https://cursor.com/docs/vulnerability-remediation.md Role: primary. Accessed: 2026-11-16T12:26:21Z Quote: "Vulnerability Scanner supports repositories on Origin, GitHub, GitLab, and Bitbucket Cloud." (Supports: Supported providers) Quote: "| [Origin](https://cursor.com/docs/origin.md) | Supported |" (Supports: Origin) Quote: "| [GitHub](https://cursor.com/docs/integrations/github.md) | Supported |" (Supports: GitHub) Quote: "| [GitLab](https://cursor.com/docs/integrations/gitlab.md) | Supported |" (Supports: GitLab) Quote: "| [Bitbucket Cloud](https://cursor.com/docs/integrations/bitbucket.md) | Supported |" (Supports: Bitbucket Cloud) Quote: "| [Bitbucket Data Center](https://cursor.com/docs/integrations/bitbucket.md#setup) | Not supported |" (Supports: Bitbucket Data Center) Quote: "| [Azure DevOps Services](https://cursor.com/docs/integrations/azure-devops.md) | Not supported |" (Supports: Azure DevOps Services) Snapshot SHA-256: c94e8caaf5760765d0822dea1675e2a1c07c13b1577f675d5d171d94d76eeaff (captured 2026-11-14T12:37:37Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-15T02:11:29Z, so the values verified then were kept. Cross-check: not-available at 2026-11-16T12:26:21Z. No independent second source is configured for this entry Last successful check: 2026-11-16T12:26:21Z Last attempt: 2026-11-20T12:41:04Z (failed) Notes and limitations: Extracted automatically from a single official source (section "Source control support"). Related: https://latestn.com/tool/cursor/integrations/webhook-headers Which headers does Cursor include in cloud agent webhook requests? https://latestn.com/tool/cursor/integrations/webhook-payload-format What is the payload format of Cursor cloud agent webhook requests? https://latestn.com/tool/cursor/integrations/when-to-use-sdk-bridge When should I use the Cursor SDK Bridge instead of the TypeScript or Python SDK? https://latestn.com/tool/cursor/integrations/trigger-reviews-from-github How do I trigger Cursor Agent SDK PR reviews from GitHub? https://latestn.com/tool/cursor/integrations/verify-webhook-signature How do I verify that a Cursor cloud agent webhook request is authentically from Cursor? https://latestn.com/tool/cursor/integrations/vulnerability-remediation-api How do I use the Cursor Vulnerability Remediation API to list findings and request fixes? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T12:52:03Z | check-failed | Extraction did not pass verification: answer does not contain any extracted value | — 2026-11-15T02:11:29Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/integrations/vulnerability-remediation-source-control-support/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/integrations/vulnerability-remediation-source-control-support POST: https://latestn.com/dispute/tool/cursor/integrations/vulnerability-remediation-source-control-support with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/integrations/vulnerability-remediation-source-control-support?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Which source control providers does Cursor Vulnerability Remediation support? Revision 1, last verified 2026-11-16T12:26:21Z. https://latestn.com/tool/cursor/integrations/vulnerability-remediation-source-control-support (accessed 2026-11-21T10:01:00Z). @misc{LatestN_tool_cursor_integrations_vulnerability_remediation_source_control_support_r1, title = {Which source control providers does Cursor Vulnerability Remediation support?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/integrations/vulnerability-remediation-source-control-support}}, note = {Revision 1; digest sha256:83b15fb422eb3066; last verified 2026-11-16T12:26:21Z; accessed 2026-11-21T10:01:00Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/integrations/vulnerability-remediation-source-control-support