Skip to main content

​
What this is for

Discovery → Repositories is the per-repo view of your discovery footprint. Every repo synced from your connected GitHub organizations appears here with its current scan state and a category map showing which AI building blocks Discovery found in it. Use it to find the repos that pull in a specific LLM provider, depend on a particular SDK, expose MCP tools, or carry gateway configs — and to trigger a fresh scan when you need an up-to-date snapshot. For aggregate organization rollups, see Organizations. For security findings (MCP reviews and SCA), see Findings.

​
Options

​
Empty / disconnected states

  • GitHub not connected — the page shows a “Connect GitHub” prompt that links to Integrations → GitHub. Discovery cannot enumerate repos without a connected GitHub installation.
  • No organizations synced — once GitHub is connected but no orgs have been synced yet, the page nudges you to Organizations to run Sync.

​
Filters

​
Inventory table

Each row represents one repository and shows:
  • Repository name (linked to its details view)
  • Scan status badge — Completed, Scanning, or another state
  • Per-category presence — LLM providers, AI services, SDKs, MCP tools, Gateways. A column lights up when Discovery found that category in the repo.
  • A Scan action that re-runs detection on demand.
The table is paginated; pick a page size of 10, 25, 50, or 100.

​
How to configure

This is a read-mostly view — the only configuration is which orgs you sync and when you trigger a re-scan.
Discovery repositories inventory

Discovery → Repositories

1

Connect GitHub

On Settings → Integrations, connect the GitHub App so Discovery can enumerate repos.
2

Sync the source organizations

On Discovery → Organizations, click Sync on each org you want repos from. Once sync finishes, repositories appear here.
3

Filter to find a specific surface

Use the Category tabs to narrow to e.g. MCP tools, then Search by repo name to locate the one you care about.
4

Re-scan a repo

Click Scan on a row to re-run detection. The status badge flips to Scanning and back to Completed when done.
5

Drill into findings

From a row, jump to Findings to see MCP review results and SCA vulnerabilities for that repo.