/**
 * Security dimension — health-side adapter over the canonical
 * security scorer.
 *
 * Translates `ScoreInput { metrics, capabilities }` into the
 * `SecurityScoreInput` partition consumed by `scoreSecurityFromInput`,
 * then wraps the resulting score in a full `DimensionScore` (status +
 * details + metrics envelope) for the health audit rollup.
 *
 * D023 closure: this file used to delegate to a separate
 * `scoreSecurity` in `analyzers/scoring.ts`; that function is gone,
 * and the canonical formula now lives in `security/scoring.ts` so
 * both the health audit and the standalone vuln scan compute the
 * same number from the same partitioned inputs.
 */
import { type SecurityScoreInput } from '../../scoring';
import { DimensionScore, ScoreInput } from '../types';
/**
 * Build the canonical `SecurityScoreInput` from the health-side
 * `ScoreInput`. Each field maps to its data source:
 *
 *   - `secretFindings`   ← `capabilities.secrets.findings.length` (gitleaks)
 *   - `privateKeyFiles`  ← `metrics.privateKeyFiles` (find on disk)
 *   - `envFilesInGit`    ← `metrics.envFilesInGit` (git ls-files)
 *   - `codeFindings`     ← `capabilities.securityAggregate.codeBySeverity`
 *                         post-G_v4_8 (C1.3). One source of truth for
 *                         every health vs vuln-scan comparison; closes
 *                         the D086 class of "same metric, different
 *                         totals." Falls back to legacy capability +
 *                         metrics counting only for ScoreInput shapes
 *                         that predate the aggregator field (test
 *                         fixtures, pre-2.4.7 callers).
 *   - `depVulns`         ← `capabilities.securityAggregate.depBySeverity`
 *                         (post-fingerprint-dedup), falling back to
 *                         `capabilities.depVulns.counts` for legacy.
 */
export declare function toSecurityScoreInput(input: ScoreInput): SecurityScoreInput;
/**
 * Score-only adapter for action ranking. The health remediation
 * planner builds `RemediationAction<ScoreInput>` patches and calls
 * `rank()` with a per-dimension scorer that maps `ScoreInput` to
 * `{ score }`. Keeping this thin wrapper lets `health/actions.ts`
 * stay symmetric across dimensions without leaking the
 * `SecurityScoreInput` shape into the health-side action code.
 */
export declare function scoreSecurityFromScoreInput(input: ScoreInput): {
    score: number;
};
/**
 * Health audit's Security dimension entry point. Produces the
 * `DimensionScore` consumed by `health.ts:analyzeHealthInternal` for
 * the dimension rollup, the dashboard summary, and the agent report.
 */
export declare function scoreSecurityDimension(input: ScoreInput): DimensionScore;
//# sourceMappingURL=shallow.d.ts.map