> For the complete documentation index, see [llms.txt](https://helm.docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/manage-sboms/manage-component.md). # Manage component You can view details about a dependency components, including its licenses, how it was matched, and any review information. In the Software Bill of Materials (Products) page, select **Actions ... > Manage component** to modify dependency component details. ### **Product details** * **Product name:** This is your product name. * **Product version:** This is your product version. ### **Component details** * **Name:** This is the firmware, software, framework, library, file, or operating system that is installed on the physical representations of your device (e.g., Windows, OpenSSL). * **Version:** This is the version for this dependency component name (e.g., 10.1 for Windows). * **Supplier:** This is the organization that supplied the dependency component. The supplier may often be the manufacturer, but may also be a distributor or repackager (e.g., Microsoft for Windows). * **Original CPE:** This is the original PURL assigned to this component in your SBOM file. Example format: (e.g., cpe:2.3:part:vendor:product:version:update:edition:language:sw\_edition:target\_sw:target\_hw:other) * **Enriched CPE:** This is the PURL that was added or enriched from the respective package manager during the component matching process. This will only display if populated. You cannot edit this. * **Original PURL:** This is the original CPE assigned to this component in your SBOM file. Example format: (e.g., scheme:type/namespace/name\@version?qualifiers#subpath) * **Enriched PURL:** This is the CPE that was added or enriched by our AI copilot during the component matching process. This will only display if populated. You cannot edit this. ### **Match details** This is how Helm matched or attempted to match your dependency component. * **Match status:** This shows the current [match status](https://app.gitbook.com/o/-LZpcTdUtrdTvi6zSb_Z/s/vNSbMpAkAfWOaOQ7r1kN/~/changes/261/~/revisions/GMqPnFWcKBgkm54MnJFN/find-known-vulnerabilities/match-statuses), as well as what [sources](https://app.gitbook.com/o/-LZpcTdUtrdTvi6zSb_Z/s/vNSbMpAkAfWOaOQ7r1kN/~/changes/261/~/revisions/GMqPnFWcKBgkm54MnJFN/find-known-vulnerabilities/match-statuses/match-sources) were matched on. * **Vuln source:** This is the source where we located this dependency component. This is currently always NVD. If it was not in the NVD, it will show a [Not found](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses.md#not-found) badge. * **Matched by:** * **System:** Helm automatically matched this dependency component based on an exact match in the NVD, which could be from a CPE, PURL package manager, name/version/supplier, or alias. * **User name:** This user manually matched this dependency component to a suggested match or created a new alias to link it to known software. ### Review details This shows the last review added for this dependency component. You can also add your own review or view all review information. * **Review status:** Shows whether the dependency component has been reviewed or needs to be reviewed. You can click this badge to set a new status. * **Last reviewed:** Shows who last reviewed this dependency component and when. * **Last review:** This is the last review note made on this dependency component to inform the team or progress, final status, or critical risk. ### Edit component 1. On the component you want to edit, click **Actions ... > Manage component.** 2. Click **Edit** on the section you would like to edit. Note that you cannot edit the **Match details** section. 3. If you edit fields in the **Component details** section, then save your changes, you will be prompted to reload this component. Note that this will assess the component anew, which will lose any previous metadata, including matching, EOS/EOL, licensing, or review information that you have manually added. 4. f you don't see your updated dependency component display, make sure **Auto-refresh** is on or click **Refresh** to manually update the page.​​ ### Delete component Click **Actions > Remove (Delete)** **component**. You will be prompted to confirm, as you cannot recover deleted components. This will only delete this component from this product version. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/manage-sboms/manage-component.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.