[duplicate-code] Duplicate Code Analysis Report

[github-actions]

🔍 Duplicate Code Analysis Report

Analysis of commit 750b010 — [test-improver] Improve tests for server/http_server (#5495)

Summary

This analysis identified 2 significant duplication patterns across the Go codebase. Both patterns exceed the reporting threshold (>10 lines of duplicated code and 3+ similar instances).

Detected Patterns

1. SecrecyLabel/IntegrityLabel Structural Duplication — Severity: Medium — See sub-issue [duplicate-code] Duplicate Code Pattern: SecrecyLabel/IntegrityLabel Structural Duplication #5518
2. Guard Policy Env Var Reading — Mixed os.Getenv vs envutil Usage — Severity: Low — See sub-issue [duplicate-code] Duplicate Code Pattern: Guard Policy Env Var Reading — Mixed os.Getenv vs envutil #5519

Overall Impact

• Total Duplicated Lines: ~30–40 lines of structural duplication in labels.go; ~10 lines of duplicated env-var reading in guard_policy_parse.go
• Affected Files: 3 files (internal/difc/labels.go, internal/config/guard_policy_parse.go, internal/cmd/flags_difc.go)
• Maintainability Risk: Medium — structural label duplication could diverge silently if a future method is added to one type but not the other
• Refactoring Priority: Low-to-Medium — neither pattern causes bugs today, but the label types are candidates for a Go generics refactor

Next Steps

1. Review individual pattern sub-issues for detailed analysis
2. Prioritize refactoring based on severity and impact
3. Create implementation plan for highest priority patterns

Analysis Metadata

• Analyzed Files: ~110 Go source files (excluding *_test.go and test/ directory)
• Detection Method: Grep/ripgrep pattern search + manual semantic analysis
• Commit: 750b010
• Analysis Date: 2026-05-12