Skip to main content
The Organizations view is where Discovery starts once you’ve connected GitHub.

​
Prerequisites

GitHub must be connected under Settings → Integrations with an active token. Until then the page shows a Connect GitHub hero instead of the org grid — see Integrations.

​
The grid

Each connected organization renders as a card showing: Click a card to drill into that organization’s repositories.
Organizations grid

​
Sync orgs

Click Sync Orgs (refresh icon, top of page). Guardway calls GitHub using your connected token, refreshes the list of organizations and repositories, and toasts one of:
  • Organizations synced — success.
  • Failed to sync organizations — GitHub call failed; usually a token scope or rate-limit issue.
Syncing is idempotent and cheap — run it any time you add repos or change GitHub access.

​
Organization detail

Click an org card to open the org detail page.

​
Metric cards

Seven KPI cards across the top:
  • Total repos (scanned)
  • Repos with AI (detected)
  • LLM providers (detected)
  • AI services (detected)
  • Dependencies (tracked)
  • MCP tools (configured)
  • Gateway configs (configured)
Below them, a Findings Overview block with five more KPIs and a Top AI Providers bar chart showing the most common providers across the org.

​
Repositories table

Filters: a search box (matches name) and status chips (All, Completed, Scanning, Failed, Never Scanned). Pagination at 25 rows per page.

​
Scan a repository

Click Scan on any row. Guardway queues the repository for analysis and starts polling every 3 seconds. While the status is scanning, the scan button shows a spinner; you can navigate away and come back. When the scan completes, Findings fills in and the per-repo tabs become populated — see Findings.

​
Export AIBOM

The Export AIBOM button (top right of the org detail) is disabled until at least one repo has completed a scan. Click it to download a CycloneDX 1.6 JSON file per repository. Org-level bulk export is not yet supported.