> For the complete documentation index, see [llms.txt](https://glide.gitbook.io/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glide.gitbook.io/main/glider-api/trust-score.md).

# Trust Score

The Glider Trust Score helps quantify the overall trust level of a smart contract by assigning a score from 0 to 100. The score is based on the number and severity of risks, as well as various contract attributes such as financial value, popularity, and more. The higher the risk level, the greater the negative impact on the score.\
Below is a table of risk levels and their descriptions.

<table><thead><tr><th width="161.2039794921875">Severity Level</th><th>Description</th></tr></thead><tbody><tr><td>🔴 High</td><td>Critical risks that allow full control, destruction, or abuse (e.g. centralized mint, selfdestruct)</td></tr><tr><td>🟠 Medium</td><td>Moderate risks that affect usability or introduce behavioral constraints</td></tr><tr><td>🟢 Low</td><td>Minor issues such as address-based privileges</td></tr><tr><td>🔵 Info</td><td>Design traits or capabilities worth noting, but not inherently risky</td></tr></tbody></table>


---

# 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://glide.gitbook.io/main/glider-api/trust-score.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.