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

# Audits

This page tracks Basket audit status and scope.

### Current status

Audit status is pending.

### What will belong here

When audits are complete, this page should list:

* The audit firm
* The audited contracts and components
* The report date
* The public report link
* Any unresolved findings

### What not to assume

Do not infer audit status from roadmap statements, previews, or partial reviews.

Only a published report counts.

{% hint style="warning" %}
Until a report is published, treat Basket and its integrations as unaudited.
{% endhint %}

***

### What this page should eventually contain

| Item               | Status today |
| ------------------ | ------------ |
| Audit firm         | `TBD`        |
| Audit scope        | `TBD`        |
| Public report link | `TBD`        |
| Findings summary   | `TBD`        |
| Remediation status | `TBD`        |

### What a useful audit section looks like

A useful audit page does not just list a logo.

It states what was reviewed, when, and what remains unresolved.


---

# 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.trybasket.live/built-on-b20/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.