Dependency Scanning

Introduced in [GitLab Ultimate][ee] 10.7.

Overview

If you are using GitLab CI/CD, you can analyze your dependencies for known vulnerabilities using Dependency Scanning.

You can take advantage of Dependency Scanning by either including the CI job in your existing .gitlab-ci.yml file or by implicitly using Auto Dependency Scanning that is provided by Auto DevOps.

Going a step further, GitLab can show the vulnerability list right in the merge request widget area.

Use cases

It helps you automatically find security vulnerabilities in your dependencies while you are developing and testing your applications. E.g. your application is using an external (open source) library which is known to be vulnerable.

Supported languages and dependency managers

The following languages and dependency managers are supported.

Language (package managers) Scan tool
JavaScript (npm, yarn) gemnasium, Retire.js
Python (pip) gemnasium
Ruby (gem) gemnasium, bundler-audit
Java (Maven) gemnasium
PHP (Composer) gemnasium

Some scanners require to send a list of project dependencies to GitLab central servers to check for vulnerabilities. To learn more about this or to disable it please check GitLab Dependency Scanning documentation.

How it works

First of all, you need to define a job in your .gitlab-ci.yml file that generates the Dependency Scanning report artifact. For more information on how the Dependency Scanning job should look like, check the example on Dependency Scanning with GitLab CI/CD.

GitLab then checks this report, compares the found vulnerabilities between the source and target branches, and shows the information right on the merge request.

Dependency Scanning Widget