# Audits and Security (/smart-contracts/audits-and-security)



Pear's smart contracts have been reviewed by **Shieldify** in multiple rounds. Audits reduce risk but do not eliminate it. As with any protocol, do your own research.

## Previous public review reports [#previous-public-review-reports]

* [PearLabs V0.9 Security Review](https://github.com/shieldify-security/audits-portfolio/blob/main/reports/PearLabs-V0.9-Security-Review.pdf)
* [PearLabs V1 Security Review](https://github.com/shieldify-security/audits-portfolio/blob/main/reports/PearLabs-V1-Security-Review.pdf)

The Pear Vault contracts on HyperEVM received two further dedicated Shieldify reviews ahead of the Vaults launch (see [Vaults](/vaults)):

* [Pear Protocol Vault Security Review](https://github.com/shieldify-security/audits-portfolio/blob/main/reports/PearProtocol-Vault-Security-Review.pdf)
* [Pear Protocol Vault Extended Security Review](https://github.com/shieldify-security/audits-portfolio/blob/main/reports/PearProtocol-Vault-Extended-Security-Review.pdf)

Beyond contracts, Pear applies security practices across the stack: encrypted exchange credentials at rest, non-custodial execution for direct trading (funds stay on the venue), restricted-territory geo-blocking, and API keys with separate `read-only` and `read+trade` scopes. See [Restricted Territories](/resources/restricted-territories) and the [API integration guide](/api-integration/overview).