SCA Results

The SCA Results page shows the SCA results for the most recent scan of your Project. This includes a list of all 3rd party packages identified in your Project as well as the specific risks associated with those packages such as vulnerabilities, legal risks, and outdated versions.

This screen includes a Header bar with general info about the Project and scan. It also shows detailed scan results, divided into the following tabs.

Packages – shows info about the open source packages used by your project and the risks that are associated with those packages, including: security vulnerabilities, license violations, and outdated versions. This tab includes two types of pages:
- All Packages – shows a list of all packages that were identified by this scan
- Package Details – shows detailed info about the risks associated with a specific package.
Tip
If there is a package that is in need for recalculation (e.g., the Package was snoozed or muted), a red dot indicator will be shown on the Packages tab.
Risks – shows info about all of the security vulnerabilities that were identified in the open source packages used by your project, including: severity level, CVE references, remediation recommendations etc. This tab includes two types of pages:
- All Risks– shows a list of all vulnerabilities identified in your open source dependencies.
- Risk Details – shows detailed info about a specific vulnerability.
Container (for projects with container images) – shows info about packages identified in your container images as well as the vulnerabilities associated with those packages.
- Container Packages – shows a list of all of the packages identified in the container images.
- Container Vulnerabilities – shows a list of all of the vulnerabilities associated with the container packages.
Licenses - shows info about all of the licenses that are associated with the open source packages used by your project.
- All Licenses – shows a list of all licenses associated with the open source packages identified in this scan.
- License Details – shows detailed info about a specific license. Click on a row in the All Licenses tab to access this page.

Header Bar

The header bar shows general info about the Project and scan that is currently displayed on the page.

The following tables describe the info shown in the Header bar and the Action buttons that are available.

Header Bar Info

Item	Description	Possible Values
Project Name	The name of the project.	e.g., webgoat5
Last scan	The date and time that the scan was run.	e.g., Feb 23, 2021 11:51 AM
Scan ID	When you hover over Scan ID, the unique identifier of the scan generated by Checkmarx SCA is shown. There is a button to copy the ID to your clipboard.	e.g., 95fc1f60-a4aa-4835-acfd-95aa315d4890

Actions

Icon	Action	Description	Options
	Recalculate Scan	Reevaluate the risks associated with the dependencies in your project. See Recalculating SCA Scan Results
	Scan Report	Click on this button to download a file containing an overview of the security of your project as well as specific vulnerabilities, legal risks, and outdated versions identified by the scan.	Report sections: All data tables (Default) Packages Vulnerabilities Licenses Policy Violations File formats: PDF (Default) XML JSON CSV
	Software Bill of Materials	Click on this button to download a file containing detailed info about each of the open source packages used by your program, and the associated risks. You can specify how the SBOM will be formatted, CycloneDX v1.5 or SPDX v2.2. Learn more about Checkmarx's SBOMs here.	File formats: XML (for CycloneDx only) JSON
	Remediation Manifest	Click on this button to start the process of remediating the Project’s manifest files. For more information see Remediation using a Manifest File.	N/A
Hide Dev Dependencies toggle		Toggle this switch on in order to hide results for dev packages. For more information, see Supported Dev Dependencies Specification.

Hiding Dev & Test Dependencies

Checkmarx SCA is able to distinguish between development dependencies and production dependencies for several package managers. On the Scan Results page, the number in parenthesis next to the Hide Dev & Test Dependencies toggle indicates the number of dev & test dependencies in the Project. Toggle the Hide Dev & Test Dependencies switch ON if you would like to hide vulnerable packages that were identified as dev and test dependencies.

Identifying Dev Dependencies

The following table shows how dev dependencies are identified for specific package managers.

Package Manager	Dev Dependency Specification
NPM	In the manifest file (package.json or bower.json), using the devDependencies attribute. For example, "devDependencies" : { "my_test_framework": "^3.1.0". "another_dev_dep": "1.0.0 - 1.2.0" }
Yarn
Bower
Composer	Packages under the require-dev section in the composer.json file.

Identifying Test Dependencies

Any package with the word "test" in the file path is identified as a test dependency.

Packages Tab

The Packages tab shows detailed info about the packages that were identified in your source code and the vulnerabilities that they contain.

The Packages tab contains sub-tabs that show two types of pages:

