import type { CommandModule } from 'yargs';
import type { IssueGroup } from '../../types/analysis.types';
import type { AnalyzeCommandArgs } from '../types/cli.types';
/**
 * Recover a stack name passed after the `--` separator.
 *
 * yargs 17 routes tokens after `--` into `argv._` but does NOT bind them to a
 * named positional, so `scan -- MyStack` (the injection-safe form the GitHub
 * Action and the usual CLI convention use) leaves `stackName` undefined — and
 * in CI that silently falls back to scanning every stack. When the positional
 * didn't bind and exactly one extra token sits in `argv._` (besides the `scan`
 * command word), treat it as the stack name. Anything ambiguous (zero or
 * multiple leftover tokens) is left alone.
 */
export declare const recoverPositionalStackName: (stackName: string | undefined, underscore: ReadonlyArray<string | number>) => string | undefined;
export declare function runStackAnalysis(finalConfig: AnalyzeCommandArgs, fingerprint?: string, authToken?: string, licenseInfo?: any, usageData?: any, _project?: string, licenseKey?: string, forceLocal?: boolean, sensitiveDataConfig?: {
    enabled?: boolean;
    warnOnly?: boolean;
    allowPatterns?: string[];
    ignoreProperties?: string[];
    strictMode?: boolean;
}, baselineExclude?: Set<string>, collectFingerprints?: Set<string>, skipRendering?: boolean): Promise<{
    totalResources: number;
    acknowledgementsPerStack: Record<string, import("../../types/analysis.types").InlineAcknowledgement[]>;
    recommendationMaps: {};
    hasCriticalIssues: boolean;
    scannedResourceIds: Set<string>;
    hasSensitiveData?: undefined;
} | {
    totalResources: number;
    acknowledgementsPerStack: Record<string, import("../../types/analysis.types").InlineAcknowledgement[]>;
    recommendationMaps: Record<string, IssueGroup>;
    hasCriticalIssues: boolean;
    hasSensitiveData: boolean;
    scannedResourceIds: Set<string>;
}>;
export declare const analyzeCommand: CommandModule<Record<string, unknown>, AnalyzeCommandArgs>;