# Audits {% hint style="success" %} Lowers smart contract risks {% endhint %} In web3, audits are extensive analyses of code by usually -and preferably- external parties. These parties go through the submitted code thoroughly to find any potential risk that could lead to the protocol being exploited. Anything that they find, however small, is included in an audit report and given back to the team. The team then decides what to do with these findings; solve it, mitigate, or just acknowledge the risk. Sometimes, the latter is unavoidable, but either way the team goes, the audit report will include any findings. Have to wonder though: "Why would a team pay tens of thousands of dollars just to ignore the findings?" Same here. That is why we fix anything the auditor may find before making the audit public. If you are interested, these audits are designed to be human-readable, unlike other aspects in web3, with every report starting with an overview and summary of findings, including their vulnerability level (low / medium / high) and the team's response. If you need any help on reading our audit reports, do reach out in our Telegram. We are happy to help such a thorough user. As we mentioned, most audits (the good ones) are in the tens of thousands, with some north of a $100k. As a result, some protocols find it to decide whether or not to go for an audit. At DegenPrime, we believe that proper security is of the highest priority, and that makes the decision easy. As such, the code of DegenPrime has been audited as much as 10 already. Four have been performed by PeckShield, one by an independent auditor Piotr Szlachcia, two by AstraSec, and one by each of Chainsulting, ABKD, and BlockSec. As DegenPrime continues to be developed on, this list will keep expanding to ensure maximum security. You can find all the audits on our GitHub. {% embed url="" %} --- # 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://degenprime.gitbook.io/degenprime/security/audits.md?ask= ``` 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.