[duplicate-code] Duplicate Code Analysis Report

[github-actions]

Analysis of commit 4227da6

Summary

The feat: add proxy mode for GitHub API DIFC filtering (#2176) commit introduced 3 significant code duplication patterns between the new internal/proxy/ package and the existing internal/server/unified.go. Total duplicated logic spans ~400 lines across the two codebases.

Detected Patterns

1. 6-Phase DIFC Pipeline – Severity: High – See sub-issue [duplicate-code] Duplicate Code Pattern: 6-Phase DIFC Enforcement Pipeline #2198
2. Guard Initialization (LabelAgent) – Severity: Medium – See sub-issue [duplicate-code] Duplicate Code Pattern: Guard Initialization (LabelAgent) #2199
3. Policy JSON Parsing & Validation – Severity: Medium – See sub-issue [duplicate-code] Duplicate Code Pattern: Policy JSON Parsing in proxy vs config package #2200

Overall Impact

• Total Duplicated Lines: ~400 lines of near-identical logic
• Affected Files: internal/proxy/handler.go, internal/proxy/proxy.go, internal/server/unified.go
• Maintainability Risk: High — any bug fix or enhancement to the DIFC pipeline must be applied in two places
• Refactoring Priority: High — the proxy was explicitly designed to reuse the same enforcement pipeline; extraction to a shared internal/difc/pipeline package would fulfill that intent

Next Steps

1. Review individual pattern sub-issues for detailed analysis
2. Prioritize internal/difc/pipeline extraction ([duplicate-code] Duplicate Code Pattern: 6-Phase DIFC Enforcement Pipeline #2198) as the highest-impact refactor
3. Consolidate guard initialization helpers after the pipeline extraction

Analysis Metadata

• Analyzed Files: 4 Go files (internal/proxy/handler.go, internal/proxy/proxy.go, internal/server/unified.go, internal/cmd/proxy.go)
• Detection Method: Semantic pattern analysis (phase-by-phase DIFC pipeline comparison)
• Commit: 4227da68b85c91ede6214d72902df83d5d6c7886
• Analysis Date: 2026-03-20