[Export Audit] DEFAULT_IMAGE_* constants - unused image configuration exports

[github-actions]

Unused Exports: Image Configuration Constants

File: src/image-resolver.ts
Symbols: (all pre-verified with 0 external usages)

• DEFAULT_IMAGE_REGISTRY (line 36)
• DEFAULT_DIND_STAGING_IMAGE (line 37)
• DEFAULT_DOH_PROXY_IMAGE (line 38)

Analysis

Three exported constants for default image configuration are never imported outside their defining file. These appear to be internal configuration values that were exposed but not consumed.

Verification:

grep -rw "DEFAULT_IMAGE_REGISTRY" src/ --include="*.ts" | grep -vE "test|image-resolver.ts"
grep -rw "DEFAULT_DIND_STAGING_IMAGE" src/ --include="*.ts" | grep -vE "test|image-resolver.ts"
grep -rw "DEFAULT_DOH_PROXY_IMAGE" src/ --include="*.ts" | grep -vE "test|image-resolver.ts"
# All return: no matches (0 usages outside defining file)

Dead Code Risk

Severity: MEDIUM (Score: 3 = unused public constants)

• Configuration confusion: Exported defaults suggest they're intended for override, but no consumers exist
• Version management: Changes to default images require maintaining these unused constants
• API clarity: Unclear whether these are public configuration points or internal defaults

Recommendation

1. If truly unused: Remove the export keyword for all three constants
2. If used via CLI flags: These may be indirectly referenced through option defaults - verify that CLI --image-registry, --dind-staging-image, etc. don't rely on these exports
3. If intended for programmatic use: Document the public configuration API and add examples

Related Context

Related to DIGEST_PINNED_IMAGE_PATTERN and isDigestPinnedImageReference unused exports - consider a holistic review of the image-resolver.ts public API.

Generated by API Surface & Export Audit · sonnet45 · 25.4 AIC · ⊞ 6.2K · ◷

• expires on Sep 23, 2026, 9:21 AM UTC