> For the complete documentation index, see [llms.txt](https://docs.tosdr.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tosdr.org/phoenix/how-are-classifications-calculated.md).

# How are classifications calculated?

Feel free to check the most up-to-date version of our algorithm [here](https://github.com/tosdr/edit.tosdr.org/blob/master/app/models/service.rb#L88-L109).

Basically, as of Sept 2025, a blocker counts as 3 bad points, and the algorithm looks at the balance:

number of good points − number of bad points − (3 × number of blockers).

* If there are no points at all, the grade is N/A.
* If the balance is −10 or lower, or if the number of blockers is greater than the number of good points, you get an E.
* Otherwise, if you have at least 3 blockers or if you have more bad points than good points, you get a D.
* Otherwise, if the balance is less than 5, you get a C.
* Otherwise, if you still have any bad points, you get a B.
* Only if you have no blockers and no bad points at all, you get an A.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tosdr.org/phoenix/how-are-classifications-calculated.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.