> For the complete documentation index, see [llms.txt](https://docs.nep.finance/neptune-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nep.finance/neptune-docs/security/audits.md).

# Audits

**PeckShield Audit Report Summary**

* Project: Neptune Finance
* Auditor: PeckShield
* Date of Audit: December 16, 2024
* Type: Smart Contract

The audit performed by PeckShield evaluated the smart contracts underpinning Neptune Finance. The assessment found no high or critical issues, with the following results:

* 2 Medium severity vulnerabilities
* 1 Low severity vulnerabilities
* 1 Informational Issue

The codebase was noted to be well-structured and organized. All identified issues were promptly reviewed, confirmed, and resolved by the Neptune Finance team. PeckShield has verified that the contracts are secure and ready for mainnet deployment.

Neptune Finance remains committed to ongoing security through periodic audits and proactive updates.

**Link to Full Audit Report**

For more details, view the complete [PeckShield Audit Report](https://docsend.com/view/yzj82bypdebi9ga8)

<br>


---

# 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.nep.finance/neptune-docs/security/audits.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.