# Connecting to the CI Pipeline

As an alternative to integrating with your source control, the Seal platform can also identify your existing vulnerabilities by integrating with your CI pipeline.

The Seal CLI was designed to be easily integrated as part of an organization's CI pipeline. The CLI can scan the vulnerabilities in your build machine, and report home to the Seal server what vulnerabilities exist. If you're going to [use the Seal CLI to fix your packages](/fundamentals/readme/package-sealing/integrating-the-cli-in-the-ci.md), then having it report the scan results back is incredibly easy, and only requires [using one more flag](/fundamentals/cli/uploading-scan-results.md).

Note that while this setup in general provides an accurate picture of your vulnerabilities, unlike the source code integrations, fixed vulnerabilities won't be identified until you go through a build process.

For instructions about how to integrate Seal's CLI into other CI platforms see [here](/fundamentals/cli/integrating-with-the-ci.md#other-ci-platforms).

To quickly run an example on your machine without configuring your CI see the [usage examples](/fundamentals/cli/usage-examples.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealsecurity.io/fundamentals/readme/package-discovery/connecting-to-the-ci-pipeline.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.