// reference
Glossary
Definitions of terms used in the Superagent dashboard and documentation.
Agreement
Contributor License Agreement (CLA) legal text stored as a template with versioned hashes. Managed under Agreements.
Contributor trust
Security signals about a GitHub contributor (identity, origin, spray patterns), published as a GitHub check and tracked on the Contributors page. See Contributor Trust.
Finding
A security issue or decision unit in the org-wide Findings queue. Findings can come from Superagent security workers, customer-provided security agents, and connected advisory sources. See Findings and reports.
GitHub App
An installation that grants Superagent access to selected repositories. Superagent Security powers scans, trust, and reports; Open CLA powers agreement checks. See Connect GitHub.
Context Guardrails
Trust scoring for the external content agents consume. Supported origins are web pages, email, messages, files, agent skills, MCP repositories, and packages. See Context Guardrails.
Message scan
A text-only Context Guardrails scan for an SMS, WhatsApp, or social message. It evaluates message text and outbound HTTPS links. Media and attachments are outside its scope. See Messages.
Runtime Guardrails
Endpoint-local monitoring and enforcement for coding agents. Superagent clients normalize agent activity, evaluate security rules locally, and report findings and enforcement decisions. See Runtime Guardrails.
MCP server
Superagent's agent-facing Model Context Protocol server. Customer agents use it to work with security workers, read findings, and return structured agent reports. See MCP.
MCP repository scan
A static Context Guardrails scan of a public GitHub repository that contains an MCP server. The scan evaluates identity, source, tool descriptions, instructions, and schemas without connecting to or executing the MCP server. It requires the Superagent Security GitHub App and fails closed when repository contents cannot be scanned. See MCP repositories.
Package scan
A Context Guardrails scan of a registry package (ecosystem:name@version). It uses the same supply chain pipeline as pull request dependency checks and maps package intelligence into identity, behavior, and content scores. See Packages.
PR scan
The two checks Superagent runs on pull request changes: Superagent Security Scan and Superagent Supply Chain Scan. Contributor Trust is a separate repository control. See PR Security and Contributor Trust.
Security worker
A built-in unit of security execution: PR Security, Secure Dependency Updates, Red Team, or Agent Guardrails. A security worker runs a defined job against protected software and produces checks, reports, findings, or enforcement decisions. It is distinct from a protected AI agent or a customer coding agent.
Report (red team)
The resulting record and evidence from a Red Team run against a repository, application, agent, or package artifact. Red-team reports live under Red team (/app/reports). See Red Team.
Structured agent report
The typed result a customer agent returns through Superagent MCP after investigation, remediation, or disposition. Superagent retains it as customer context for subsequent work.
Customer context
Customer-specific structured agent reports and related security context that Superagent retains and applies across protected software and security workers.
Repository
A GitHub repository connected through a GitHub App installation, with per-repo scan and CLA settings on its detail page. See Repositories.
Template (agreement)
A versioned CLA document in Agreements, assigned to repositories on the repository detail page.