[duplicate-code] Duplicate Code Analysis Report

[github-actions]

Analysis of commit 68537a8

Summary

Analysis of the initial commit to this repository identified 2 significant code duplication patterns in the Go source files, both located in internal/proxy/handler.go. An additional minor inconsistency was found in internal/cmd/flags_difc.go.

Detected Patterns

This analysis found 2 significant duplication patterns (threshold met: >10 lines or 3+ instances):

1. Inline JSON Response Construction in proxy/handler.go — Severity: Medium — See sub-issue [duplicate-code] Duplicate Code Pattern: Inline JSON Response Construction in proxy/handler.go #2301
2. Upstream Forwarding + Response Reading in proxy/handler.go — Severity: Low — See sub-issue [duplicate-code] Duplicate Code Pattern: Upstream Forwarding and Response Reading in proxy/handler.go #2302

Overall Impact

• Total Duplicated Lines: ~30 lines across both patterns
• Affected Files: 1 file (internal/proxy/handler.go)
• Maintainability Risk: Medium — the JSON response pattern already has a centralised helper in internal/server/http_helpers.go; the proxy package simply doesn't use it
• Refactoring Priority: Low-Medium — patterns are self-contained; refactoring would reduce bug-risk from inconsistent status codes or bodies in future edits

Next Steps

1. Review individual pattern sub-issues for detailed analysis
2. Add a writeJSONResponse helper to internal/proxy/ (or extract a shared HTTP util)
3. Extract the forwardAndReadBody helper to remove the two identical forwarding blocks

Analysis Metadata

• Analyzed Files: 87 Go source files (excluding *_test.go and test/ directory)
• Detection Method: Semantic pattern search using ripgrep and file analysis
• Commit: 68537a8
• Analysis Date: 2026-03-22