/**
 * Whether `sf audit security` should auto-archive its result to the local history store.
 *
 * A CI runner is usually ephemeral, so archiving there only writes org data to a disk
 * nobody reads again, and on a shared self-hosted runner it leaves that data behind for
 * the next job. Archiving is therefore off in CI unless the caller opts back in.
 */
export interface ArchiveFlags {
    'no-history'?: boolean;
    'keep-history'?: boolean;
}
/**
 * Detect a CI environment. `CI` is the de-facto convention (GitHub Actions, GitLab,
 * CircleCI, Buildkite, Travis, Bitbucket all set it); the others cover runners that don't.
 */
export declare function isCiEnvironment(env?: NodeJS.ProcessEnv): boolean;
/** `--keep-history` always wins; otherwise `--no-history` or a detected CI run skips the archive. */
export declare function shouldArchiveHistory(flags: ArchiveFlags, env?: NodeJS.ProcessEnv): boolean;
//# sourceMappingURL=archivePolicy.d.ts.map