> 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/integrations/internal-scanners/cycode.md).

# Cycode integration

<figure><img src="/files/w7mWlQzvlJlyHhnn87u3" alt="Cycode" width="240"><figcaption></figcaption></figure>

Cycode reads ignore entries from a `.cycode/config.yaml` file in the repository. The Seal CLI writes entries to that file for the vulnerabilities Seal has sealed, and Cycode suppresses them on the next scan.

Like the [Snyk](/integrations/internal-scanners/snyk.md) and [Grype](/integrations/internal-scanners/grype.md) policy-file integrations, the Cycode integration is meaningful only in **Local** fix mode, where the Seal CLI already writes into the repository checkout (`.seal-actions.yml`). In **Remote** or **all** mode the CLI does not modify your repository, so there is no natural place to land the policy-file edit.

## Before you start

The Seal CLI step that drives the integration must have write access to the repository checkout in CI.

## Enable policy-file generation

Invoke the Seal CLI with the explicit flags:

```bash
seal scan --generate-actions-file --generate-cycode-policy
```

The CLI generates or updates `.cycode/config.yaml` at the project root with CVE-exclusion entries for each vulnerability Seal sealed in this run.

The generated file follows the same format Cycode's own CLI writes via `cycode ignore --by-cve … --scan-type sca`.

## Committing the file

`.cycode/config.yaml` is part of your repository. Commit it like any other source-controlled config. Cycode reads the version of the file present in the branch being scanned.

## Verify

After a `seal fix` run with the integration configured, inspect the generated `.cycode/config.yaml`. The CVE-exclusion entries should match the vulnerabilities Seal sealed.

## Related

* [How CLI-driven sync works](/integrations/internal-scanners/how-cli-sync-works.md)
* [Snyk integration](/integrations/internal-scanners/snyk.md), [Grype integration](/integrations/internal-scanners/grype.md): the other policy-file-edit integrations.