All Packages – shows a list of all packages that contain vulnerabilities that were identified by this scan. This tab is accessed by clicking on the Show All button on the Project page.
Notice
Alternatively, whenever you navigate to the Scan Results page the All Packages sub-tab is shown under the Packages tab.
Package Details – shows detailed info about a specific package. Click on a row in the All Packages sub-tab or in the Project page to access this page.
Notice
Alternatively, you can access this page by clicking on a package in the Global Inventory & Risks > Packages page.

You can navigate between the various tabs that you have opened.

All Packages Page

The All Packages sub-tab shows separate tabs for the different types of packages (Direct 3rd Party Packages, Transitive 3rd Party Packages, and Saas Providers). Each tab shows the overall number of packages of this type as well as the number of policy violations for that category.

Notice

For a package that is referenced both directly and transitively, the total number of packages shown at the top of the All Packages tab counts that package only once. Therefore, the total number of packages may be fewer than the total of the Direct packages plus the number of Transitive packages.

Clicking on a category heading expands that section, to show a list of packages of that type that were identified by this scan of your Project. For each package, info is shown about the risks related to that package. You can search for specific packages using the search box.

You can also sort by column headers and set filters for each column.

The following table describes the info shown for each package identified by this scan.

Item

Description

Possible Values

Package

The name of the package.

e.g., dom4j:dom4j

Version

The version of the package that you are using.

e.g., 1.6.1

Outdated

Indicates whether or not a more recent version of the package is available.

The package is outdated. Hover over the icon to view additional info about the more recent versions.

An empty field indicates that the package is up to date.

Effective License

Shows the Licenses that are associated with the package. For multiple licenses, hover over the display to show all licenses and the associated legal risks.

e.g., GPL 2.0, Apache2.1

Risks (Aggregated)

A color coded bar graph indicating the number of vulnerabilities of each severity level. Hover over the bar to view a breakdown of the results by Vulnerability, Legal Risk and Supply Chain.

Tip

You can apply complex filters to show only packages that contain risks of a specific type and of a specific severity.

Tip

If a Package is muted or snoozed, the respective icon will be placed instead of the bar.

e.g.,

Identified By

Indicates how the package was identified.

Manifest – identified by resolving the manifest file
Binary – identified by analyzing hashes and fingerprints of files in the Project

References

Shows the number of paths that reference this package.

Tip

Packages that are referenced both directly and transitively, are included in the Direct 3rd Party section and the number of direct (D) and transitive (T) paths are given.

e.g., 1D, 12T

Usage

(for Projects with Exploitable Path activated)

Indicates whether or not this package is used (called) by your project’s source code.

Used - This package is used by your project’s source code.
Potentially Used - This package is a dependency of a direct package that is used by your project’s source code.
Unused - No usage of this package was found.
Unknown - Checkmarx SCA could not determine whether the package is used.

Dependency

Shows labels that Checkmarx applied to the package. There is a label indicating the package manager used for package resolution. Additional labels are applied to special types of dependencies.

Package Manager - shows the package manager that was used for resolution, e.g., Maven, Pip, Nuget, Npm etc.
Dev - is applied to dev dependencies.
Test - is applied to all packages that have the word "test" in their file path.
Verified by NPM - is applied to packages for which the signatures were verified using npm audit signatures.
Private Package - is applied to packages that are hosted on private repositories.
Framework - is a package that is included in the Framework installation. These packages usually can't be remediated without updating the version of the overall framework.
Tip
Currently supported only for .NET projects.

AppSec Knowledge Center

Link to the AppSec Knowledge Center page for each package.

Package Details Page

The Package Details sub-tab shows detailed info about a specific package. The top info pane gives general info about the package, and the separate cards below it show detailed info about various aspects of the risks posed by the package. If the package requires recalculation (e.g., the package was snoozed or muted), a red dot indicator will be shown on the sub-tab.

Info Pane

Item	Description
Package	The name and version of the package.
Dependency Type	The type of package manager used for this package.
License(s)	Shows all licenses that you have that are associated with this package.
Published	The date that this version of the package was published.
State	The state of the package. Clicking on the state opens a side panel with a drop down list to choose the state from. Warning Changes in package state are a serious matter; Saving changes can only be implemented with a comment explaining your consideration. Options are: Monitored (default) - vulnerabilities are displayed based on the risk score. Muted - vulnerabilities associated with the package will permanently not be shown as risks to your project. Snoozed - vulnerabilities associated with the package will be muted temporarily. It is required to choose a date for the snooze to expire. The side panel includes a History tab where you can view a log of previous state changes and comments.

