Glossary
The terms the console uses, defined once.
TermsPermalink to Terms
| Term | Definition |
|---|---|
| Workspace | The personal or organization context that owns repositories, scans, findings, keys and usage. |
| Repository | A GitHub repository connected through the GitHub App installation. |
| Scan | One analysis run against one repository. |
| Progress phase | Where a running scan has reached: queued, preparing repository, analyzing code, validating findings, or preparing report. |
| Terminal state | How a scan ended: complete, failed, canceled, or needs review. |
| Result | What a completed scan produced: a headline, a coverage assessment and any findings. |
| Coverage | How much of the repository the scan was able to examine. Adequate coverage is required before a zero-finding scan can be called clean. |
| Limited coverage | The scan finished without examining enough to vouch for the result. Not an all-clear. |
| Finding | One reported issue, with a severity, a proof state and — where known — a file and line. |
| Severity | How serious an issue would be: critical, high, medium, low, informational, or unknown. |
| Proof state | How well evidenced a finding is: confirmed, needs validation, or unconfirmed. |
| API key | A credential that authenticates programmatic requests. Shown once at creation and revocable at any time. |