# Glossary

The words Kelrova uses for code hosts, code sources, projects, scans, findings, fixing with your own agent, plans and members, with links to the page for each.

*Last updated: 2026-10-21*

The terms used across these pages, grouped by where you meet them.

## Code and projects

| Term | Meaning |
| --- | --- |
| Connection | Your organization's link to a namespace at a code host: a GitHub account or organization, a GitLab group or personal namespace, or a Bitbucket workspace. Managed on **Connections**. [Connect GitHub](https://kelrova.com/docs/getting-started/connect-github) |
| Needs attention | A GitLab or Bitbucket connection whose credential stopped working. New scans are blocked until an admin reconnects it. [Details](https://kelrova.com/docs/getting-started/connect-gitlab-bitbucket) |
| Code source | One linked repository on one branch: the whole repository or a single folder of it. [Add a code source](https://kelrova.com/docs/getting-started/code-sources) |
| Tracked branch | The branch of a code source. Scans and fixes always work on it. |
| Excluded paths | Folders of a code source that scans never review, such as `vendor/`. |
| Project | The code sources that make up one product. It decides who sees its scans and findings. [Create a project](https://kelrova.com/docs/getting-started/projects) |
| Visibility | **Organization**, where everyone can view a project, or **Restricted**, where only the members you add can. |
| Project role | Viewer, Contributor or Maintainer, given to a member of a restricted project. |

## Scans

| Term | Meaning |
| --- | --- |
| Scan | A review of a project at a level. A scan you start by hand runs once. |
| Level | How much a scan reviews: Quick, Focused, Standard, Extended, Full or Adversary. Quick needs an earlier completed scan; Adversary needs Pro or above. [Scan levels](https://kelrova.com/docs/scans/levels) |
| Model tier | Fast, Balanced or Best. Best comes with Pro and above. [Model tiers](https://kelrova.com/docs/scans/model-tiers) |
| Run page | The page of one scan: its progress and its findings. [Read the run page](https://kelrova.com/docs/getting-started/read-results) |
| Partial run | A scan that did not review everything it set out to. [Outcomes](https://kelrova.com/docs/scans/outcomes) |
| Schedule | A repeating scan: daily, weekly or every two weeks. [Scheduled scans](https://kelrova.com/docs/schedules/schedules) |
| Threat model | An optional description in Security settings that tells scans what matters most to you. |

## Findings

| Term | Meaning |
| --- | --- |
| Finding | A weakness a scan confirmed, with its severity, its location and the evidence for it. |
| Severity | Critical, High, Medium, Low or Info. |
| Status | Open, Unverified, Fixed, Accepted risk or False positive. A proposal from a connected agent waits for a member on top of the status. [Statuses](https://kelrova.com/docs/findings/statuses) |
| Attack path | How an Adversary finding is reached, step by step, with **Affects** saying whether it reaches one user, one tenant or all users. |
| Dependency advisory | A finding about a package your code depends on. It says so when it is not known whether your code reaches the package. [Dependency advisories](https://kelrova.com/docs/findings/dependency-advisories) |
| Go Fix | The three actions on a finding: **Fix it now**, **Re-check this finding** and **Ask about this finding**. [Go Fix](https://kelrova.com/docs/findings/go-fix) |
| Merge gates | Reviews a fix must pass before its pull request can be merged. Security Review and Code Review are built in; an owner can add custom gates. [Merge gates](https://kelrova.com/docs/findings/merge-gates) |

## Fixing with your own agent

| Term | Meaning |
| --- | --- |
| MCP server | Kelrova's remote server at `https://mcp.kelrova.com/mcp`, which lets an agent work through findings in its own checkout. [The MCP server](https://kelrova.com/docs/mcp/overview) |
| Access level | What a connected agent may do: **View findings**, **Report progress** or **Request re-checks**. |
| Stay connected | The access that keeps an agent connected without signing in again. |
| Machine client | A client for CI and other automation. Its token lasts 15 minutes and has no refresh token. [Machine clients](https://kelrova.com/docs/mcp/machine-clients) |

## Plans and members

| Term | Meaning |
| --- | --- |
| Plan | Basic, Go, Pro, Max or Enterprise. It sets members, model tiers, levels and included usage. [Plans](https://kelrova.com/docs/organization/plans) |
| Trial | Basic starts with 14 days. Scans run at Quick and Focused. |
| Included usage | Usage equal to the plan's monthly price. Unused usage does not roll over. |
| Balance | An organization's prepaid credit, topped up when you choose. |
| On-demand | A billing setting that lets scans keep running on the balance once plan usage is used up. It can have a cap. Scans wait when it is off, at its cap or the balance is empty. [Billing](https://kelrova.com/docs/organization/billing) |
| Owner, Admin, Member | The roles of an organization. Owners and admins manage connections, code sources and projects, and invite members. [Members and roles](https://kelrova.com/docs/organization/members) |

## Related

- [Start here](https://kelrova.com/docs/getting-started/overview)
- [Questions people ask](https://kelrova.com/docs/reference/faq)
- [Limits](https://kelrova.com/docs/reference/limits)