> ## Documentation Index > Fetch the complete documentation index at: https://zeropath.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Repositories > See every repository you can view, ranked by risk, with its open findings, exploit evidence and protection settings ## Overview **Repositories**, under Assets in the sidebar, lists the repositories you can view as a risk table with the columns **Repository**, **Open findings**, **Fix now**, **Exploit evidence** and **Protection**. You can search with **Search repositories...** and narrow the list by **Severity** and **Provider**. **Sort** orders it by **Risk**, **Open findings**, **Name** or **Last scan**. To add repositories, click **Add repository** at the top of the page, or choose **Add repository** from the **+** Create menu in the sidebar. Both need the **Create Repositories** permission. The page is shown to members with the **View Repository** permission. See [Navigating ZeroPath](/docs/platform/navigation) for the sidebar. The list follows the repository filter in the top bar. It opens with the riskiest repositories first. ## The risk table Each row is one repository. Click a row, or the repository name, to open the [repository page](#repository-page). | Column | What it shows | | - | - | | **Repository** | The provider icon and the repository name. The line under the name shows up to two [tags](/docs/platform/repository-tags), then **+N** for any more, and the default branch. A badge reads **Unlinked** when a GitHub installation was removed or its token is invalid, and **GitLab Unlinked** for a GitLab connection problem. The Security Compass icon marks a repository [linked to Security Compass](/docs/integrations/security-compass). | | **Open findings** | The number of open findings, with Critical, High, Medium and Low counts under it, by CVSS severity. Hover a count to see its severity name. | | **Fix now** | The number of open findings in the [Fix now](/docs/platform/issues#fix-now) lane of the Issues page. | | **Exploit evidence** | Up to two lines of evidence counts, in this order: **known exploited**, **secrets verified live**, **runtime confirmed**, **internet exposed**, **reachable**. Known exploited and verified live secrets show in red. | | **Protection** | The repository's [protection status](#protection). Click it to see its settings and turn on missing ones. | A dash in **Open findings**, **Fix now** or **Exploit evidence** means the repository has none. ### What Open findings counts **Open findings** counts the same findings as the **Open** group of the [Issues page](/docs/platform/issues#status-groups) for that repository: findings in **Needs review** or **Backlog**, from full scans, in every category except Containers. The count comes from the repository's most recent full scan and dependency scan. Findings in **Reviewing** or **Patching** are in the **In progress** group, so they are not counted here. The **Fix now** and **Exploit evidence** columns count findings from the same open set. ### Row action The last column has one action, picked from the repository's state: | Action | When it shows | What it does | | - | - | - | | **Fix scan** | The last full scan failed | Opens the repository's **Settings** tab | | **Start first scan** | The repository has never been scanned | Starts a full scan. It needs the **Start Scans** permission on the repository. | | **Review fix now** | The repository has findings in the Fix now lane | Opens the Issues page on the **Fix now** lane, filtered to the repository | | **Open** | Any other state, including an empty repository | Opens the repository page | ## Search, filters and sort * **Search repositories...** matches repository names. * **Severity** shows only repositories with at least one open finding of the chosen severity: **Critical**, **High**, **Medium** or **Low**. **Any severity** clears it. * **Provider** shows only repositories from one provider, such as GitHub or GitLab. Each option shows how many repositories match the search and severity filter. **Any provider** clears it. * **Sort** sets the order: | Sort | Order | | - | - | | **Risk** (default) | Most Fix now findings first, then most critical, then most high, then most open findings | | **Open findings** | Most open findings first | | **Name** | Alphabetical | | **Last scan** | Most recent successful full scan first. Repositories never scanned successfully come last. | The pager under the table shows 25 repositories per page and states the order, for example "1–25 of 77 repositories, riskiest first". The search, filters, sort and page are kept in the page URL, so you can bookmark or share a view. ## Bulk actions Select repositories with the checkbox on each row, or with the checkbox in the header for the whole page. Shift-click selects a range. **Select all** selects every repository that matches the current search and filters, across all pages. **Deselect all** clears the selection. With repositories selected, the **Action** menu offers: | Action | What it does | Permission needed on every selected repository | | - | - | - | | **Scan** | Starts a full scan of each repository and opens the [Scans](/docs/platform/scans) page. Empty repositories and repositories without a scan branch are skipped. | **Start Scans** | | **Schedule Scan** | Sets one recurring scan schedule for all of them. See [Bulk Scheduling](/docs/platform/scanner-settings#bulk-scheduling). | **Create/Edit Scan Schedule** | | **Scan PRs** | **Scan PRs On** or **Scan PRs Off** | **Toggle PR Scanning** | | **PR Comments** | **PR Comments On** or **PR Comments Off** | **Toggle PR Summaries** | | **Natural Language** | **NL Modification On** or **NL Modification Off** | **Toggle Semantic Patch Improvements** | | **Reset Settings** | Clears the repositories' custom scanner settings so they use the defaults again, after you confirm | Every repository scanner settings permission | | **Delete** | Deletes the repositories, after you confirm | **Delete Repository** | When you open the menu, it shows **Checking available actions…** while ZeroPath checks your permissions on the selection. An action you cannot run on every selected repository is disabled with the note "You need this permission on every selected repository." **Delete** is also disabled while researcher mode is on. For organizations billed in credits, if a scan cannot start for lack of credits, ZeroPath shows **Confirm scan cost** with a quote before starting the scans. ## Protection The **Protection** column shows whether a repository's scan settings keep it covered. Its status ignores open findings. | Status | Meaning | | - | - | | **Protected** | The last full scan succeeded, and the repository has a scan schedule, PR scanning and PR comments. Repositories without pull requests (generic Git, CVS and uploaded repositories) need only the schedule. | | **Partial** | The last full scan succeeded, but a recommended setting is missing. Hover the status to see which, for example "No schedule, PR comments off". | | **Scan failing** | The last full scan failed. Hover the status to see the error. | | **Not protected** | The repository has never been scanned successfully ("Never scanned"), or it is empty and cannot be scanned. | Click the status to open the **Protection** panel. It lists: | Item | Value | | - | - | | **Scheduled scans** | The schedule's cadence (**Weekly**, **Monthly**, **Quarterly** or **Custom**), or **Off** | | **PR scanning** | **On** or **Off** | | **PR comments** | **On** or **Off** | | **Natural-language fixes** | **On**, or **Optional** when off. This setting does not change the status. | | **Last full scan** | How long ago the last successful full scan ran, the failure message, or **Never** | Next to each missing recommended setting, a button turns it on for the repository: * **Set weekly** creates a repository scan schedule that runs a full scan of the default branch every Sunday at 00:00 UTC. It needs the **Create/Edit Scan Schedule** permission. Scheduled scans use credits for organizations billed in credits. * **Turn on** next to **PR scanning** turns on PR scanning. It needs the **Toggle PR Scanning** permission. * **Turn on** next to **PR comments** turns on PR comments. It needs the **Toggle PR Summaries** permission. For a **Partial** repository, **Turn on recommended** turns on every missing setting you have permission for, in one click. The change applies right away, with no confirmation. If it fails, the panel goes back to the previous value and shows an error. Buttons appear only for the settings you have permission to change. **All settings** opens the repository's **Settings** tab, where you can choose another schedule. See [Scan Scheduling](/docs/platform/scanner-settings#scan-scheduling). ## Monorepos **Monorepos**, at the top of the page, opens the page where you split one repository into separately scanned directories. See [Directory Partitions](/docs/platform/scanner-settings#directory-partitions-monorepo-support). ## Repository page Open a repository to see its page. The header shows the repository name and provider. It also shows a Wiz **Connected** badge when your organization has [Wiz](/docs/integrations/wiz) connected, the Security Compass logo for a linked repository, and **Unlinked** for a GitHub repository whose connection is broken. The header has these actions: * **Explore latest scan** opens the repository's most recent full scan in the [scan explorer](/docs/platform/scans#scan-explorer). * **Scan repository** opens the scan dialog, where you pick the branch to scan. For an uploaded repository, this button reads **Upload & scan** and opens the upload dialog. * An arrow button opens the repository in its version control provider, in a new tab. When the last full scan failed, a warning under the header explains the failure. It links to **Review Git connections** or **Review scan branch** when one of those can fix it, and to **Scan details**, which opens that scan in the scan explorer. The page has these tabs: | Tab | What it shows | | - | - | | **Scans** | The repository's scans, with **Full Scans** and **PR Scans** buttons, a search, a branch menu (when more than one branch was scanned), the **Score** filter and, for PR scans, **Has issues**. Click a scan to open its findings on the **Issues** tab. | | **Issues** | The repository's findings, in the same view as the Issues page. See [Global and repository Issues views](/docs/platform/issues#global-and-repository-issues-views). | | **Inventory** | The repository's packages, in the views **Overview**, **Risk**, **Dependencies**, **Licenses** and **AI components** | | **Threat model** | The repository's [threat model](/docs/platform/threat-model) | | **Runtime validation** | [Runtime Validation](/docs/scanning/runtime-validation) for the repository. This tab shows an **Early access** badge in the header while it is open. | | **Feedback** | The written reasons recorded when people triaged the repository's findings, which you can edit. See [Triage Feedback Tab](/docs/platform/scanner-settings#triage-feedback-tab). | | **Security Compass** | Shown only for a repository linked to [Security Compass](/docs/integrations/security-compass) | | **Settings** | The repository's scanner settings. See [Scanner Settings](/docs/platform/scanner-settings). | The page opens on the **Scans** tab. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.