> For the complete documentation index, see [llms.txt](https://codethreat-sast.gitbook.io/codethreat-knowledge-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codethreat-sast.gitbook.io/codethreat-knowledge-center/usage-guide/projects/licences.md).

# Licences

<figure><img src="/files/gQH8YD1Qhd3S1ZnebyS7" alt=""><figcaption></figcaption></figure>

* Each license entry will typically include the license name and may have a link or arrow to expand for more details.
* Review the licenses to ensure compliance with legal requirements and project standards.

1. **Identify Licenses**: Each license listed represents the legal terms under which a component or library is used. Ensure that you recognize each license type present in your project.
2. **Expand License Information**: If more information is available for a license, click the arrow or link associated with the license to view details such as the full license text, obligations, and compatibility with other licenses.
3. **Check Compliance**: Verify that the use of each component or library is in compliance with its license terms. Pay attention to restrictions or obligations like attribution, redistribution, or modification.
4. **Resolve License Issues**: If potential license issues are identified, such as incompatible licenses or use that is not in accordance with the license terms, take the necessary steps to resolve these issues. This may involve replacing a component, modifying the usage terms, or obtaining additional permissions.
5. **Document License Compliance**: Keep records of license compliance checks and resolutions to ensure that the project documentation is up


---

# 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://codethreat-sast.gitbook.io/codethreat-knowledge-center/usage-guide/projects/licences.md?ask=<question>&goal=<endgoal>
```

`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.