Skip to main content

How to respond

When a PR opens, AISafe posts review comments on the specific lines of the diff, similar to a human code reviewer. Each comment includes:

  • The vulnerability type and severity.
  • A brief explanation of the issue.
  • A suggested fix, with a code snippet where applicable.

What developers do​

Treat the inline comments like feedback from a human reviewer. Agree with the assessment, apply the suggested fix or a better one that resolves the issue, and push the change. AISafe also reviews PR updates, so a corrected PR is checked again.

For a deeper look at the capability, see PR Review: how it works.

Why a review missed a PR​

If a PR did not get a review, open the project's Source tab. The delivery log shows whether AISafe received the pull-request or push event and why it was ignored. Common reasons shown include no project bound to the repository, a branch filter mismatch, PR review disabled, or insufficient credits.

Next steps​