# The Sealed packages tab

Every package that has been replaced with a sealed version in your environment appears here, with a row per Seal Project that has pulled the sealed version at least once. Use this tab to verify that remediation is taking hold and to download the attestations you need for audit.

## Columns

| Column                    | Contents                                                                                                    |
| ------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Package**               | The package name.                                                                                           |
| **Version**               | The sealed version in use (for example, `2.7.4-sp1`).                                                       |
| **Ecosystem**             | The package's ecosystem.                                                                                    |
| **Project**               | The Seal Project this row belongs to.                                                                       |
| **Vulnerabilities**       | The vulnerabilities the sealed version remediates.                                                          |
| **Last scanned / pulled** | The most recent time Seal saw this sealed package being used, whichever discovery mode produced the signal. |

The default sort is by **severity, descending**.

## Filters

The same filters as the [Vulnerable packages tab](/new-documentation/new-docs/protection-page/vulnerable-packages-tab.md#filters), minus the Availability filter (since every row here is in the Sealed state).

## Per-row actions

| Action                                                                      | Roles                       |
| --------------------------------------------------------------------------- | --------------------------- |
| **Hide package** / **Unhide package**                                       | Admin, Sealer, Collaborator |
| **Download attestation** (the human-readable PDF for this row)              | Any authenticated user      |
| **Download VEX attestation** (the machine-readable VEX record for this row) | Any authenticated user      |

## Bulk downloads

Above the table, a download menu offers two bulk actions that operate on the current filtered set:

* **Download all attestations**: a single PDF that combines the attestations for every row in the filtered set.
* **Download all VEX attestations**: a single JSON file that combines every row's VEX record.

A separate **Download report** action exports the filtered set as a Sealed Packages report. See [Reports Manager](https://github.com/seal-community/gitbook/blob/main/new-docs/using-the-platform/reports-manager/README.md).

## Related

* [Attestations](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-and-compliance/attestations/README.md): the canonical home for both attestation formats.
* [Sealed package](/new-documentation/new-docs/seal-approach/sealed-packages.md): the concept behind every row in this tab.


---

# 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/protection-page/sealed-packages-tab.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.