> 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-your-sbom/how-do-i-know-when-software-has-been-successfully-matched.md). # How do I know when software has been successfully matched? ## Match statuses ### **Matched** This status indicates that the component has an exact match with software listed in the National Vulnerability Database (NVD). This status confirms that the software has reported vulnerabilities, which are visible on the [Vulnerabilities](/~/changes/KjixZskptrAaNWiTYnvj/prioritize-vulnerabilities/manage-vulnerabilities.md) page for the respective product version. Components with a correct CPE or PURL identifier but incorrect supplier information are automatically corrected and matched by our system. ### **Select match** This status indicates that Helm found multiple potential matches using one or more [match sources](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/match-sources.md). Refer to [Resolve match statuses](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md) to try to uniquely identify this component. ### **Matched to package manager** This status indicates that a dependency component is matched to a package manager but is not found in the NVD. Refer to [Matched statuses](#match-statuses) and [Resolve match statuses](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md) for more information. ### **Not found** For components that do not match any known software in the NVD or supported package managers, refer to [Resolve match statuses](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md) to try to identify this component. ### **Create an alias to link to known software** You can use [aliases](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/create-an-alias-to-link-unmatched-software-to-known-software.md) to match any components in your SBOM that have multiple matches or are unmatched to known software components in the NVD. Administrators can create new aliases. ### **Other statuses** * **Scanning:** This is an interim status that indicates that Helm is processing this match. If you have been waiting and haven't seen this update, try refreshing the page. * **Fix version:** The software version provided for this dependency component does not align with the expected version. If you see this, you will also see a warning icon next to the version. Refer to [Resolve match statuses](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md#resolve-fix-version-status) for more information on resolving this issue. * **Contact us:** Helm was unable to process this version. We have logged this issue and will try to rectify it quickly. Refer to [Resolve match statuses](/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/resolve-match-statuses.md#resolve-contact-us-status) for more information on resolving this issue. * **Error:** Some other error occurred while trying to process this component. This should be extremely rare. [Contact us](mailto:helm.support@medcrypt.co) for help in resolving this issue. ### **Removing duplicates** Helm checks CPE and PURL IDs to determine if a dependency component is unique. If a duplicate is detected, it will automatically be removed, streamlining your SBOM management. --- # 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-your-sbom/how-do-i-know-when-software-has-been-successfully-matched.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.