unsafe_reflectionUnsafe Reflection — 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.
// WRONG — any class can be loaded
Class.forName(req.getParameter("cls"));
// RIGHT — explicit allowlist
Set<String> ALLOWED = Set.of("com.x.A", "com.x.B");
String name = req.getParameter("cls");
if (!ALLOWED.contains(name)) throw new IllegalArgumentException();
Class.forName(name); 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.