OpenText Core SCA CLI migration guide
Learn why you should migrate to the new CLI and what actions are needed from your side.
Last updated
Was this helpful?
Learn why you should migrate to the new CLI and what actions are needed from your side.
Last updated
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 OpenText Core SCA CLI. Thus, OpenText Core SCA 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.
The new OpenText Core SCA 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 the new CLI is a simple process, but the pipeline configuration needed will differ depending on your CI/CD tool. OpenText Core SCA 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.