# Search for a Finding

Solodit is designed to aggregate and simplify the search for web3 security audit findings from diverse sources. Through a range of filters, users can streamline their search and get insights tailored to their specific interests.

<figure><img src="/files/5Fb3c7fcKCVTdIa9nUHc" alt=""><figcaption><p>Solodit findings filters</p></figcaption></figure>

### Fields

* **Keywords:** Enter specific terms or phrases to narrow down findings.
* **Source:** Filter by the origin or platform of the audit.
* **Impact:** Categorize findings based on their potential severity. Options include High, Medium, Low, and Gas.
* **Author (previously "User"):** Find findings based on the individual or entity that authored the report.
* **Protocol Name:** Target findings that are specific to a named protocol.
* **Protocol Category:** Classify findings by protocol type. Options encompass Lending, NFT Marketplace, Oracles, Liquid Staking, Gaming, and more.
* **Forked From:** Focus on findings in protocols derived from existing ones.
* **Report Tag:** Use tags or labels for more specific categorization or topic identification. For more information on Report Tags see [Tag a Finding](/findings-explorer/rating-a-finding.md).

The 'View More' Dropdown will reveal additional ways to filter and customize your search.

* **Number of Finders:** Filter based on how many individuals identified a particular issue.
* **Reported After:** Highlight findings based on their report date.
* **Rarity Score:** A community-voted score denoting the uniqueness of a bug. A higher score indicates greater rarity. For more information on Ratings see [Rate a Finding](/findings-explorer/rating-a-finding.md).
* **Quality Score:** Represents the community's assessment of the report's overall quality.

### **Findings Viewer**

Your filtered results will be displayed to the right in the Findings Viewer:

<figure><img src="/files/sg3oemIPADmB0rrBbO8X" alt=""><figcaption><p>Findings Viewer</p></figcaption></figure>

1. This area represents an itemized list of findings which match your applied filters. The list can further be filtered by Bookmarked, Read and Unread results.
2.

```
<figure><img src="/files/zub5P9AcQe8XHUMHSar9" alt=""><figcaption><p>A Result Displayed in the Findings Viewer</p></figcaption></figure>
```

In the above, we can clearly see the:

* **Title of the finding**
* **Date found**
* **Protocol impacted**
* **Finding authors** &#x20;

To the right there are options to copy a link to the finding and to bookmark it.

2. The heading section further details the finding selected in the filtered list. In this view we can see the previous summarization as well as [community submitted Rarities, Categories and Tags](/findings-explorer/rating-a-finding.md). To the right you'll be able to (from top to bottom):
   1. Go to the report
   2. Copy a link to the report
   3. Bookmark
   4. Mark the report as Read

<figure><img src="/files/zYRnJgDZMD7UaMy54zjs" alt=""><figcaption><p>Solodit Finding Header</p></figcaption></figure>

3. The details section of the Findings Viewer displays an explicit breakdown of the reported finding including:&#x20;
   1. **Description**
   2. **Severity**&#x20;
   3. **Impact**
   4. **PoCs - Proof of Concepts (when applicable)**
   5. **Recommended mitigations.**&#x20;

Links directly to GitHub discussions of the findings are available, allowing users to actively contribute.

<figure><img src="/files/kz9C0yhozdS2w0Xwb051" alt=""><figcaption><p>Solodit findings details</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.solodit.cyfrin.io/findings-explorer/search-for-a-finding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.