/**
 * Shared security-relevance heuristics for the LLM analysis agents.
 *
 * The LLM pass is capped (cost guardrail), so on a large repo the cap must be
 * spent on the files most likely to hold security/logic bugs — routes, auth,
 * data access, handlers — not incidental files. The zero-day hunter already
 * filtered to security-relevant files; this centralises that heuristic so the
 * logic-flaw detector can *rank* its candidates the same way.
 *
 * @module agents/security-relevance
 */
/** True if the code content (or its imports) touches a security-sensitive area. */
export declare function isSecurityRelevant(content: string, imports?: string[]): boolean;
/**
 * Rank a file by security relevance (higher = analyse first). Used to order the
 * LLM candidate list within the cap so the budget is spent where it matters.
 */
export declare function securityRelevanceRank(file: string, content: string): number;
//# sourceMappingURL=security-relevance.d.ts.map