Package Details Sections

Item	Description
Watch Out! (for malicious packages)	This warning card will be displayed if this version of the package is known to be malicious.
Policies	The total number of policies this project is assigned to, followed by the number of Policy Violations.
Vulnerability	The total number of vulnerabilities in this package, followed by a color coded bar graph indicating the number of vulnerabilities of each severity level.
Legal Risk	The total number of Legal Risks in this package, followed by a color coded bar graph indicating the number of Legal Risks of each severity level.
Suspected Malware	The total number of Suspected Malware risks affecting this package, followed by a color coded bar graph indicating the number of Suspected Malware risks of each severity level.
Package Reliability Indicators (for packages with Suspected Malware risks)	Shows gauge widgets representing three risk categories (Reputation, Reliability and Behavior). The scores are given on a scale of 0-10, with 10 indicating the highest level of security.
Version	Shows the version you are using, the newest version, the number of newer versions released since you last updated and an overall assessment of whether there is a need to update your version.
Learn More About This Package	Shows a link to the AppSec Knowledge Center for more information about this package.
Management of Risks	Shows if any vulnerabilities and Suspected Malware risks have been marked as ignored.
Management of Licenses	Shows the number of Licenses that have been marked as Effective Licenses. In addition, a link is given to view detailed information about this license in the risk details tab.
References	Shows the number of manifest files that refer to this package and indicates whether it is a direct or transitive dependency.
Identified By	Indicates how the vulnerable package was identified. Possible values are: Manifest – identified by resolving the manifest file Binary – identified by analyzing hashes and fingerprints of files in the Project
File Path	The file path to the manifest file where this package was identified is shown. Click on the icons to view or download the file.
Package Path	The selected package is displayed in blue. If this is a transitive dependency (i.e., it is accessed via other packages), then the full path by which the package is accessed is shown above it. You can click on any package shown in the path in order to open a new tab showing details for that package. If there are multiple paths to this package, then you can click on the forward and back arrows at the bottom of the pane to view each of the paths. Tip For packages that were identified by binaries (and not by a manifest file), no data is shown for the package path. Tip Frequently you can fix the vulnerabilities by updating the transitive packages with their latest versions.
Package Usage (for projects with Exploitable Path activated)	Shows the places in your code where the vulnerable package is called. Results are grouped by file path. Expand an item to see the line number and node of each place where the package is called.

Risks Tab

The Risks tab shows info about all of the Risks that are associated with the open source packages used by your project. This includes vulnerabilities (e.g., CVEs), as well as suspected malware (e.g., malicious packages), legal risks and outdated packages.

The Risks tab contains sub-tabs that show two types of pages:

All Risks – shows a list of all Risks identified by this scan. This tab is accessed by clicking on the Show All button on the Project page and then selecting the Risks tab. The results on the All Risks tabs are divided into the following tabs:
- Vulnerability - shows a list of vulnerabilities in your open source packages that can be exploited by an attacker. This includes vulnerabilities that have been published as CVEs as well as vulnerabilities identified by the Checkmarx Vulnerability Research Team (i.e., Cx). The summary graph shows the total number of vulnerabilities and a breakdown by severity level.
- Suspected Malware - shows various types of suspected malware risks that affect the packages in your project, such as packages that are Malicious by design and packages that are vulnerable to ChainJacking attacks etc. The summary graph shows the total number of suspected malware risks and a breakdown by severity level.
- Legal Risk - shows all of the Legal Risks relating to the licensing of the packages used in your project. The summary graph shows the total number of legal risks and a breakdown by severity level. Learn more about Legal Risks in the section below.
- Outdated - shows a list of all packages that have vulnerabilities or suspected malware risks, for which a more recent package version is available. The summary graph shows the total number of vulnerable outdated packages as well as a breakdown by severity level (i.e., highest severity vulnerability in the package).
Risk Details – shows detailed info about a specific Risk. Click on a row in the All Risks tab to access this page.

Notice

Alternatively, you can access this page by clicking on a Risk in the Global Inventory & Risks > Risks page.

Notice

