Score did not change

Symptom

You fixed or merged something, but the audit metric still shows the same score or zone.

Quick checks

• Confirm the proposed issue or PR/MR was actually merged.
• Confirm the default branch contains the change.
• Confirm a new audit completed after that merge.
• Compare the commit in the new report with the commit containing the fix.
• Verify that you reran the audit that owns the original finding.

Diagnose the score

An open review request does not change repository health. The existing score remains correct for its recorded commit until a later audit finishes. Even after a real fix, another finding, criterion, deduction, or evidence-backed cap can keep the final number in the same place. The report’s calculation and findings show whether the repaired evidence disappeared.

A score can also remain numerically equal while its evidence changes. Conversely, a runbook or available tool change can affect comparability between runs. Read criteria, limitations, and commit coverage instead of comparing only the gauge.

Resolve the problem

Merge the intended change through normal review, wait for the provider default branch to include it, and request or await an eligible rerun. Open the new report and search for the original evidence. If the finding remains, check whether the fix addressed a symptom rather than the root cause or whether the audited surface differs from the changed code.

If a cap remains, resolve the fact that justifies the cap rather than trying to increase unrelated criterion scores.

Escalate safely

Provide the old and new audit names, checked commits, source finding title, merged PR/MR link, and the relevant score-calculation text. Redact private paths or report evidence as required. Do not share credentials or assume that manually editing a provider artifact can change the score.