Projects
A project is the container for the scans, findings, and dependencies of one repository. The /projects page lists every project in your organization. Projects are created automatically — on the first CLI scan, or when you enable a repository from an SCM connection.
The projects grid
Section titled “The projects grid”Each card shows the project name, its Git provider, the severity mix of its open findings, the last scan time, and whether a scan is currently running. Click a card to open Project Detail.
Each card also has a mute / unmute button in its top-right corner. Muting removes a noisy or low-priority project from the org dashboard rollup without changing any of its findings — the card stays here in full and gains a Muted badge. The button appears on hover for active projects and is always shown (as unmute) once a project is muted.
Filtering and sorting
Section titled “Filtering and sorting”| Control | Effect |
|---|---|
| Search | Match projects by name. |
| Tags | Show only projects carrying the selected tags (multiple tags are ANDed). |
| Provider | Filter to GitHub, GitLab, or Bitbucket. |
| Sort | Order by name, last scan, or newest. |
Filters are reflected in the URL, so a filtered view can be bookmarked or shared.
Scope navigation
Section titled “Scope navigation”The tree on the projects page groups projects by Git host and then by namespace path (for example a GitLab group and subgroup). Drill in to scope the grid to one host or folder. Projects with no SCM link — such as CLI-scanned repositories — appear under an Ungrouped node.
Tags are free-form labels (up to 16 per project, lowercase) you apply to projects to group them across SCM boundaries — team:payments, tier:1, pci. Once applied, they drive the Tags filter above.
Adding a repository
Section titled “Adding a repository”- Click Connect repository at the top of the page.
- Choose a provider: an SCM connection you already have, or a new one. A new one sends you to the provider to authorize Vygl and brings you back. See Connecting Your Code.
- Pick repositories: tick the ones you want scanned (or Select all) and click Add. Repositories already added are marked as such.
Each enabled repository becomes a project and is scanned automatically on every push and pull request.
Triggering a scan
Section titled “Triggering a scan”For a managed (SCM-linked) project, the scan action on the card queues a fresh scan immediately, without waiting for a push. CLI-scanned projects are re-scanned by running the CLI again.