Skip to main content

🛡️ GitLab Dependency Scanning

vet supports native GitLab Dependency Scanning. You can use vet to protect your project from malicious and vulnerable dependencies on every push and merge request to GitLab.

Prerequisites​

  • GitLab Account
  • GitLab Group with Ultimate Plan
info

Any kind of security scanning is only available to GitLab Ultimate plans.

Free users can still use vet ci component to check for Policy Violations in their project. See Policy input configuration for more details.

Configure GitLab Dependency Scanning​

To enable vet dependency scanning in your GitLab project, you need to:

1. Enable CI on your project.​

To do this, create a .gitlab-ci.yml file in the root of your project.

touch .gitlab-ci.yml

2. Add vet as a CI Component in your ci pipeline.​

To do this, add the following to your .gitlab-ci.yml file:

Here we use v1.5.0 version of the ci component. Check the Release for latest version.

include:
  - component: gitlab.com/safedep/ci-components/vet/[email protected]

Now commit and push changes to your project to trigger the first scan.

This is it! 🚀, congrulation you have enabled vet dependency scanning in your GitLab project.

You will see the vet job in your pipeline, with a security tab.

GitLab Dependency Scanning Pipeline view

You can find all the vulnerabilities and malware found by vet in the security tab.

GitLab Dependency Scanning Security tab

You can also view these details on the Project > Secure > Vulnerabilitiy Report page.

GitLab Dependency Scanning Vulnerability Report

Inputs & Configuration​

This CI Component supports many inputs and configuration options.

All inputs & configuration options are available in the vet's GitLab Component Catalog.

Cloud Sync​

To enable cloud sync you need to set the following input:

include:
  - component: gitlab.com/safedep/ci-components/vet/[email protected]
    inputs:
      cloud: true
      cloud-key: $CLOUD_KEY
      cloud-tenant: $CLOUD_TENANT
danger

Make sure to put the CLOUD_KEY and CLOUD_TENANT in the GitLab CI/CD variables.

This will sync the scan results to SafeDep Cloud.

Policy Configuration​

To scan with filters and policy file, you can use the following input:

include:
  - component: gitlab.com/safedep/ci-components/vet/[email protected]
    inputs:
      policy: '.gitlab/vet/policy.yml' # path to your policy file

See Policy as Code for more details.

The CI Job will fail if any policy violations are found. You have to see the logs for finding which policy is violated.

Other Inputs​

Version​

Specify which version of vet to use.

include:
  - component: gitlab.com/safedep/ci-components/vet/[email protected]
    inputs:
      version: v1.9.0

Trusted Registries​

Trusted registry URLs to use for package manifest verification.

include:
  - component: gitlab.com/safedep/ci-components/vet/[email protected]
    inputs:
      trusted-registries:
        - https://url.com
        - https://url2.com

Artifacts Access Configuration​

Artifact access to determine who can access the job artifacts from the GitLab UI or API. It can be set to all, developer, or none.

include:
  - component: gitlab.com/safedep/ci-components/vet/[email protected]
    inputs:
      artifact-access: 'developer'
danger

Only use all if you are ok with exposing the security scan results to pulic.

Issue Reporting​

If you find any issue with vet GitLab Component, please report it to us on Repository.