`ai_security_risk`

Ai Security Risk — a PullGuard finding type. Findings of this type appear in the PR comment, Step Summary, SARIF (GitHub Security tab / IDE viewers), and the HTML report, each with severity, location, and the remediation guidance below.

How to fix

Human-review this AI-generated file before release medium effort

// This file shows AI-generation signals AND a real security finding.
// AI-assisted code has higher defect density (Stanford 2023), so:
//   1. Manually verify the flagged security finding is remediated
//      (do not trust an AI-suggested "fix" without review).
//   2. Confirm the AI-authored logic matches the intended behaviour.
//   3. Add tests covering the security-relevant path.

Triage

Suppress a confirmed non-issue with a committed .pullguardignore entry (pullguard ignore locally, or comment /pullguard ignore <fingerprint> <reason> on the PR — the fingerprint is printed in the PR comment’s Triage section). Entries support expiresAt for time-boxed snoozes.

Security findings at major or critical severity — and any critical finding — always surface: .pullguardignore cannot hide them. The reviewed paths that keep them visible are acknowledged (reviewed, stays in reports) and, for a confirmed false positive, a reasoned false_positive entry — visible and audited, excluded only from the merge block.