Reference
Glossary
Every Lighthouse term, with a one-line definition.
For a guided explanation of the main terms, read Key concepts.
| Term | Meaning |
|---|---|
| Admin | A team member who manages the team: GitHub connection, repositories, members, API keys, and settings. See Roles. |
| API key | A personal credential for the CLI, the pre-commit hook, and your coding agent. Shown to its owner once. See API keys. |
| Archived branch | A branch hidden from lists, with its history kept. New activity brings it back. See Branches. |
| Blocked | The outcome of a completed scan whose findings reached the blocking policy. Stops the commit, or fails the pull request check. |
| Blocking policy | The severity at which a scan blocks: Never, Critical, High+, or Medium+. Set separately for commits and merges. See Blocking policy. |
| Branch | A branch Lighthouse tracks. Cards, scans, and enhancements are kept per branch. |
| Check | The Lighthouse Security Scan result on a GitHub pull request. See The check and the comment. |
| Credits | The unit Lighthouse uses to measure AI work. See Credits and plans. |
| Credit cap | An optional monthly limit on one API key's credits. |
| CWE | Common Weakness Enumeration, the standard catalog of weakness types. CWE-89 is SQL injection. |
| Default branch | The repository's main line, usually main. Used when a branch has no cards of its own. |
| Developer | A team member who works with the repositories they can access. |
| Enhanced prompt | Your coding request with the relevant security guidance attached. |
| Enhancement | Adding security guidance to a request before your agent starts. Listed as Guardrails in the dashboard. See Prompt enhancement. |
| Fail-open | Lighthouse's rule that its own problems never block a commit or merge. See When Lighthouse can't scan. |
| False positive | A finding marked as not a real problem. It stops counting toward blocking. See Mark a false positive. |
| Finding | One security problem reported by one scan. See Findings and severity. |
| Global card | A security card from Lighthouse's catalog for an open source library, matched to the version you use. |
| Guardrail | The dashboard's name for an enhancement. |
| Ingestion | Lighthouse reading a branch at one commit to learn its security rules. See What ingestion does. |
| Local card | A security card learned from your own code. Can be edited or deleted. |
| Maintainer | A developer who manages one repository's settings, access, and branches. See Maintainers. |
| Max | The thorough scan depth, which also uses what ingestion learned. See Scan depth. |
| MCP server | A small process your coding agent runs to request guidance from Lighthouse. Set up by init. |
| Normal | The fast scan depth, which reviews only the change. |
| Plan | Your team's monthly credit allowance, assigned by RewareLabs. |
| Pre-commit scan | A scan of your staged changes that runs when you commit. See Pre-commit scans. |
| Project | The CLI's word for a repository in Lighthouse. |
| Pull request scan | A scan of a GitHub pull request, reported as a check. See Pull request scans. |
| Repository | A GitHub repository your team tracks in Lighthouse. |
| Repository summaries | Ingestion's description of the repository: Persistence, Routes, Entry points, Controls, and Libraries. Used by Max scans. |
| Rule evidence | Why a local card exists: its rationale, enforcement point, and source files. |
| Run reference | An ID shown on a failed run. Include it when you contact support. |
| Scan | A review of a code change for security problems. |
| Scan depth | How thorough a scan is: Normal or Max. |
| Scan exception | A plain-language description of something intentional that scans should not report. See Scan exceptions. |
| Security card | One secure-coding rule your coding agent can follow. Local or global. See Security cards. |
| Security point | One piece of guidance added to a prompt by enhancement. |
| Severity | How serious a finding is: critical, high, medium, or low. |
| Team | Your organization in Lighthouse. Owns repositories, members, API keys, settings, and credits. |
| Team defaults | Scan settings copied to each new repository. See Team defaults. |
Still stuck after reading this page?