LogoLogo
WebsitePricingBlog
  • Debricked Documentation
  • Overview
    • Getting started
      • Create a OpenText Core SCA account
      • Running OpenText Core SCA
    • Help
      • Frequently asked questions (FAQ)
      • Upgrade your account
      • Get help in OpenText Core SCA tool
    • Language support
      • C# - Nuget, Paket
      • CycloneDX SBOM
      • Go - Go Modules, Go Dep, Bazel
      • Java & Kotlin - Gradle, Maven, Bazel
      • JavaScript - NPM, Yarn, Bower
      • Objective-C - CocoaPods
      • PHP - Composer
      • Python - Pip, Pipenv
      • Ruby - RubyGems
      • Rust - Cargo
      • Swift - CocoaPods
      • Linux package managers
      • Scala - SBT
    • Security overview
  • Product
    • Vulnerability management
      • Security terms
      • Data sources
      • See your data
      • Pull Requests (PR)
        • Enable Pull Request support
        • Solve vulnerabilities using Pull Requests (PR)
        • Solve vulnerabilities using Pull Requests (PR) via API
      • Set a review status
        • Snooze or pause a review status
      • Reachability Analysis
        • Set up Reachability Analysis for Java
        • Set up Reachability Analysis for Go
      • Solve vulnerabilities manually with root fixes
    • License risk management
      • Licence families
      • License risks
      • Set up a use case
        • Set up a use case using API
      • Proxy non-standard license identifiers
    • Project health
      • Contributors
      • Popularity
      • Security
    • Open source select
      • Search projects
      • Compare projects
      • View more details
      • Start left policies
      • OpenText Core SCA Select Browser Extension
      • End of Life (EOL)
    • Automation
      • Create an automation rule
      • Edit an automation rule
      • Default automation rules
      • Set up webhooks
      • Policies
      • Monitoring
    • Exporting or SBOM
      • Overview
      • License export
      • Vulnerability export
      • SBOM export
        • CycloneDX SBOM export
        • SPDX SBOM export
    • Administration
      • Generate access token
      • Account
        • Change your password
        • Delete your account
        • Delete company account
      • Billing
        • Manage contributing developers
        • Manage billing frequency
        • Manage payment methods
        • Access invoices
        • Manage your subscription
      • Settings
        • Enable and disable snoozing vulnerabilities
        • Supported language for Debricked tool
        • View logged events
        • Two-Factor Authentication (2FA)
      • Users
        • User roles (freemium and premium)
        • Role-Based Access Control (Enterprise)
        • Manage users
          • Add a new user
      • Repositories
        • Default Branch
        • Repository groups
        • Manually upload a dependency file
        • Manage your commits
  • Tools & Integrations
    • Command Line Interface (CLI)
      • Debricked CLI
        • High performance scans
        • File fingerprinting
      • Legacy CLI
    • CI/CD integrations
      • GitHub
      • CircleCI
      • BuildKite
      • GitLab
      • Bitbucket
      • Azure DevOps
      • Argo workflows
      • Travis CI
      • Jenkins
      • Bamboo
      • TeamCity
    • Fortify on Demand (FoD)
    • Fortify Software Security Center (SSC)
    • Debricked APIs
      • Open source select API
    • Integrated Development Environments (IDEs)
    • Single Sign-On (SSO)
      • Single Sign-On (SSO) through Okta
      • Single Sign-On (SSO) through Microsoft Entra ID
      • Single Sign-On (SSO) through JumpCloud OIDC
      • Single Sign-On (SSO) through GitHub
  • Tips & Tricks
    • Debricked CLI migration guide
    • Workarounds
      • Scanning Conan (C++) projects
      • Scanning a repository with different services
      • Scanning Docker images
      • Automations: Do not fail on found CVE lacking a fix
Powered by GitBook
LogoLogo

Company

  • Pricing
  • Blog

Support

  • Privacy Policy
  • Terms & Conditions
  • Service Status

Resources

  • Vulnerability DB
  • Open Source Select

© 2018-2024 | Open Text

On this page
  • Advantages of new CLI
  • Migration to new CLI

Was this helpful?

Export as PDF
  1. Tips & Tricks

Debricked CLI migration guide

Learn why you should migrate to the new CLI and what actions are needed from your side.

Last updated 2 months ago

Was this helpful?

The Legacy CLI has now been officially deprecated. Going forward, all the efforts and enhancements will be dedicated solely to the new Debricked CLI. Thus, Debricked strongly recommends and encourages your transition to the new CLI in order to stay aligned with the latest features and improvements. Read on to find out why you should migrate to the new CLI and what actions are needed from your side.

Advantages of new CLI

The new Debricked CLI is distributed as a self-contained binary, removing the need for a PHP environment. This makes it easier to install, integrate, run, and upgrade. Following are the new functionalities and improvements made the new CLI:

  • Automatic application of git metadata to scans

  • Faster scanning*: Finding and uploading files is now significantly faster

  • Improved call graph generation for vulnerable functionality

  • Manifest-less/fingerprint matching

*In the new CLI, a new cutting-edge technology: is incorporated . This technology enables you to accurately and swiftly resolve full dependency trees for repositories without a lock file.

Migration to new CLI

Migration to the new CLI is a simple process, but the pipeline configuration needed will differ depending on your CI/CD tool. Debricked has created templates using the new CLI for all natively supported integrations. With the new CLI it is also easier than before to set up an integration with a non-natively supported CI/CD tool. The templates for setting up the integration can be found below. If you need help in setting up your migration, do not hesitate to which will help you get set up with the new CLI.

  • GitHub actions

    • To integrate several repositories with a single configuration check out

  • Azure DevOps

    • To integrate several repositories with a single configuration check out

  • GitLab CICD

    • To integrate several repositories with a single configuration check out

  • Bitbucket

    • To integrate several repositories with a single configuration check out

  • Argo

  • Travis

  • CircleCI

  • Jenkins

  • BuildKite

  • Other, If your CI/CD tool is not mentioned above

    • Because the CLI is distributed as a self-contained binary, using it in your CI/CD is often as simple as downloading the binary and running `debricked scan`. An example of how that script might look, using a linux based CI/CD setup, can be found below.

      - curl -L https://github.com/debricked/cli/releases/download/release-v1/cli_linux_x86_64.tar.gz | tar -xz debricked
      - ./debricked scan
High Performance Scans
contact Debricked support team
GitHub example template
Azure example template
GitLab example template
Bitbucket example template
Argo example template
Travis example template
CircleCI example template
Jenkins example template
BuildKite example template
this page
this page
this page
this page