Keyword Search
Use the Keyword option to search components by their name in the Code Insight Data Library. For the search criterion, enter one or more character strings found in a component name. Multiple strings must be separated with spaces (not commas) and can be listed in any order, as in the following example:
tomcat apache
The search will filter to only those component names that contain all the strings entered for the Keyword field.
Note:The search is case-insensitive, so it filters to all such components, no matter the upper or lower case used in the strings in the Keyword field or in the actual component name.
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. For your reference, the following shows the common conventions used for component names in the various forges:
|
•
|
Apache— <PROJECT_NAME>, for example “apache-batik” |
|
•
|
Debian—<PACKAGE_NAME>, for example “0ad” |
|
•
|
GitLab—<AUTHOR/ORGANIZATION>-<REPOSITORY_NAME>, for example: |
|
•
|
“cryptsetup-cryptsetup” (as found in component URL: https://gitlab.com/cryptsetup/cryptsetup) |
|
•
|
“redhat-bison” (as found in 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” |
To search for components by a keyword, do the following:
|
1.
|
On the Global Component & License Lookup > Components tab, select the Keyword option. |
|
2.
|
In the Keyword field, enter one or more character strings found in the name of the component(s) for which you are searching. For more information about this value, see the introductory content (just above) in this section. |
Note: If a component that you want to explore is not available with the keyword search, try the URL, forge, or component ID search. If you are still unable to locate the component, the component might not exist in the Code Insight Data Library nor be saved as a custom component.