> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/legacy-documentation/cli-integration/remote-mode/sca-integration.md).

# SCA Integration

Seal supports direct API integrations with a variety of major scanners (Snyk, BlackDuck, GitHub Advanced Security, Ox Security, etc.).

* **How it works:** The Seal CLI communicates with your scanner's API to synchronize findings, marking specific vulnerabilities as "remediated" within the scanner's dashboard.
* **Best for:** Internal scans and operational dashboards.

```bash
SNYK_URL
SNYK_TOKEN
SNYK_ORG_ID
SNYK_PROJECT_ID
seal fix --mode=XXX
```

### CI Integration Workflow

Regardless of the CI system, the golden rule of Seal CLI integration is **Timing**.

> **Timing Rule:** The Seal CLI must run **immediately after** packages are fetched/installed, but **before** the project is compiled or built.

#### Common Integration Patterns

1. **Standard CI (Jenkins, GitLab CI, CircleCI):** Add a shell step to download the CLI and run the `seal fix` command after your dependency fetch step (e.g., after `npm install` or `go mod download`).
2. **GitHub Actions:** Seal Security provides a dedicated GitHub Action. Simply add it to your workflow file `.github/workflows/main.yml`.
3. **Docker:** Add the CLI run command directly into your `Dockerfile` (often strictly for the build stage to keep the final image slim).