Dashboard and repositories

The dashboard collects every scan you have run. Open it with the Dashboard button in the top bar. The menu on the left has Overview, Repositories, Leaked Secrets, Risky APIs and Settings, with New Scan at the bottom.

Overview

The Overview page summarises your security posture across all scanned repositories.

CardWhat it shows
Repos scannedHow many different GitHub repositories you have analysed at least once.
Health scoreThe share of your last 10 scans that completed successfully.
Top 5 Leaked SecretsThe five most urgent secrets found in your repositories, live ones first. Click View all to open Leaked Secrets.
Top 5 Risky APIsComing soon. See Risky APIs.
Recent scansYour 8 most recent scans with repository, status, branch and date. Click a finished scan to open its report.

Repositories

The Repositories page lists every repository you have scanned, newest first. Each card shows the latest scan's status, when it ran and which branch it scanned.

  1. 1
    Click Repositories in the dashboard menu.
  2. 2
    Click View report on a repository to open its latest report.
  3. 3
    To see older scans, click the arrow button at the left of the repository card. Scan history lists every scan of it, with status and branch. Click any finished scan to open that report.
lightbulb
Comparing scan history is a quick way to check a fix: re-scan after upgrading a package and compare the new report with the previous one.

A report only opens once its scan is done. Until then, the card shows Report unavailable.

Scan statuses

StatusMeaning
QueuedWaiting for a free scanner.
RunningDownloading the repository and mapping its dependencies.
Scanning CVEsChecking packages against vulnerability databases.
Scanning secretsChecking files for leaked keys, tokens and passwords.
DoneThe report is ready.
ErrorThe scan failed and has no report. Check the reasons below, then start a new scan.

Common reasons a scan fails:

  • The repository is private and GitHub is not connected, or the connection lacks private access.
  • The URL is mistyped, or the repository or branch no longer exists.
  • The repository is larger than the download limit (100 MB compressed).