> 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/can-i-review-the-tearank-of-my-favorite-oss-project.md).

# Can I review the teaRank of my favorite OSS Project?

Absolutely! The ***tea*** Protocol provides a comprehensive and transparent system for evaluating the impact and contribution of OSS projects through Proof of Contribution. By reviewing the Proof of Contribution of your favorite OSS project, you can gain valuable insights into its significance and overall impact to the open-source software ecosystem.

To review the teaRank of an OSS project,

1. Select "Check My Project teaRank" on the [***tea*** website](https://tea.xyz/).

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

2. Enter the name of your favorite OSS project in the search box

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

3. Click on your favorite project's name to visualize its' properties
4. Review your favorite project's teaRank, package manager, Git source URL and impact level.
5. Review your favorite's project's dominance in the open-source ecosystem.

teaRank not only enhances the accuracy of evaluating OSS project impact but also facilitates a fair and proportional distribution of rewards to contributors. By accurately assessing the impact of a project and its dependencies, the rewards can be allocated accordingly, allowing contributors to be fairly recognized and incentivized for their contributions.

*(\*) Estimation based on `nodejs`' teaRank, current dependencies, and other projects registered. Projected rewards may vary, might not hold any inherent value, their value can be subject to change due to various factors.*


---

# 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.tea.xyz/tea/i-want-to.../learn-about-proof-of-contribution/can-i-review-the-tearank-of-my-favorite-oss-project.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.