License export
Learn how to create a License Export.
Last updated
Was this helpful?
Learn how to create a License Export.
Last updated
Was this helpful?
Knowing what kind of licenses you have imported through your dependencies is crucial, as failing to comply with open-source licenses puts you at legal risk. OpenText Core SCA allows you to make an export with all licenses and the affected repositories. This enables you to let relevant stakeholders get an easy overview of the state of compliance and keep track of your progress over time.
Click Generate Export on the top right corner of the page.
Select the scope of the export as wither global, repositories or groups.
Under Export Type, select License Export.
Check your email for the exported data, which will be sent to you in the .xslx format. If you cannot find the email in your inbox, check the SPAM folder.
Depending on the selected scope, you might receive three different types of exported data:
The excel sheet is divided into three columns:
License - The name of the license.
Repositories - The name of the repository using that license, the latest commit hash, and the creation date of that commit.
License family - The name of the license family.
The excel sheet contains the name of the repository in the first row, divided into five columns:
Dependency - The name of the dependency.
Dependency id - The ID number of the dependency.
License - The name of the licenses used by the dependency.
Version - The version of the dependency.
Direct/Indirect - The type of the dependency, which can be listed as "D = Direct", "I = Indirect" and "? = undefined".
The excel sheet contains the name of the license in the first row, divided into two columns:
Repositories - The name of all the repositories using that license.
Dependencies - The name of all the dependencies using that license per repository.