What you’ll see #

The Overview has three things to know about, in order of importance:

1. Production Ready Score — a single number from 0 to 100, with a READY or NOT READY label derived from it.
2. Score by impact area — four cards breaking the score down across the four impact areas.
3. The stack and ruleset summary — what Norma detected and applied.

Production Ready Score #

This is the headline number. It reflects how many of Norma’s rules your code is passing — not the number of findings. The score and the READY / NOT READY label are one signal: when the score crosses the production-ready threshold, the label flips to READY; below it, NOT READY.

A few cases to anchor the formula:

• 7 rules in an area, 1 fires HIGH — the area scores 86% (six of seven rules clean).
• 7 rules in an area, 1 fires MEDIUM — the area scores 93% (six clean + one half-credit, averaged).
• Same rule fires in 50 files vs. just 1 file — the area score is identical. Files don’t change the rule’s pass/fail state.

For the full formula and edge cases, see Production Ready Score.

Score by impact area #

The overall score is a weighted average of six area sub-scores:

• Security — vulnerabilities, secret leaks, unsafe patterns.
• Performance — code that will be slow at scale.
• Maintainability — readability, test coverage, complexity.
• Scalability — patterns that won’t survive growth.

Each area has its own card on the Overview page showing:

• The area’s score (0–100), or Not measured if no rules apply to your stack in that area.
• A status chip — PASS or FAIL.
• The breakdown by severity (H/M/L).
• The number of issues and the count of rules affected.
• The area’s weight in the overall score (e.g. w 20%).

Click any area card to see the issues that contributed to its score.

What to do first #

If your score is NOT READY, work in this order:

1. Open the lowest-scoring area first. That’s where fixing rules will move the overall score most.
2. Inside that area, fix HIGH findings before MEDIUM before LOW. A HIGH fix moves a rule from 0 → 100; a LOW fix moves it from 75 → 100. Bigger lever, more score recovered.
3. Repeat for the next area down. Watch the label flip to READY the moment the score crosses the threshold.

Each issue has a fix recommendation. Open the issue to see the file, line, and exactly what we suggest changing.

Re-scanning #

Norma does not scan automatically on every push (yet — multi-branch scanning is on the roadmap). When you’ve made changes, click Run Scan on the repository card or on the top-right of the Overview page. The scan reads the current code on your default branch and updates the score in place.

You have a weekly scan quota depending on your tier — see Tiers and quotas.

Frequently asked questions #

Why is my score different from a colleague’s score on the same repo?
It shouldn’t be — the score is per repository, not per user. If you see different numbers, you might be looking at different scans (compare the timestamps).

My score dropped after the latest scan. What happened?
Either your code changed (new issues were introduced) or we updated rules in the latest release. Open the Coverage tab — newly-introduced rules appear in the rule execution log so you can pinpoint what shifted.

An area shows “Not measured” — is something broken?
No. That area has no rules configured for your detected stack. It’s excluded from the overall weighted average.

Can I disable a rule that’s flagging something my team accepts as a trade-off?
Not in the July 2026 release — rule-level disabling is on the roadmap.

Related #

• Connect your first repository — the step before this one.
• Production Ready Score — the deep dive on the score, the threshold, and the area formula.
• Reading results — the Issues tab in detail.
• Supported languages and frameworks — what got scanned in your repo.
• Tiers and quotas — how many scans you get per week.