/**
 * log10x_dependency_check — find SIEM dependencies on a pattern.
 *
 * Two execution paths:
 *
 *   1. **In-process scan** (preferred). When credentials for the resolved
 *      SIEM are present in the environment, this tool issues read-only
 *      API calls directly (Splunk REST, Datadog SDK, CloudWatch SDK,
 *      Kibana saved-objects) and returns counts + names + console URLs
 *      of matching dashboards / alerts / saved searches / monitors /
 *      metric filters. Fully read-only — no POST/PUT/DELETE.
 *
 *   2. **Paste-ready bash fallback**. When credentials are missing (or
 *      the in-process scan errors before producing results), the tool
 *      returns the original `curl + python3 siem-check-<vendor>.py`
 *      block so the user can run the scan themselves.
 *
 * Vendor selection:
 *   - When `vendor` is omitted, auto-detect via the same resolver
 *     `log10x_poc_from_siem_submit` uses. Single SIEM detected → use it.
 *     Multiple → return a structured "pick one" error listing the
 *     candidates. None → require an explicit vendor argument.
 *   - The dep-check tool covers 4 of 8 SIEMs in the registry: datadog,
 *     splunk, elasticsearch, cloudwatch. Auto-detection is restricted to
 *     that subset so a user with only ClickHouse/GCP/Azure creds gets a
 *     clear "no supported SIEM detected" message instead of being
 *     silently routed to a vendor we don't have a script for.
 */
import { z } from 'zod';
export declare const dependencyCheckSchema: {
    pattern: z.ZodString;
    vendor: z.ZodOptional<z.ZodEnum<["datadog", "splunk", "elasticsearch", "cloudwatch"]>>;
    service: z.ZodOptional<z.ZodString>;
    severity: z.ZodOptional<z.ZodString>;
};
export interface DependencyCheckArgs {
    pattern: string;
    vendor?: string;
    service?: string;
    severity?: string;
}
export declare function executeDependencyCheck(args: DependencyCheckArgs): Promise<import('../lib/output-types.js').StructuredOutput>;