Workspace #

The top-level container for everything you do in Norma. A workspace holds repositories, members, and settings. Free accounts get one workspace; Pro accounts get three. See Tiers and quotas.

Repository (or “repo”) #

A source code repository connected to Norma. Repositories live inside a workspace and are connected through a provider — GitHub, Bitbucket, or GitLab. Each repository can be scanned independently.

Provider #

The service hosting your source code: GitHub, Bitbucket, or GitLab. You authorise Norma to read your code by connecting the provider once per workspace.

Scan #

A single run of Norma’s analysis engine against one repository. A scan reads the code, detects which languages and frameworks are present, runs the matching scanners, and produces a list of issues plus an updated Production Ready Score.

Scanner #

The technical name for a Ruleset. In customer-facing UI and copy, prefer Ruleset — that’s what the product tab is called. The two terms refer to the same thing.

Rule #

A single check inside a scanner. A scanner runs many rules; each rule produces zero or more issues.

Issue #

A specific finding from a scan — a place in your code where a rule was violated. Every issue has:

• A severity — HIGH, MEDIUM, or LOW. (There is no “Critical” severity.)
• An impact area — one of Security, Performance, Architecture, Maintainability, Scalability, or Manageability.
• A file and line where the issue was found.
• A recommendation for how to fix it.

READY / NOT READY #

A label shown alongside the Production Ready Score, derived from whether the score is at or above the production-ready threshold. READY means the score is high enough to ship; NOT READY means it isn’t yet. The threshold is the same for every Norma customer in this release. See Production Ready Score.

Production Ready Score #

A single number, per repository, that summarises how safe your code is to ship. The score is recomputed on every scan and reflects the count, severity, and impact area of the issues found. A higher score is better.

Quality Certification Badge #

An embeddable SVG badge that surfaces a repository’s Production Ready Score in places like a project README. Not available in the July 2026 release — on the roadmap for a later release.

AI Findings #

Results produced by AI-powered scanners (currently the Architecture / SOLID Analyzer and the Prompt Scanner), shown on a dedicated AI Findings tab on every repository. AI findings are visible, actionable, and each carries an AI-reported confidence score and — where possible — a per-finding suggested fix. They don’t contribute to the Production Ready Score, the READY / NOT READY label, the badge, or any area sub-score — the score stays deterministic. See AI Findings.

Confidence (AI Findings) #

An AI-reported score from 0% to 100% shown on every AI finding, indicating how sure the scanner is that the finding is real and worth acting on. Rendered as a percentage plus a 3-bar meter in the AI Findings list and detail. It’s a triage hint — a high-confidence finding is a stronger signal than a low-confidence one — not a guarantee. Findings without a confidence score display as — and sort last. See AI Findings — Reading a finding.

Ruleset #

A collection of rules that Norma runs against your code during a scan. Each ruleset targets a specific language or framework — for example, the Python ruleset, the React ruleset, the PHP ruleset. When you connect a repository, Norma auto-detects your tech stack and applies the matching rulesets through a Stack Profile. The Rulesets tab in the product shows you which rulesets are active and what they check. Some rulesets are Pro-only — they appear with a padlock on Free accounts. See Pro-only rulesets. Also called a Scanner in technical contexts.

Locked ruleset #

A ruleset that applies to your repository but that your subscription tier doesn’t include. Locked rulesets appear on the Rulesets tab, the Coverage tab, and the repository target/tool view with a padlock icon and an Upgrade to Pro button — they’re never hidden, so you can see what upgrading unlocks. Locked rulesets don’t run on scan and don’t contribute to your Production Ready Score. See Pro-only rulesets.

Stack Profile #

A bundled collection of scanners tailored for a specific tech stack — for example, “Spring Boot Enterprise” or “React TypeScript Web App”. When you connect a repository, Norma auto-detects the stack and assigns the matching profile.

MCP (Model Context Protocol) #

The protocol Norma uses to talk to local AI editors (Cursor, Windsurf, Claude, etc.). When you connect Norma to your editor via MCP, your scanner findings appear inside the editor while you work.

Execution #

A historical record of a single scan. The Execution History view shows every scan you’ve run on a repository — when it ran, what was found, how long it took.

Tier #

Your Norma plan — Free or Pro. The tier determines your quotas (workspaces, repositories, scans per week) and which features you can access. See Tiers and quotas.