Awesome Reviewers

Verification · Finding validation · Severity scoring

Impact category

Data loss, security, crash, wrong behaviour, performance, leak or maintainability.

How to build it

  1. Pick one impact category from a fixed list for each finding.
  2. Use the list: data loss, security, crash, wrong behaviour, performance, leak or maintainability.
  3. Reject findings that name no impact category.

Signals in a repository

  • A severity rubric in review guidelines with an impact category list.
  • Finding templates with a required impact field.
  • Review comments that label a finding as a data loss or security issue.

In practice

No scanned repository runs a tool for this check. The steps above are the only guidance.