/**
 * Application detection signatures for CMS platforms, e-commerce solutions,
 * and backend frameworks.
 *
 * Each entry defines multiple detection vectors: meta tags, characteristic
 * URL paths, script/global patterns, cookie names, HTTP headers, and body
 * content patterns. Matching any subset of these signals with sufficient
 * confidence identifies the technology.
 *
 * Version detection methods (where available) describe how to extract the
 * exact version from a response — typically via generator meta tags, static
 * file checksums, or error page content.
 *
 * References:
 *  - https://www.wappalyzer.com/
 *  - https://builtwith.com/
 */
/** An application / platform detection signature. */
export interface AppSignature {
    /** Application name */
    name: string;
    /** Functional category */
    category: "cms" | "ecommerce" | "framework";
    /** Detection heuristics — multiple signals increase confidence */
    detection: {
        /** Regex patterns matched against <meta> tags */
        meta?: string[];
        /** Characteristic URL paths that indicate the application */
        paths?: string[];
        /** Script src or inline script content patterns */
        scripts?: string[];
        /** window.* global variable names */
        globals?: string[];
        /** Cookie name patterns (regex) */
        cookies?: string[];
        /** HTTP response header patterns (header name → regex for value) */
        headers?: Record<string, string>;
        /** Response body content patterns (regex) */
        body?: string[];
        /** Error response format pattern */
        errorFormat?: string;
    };
    /** How to extract the exact version */
    versionDetection?: {
        /** Method description (e.g., "meta generator tag", "static file hash") */
        method: string;
        /** Regex with a capture group for the version string */
        pattern: string;
    };
}
export declare const APP_SIGNATURES: AppSignature[];
//# sourceMappingURL=app-signatures.d.ts.map