/01 Reference
Every Nexdge review returns a structured report with findings from each specialist.
Severity grades
| CRITICAL | Immediate exploitation possible. Fix before deploying. |
| HIGH | Significant risk under specific conditions. Fix this sprint. |
| MEDIUM | Technical debt or limited risk. Add to your backlog. |
| LOW | Best practice violation. Fix when convenient. |
| PASS | No issues found by this specialist. |
Reading a finding
Each finding contains: a short title describing the issue, a plain English explanation of what the problem is and why it matters, the line number where it was found, and a suggested fix, a corrected version of the affected code.
Applying a fix
- In the web app: click Apply fix on any finding to replace the affected code with the verified rewrite.
- In VS Code: run Nexdge: Review Now, then apply the suggested fix from the diagnostic.
- In GitHub: copy the suggested fix from the PR comment and commit it.
The verified rewrite loop
Every suggested fix is verified before you see it. After rewriting the code, Nexdge re-runs analysis on the rewrite. If issues remain, the loop runs again, up to three iterations. If something can't be resolved, it's flagged honestly with a note that manual review is recommended, rather than silently marked clean.
Overall score
| 90–100 | Excellent. Ship with confidence. |
| 70–89 | Good. Minor issues to address. |
| 50–69 | Needs work. Resolve HIGH findings before deploying. |
| Below 50 | Significant issues. Do not deploy without fixes. |