Product guide · English
Understand scores and grades
Use scores to prioritize review within the checks that ran. Always read the grade alongside coverage, critical findings and the report’s scoring version.
Steps
- Open a completed report and inspect its suite and category scores. Only covered scored categories contribute; an absent category is not a score of 100.
- Read the category deductions and their underlying findings. Categories start at 100; severity-weighted deductions have caps, and suppressed findings are excluded from deductions.
- Inspect critical findings even if the numeric score is high. An open critical finding caps the grade at D.
- Compare reports only after checking their scope and scoring version. A change in checks can change the score without a corresponding code improvement.
Read the result
The current scoring model combines covered categories into five weighted suites. Grades start at A for 90, B for 80, C for 70 and D for 60; lower scores receive F, subject to the critical cap. Privacy checks and Git history analytics are unscored; secrets recovered from Git history count under Security.
Limits and availability
A partial scan or smaller check selection can hide risk behind a good score. Unscored reviews are not failed numerical grades and should be read on their own evidence. A score is neither a compliance verdict nor a probability that an attack will succeed.
This guide describes the implemented workflow. The features available in your workspace depend on account capabilities and configuration; advanced workflows are not all included in Free Quick Scan. Check the available controls and the evidence returned by each run.