unresolved_import

Verify the package exists, then declare it (or fix the typo) low effort

npm view <pkg>

// A bare import that resolves to no declared dependency and no
// built-in is often an AI hallucination (a plausible name that does
// not exist) or a typo. Both are supply-chain risks — a hallucinated
// name is a slopsquatting target.
//   1. Check it exists:  npm view <pkg>
//   2. If real:          npm install <pkg>   (commits it + the lockfile)
//   3. If a typo:        fix the import to the correct package
//   4. If local:         use a relative path or a configured alias

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.