Which source control systems does Eureka support?

Eureka supports common source control platforms including GitHub, GitLab, Bitbucket, Azure DevOps, and self-managed GitLab where supported.

Which CI/CD systems can Eureka work with?

Eureka supports common CI/CD workflows including GitHub Actions, GitLab Pipelines, Bitbucket Pipelines, and Azure DevOps Pipelines. Radar CLI supports teams that want scans to run inside their own pipeline.

Can Eureka work with our existing scanners?

Yes. Eureka can ingest supported scanner output and SARIF-compatible results so teams can bring findings into one AppSec workflow instead of managing separate dashboards and exports.

What happens after we connect Jira, GitHub Issues, or Linear?

Findings can remain connected to remediation tickets so ownership, status, decisions, and evidence stay tied to the vulnerability record.

Can we bring in a scanner that is not listed?

If the scanner exports compatible SARIF results, Eureka can import them into the vulnerability workflow.

Do integrations force developers into another dashboard?

No. Eureka is designed to keep work close to existing developer workflows, including source control, pull requests, issue trackers, and CI/CD systems.

INTEGRATIONS

Works with the stack you already have.

Eureka connects to your source control, issue trackers, CI/CD, and scanners, by name.

Bring your own scanner, import SARIF, and keep findings, fixes, and the record where the work already happens.

Start with a scan See supported scanners

30-day free trial. No credit card required.

IntegrationsNamed tools one workflow

Connected tools

Source controlGitHub
CI/CDGitHub Actions
ScannersSemgrep
TrackersJira

Eurekaorchestration

NormalizeSARIF · native

Correlatededup · merge

Routeowner · tracker

Owned outcomeAPP-2418

Finding

Deserialization · payment-svc

Tracker

Jira · SEC-1042

PR check

GitHub · pr-118

Evidence

captured · exportable

THE INTEGRATION MAP

Named, and grouped by role.

eureka · integrations · source control5 connectors

Source control

Where your code lives. Connect a repo and Eureka takes it from there.

GitHub

Available

GitLab

Available

Bitbucket

Available

Azure DevOps

Available

Self-managed GitLab

Available

eureka · integrations · trackers3 connectors

Issue trackers

Findings become tickets in the tracker your team already works in.

Jira

Available

GitHub Issues

Available

Linear

Available

eureka · integrations · CI/CD4 connectors

CI/CD pipelines

Scans run where your builds and deploys already run. PR / MR checks are GitHub-only today.

GitHub Actions

Available

GitLab Pipelines

In progress

Bitbucket Pipelines

In progress

Azure DevOps Pipelines

In progress

NotePR / MR check parity for GitLab, Bitbucket and Azure DevOps is in progress. Repository connectivity is separate and available today.

eureka · integrations · scanners8 connectors

Third-party scanners

Already run scanners? Eureka takes their output and adds its workflow on top.

Opengrep

Available

Semgrep

Available

OWASP dep-scan

Available

Grype

Available

Gitleaks

Available

Veracode SCA

Available

Veracode SAST

Available

Snyk

Available

eureka · integrations · importSARIF

Import

Anything that speaks SARIF comes in without changing your scanning stack.

SARIF · Import

Available

Get started for free See how Eureka works

BRING YOUR OWN SCANNER

Keep the tooling you've paid for.

YOUR EXISTING SCANNERS

Veracode SAST

license: BYOL · retained

SASTIn use

Veracode SCA

license: BYOL · retained

SCAIn use

Snyk

license: BYOL · retained

SCAIn use

EUREKA

SARIF import

normalize findings · dedupe · map to controls

Normalized

Eureka Radar (built-in)

SAST + SCA checks running alongside your scanners

SASTSCAIncluded

Managed scans

auto-run on commit and pull request

on commiton PR

EUREKA WORKFLOW

Triage & prioritization

context, exploitability, ASVS mapping

one queue

Remediation

fix in the pull request · ticket sync

GitHub PRJira

Evidence record

finding → control → PR → close

captured

Already invested in Veracode? Bring it. Eureka works with your existing scanner license (BYOL) and adds Eureka Radar's built-in checks on top, so you keep the tooling you've paid for and gain the workflow around it.

THE TRACE

How an integration becomes a record.

01 · REPOSITORY

Repository connected

source: github.com/acme/payments-api
branch: main

GitHub

02 · SCAN SOURCE

Scan source identified

scanner: Veracode SAST
commit: 4f9a2c1

SARIF

03 · FINDING

Finding normalized

CWE-89 · SQL injection
file: src/orders/query.ts:142

1 signal

04 · WORKFLOW

Workflow context attached

control: ASVS 5.3.4
ticket: JIRA SEC-1284 · PR #217

in review

05 · EVIDENCE

Evidence record captured

closed at commit 8b31d0e
record: EV-2026-0417

captured

01 · REPOSITORY

Repository connected

source: github.com/acme/payments-api
branch: main

GitHub

02 · SCAN SOURCE

Scan source identified

scanner: Veracode SAST
commit: 4f9a2c1

SARIF

03 · FINDING

Finding normalized

CWE-89 · SQL injection
file: src/orders/query.ts:142

1 signal

04 · WORKFLOW

Workflow context attached

control: ASVS 5.3.4
ticket: JIRA SEC-1284 · PR #217

in review

05 · EVIDENCE

Evidence record captured

closed at commit 8b31d0e
record: EV-2026-0417

captured

THE QUESTION

What does connecting a tool actually get me?

Connecting a tool isn't the end, it's the start of a trace. A finding maps to a control, moves through a pull request, links to a ticket, and closes, and every step is written to the record. The integrations are what keep that trail unbroken.

SARIF · ROADMAP

Don't see your tool?

Import findings from any SARIF-compatible tool, or talk to us about what you run. If it's on the roadmap, we'll tell you straight.

Request an integration

FAQ

Frequently asked questions.

Bring the stack you already have

Connect your source control, trackers, pipelines, and scanners, and start with a scan.

Start with a scan See supported scanners

30-day free trial. No credit card required.