Clicking on a Legal Risk opens the Licenses tab filtered for the relevant license.

The packages listed in the Outdated section aren’t clickable and don’t have a Risk Details page associated with them.

You can navigate between the various tabs that you have opened.

Legal Risks

Overview

Checkmarx identifies all of the licenses associated with the open source packages used in your project. The complete list of licenses is shown in the Scan Results > Licenses tab.

Notice

The License Score represents the level of risk associated with using a package under that license. However, the license doesn't pose an actual risk to your project unless you are actually using the package under that license (i.e., it is your Effective license).

In addition, Checkmarx identifies actual risks to your project based on legal issues related to improper usage of open source packages. These risks are shown in the Scan Results > Risks tab in the Legal Risk section.

Marking Licenses as Effective or Not Effective

Packages often have several different licenses associated with them. This gives users the option to choose which license to consider "effective" for that package, i.e., which set of license restrictions they would like to follow. As long as you are abiding by the terms of the effective license, the other licenses don't constitute a legal risk.

Initially, the state of most licenses is set as To Verify. However, when there is a sole license for a package and it was identified in a reliable source, that license is automatically marked as Effective. You can then review the licenses and mark each license as Effective or Not Effective based on your assessment of the package usage. Changing the state of a license is done via the Checkmarx One web application, on the Risk Details page.

Legal Risks are only shown if they relate to an Effective license.

Types of Legal Risks

We currently identify the following types of legal risks.

Risky effective license - A license with high severity License Score is marked as Effective for this package.
Package with no effective license - There is an open source package in your project for which no license has been marked as Effective.
Package with no license - Checkmarx didn't identify any licenses associated with this package.

Recommended Workflow

The following E2E workflow explains how you can leverage the legal risk functionality provided by Checkmarx to get results that accurately reflect the security posture of your project from a legal perspective.

Create a project and run a scan.
Go to the Risks tab > Legal Risks and check for packages with no license associated.
If you aware of the relevant licenses for these packages, add them via API, using POST /management-of-risk/package-licenses.
Go to the Scan Results > Licenses tab. Review each license and mark whether or not it is the Effective license for the specified package (via the web application).
On the Scan Results page, click on > Recalculate Last Scan.
After the recalculation is complete, go to the Risks tab > Legal Risks and check what Legal Risks were identified in your project.
Take the required steps to remediate these risks.

All Risks Page

The All Risks sub-tab shows separate tabs for the different types of Risks (Vulnerability, Suspected Malware, Legal Risk and Outdated). Each tab shows the overall number of Risks for this type and the number of Risks for each risk level. Clicking on the arrow on the left of the tab expands a list below it to show all Risks of this type identified by this scan of your Project. For each Risk, info is shown about the nature of the Risk. You can search for specific Risks using the search box.

Notice

If a risk affects several packages in your Project, a separate record is listed for each instance of the risk.

You can also sort by column headers and set filters for each column.

Clicking on the arrow on the left of the tab expands a list showing all of the risks of that type.

Notice

Risks that have been marked as Not Exploitable are shown with a strikethrough line and they aren't counted towards the total number of risks. However, changes to the summary counters only take effect when a subsequent scan or scan recalculation is run.

The following table describes the info shown for each vulnerability identified by this scan.

