Component Fields

Code Insight 6.14.2 SP1

The following fields are available for every component in the Code Insight system. Additional component data may be stored in custom metadata fields. See Metadata Framework for more information.

Fields and Descriptions

Field

Description

Id

The unique ID of the component. Custom components have negative IDs while non-custom have positive IDs.

Name

The name of the component as stored in Code Insight.

Code Insight components (non-custom) are typically named according to convention based on the forge from which they are obtained. For example, Code Insight components obtained from GitHub include the author name and project name separated by a “-” in the name (OpenSSL from GitHub has the name “openssl-openssl” in Code Insight). Code Insight component names do not contain spaces.

Click the Help icon () in the Components Details tab to see other naming conventions based on forge.

Title

The unique title of the component as stored in Code Insight, the components (non-custom) of which are also named according to the convention based on the forge. For example, Code Insight components obtained from GitHub include the author name and project name separated by a “/” and appended with the term “GitHub” (OpenSSL form GitHub has the title “openssl/openssl – GitHub”.

Forge

The downloaded-from URL pointing to the page from which the component was downloaded.

URL

The project URL pointing to the project home page.

Description

The project description.

Encryption

Indicates whether the component uses encryption.

Vulnerabilities

Indicates whether the component contains one or more vulnerabilities. Click the icon to view details for the vulnerabilities associated with the different component versions.

Note:The scores and severities displayed in the security vulnerability details are based on the CVSS v2 scoring system.

Custom

Specifies whether the component is custom (user-created) or non- custom (Code Insight-created).

Important

Specifies whether the component has been marked for importance by Code Insight or is referenced in the system.

Available Platforms

The list of operating systems for which this component is developed (if any).

Categories

The list of tags to classify the component in a catalog-type structure. For example, a user may choose to label a set of components as “Permissive” based on their license type.

CPE Name

The list of CPE names—manually created or pulled from the National Vulnerability Database—that are mapped to the OSS or third-party component. CPE is a structured naming scheme for a component that includes the component’s vendor name and product name and uses the following format:

cpe://<part>:<vendor>:<product>

where <part> is either a (applications), h (hardware platforms), or o (operating systems).

To add a custom CPE name for the component or remove any of the component’s custom or NVD-published CPE names, click Manage CPE Name. When you add a CPE name, Code Insight validates that the name is in the correct format.

Programming Language

The list of programming languages that are used in the codebase for the component.

Last Update Date

The date the codebase was last uploaded to the forge for this component.

Registered Date

The date corresponding to the first code upload to the forge for this component.

Versions

The versions associated with this component.

Licenses

The licenses associated with this component.