Skip to main content

Choose a report or export

Start with the data you need to share. Reports → Generate prepares files in the background. Issues, Report Views, and several inventory pages also have their own export actions.

Generate a report

Open Reports → Generate, click Generate on the report you want, and choose its scope and format. Download it once it is Ready under Recent or History. Reports pass through Queued and Generating as ZeroPath prepares them. The four organization-wide report rows and the Organization SBOM row display this status in place of the Generate button while a request is active. The Scan report button stays available for another scan. Generate and History require repository view access. The Scan report and Organization SBOM options use that access to limit the repositories you can select or export. Monthly security report, Organization summary, SLA compliance, and SOC 2 also require View Custom Reports. These four reports cover the organization by default. You can narrow them to a set of tags or repositories, and the file describes the selected scope. Report Views and Assets are available by direct link. Views requires View Custom Reports. Assets requires repository view access and shows repository, application, endpoint, and open issue counts with a searchable application table. The Reports sidebar entry opens the first page you can access.

Scan Report

Choose a repository, a completed full or pull request scan, and a format. Completed scans with zero findings are eligible. The report uses the chosen scan and each finding’s current lifecycle status.
  • In Issues, choose Open issues (Needs Review, Reviewing, Patching, and Backlog), Closed issues (Resolved, Accepted Risk, False Positive, and Non-exploitable), Informational issues, or All issues. The default is Open issues.
  • A Threshold of 0 includes unscored findings. A positive threshold includes only findings with a score at or above that value.
  • Both filters apply to DOCX, CSV, and SARIF. The SBOM uses the scan’s linked dependency inventory when available. If the scan has no linked inventory, ZeroPath can build the SBOM from the repository snapshot. If the linked inventory was retired, select a newer scan.

Organization SBOM

Choose CycloneDX 1.6 (JSON) or SPDX 2.3 (JSON) and check the preview. ZeroPath prepares a ZIP with one SBOM per eligible repository you can view, based on the latest qualifying dependency inventory on its default branch. The manifest.json lists included and skipped repositories and explains why each repository was skipped. At least one repository must qualify, and you can have one organization SBOM export in progress. See Organization SBOM export.

Monthly Security Report

Choose the month, year, and severity levels to include. You can give the report a title and limit it to tags or repositories. It generates a DOCX with month-over-month findings, per-repository scan activity, and an executive summary.

Organization Summary

Optionally enter a company name and narrow the scope. The PDF shows findings by severity, repository breakdowns, and trends in remediation and exposure.

SLA Compliance Report

With an enabled SLA policy, select that policy or All SLA Policies and optionally narrow the repository scope. The ZIP contains sla-compliance-report.pdf, findings.csv, and findings.json with the findings counted by the report. When Export report is available in Reporting → SLA → SLO / SLI, it opens Generate with the selected policy prefilled.

SOC 2 Report

Optionally enter a company name and narrow the scope. The PDF summarizes repository coverage, scan activity, and security metrics for your SOC 2 evidence.

Report History

Use Reports → History to search by title or file name and filter by Type, status, or Requested by. The history refreshes during generation and shows status, requester, and file size. Download is available for ready files.
  • Retry starts a new request using the original settings when they are available. It checks current permissions, scope, and eligibility. For an Organization SBOM, a retry uses the originally selected format and the repositories you can view now.
  • Delete removes ready, failed, and stalled reports you can see. Most reports become stalled after 30 minutes. For an Organization SBOM, deletion is also available while queued and cancels the request. A generated per-repository SBOM file expires separately, after 24 hours by default.
  • Older scan reports generated with Exclude False Positives and per-repository SBOM exports must be generated again. Older scan reports generated with All Issues can be retried with the Open, Closed, and Informational groups selected.
Within History, you can see reports you requested, scan and SBOM reports for repositories you can view, and organization-scoped reports if you have View Custom Reports. An Organization SBOM is visible in the dashboard to its requester only. An organization admin’s personal API token can read every generated report in the organization. Other personal tokens follow their owner’s access, and service tokens cannot read generated reports.

Export current findings

Open Issues or a repository’s Issues tab and click Export. Select specific findings or use the current filters, then review the export scope in the dialog. Choose Regular CSV, CASA Relevant CSV, SARIF, or Vulnerability report (.docx). SARIF requires a code location for each exported finding. Use CSV if your set includes findings without one. For container findings or CI/CD security findings, open the Containers or CI/CD category in Issues before exporting. In a Report View, set Type to Container or CI/CD.

Per-issue vulnerability report

  • One issue. Open the issue panel or full page and choose More actions → Export report (.docx).
  • Several issues. In Issues → Export, choose Vulnerability report (.docx).
  • A custom view. In Report Views → Export, choose Vulnerability report (.docx).
The Word document provides the title, status, description, severity, and recorded evidence and fix for each issue you can view. A document holds up to 25 issues. If the set is larger, select fewer issues or narrow the filters. These downloads are available directly from the browser. You can also request the single-issue report as Markdown via the issues.vulnerabilityReport MCP tool. To create tickets directly from findings, use Export to Jira or Export to Linear from the issue or the Issues export dialog. These actions require a connected integration and permission to create tickets for the relevant repositories. See Jira and Linear.