Item	Description	Possible Values
Status	Indicates the status of this vulnerability for this project.	For vulnerability or suspected malware risks: To Verify - This is the initial state of all vulnerabilities and suspected malware risks, indicating that it is a new finding that hasn’t yet been assessed by your AppSec team. Not Exploitable - Select this state if your team has determined that this risk doesn’t pose a threat to your application (and isn’t expected to cause a risk at any time in the future). Proposed Not Exploitable - Select this state if your team has suggested tentatively that this risk doesn’t pose a threat to your application. Confirmed - Select this state if your team has confirmed that this risk does pose a threat and requires mitigation. Urgent - Select this state if your team has determined that this risk poses an imminent threat and requires urgent mitigation. Tip When the state is set as Not Exploitable, the risk is marked with a strikethrough line and the Risk Details page is grayed out. Indicates a legal risk that was marked as “effective”.
Exploitability	Shows which exploitability indicators apply to this vulnerability.	Exploitable Path - indicates that a path was detected from your source code to the vulnerable method in the package, enabling attackers to exploit the vulnerability. Tip Results are only returned if Exploitable Path was activated for this project and the project uses a language that is supported for Exploitable Path. Known - This vulnerability is cataloged by CISA as a Known Exploited Vulnerability (KEV), indicating that it poses a severe and imminent threat. PoC - A Proof of Concept (POC) for exploiting this vulnerability is available in the wild, making it easy for threat actors to implement an exploitation of this vulnerability. We draw this info from Offensive Security's Eploit Database. EPSS - The EPSS (Exploit Prediction Scoring System) is a score provided by First for vulnerabilities. The score is an estimate of the likelihood for a vulnerability to be exploited. The score is presented as a percentage indicating the likelihood of this vulnerability to be exploited within the next 30 days. Hovering over the score will display a percentile indicating the ranking of this risk relative to other vulnerabilities.
Risk Score	Shows the the severity level of the vulnerability based on its CVSS score in the NVD, as well as the precise CVSS score. Tip The Common Vulnerability Scoring System (CVSS) is an open framework for communicating the characteristics and severity of software vulnerabilities.	- this package version is malicious by design. HIGH MEDIUM LOW Tip For Legal Risks, risks with UNKNOWN severity are shown in light grey. For more info see Severity Levels.
ID	The ID of the CVE listing. The ID consists of the CVE prefix followed by the year that the CVE was discovered and the serial counter for that year's CVE listings. Tip Vulnerabilities discovered by the Checkmarx Vulnerability Research Team which are net catalogued as CVEs, are indicated by the “Cx” prefix.	e.g., CVE-2020-9488
Category	The category of the vulnerability. For CWEs, the CWE is given as well as a brief description of the vulnerability.	e.g., CWE-89\|SQL Injection, Malicious, ChainJacking etc.
Identified in Package	The name and version of the package in which the vulnerability was identified. In addition, an indication is shown for the type of dependency: D - Direct dependency T - Transitive dependency M - Mixed dependency (i.e., the package is used in the project both directly and also transitively) Results can be filtered by dependency type.	e.g., loadash @ 4.13.1 ^(T)
Detection/Publication	Click on the desired header to alternate between the detection and publication dates. Detection - the date that this vulnerability was first identified in this project. For vulnerabilities that were first identified in this scan, the NEW label is shown. Publication - the date that this vulnerability was first officially published on a supported public Security Advisory.	e.g., Nov 16, 2020
Explore in AppSec Knowledge Center	Click on the icon to learn more about this vulnearbility in our AppSec Knowledge Center.

Risk Details Page

The Risk Details sub-tab shows detailed info about a specific Risk. The top info pane gives general info about the vulnerability, and the separate cards below it show detailed info about various aspects of the risks posed by the vulnerability.

The different risk types are:

Vulnerability - a vulnerability that can be exploited by an attacker. This includes vulnerabilities that have been published as CVEs as well as vulnerabilities identified by Checkmarx AppSec experts (i.e., Cx).
Suspected Malware - shows various types of Suspected Malware risks that affect the packages in your project, such as packages that are Malicious by design and packages that are vulnerable to ChainJacking attacks.

Notice

There are no Risk Details pages associated with Legal Risks or Outdated packages. Clicking on a Legal Risk opens the Licenses tab filtered for the relevant license. Outdated packages aren’t clickable.

Each type of risk shows different cards on the details page. The different cards are described in the tables below.

Vulnerability Details

Vulnerabilities are risks that can be exploited by an attacker. This includes vulnerabilities that have been published as CVEs as well as vulnerabilities identified by the Checkmarx Vulnerability Research Team (i.e., Cx).

Info Pane

Item	Description	Possible Values
ID	The ID of the CVE listing. The ID consists of the CVE prefix followed by the year that the CVE was discovered and the serial counter for that year's CVE listings. Tip Vulnerabilities discovered by the Checkmarx Vulnerability Research Team which are net yet catalogued as CVEs, are indicated by the “Cx” prefix.	e.g., CVE-2019-12384
Package	The name of the package in which the vulnerability was identified.	e.g., com.fasterxml.jackson.core:jackson-databind 2.9.8
Version	The version of the package where the vulnerability was identified.	e.g., 5.1.26
Detected in Project	The date that the vulnerability was first identified in this project.	e.g., May 12, 2024
Risk Level	The severity level of the vulnerability, based on its CVSS score in the NVD database.	HIGH - 7.0-10.0 MEDIUM - 4.0-6.9 LOW - 0.0-3.9 For more info see Severity Levels.
Risk State	This indicates the current state of the vulnerability as determined by your AppSec team. All new risks are initially marked as To Verify. A user with `manage-risk` role (e.g., Admin, SCA Manager) can change the Risk state for this Project by clicking on the Risk State field and selecting the radio button for the desired state. See Risk Management.	To Verify Not Exploitable Proposed Not Exploitable Confirmed Urgent Tip When the state is set as Not Exploitable, the page is grayed out and the risk is marked with a strikethrough line on the All Risks tab.

