> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/using-platform/reports-manager.md). # The Reports Manager The Reports Manager builds downloadable reports from the data Seal has about your tenant. It is the export channel for security leaders preparing periodic posture reviews, for auditors who need a snapshot of remediation activity, and for anyone who wants the Protection page's data in a file they can attach to a ticket or hand to a downstream consumer. The Reports Manager lives at the **Reports** entry in the left navigation of the Seal UI. ## The three report types Three reports are available today: * **Vulnerable packages.** The current set of vulnerable packages across your tenant. Columns and filters mirror the Vulnerable packages tab; you pick the slice you want, generate, and download. * **Sealed packages.** The current set of sealed packages, meaning what is currently being sealed in your builds. Useful as an inventory of remediation coverage, and as the closest thing the Reports Manager offers to a "what did Seal fix" snapshot. * **ROI.** A different shape from the other two: instead of one row per package, the ROI report is a set of aggregate metrics covering, for example, counts of vulnerable packages and vulnerabilities by severity, counts of sealed packages pulled, and time-saved estimates. It is the same data the Dashboard shows in tiles, packaged for inclusion in an executive report. ## Configuring and running a report The Vulnerable packages and Sealed packages reports both open into a **table editor**: columns, filters, and an output-format choice in the page body, with a **Generate report** footer and a **Download** button.
The Reports Manager table editor for the Vulnerable packages report, showing columns, filters, format selector, and Generate report button.

The Vulnerable packages report in the table editor.

The configuration choices: * **Columns.** Which columns to include. The default set covers package name, version, ecosystem, vulnerabilities, project, severity, package state, and a few others; column toggles let you add or remove the rest. The order you set is the order in the output. * **Filters.** The same filter set the Vulnerable packages tab uses: project, ecosystem, minimum severity, package state (availability), token, dependency type (dev or runtime), and visibility. The defaults match the platform-wide defaults; adjust to scope the report. * **Sort order.** A sort column and direction for the rows. * **File format.** PDF or CSV. PDF for human-readable handoff; CSV for downstream tooling. Click **Download** to generate. The report runs server-side; when it completes, the file downloads automatically. Larger tenants may see a brief wait. If you reopen the page mid-generation, the same loading indicator appears and the page picks up where it left off. ## Including hidden rows Rows hidden from the Vulnerable packages tab (through the per-row Hide action) are excluded by default from the Vulnerable packages report. The Visibility filter on the report builder controls this: pick the visibility states you want included, including hidden if you do. The default tracks the platform default: hidden rows are out unless you ask for them. ## The ROI report The ROI report covers tenant-wide aggregate metrics, not per-package rows. The items you can include: * Counts of vulnerable packages, broken down by severity tiers. * Counts of total vulnerabilities, broken down by severity tiers. * Counts of sealed packages currently pulled in your builds. * Counts of available sealed packages Seal could pull but is not pulling yet (the addressable upside). * Estimates of engineering time saved by sealed-package adoption, and the potential time savings still on the table. Each metric is a checkbox in the report builder; the output includes whichever you enable. The metrics are the same ones the [Dashboard](/discovering/dashboard.md) shows in its tiles, presented in a format you can attach to a status review or a board update. ## Reports history The **Reports history** entry in the Reports sidebar lists every report you have generated previously. Each row records the report type, the configuration, when it was created, and a download link for the original file. Use it to grab a copy of a report you sent last quarter without rebuilding it from scratch, or to confirm the configuration that produced a specific report. ## When to use Reports vs the Dashboard * **Use the Dashboard** for a live look at your tenant's posture. The tiles refresh once a day; the page is always current. * **Use the Reports Manager** when you need a file: an attachment to share, a CSV for a downstream pipeline, a snapshot for an audit trail. The two address the same underlying data; one keeps it inside the platform, the other lets you take it elsewhere. ## Related * [The Dashboard](/discovering/dashboard.md): the live aggregate view the ROI report mirrors in file form. * [The Vulnerable packages tab](/discovering/protection-page/vulnerable-packages-tab.md): the live source of the Vulnerable packages report. * [The Sealed packages tab](/discovering/protection-page/sealed-packages-tab.md): the live source of the Sealed packages report.