Build a reusable Report View

Open Report Views with the View Custom Reports permission to analyze findings by repository, application, or issue criteria and return to the same filters later.

Interactive Dashboard

The view updates total findings, severity, top vulnerability classes, mean time to remediation, and finding trends as you adjust its filters.

Filter Bar

Select Add filter and choose an issue, repository, or scan field. Common choices include severity, type, status, validation state, reachability, application, repository, tags, scan type, and detection or resolution date. Click a filter chip to edit it and Clear to reset the set.

Preset Reports

Use a preset for dependency vulnerabilities, pull request findings, secrets, high and critical severity, SAST, or new findings from the last 30 days. To keep a variation, adjust its filters and save it as a named view.

Saved Custom Reports

Choose New Custom Report or start from a preset, adjust the filters, and choose Save. Reopen it from Saved Reports. Saving requires Create Custom Reports and deleting requires Delete Custom Reports.

Saved Issue Rules

On the Issues page, save a filter set as a rule to reuse it in Saved rules. The same View Custom Reports, Create Custom Reports, and Delete Custom Reports permissions apply.

Exporting Custom Reports

Click Export in the view and choose a format. The export uses the view’s active filters and downloads from the browser.

Export Formats

Export Completeness

CSV, CASA CSV, and SARIF exports process up to 10,000 matching findings. Narrow the filters to export a larger set in parts. Unscored findings remain eligible. A missing score or confidence is recorded as blank or null, depending on the format. For detected secrets, finding exports mask the credential and withhold model-written descriptions, evidence narratives, and patches that could repeat it. Issue and scan report CSVs include Tickets and Ticket URLs for linked Jira and Linear tickets. Multiple tickets are separated by a semicolon, and the two columns preserve the same order. An unknown URL leaves a blank entry. The tickets array in POST /api/v2/issues/export exposes the same links as JSON. Scan report CSV uses State for the current lifecycle status and Validation for the stored validation verdict. Unscored findings have a blank score and unscored severity.

PDF Export Details

The PDF includes a cover page, charts for the filtered findings, and a table of up to 100 highest-scoring findings. Unscored findings sort below scored findings. The PDF indicates when there are more matching findings than the table includes.

Filter Schema Discovery

Use GET /api/v2/custom-reports/filter-schema to discover available fields and operators. Read about API access for authentication and request options.

SBOM and ML-BOM exports

In Assets → Repositories, select the repository and open Inventory → Dependencies. Choose Export SBOM, select CycloneDX JSON or SPDX JSON, and click Generate SBOM. A retained SCA inventory also supports CycloneDX VEX for vulnerability and reachability data or optional VEX metadata in CycloneDX JSON. Keep the dialog open for the automatic download. The export covers the complete inventory from the displayed scan. See SBOM formats, eligible inventories, and retention.

ML-BOM Export (AI Inventory)

In Assets → Repositories, select the repository and open Inventory → AI components. Choose Export ML-BOM, then Generate SBOM. The CycloneDX 1.6 JSON file captures all AI components detected in the displayed scan, including models, datasets, SDKs, and agent tools and configurations. Keep the dialog open for the automatic download. See AI Inventory.

Exports from other pages

Generated report reference

Report Types

The Generate tab groups reports For leadership, For auditors, and For engineering teams. See the report and export chooser for their scope and files.

Export Formats

Scan Report (DOCX)

The document includes severity totals, repository and scan metadata, affected files, CWE classifications, and remediation guidance. Findings without a numeric score are labeled Unscored.

Monthly Security Report (DOCX)

The report includes findings by severity, top vulnerability families, scan activity, and a summary. Mean time to remediate, when available, includes the number of resolutions and the month it covers.

Organization Summary (PDF)

The summary includes organization trends and per-repository detail for the selected scope. Remediation time includes its date window and sample size when available.

SLA Compliance Report (ZIP)

The PDF summarizes findings within or past configured remediation windows. The CSV and JSON contain the underlying findings.

SOC 2 Report (PDF)

The report includes security metrics, repository coverage, and scan activity for the selected scope.

Dashboard metrics

On the Dashboard, use the charts to review posture and open matching issues. Use Reports → Generate or Report Views when you need a file.

Dashboard Filters

Scope the dashboard by date, severity, vulnerability class, and application. The scope strip lists active filters. Linked metric cards carry their filters into Issues.

Open Issues By Vulnerability Type

Review open finding counts by vulnerability class. Hover to read the full class name and count.

Issues By Application

Compare open and resolved issues by application, including separate applications in a monorepo.

Open Issues By PR Author

Review open findings by author from each repository’s latest merged pull request scan. The chart excludes findings seen only in full scans or unmerged pull requests.

Mean Time To Resolve Chart

The trend shows average time from detection to resolution for findings resolved in each period. The summary card shows the average for the selected range and flags samples below ten. Periods with no resolutions have no value.

Estimated Exposure Window

Review the estimated average time open findings had been exposed, in days, by severity and period.

Dashboard Profiles

Use the profile switcher to restore a saved widget layout and filters. Edit Layout lets you change the widgets. Manage profiles lets you open, duplicate, delete, or set a default profile. Creating, editing, or deleting a shared organization template requires Manage Dashboard Templates.