Guidelines for Component Lookup
When possible, use the Forge or URL search for the most targeted search results, and use the Keyword search in other cases.
|
•
|
Use the Forge option if you know the names of the component’s forge and third-party project/repository. |
|
•
|
Use the Keyword option to search all component names in the Code Insight data library. 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 the search criterion, you can enter any character string found within a name.: |
|
•
|
Github— <AUTHOR>-<REPOSITORY_NAME>, for example “jquery-jquery-ui” |
|
•
|
NuGet Gallery— <PACKAGE_NAME>, for example “newtonsoft.json” |
|
•
|
Apache— <PROJECT_NAME>, for example “apache-batik” |
|
•
|
Pypi—<PACKAGE_NAME>, for example “hash_ring” |
|
•
|
RubyGems— <GEM_NAME>, for example “x-editable-rails” |
|
•
|
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) |
|
•
|
Other— <PROJECT_NAME>, for example “openssl” |
|
•
|
If you a component you want to explore is not available by a keyword search, select a Forge or URL search. If you are still unable to locate the component, the component might not exist in the Code Insight data library. |
|
•
|
Create your inventory item as Work in Progress and name it using the convention <COMPONENT> <VERSION> (<LICENSE>). For example, myComponent 1.2 (MIT). (You can later edit this inventory item to convert it to one of the other inventory types—Component or License.) |