> For the complete documentation index, see [llms.txt](https://docs.solodit.cyfrin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solodit.cyfrin.io/findings-explorer/add-new-findings.md).

# Add New Findings

Solodit aggregates findings from a variety of sources, as well as individual auditors and auditing companies contributing with new firms and findings is always an available option. 

Currently this is done directly through the [Solodit Content GitHub Repo](https://github.com/solodit/solodit_content/tree/main).

### 1. Fork the Solodit Content GitHub repository

To add new findings on Solodit, navigate to the [Solodit Content GitHub repository](https://github.com/solodit/solodit_content/tree/main) and fork it by clicking on the fork button on the top right corner:

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

&#x20;Give your fork a name and clone it:

```
git clone https://github.com/your-user-name/solodit_content.git
```

\
Inside the cloned repository>reports folder, if not already present, create a new subfolder, and name it after the audit firm or solo auditor you're adding the findings for.

### 2. Prepare your assets

Include two logo images you'll want the findings to be associated with:

* logo\_256\_256.png This logo will be used in the search list and the finding detail page.
  * type: png
  * size: 256px \* 256px
  * background: transparent

Example: [Cyfrin Square Logo](https://github.com/solodit/solodit_content/blob/main/reports/Cyfrin/logo_256_256.png)

<figure><img src="/files/M9DCGVPnWMCr7aAwCqw5" alt=""><figcaption><p>Cyfrin Square Logo</p></figcaption></figure>

* logo\_450\_225.png This logo will be displayed on the Solodit landing page.

  * type: png
  * size: 450px \* 225px
  * Put the brand name at the right side of the logo.
  * background color: #292634
  * logo color: #BBBABD
  * name text color: #BBBABD

  Example: [Cyfrin Horizontal Logo](https://github.com/solodit/solodit_content/blob/main/reports/Cyfrin/logo_450_225.png)

Last step, is adding the reports.

### 3. Formatting the reports

1. Properly name the report file (`{Date}-{Protocol}.md`).
2. Prepend the report with Auditor details
3. Use #Findings to denote the start of findings content
4. Indicate:
   1. &#x20;the severity - Findings may be classified into 5 categories:
      * **High Risk**
      * **Medium Risk**
      * **Low Risk**
      * **Gas Optimizations**
      * **Informational**
   2. **The title of the finding(s)**
   3. **Their content**

Ensure that the report is formatted correctly. Here's a template you can use, or get inspiration from the  [Cyfrin Reports](https://github.com/solodit/solodit_content/tree/main/reports/Cyfrin) &#x20;

```
**Auditors**

[Giovanni Di Siena](https://twitter.com/giovannidisiena)

[Hans](https://twitter.com/hansfriese)

# Findings

## High Risk
### [Title of Finding-1]
[Content of Finding-1]

### [Title of Finding-2]
[Content of Finding-2]

........

## Medium Risk

........

## Low Risk

........

## Gas Optimizations

........

## Informational

........
```

**Once finished, your folder should look like this:**

```
├── ...
├── reports                                # Reports folder
│   ├── Audit firm name                    # Root folder of your reports.
│        ├── logo_256_256.png              # Square logo image
│        ├── logo_450_225.png              # Horizontal logo image
│        ├── {Date}-{Protocol}.md          # Report file.(e.g. `2023-06-01-sudoswap.md`)
│        └── ...
│   └── ...
└── ...
```

### 4. Send a PR with the new findings

Once your folder is ready, push it to your fork and [create a new pull request.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)&#x20;

A Solodit team member will review the pull request, and, if there's any problem, guide you through the correct process to add your findings on the platform.


---

# 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.solodit.cyfrin.io/findings-explorer/add-new-findings.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.