Repositories is your source-code inventory. It lists every repository Vibgrate tracks, each with its latest drift score, risk level, scan coverage, and the application it belongs to. This is where engineers go to find a specific repository and see its current state.
What you'll see
- Drift score and risk level for each repository, from its most recent scan.
- Scan coverage — when it was last scanned, and whether security and SBOM analysis ran.
- Application mapping — which application each repository is part of.
Repositories are identified by their normalized remote URL, so the same repository is recognized across scans even if it's checked out in different places.
Open a repository
Select a repository to see its full detail: the score breakdown, its projects, VCS information, and scan history. Use this to understand why a score is what it is, not just what it is.
Repositories vs applications
A repository is a single source-code repo. An application is a product or service that may span several repositories. If you want "all the repos in product X", look under Applications — that's where the catalog bindings live. Use Repositories when you're working with the code itself.
If a repository is missing
Connect it under Settings → Source control, then run a scan. A repository only appears here once it has been connected and scanned at least once.