Vulnerability Details Sections

Item	Description
Category	The ID and description of the CWE (Common Weakness Enumeration) listing. The ID consists of the CWE prefix followed by the serial counter.
CVE Details	A description of the nature of the threat posed by the vulnerability and the date the vulnerabiliity was published in the NVD.
References	Links to external resources about the vulnerability. Links are given for topics such as: Advisory, Commit, Release Notes, Issue etc.
Remediate this Vulnerability	Recommended steps that should be taken to remediate this vulnerability. Tip The recommended package version, is the minimum version that does not contain this particular vulnerability. To find the minimum version that doesn’t contain any vulnerabilities, click on Find best package version.
Policies	The number of Policies the Project is assigned to and the number of Policy violations.
Vulnerable Package Path	The vulnerable package is displayed in blue. If this is a transient dependency (i.e., it is accessed via other packages), then the full path by which the package is accessed is shown above it. You can click on any package shown in the path in order to open a new tab showing details for that package. Tip Frequently, you can fix the vulnerabilities by updating the transient packages with their latest versions.
Exploitability	Shows which exploitability indicators apply to this vulnerability. (KEV, POC, EPSS and Exploitable Path)
Vulnerability Score	Shows the CVSS Version, Score, and Severity, as well as the components that make up the CVSS score including: Attack Vector, Confidentiality Impact, Attack Complexity, Integrity Impact, Authentication, and Availability Impact. For a full explanation of the metrics that make up the CVSS score, see section 2 of this article.
Customization	Displays comments regarding this vulnerability and a link to view the risk management history.

Suspected Malware Details

Suspected Malware includes various types of risks that affect the packages in your project, such as packages that are Malicious by design and packages that are vulnerable to ChainJacking attacks.

Info Pane

Item	Description	Possible Values
ID	An internal ID starting with the “Cx” prefix that was assigned to this risk by the Checkmarx Vulnerability Research Team.	e.g., Cx27b685d0-978d
Package	The name of the package in which the vulnerability was identified.	e.g., com.fasterxml.jackson.core:jackson-databind 2.9.8
Version	The version of the package where the vulnerability was identified.	e.g., 5.1.26
Risk Level	The severity level of the vulnerability, based on its CVSS score in the CVE database. Malicious (suspected malware) packages are labeled Malicious and the icon is shown.	- Malicious HIGH MEDIUM LOW For more info see Severity Levels.
Risk State	This indicates the current state of the suspected malware Risk as determined by your AppSec team. All new risks are initially marked as To Verify. A user with `manage-risk` role (e.g., Admin, SCA Manager) can change the Risk state for this Project by clicking on the Risk State field and selecting the radio button for the desired state. See Risk Management	To Verify Not Exploitable Proposed Not Exploitable Confirmed Urgent Tip When the state is set as Not exploitable, the page is grayed out and the risk is marked with a strikethrough line on the All Risks tab.

Suspected Malware Details Sections

Item	Description
Information	A description of the nature of the threat posed by the suspected malware and the date the suspected malware was published on the NVD.
References	Links to external resources about the risk. Links are given for topics such as: Article, etc.
Remediate this Vulnerability	Recommended steps that should be taken to remediate this vulnerability.
Policies	The number of Policies the Project is assigned to and the number of Policy violations.
Vulnerable Package Path	The vulnerable package is displayed in blue. If this is a transient dependency (i.e., it is accessed via other packages), then the full path by which the package is accessed is shown above it. You can click on any package shown in the path in order to open a new tab showing details for that package. Tip Frequently, you can fix the vulnerabilities by updating the transient packages with their latest versions.
CVSS/Risk Score	Shows the CVSS Version, Score, and Severity. For a full explanation of the metrics that make up the CVSS score, see section 2 of this article.

