Snyk CI/CD integrations

Snyk recommends using the Snyk CLI for CI/CD integrations for the following reasons:

• You have the flexibility to test in-progress features of the CLI by using the preview channel.

• The CLI provides feature-rich stable releases at a regular cadence.

• With the CLI, you have options to extend use cases as you deploy Snyk at scale

Adopting a CI/CD integration

When you decide to use a CI/CD integration, you typically adopt the integration in stages. You will select a deployment method and implement strategies for the code you are scanning. See Snyk CI/CD Integration deployment and strategies.

For detailed information, you can refer to the pages for the integration you are using:

• AWS CodePipeline integration

• Azure Pipelines integration

• Bitbucket Pipelines integration

• CircleCI integration

• GitHub Actions integration

• Jenkins integration

• Maven integration

• TeamCity integration

• Terraform Cloud integration for IaC

• Terraform Enterprise integration for IaC

For integration with GitLab pipelines integration, see this pipeline configuration.

For additional examples of binary and npm integrations for CI/CD, see GitHub CI/CD examples.

Support policy

This policy will be effective beginning on June 24, 2025.

Snyk supports the latest 12 months of CI/CD plugin versions, ensuring functionality and performance. Older versions are considered End-of-Support (EOS) and will not receive bug fixes or troubleshooting.

Snyk provides fixes only in new versions and cannot fix older versions. Customers must upgrade to benefit from improvements.

This policy fosters innovation while optimizing resources.

If you need help, submit a request to Snyk Support.