About custom components

You may want to use a component in your BOM that is not available from Black Duck KnowledgeBase; for example, your project uses an open source component that is not tracked by the Black Duck KB or there is a commercial component you want to add to your BOM. So that your BOM accurately reflects your project, users with the Component Manager role can create and manage custom components which can then be added to a BOM.

Note: Contact Black Duck Customer Support for missing versions of open source components that are managed by Black Duck KnowledgeBase.

Black Duck provides the information Component Managers need to successfully manage their custom components. They can use the:

Note the following:

  • In the BOM:
    • The match type for a custom component added to a BOM is Manually Added.

    • Custom components display license risk. (Note that the license risk shown is determined by the license selected for this component.) No security risk values are shown as no security vulnerabilities are associated with the custom component. Also, no operational risk is shown.

  • Policy Managers can create policy rules for custom components.

  • You can use the search feature for custom components. A component filter, Component Source, has the value Black Duck Custom Component for custom components.

  • In the components_date_time.csv and bom_component_custom_fields_date_time.csv files in the Project Version report, a new column, labeled Source/Type denotes whether the component is a custom component (value of CUSTOM_COMPONENT) or a component that is managed by Black Duck KnowledgeBase (value of KB_COMPONENT).

  • Custom components do not have origins.