> For the complete documentation index, see [llms.txt](https://docs.metatrust.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metatrust.io/introduction/metascore/score-and-rating.md).

# Score and Rating

## 1. Score

Our proprietary tool is used to scan the projects to be analyzed. In each rating dimension, the project is ranked based on the tool's scan results and a ranking score is calculated, ranging from 0-100. The ranking scores of several dimensions are weighted to give each project a total score, which serves as the project's final security score. The determination of the weight value of each dimension is based on the APH hierarchical method \[1].

The scoring process involves the following important aspects: 

1\). A higher security score for a project indicates that it is more secure and trustworthy. 

2\). When calculating the ranking score based on the engine's scan results, a reverse ranking is used. For example, if a project has more vulnerabilities detected by the vulnerability scanning engine, its ranking score will be relatively lower.

## 2. Rating

Here is the score and rating comparison table in descending order:

| Score Range | Rating |
| ----------- | ------ |
| 95-100      | AAA    |
| 90-95       | AA     |
| 80-90       | A      |
| 75-80       | BBB    |
| 65-75       | BB     |
| 60-65       | B      |
| 50-60       | CCC    |
| 45-50       | CC     |
| 40-45       | C      |
| 30-40       | DDD    |
| 20-30       | DD     |
| <20         | D      |

This table is used to assign the corresponding rating to the project based on its final security score. The rating system ranges from AAA (highest) to DDD (lowest).

\[1] AHP, <https://en.wikipedia.org/wiki/Analytic_hierarchy_process#Hierarchies_in_the_AHP>


---

# 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.metatrust.io/introduction/metascore/score-and-rating.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.