> For the complete documentation index, see [llms.txt](https://docs.threatrix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatrix.io/codecertify/components-tab/custom-components.md). # Custom Components ## What are Custom Components Custom components allow organizations to create and maintain a private knowledge base of component artifacts with their associated meta data such as versions, licenses and copyrights. ## How are Custom Components Used Custom Components can be used to automatically associate Custom Component data with components that were unmatched during a scan. Unmatched components happen for a variety of reasons, but your team may still need to account for an artifact that was unmatched by Threatrix. This is where Custom Components comes in handy. Custom Components are first class components that contain all of the necessary data that your team will need to account for any risk associated with the unmatched artifact, including licenses, copyrights and vulnerabilities. All of this data will be present on reports and risk management tools such SecureCore and Artifact Risk Graph(ARG). ## Important Notes Please read and understand some[ Important Notes](/codecertify/components-tab/custom-components/important-notes.md) regarding the creation, administration and application of Custom Components. --- # 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://docs.threatrix.io/codecertify/components-tab/custom-components.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.