# Browsing sealed packages The public catalog at [`https://app.sealsecurity.io/repository/packages`](https://app.sealsecurity.io/repository/packages) lists every sealed package Seal has built. Browsing requires no account. ## The grid Each sealed package is a card in an infinite-scroll grid. Each card shows the package name with the ecosystem icon, the package version, and vulnerability chips color-coded by severity that summarize the vulnerabilities the sealed version remediates relative to its origin version. A search-and-filter sidebar narrows the grid by package name or CVE, by version (prefix match), and by ecosystem. ## Per-package detail Clicking a card opens a detail page for that exact `package@version` combination. The detail page has two tabs: * **Vulnerabilities**: the table of vulnerabilities affecting the origin version, with severity, status (sealed by Seal or open), and links to the upstream advisory. The same model as the [Vulnerability detail](/new-documentation/new-docs/vulnerability-detail.md) drawer in your tenant, just for the public catalog. * **Hashes**: the cryptographic hashes of the sealed artifacts (the JAR, wheel, tarball, etc.) for verification. A side drawer on the same page shows the per-vulnerability [code diff](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-and-compliance/code-diff/README.md) between the sealed version and its origin version. The diff covers every change Seal made to remediate the vulnerability: the patch itself, plus the dedicated tests Seal added to confirm the patch is effective. The tests are backported alongside the patch so the proof of remediation lives in the same artifact. ## Sharing a code diff The code-diff drawer has a **Share** button that copies a public link to the same diff. The link works without authentication; you can paste it into an email, a ticket, or a chat without granting access to anything else in your tenant. The two common reasons to share a diff: * An auditor wants to verify that a specific vulnerability was actually addressed in code, not just label-changed. * A downstream customer wants to verify that the package shipped in your product no longer carries the vulnerability they flagged. The shared link points at a real, public, verifiable artifact: the patch and its tests. There is no need to share screenshots, internal tooling outputs, or paraphrased descriptions. ## Related * [Vulnerability detail](/new-documentation/new-docs/vulnerability-detail.md): the per-vulnerability content equivalent inside an authenticated tenant. * [Code diff](https://github.com/seal-community/gitbook/blob/main/new-docs/trust-and-compliance/code-diff/README.md): the canonical home for what the side drawer shows. * [Free assessment](/new-documentation/new-docs/repository-page/free-assessment.md): upload your manifest and get back the sealed-coverage answer for every package in it. --- # 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/repository-page/sealed-packages.md?ask= ``` 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.