Keyword Search

In the Lookup Component window, select the Keyword option to search components by their name. For the search criterion, enter a single string for the component name. This can be the full component name, such as jquery-jquery-ui, or a string within the name, such jquery. (Multiple strings are not allowed.)

Note:The search is case-insensitive, so it filters to all components whose names contain the string, no matter the case used in the entered string or in the actual component name.

For common name conventions used for components in various forges, see the next section.

Component Name Conventions Used in Various Forges

In general, the name of a component is a unique identifier that can be based on the project, package, or gem name of the component or on another convention such as the component’s author or repository. The following shows the common conventions used for component names in certain forges. You can use this as a reference for helping you enter an appropriate string for the component name.

Apache—<PROJECT_NAME>, for example “apache-batik”
Debian—<PACKAGE_NAME>, for example “0ad”
Github—<AUTHOR>-<REPOSITORY_NAME>, for example “jquery-jquery-ui”
GitLab—<AUTHOR/ORGANIZATION>-<REPOSITORY_NAME>, for example:
“cryptsetup-cryptsetup” (as found in the component URL: https://gitlab.com/cryptsetup/cryptsetup)
“redhat-bison” (as found in the component URL: https://gitlab.com/redhat/centos-stream/rpms/bison)
NuGet Gallery—<PACKAGE_NAME>, for example “newtonsoft.json”
Pypi—<PACKAGE_NAME>, for example “hash_ring”
RubyGems—<GEM_NAME>, for example “x-editable-rails”
Other—<PROJECT_NAME>, for example “openssl”