> For the complete documentation index, see [llms.txt](https://docs.ts.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ts.finance/security-and-risks/defisafety-pqr-score-93.md).

# DeFiSafety PQR Score: 93%

### DeFiSafety PQR Score

TermMax has achieved a **93% Process Quality Review (PQR) score** from [DeFiSafety](https://defisafety.com/app/pqrs/613), earning a PASS rating that significantly exceeds the passing standard of 70%.

<figure><img src="https://3496430163-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbey3QqLkQrkCxlgDKPaz%2Fuploads%2FBOOXUiGtboKS3oDsk9Z2%2Fdefisafety-gold-banner.png?alt=media&amp;token=5d443f00-e52e-406f-b36d-41401106f541" alt=""><figcaption></figcaption></figure>

### About DeFiSafety PQR

DeFiSafety is an independent quality and ratings organization that evaluates DeFi products to attribute security scores based on a transparent quality standard. PQRs are computed from the weighted average of a protocol's score across 6 categories: Code & Team, Code Documentation, Testing, Security, Admin controls, and Oracles.

High scores indicate that a protocol follows best practice in terms of development, documentation, testing, security and transparency, and can be considered trustworthy and safe because the potential risk vectors are being accounted for and guarded against.

### TermMax PQR Performance

**Overall Score: 93% PASS**

Our comprehensive evaluation demonstrates TermMax's commitment to security excellence across all critical areas:

1. Code & Team: 100%
2. Code Documentation: 70%
3. Testing: 89%
4. Security: 94%
5. Admin Controls: 97%
6. Oracles: 100%

View Full Report: [DeFiSafety TermMax Review](https://defisafety.com/app/pqrs/613)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ts.finance/security-and-risks/defisafety-pqr-score-93.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
