> For the complete documentation index, see [llms.txt](https://docs.tea.xyz/tea/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tea.xyz/tea/i-want-to.../learn-about-proof-of-contribution/why-was-my-tearank-not-detected.md).

# Why was my teaRank not detected?

Millions of projects from supported package managers are assigned a teaRank score daily based on the ***tea*** protocol’s Proof of Contribution algorithm. If a project does not have a teaRank detected, it could be because:

1. The project is not in a supported package manager. The ***tea*** protocol currently supports projects listed in APT, Crates, Homebrew, npm, pkgx, PyPI and RubyGems, with more to come in the future. 
2. The project does not have any dependents or dependencies.
3. The project was categorized as spam or malicious by the protocol.


---

# 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.tea.xyz/tea/i-want-to.../learn-about-proof-of-contribution/why-was-my-tearank-not-detected.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.