License Details Page

Legal Risks include all of the Legal Risks relating to the licensing of the packages used in your project.

Info Pane

Item	Description	Possible Values
ID	The name of the License.	e.g., MIT
Package	The name and version of the package that the license is associated with.	e.g., Fuzzball@1.4.0
State	The current state of the license.	To Verify Effective Not Effective

Legal Risk Details Sections

Item	Description
Information	The source of the license detection followed by a description of the nature of the threat posed by the legal risk.
References	Links to external resources about the vulnerability. Links are given for topics such as: License URL, etc.
Customization	View state changes and comments for this license. An admin user can mark a license as “Effective” for this package (i.e., if they intend to consume this package in accordance with the licensing restrictions of this license.).
Policies	The number of Policies the Project is assigned to and the number of Policy violations.
Legal Score	Shows the License Score and Severity, as well as the components that make up the License score including: Copyright Risk, Patent Risk and Copyleft. For an explanation on the calculation of these scores, see below.
License Details	Additional details about the terms of use of the license. This is divided into sections for Permissions, Limitations and Conditions.

Legal Risk Scores

You can view detailed info about legal risks affecting your packages by clicking on a legal risk in the Scan Results > Risks tab. The Legal Risks Details page opens showing detailed info about the related licenses and legal risks. The Legal Risk pane shows the overall License Score as well as scores for specific license risk categories. The following table explains these scores:

Field	Value type and range	Details
Copyright Risk Score	A number between 1 and 7 Sometimes represented as a multiple of 13, since in CxOSA it is presented on a scale of 1-100.	The score is defined as follows: 1 - Licensed users may use code without restriction. 2 - Anyone who distributes the code must retain any attributions included in original distribution. 3 - Anyone who distributes the code must provide certain notices, attributions and/or licensing terms in documentation with the software. 4 - Anyone who distributes a modification of the code may be required to make the source code for the modification publicly available at no charge. 5 - Anyone who distributes a modification of the code or a product that is based on or contains part of the code may be required to make publicly available the source code for the product or modification, subject to an exception for software that dynamically links to the original code. 6 - Anyone who distributes a modification of the code or a product that is based on or contains part of the code may be required to make publicly available the source code for the product or modification. 7 - Anyone who develops a product that is based on or contains part of the code, or who modifies the code, may be required to make publicly available the source code for that product or modification if s/he (a) distributes the software or (b) enables others to use the software via hosted or web services. Tip The Legal Risk calculation is based on the copyright risk score, where Level 1-3 is considered as a low risk, Level 4-5 as a medium risk, and Level 6-7 as a high risk.
Patent Risk Score	A number between 1 and 4 Sometimes represented as multiplications of 20, since in CxOSA is presented on a scale of 1-100	Ranks the license based on 1- Royalty free and no identified patent risks 2- Royalty free unless litigated 3- No patents granted 4- Specific identified patent risks
Copyleft	One of the following: Full, Partial, No	Copyleft is a property of the license that means that the package is free to use, but it is forbidden to make it proprietary. A copyleft license is also viral since any work containing a package that has a copyleft-license must also retain this property. The valid values are described as follows: Full - Full copyleft license Partial - Copyleft applies on modifications only No - Not a copyleft license
Linking Type	One of the following: Viral, NonViral, Dynamic	This parameter describes the situation where a package is linked to an application. (This use case is mainly covered in the GPL / LGPL license.) Viral - Infects the code using this package, meaning it will have to be under the same license ans the linked package. Non Viral - will not affect the licensing of the linking code Dynamic - Only cases of dynamic linking will not effect the licensing of the linking code (e.g., LGPL)
Royalty Free	Yes, No or Conditional	Some licenses explicitly grant a patent license. Some explicitly say they do not. Some condition the patent license on not being sued by the user, and if sued the license is revoked. Yes – patent license is granted No – patent license is not granted Conditional – patent license granted under some condition – this may change according to each license and requires consultation.
License Source Detection	e.g., Manifest File, Package Binary etc.	Indicates the source of information that identified the legal risk.

Container Tab

In addition to scanning the packages in your source code itself, Checkmarx SCA also scans the containers (i.e., Docker image files) on which your source code runs. Checkmarx SCA identifies each of the Docker files being used, extracts all layers of each Image file and identifies the packages used by each layer.

