# Audits

Formal Audits

* [x] TechRate (done) See [HERE](https://github.com/TechRate/Smart-Contract-Audits/blob/main/DrFrankenstein%20Standart%20Smart%20Contract%20Security%20Audit.pdf)
* [x] Hashex (done) See [HERE](https://github.com/HashEx/public_audits/blob/master/rugzombie/Zombie%20report.pdf)

  Haechi (in discussion)&#x20;

Community Reviews

*There are various crypto communities out there trying to provide a service for the defi space. Let us know if we get a positive review from a community you are a part of! These are NOT Audits*

* [x] Rug Warnings (See [HERE](https://rugzombie.gitbook.io/docs/security-and-team-information/basic-team-security-information/www.rugwarnings.com))
* [x] Rug Seekers (See [HERE](https://twitter.com/rugseekers/status/1432930057295704067?s=21))
* [x] RugDoc Review\* (See [HERE](https://rugdoc.io/project/rugzombie/))
* [x] Ape O Clock Featured (See [HERE](https://www.apeoclock.com/launch/rugzombie-nft-launch/))

\*RugDoc determined our code was too complex to warrant a full review. We have respectfully asked them post our HASHEX audit report to get that coveted "low risk" button, however this is not in our control.

![](/files/-Mki4L9648_kty2YUsRL)

**Techrate Audit In Depth**

Our Initial Techrate Audit can be see [HERE](https://github.com/TechRate/Smart-Contract-Audits/blob/main/DrFrankenstein%20Standart%20Smart%20Contract%20Security%20Audit.pdf) and is also provided below, however because our master chef contract was named "Dr. Frankenstein", in order to avoid confusion we have asked the techrate team to redraw their audit report with Rug Zombie as the title. You can both attached here below for your review. [Here is an article we wrote](https://rugzombie.medium.com/token-contract-address-has-been-updated-765b96dfc020) explaining the situation as well. This audit was re-sent to the RugZombie team on 6/27/2021. All contract information is the same for these two original audit reports:

**PRELAUNCHED Old Token Address:** ~~0xbefd2cD02021E59116953d42a74DC834dDCf9c9f~~ (this token address was changed before launch, do not use)&#x20;

As this audit was an audit commissioned preliminarily to launch, there are certain smart contracts not included in this audit, our most up to date and recent to date audit was conducted by HASHEX and can be viewed below.&#x20;

{% file src="/files/-MdDx1uw7IE4rrglkeCv" %}
Dr. Frankenstein Audit
{% endfile %}

{% file src="/files/-MdDwbwnJWvOSyVhVt9q" %}
Techrate Audit of Original Contract
{% endfile %}

{% file src="/files/-MkCyjI6Ky3ZtUfJJ7-8" %}
Hashex Audit of Masterchef (Dr.Frankenstein)
{% endfile %}


---

# 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://rugzombie.gitbook.io/docs/security-and-team-information/basic-team-security-information/audits.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.
