50 lines
2.3 KiB
Markdown
50 lines
2.3 KiB
Markdown
# Dashboard Overview
|
|
|
|
The Overview page is the landing page of the Compliance Scanner. It gives you a high-level view of your security posture across all tracked repositories.
|
|
|
|
## Stats Cards
|
|
|
|
The top section displays key metrics at a glance:
|
|
|
|
| Metric | Description |
|
|
|--------|-------------|
|
|
| **Repositories** | Total number of tracked repositories |
|
|
| **Total Findings** | Combined count of all security findings |
|
|
| **Critical** | Findings with critical severity |
|
|
| **High** | Findings with high severity |
|
|
| **Medium** | Findings with medium severity |
|
|
| **Low** | Findings with low severity |
|
|
| **Dependencies** | Total SBOM packages across all repositories |
|
|
| **CVE Alerts** | Active CVE alerts from dependency monitoring |
|
|
| **Tracker Issues** | Issues created in external trackers (GitHub, GitLab, Gitea, Jira) |
|
|
|
|
These cards update after each scan completes, so you always see the current state.
|
|
|
|
## Severity Distribution
|
|
|
|
A visual chart shows the distribution of findings by severity level across all your repositories. This gives you an immediate sense of your risk profile -- whether your findings are mostly informational or if there are critical issues that need attention.
|
|
|
|
## AI Chat Cards
|
|
|
|
The overview includes quick-access cards for the AI Chat feature. Each card represents a repository that has embeddings built, letting you jump directly into a conversation about that codebase. See [AI Chat](/features/ai-chat) for details.
|
|
|
|
## MCP Server Cards
|
|
|
|
If you have MCP servers registered, they appear on the overview page with their status and connection details. This lets you quickly check that your MCP integrations are running. See [MCP Integration](/features/mcp-server) for details.
|
|
|
|
## Help Chat Assistant
|
|
|
|
A floating help chat button is available in the bottom-right corner of every page. Click it to ask questions about the Compliance Scanner -- how to configure repositories, understand findings, set up webhooks, or use any feature. The assistant is grounded in the project documentation and uses LiteLLM for responses.
|
|
|
|
## Recent Scan Runs
|
|
|
|
The bottom section lists the most recent scan runs across all repositories, showing:
|
|
|
|
- Repository name
|
|
- Scan status (queued, running, completed, failed)
|
|
- Current phase
|
|
- Number of findings discovered
|
|
- Timestamp and duration
|
|
|
|
This helps you monitor scanning activity and quickly spot failures or long-running scans.
|