Home
The organization at a glance — what is scanned, what breaks the allowlist, and what waits for someone.
Home summarizes the organization. Until GitHub is connected and one repository is scanned, it shows the next step instead — connect GitHub, or scan a repository.
The cards
| Card | Shows |
|---|---|
| Repositories scanned | How many of the repositories the GitHub App can see are scanned, and when the last scan finished (or how many are scanning now). |
| Violations | Packages the allowlist denies, or does not list, in an audited ecosystem — split into Denied and Not listed. Opens the dependency list filtered to violations. |
| Needs attention | Failed scans, notes waiting to be imported, and allowlist entries running out. One button leads to the most urgent of them. |
| Policy | The mode of each ecosystem in use (Off, Audit, Enforce) and which repositories get pull request checks. |
| Most violations | The repositories with the most violating packages. |
| Packages | The packages in use, by ecosystem. |
| Recent activity | The latest changes: packages added or removed, and changes to notes, the allowlist and the policy. |
| Expiring entries | Allowlist entries that run out in the next 14 days, soonest first. |
A violation counts packages, not usages: a package used in five repositories is one violation.
Sidebar counts
Two items in the sidebar carry a count when something waits:
- Allowlist — the number of violating packages, the same number as the Violations card.
- Notes — the packages in the review queue.
The counts update after you save a note, an allowlist entry or the policy, when a scan you are watching finishes, and when you come back to the tab after a while.