The Container tab shows the container packages identified in your project and the vulnerabilities associated with them.

The Container tab contains two sub-tabs:

Container Packages – shows a list of all of the packages identified in the container images.
Container Vulnerabilities – shows a list of all of the vulnerabilities associated with the container packages.

Container Packages Page

The Container Packages sub-tab shows a list of all of the packages identified in the container images. For each container package, info is shown about the risks related to that package. You can search for specific packages and images using the search box.

You can also sort by column headers and set filters for each column.

The following table describes the info shown for each package identified in the containers.

Item

Description

Possible Values

Package Name

The name of the package.

e.g., musl

Version

The version of the package.

e.g., 1.2.2-r1

Image

The name of the image that was scanned.

e.g., python

Image Tag

The version of the image.

e.g., rc-alpine3.13

Vulnerabilities

A color coded bar graph indicating the number of vulnerabilities of each severity level.

e.g.,

Identified By

The path to the Docker file in which the specific image is found. (Hover to view the entire path.)

e.g., Joao4/JavaVulnerableLab-dockerfile/JavaVulnerableLab-master/dockerfile1/Dockerfile

Dep. Type

The repository in which the image is located.

e.g., Docker Hub

Container Vulnerabilities Page

The Container Vulnerabilities sub-tab shows a list of all of the vulnerabilities associated with the container packages. Detailed information is shown for each vulnerability. You can search for specific vulnerabilities and packages using the search box.

You can also sort by column headers and set filters for each column.

You can click on a vulnerability to open a new tab showing additional info about the vulnerability.

Notice

Container vulnerabilities for which the Category is "unknown" are marked as Low severity. Also, these vulnerabilities are only shown in the summary table, but you can't drill down to view the details page, since there are no details that we can provide.

The following table describes the info shown for each vulnerability that was identified in the containers.

Item	Description	Possible Values
Risk Level	The severity level of the vulnerability.	HIGH (RED) - (7.1 to 10.0) MEDIUM (ORANGE) - (3.1 to 7.0) LOW (GREY) - (0.0 - 3.0) For more info see Severity Levels.
ID	The ID of the CVE listing. The ID consists of the CVE prefix followed by the year that the CVE was discovered and the serial counter for that year's CVE listings.	e.g., CVE-2020-9488
Category	The category of the vulnerability.	e.g., CWE-20
Package Name	The name of the package in which the vulnerability was identified.	e.g., musl
Version	The version of the package in which the vulnerability was identified.	e.g., 1.2.2-r1
Publication Date	The date that this vulnerability was first officially published on a supported public Security Advisory.	e.g., Nov 16, 2020

Licenses Tab

The Licenses tab shows info about all of the licenses that are associated with the open source packages used by your project.

Notice

This page shows all licenses, even those that don't pose any particular legal risk. All license that pose a specific legal risk are shown in the Legal Risks section on the Risks tab.

The Licenses tab contains sub-tabs that show two types of pages:

All Licenses – shows a list of all licenses associated with the open source packages identified in this scan.
License Details – shows detailed info about a specific license. Click on a row in the All Licenses tab to access this page.

You can navigate between the various tabs that you have opened.

In this section:

SCA Results

Tip

Header Bar

Header Bar Info

Actions

Hiding Dev & Test Dependencies

Identifying Dev Dependencies

Identifying Test Dependencies

Packages Tab

Notice

Notice

All Packages Page

Notice

Tip

Tip

Tip

Tip

Package Details Page

Info Pane

Warning

Package Details Sections

Tip

Tip

Risks Tab

Notice

Notice

Legal Risks

Overview

Notice

Marking Licenses as Effective or Not Effective

Types of Legal Risks

Recommended Workflow

All Risks Page

Notice

Notice

Tip

Tip

Tip

Tip

Tip

Risk Details Page

Notice

Vulnerability Details

Info Pane

Tip

Tip

Vulnerability Details Sections

Tip

Tip

Suspected Malware Details

Info Pane

Tip

Suspected Malware Details Sections

Tip

License Details Page

Info Pane

Legal Risk Details Sections

Legal Risk Scores

Tip

Container Tab

Container Packages Page

Container Vulnerabilities Page

Notice

Licenses Tab

Notice

Search results