api_inconsistency

Standardize API route naming convention low effort

// Before: mixed conventions
app.get('/api/getUsers', ...);     // camelCase
app.get('/api/user-groups', ...);   // kebab-case

// After: consistent kebab-case (REST convention)
app.get('/api/users', ...);
app.get('/api/user-groups', ...);

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.