`circular_import`

Circular Import — 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

Break circular dependency by extracting shared types medium effort

// Before: A imports B, B imports A
// a.ts: import { BType } from './b';
// b.ts: import { AType } from './a';

// After: extract shared types to a third file
// types.ts: export type AType = ...; export type BType = ...;
// a.ts: import { BType } from './types';
// b.ts: import { AType } from './types';

Use dependency injection to invert the dependency medium effort

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.