API Surface Issue
Category
Unused export
Summary
- File:
src/services/agent-volumes/volume-builder.ts
- Symbol:
AgentVolumesParams
- Issue: Type interface exported but never imported from any external module
Evidence
The AgentVolumesParams interface is exported from volume-builder.ts and the volume-builder is the only module that uses this type:
$ grep -rw "AgentVolumesParams" src/ --include="*.ts"
src/services/agent-volumes/volume-builder.ts:export interface AgentVolumesParams {
src/services/agent-volumes/volume-builder.ts:export function buildAgentVolumes(params: AgentVolumesParams): string[] {
No external imports found:
$ grep -r "import.*AgentVolumesParams" src/ tests/ --include="*.ts"
(no results - only used internally within volume-builder.ts)
The type is only used as a parameter type for the buildAgentVolumes function within the same module. TypeScript consumers don't need this type since they're calling the function with an object literal, not declaring variables of this type.
Recommended Fix
Remove the export keyword from the interface declaration:
// Before
export interface AgentVolumesParams {
config: WrapperConfig;
sslConfig?: SslConfig;
...
}
// After
interface AgentVolumesParams {
config: WrapperConfig;
sslConfig?: SslConfig;
...
}
This keeps the type available for internal use while reducing the public API surface.
Impact
- Dead code risk: Low — The type is used internally, just unnecessarily exported
- Maintenance burden: Low — Simple one-word fix
- API clarity: Medium — Reduces public API surface by removing unused type export
Detected by Export Audit workflow. Triggered by push to main on 2026-05-25
Generated by API Surface & Export Audit · ● 5M · ◷
API Surface Issue
Category
Unused export
Summary
src/services/agent-volumes/volume-builder.tsAgentVolumesParamsEvidence
The
AgentVolumesParamsinterface is exported fromvolume-builder.tsand thevolume-builderis the only module that uses this type:No external imports found:
The type is only used as a parameter type for the
buildAgentVolumesfunction within the same module. TypeScript consumers don't need this type since they're calling the function with an object literal, not declaring variables of this type.Recommended Fix
Remove the
exportkeyword from the interface declaration:This keeps the type available for internal use while reducing the public API surface.
Impact
Detected by Export Audit workflow. Triggered by push to main on 2026-05-25