# Trust by default

Every artifact Seal ships is accompanied by mechanisms that let you, your auditors, and your customers verify what was changed, who built it, and whether it has been tampered with. The full surface lives in [Trust, transparency & compliance](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-compliance/README.md). A short overview here.

## Code diff

For every sealed version, Seal publishes the diff against the origin version. The change is a targeted patch that fixes the vulnerability. You can read the change, in source, before you accept the sealed package. See the [code diff](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-compliance/code-diff/README.md) page.

## Attestations

Each sealed artifact ships with an attestation listing exactly which vulnerabilities have been remediated. Two formats are produced for every artifact: a **PDF attestation** for human review, and a **VEX record** for machine consumption (Trivy, Wiz, and other scanners). Per-package and bulk download are both supported. See [Attestations](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-compliance/attestations/README.md).

## Cryptographic signing

Every sealed artifact is cryptographically signed before publication. The Seal CLI validates signatures automatically before installing a sealed package. Hashes are published for independent verification. See [Cryptographic signing and hash verification](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-compliance/signing-and-hashes/README.md).


---

# 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://docs.sealsecurity.io/new-documentation/new-docs/seal-approach/trust-by-default.md?ask=<question>
```

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.