Public report of astaxie/build-web-application-with-golang, published 13 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 13 November 2026, 11:18 UTC · Survey ID cd_2bd298a9df454ee8b697edef73025710

astaxie/build-web-application-with-golang

Measured 13 November 2026, 11:18 UTC, at code version c294b08

Bus factor is not measured: No living knowledge left to concentrate.

CAI score 36out of 100 Weak
CriticalWeakAdequateStrongExemplary
Up 3 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A small codebase: 13,798 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: under 0.1 person-years · Weakest lens: Production Readiness, 18

Findings by how serious they are

2 critical 280 serious 49 minor

25 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 11:18 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

31of 31 dimensions measured by tools.
323of 331 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
31dimensions across 5 lenses, read from 13,798 lines of product code in 9 projects.
Chapters

Executive summary

astaxie/build-web-application-with-golang falls short of our standard for production because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 36 out of 100 and is rated Weak, and one of its two critical findings is a leaked password or key.

Production Readiness, at 18, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 7 points. Adding automated tests would lift Production Readiness itself, worth about 18 points. Raising Production Readiness to 70 would lift the score to about 51.

One password or key is open to anyone who can read the repository. The project has no automated tests, so a change can break it without warning. Adding automated tests and replacing the exposed password or key would close both risks.

The product code is 13,798 lines, about €12,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 18 · counts for 47%Maturity 40 · counts for 26%Security and Compliance 45 · counts for 14%Code Health 75 · counts for 8%Architecture 100 · counts for 4%

If Production Readiness rose from 18 to 70, the lowest score rated Strong, the score would rise from 36 to about 51.

Code composition: what the lines of code are
Product code 100%
Fixed since the last survey: 1 finding

This critical or serious finding was in the previous survey, on 23 October 2026, and is gone from this one.

  • Code Duplication · Duplicated block (9 lines × 5) de/code/src/apps/ch.2.5/box_example/main.go
Rebuild cost: about €12,000 · Estimate
Cost to rebuild€3,900 to €20,000, for 65 to 206 hours of work, under 0.1 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 13,798 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
Raises the score by about 7 points · Low effort · ADR Quality
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 18 points · High effort · Code Coverage
3
Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (30), build.go (5), build_new.go (2).
Raises the score by about 7 points · Medium effort · Knowledge Freshness

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €12,000 to build again, under 0.1 person-years of work. Its weakest lens is Production Readiness, at 18 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

281 modules, with 20 dependencies between them. One loop runs through 5 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 241 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 local/repository/de/code/src/apps/ch.1.22 local/repository/de/code/src/apps/ch.2.13 local/repository/de/code/src/apps/ch.2.24 local/repository/de/code/src/apps/ch.2.2/what_is_wrong_with_this5 local/repository/de/code/src/apps/ch.2.36 local/repository/de/code/src/apps/ch.2.3/basic_functions7 local/repository/de/code/src/apps/ch.2.3/hidden_print_methods8 local/repository/de/code/src/apps/ch.2.3/import_packages9 local/repository/de/code/src/apps/ch.2.3/import_packages/only_call_init10 local/repository/de/code/src/apps/ch.2.3/panic_and_recover11 local/repository/de/code/src/apps/ch.2.3/pass_by_value_and_pointer12 local/repository/de/code/src/apps/ch.2.3/type_function13 local/repository/de/code/src/apps/ch.2.3/variadic_functions14 local/repository/de/code/src/apps/ch.2.415 local/repository/de/code/src/apps/ch.2.4/compare_age16 local/repository/de/code/src/apps/ch.2.4/embedded_structs17 local/repository/de/code/src/apps/ch.2.4/embedded_structs218 local/repository/de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict19 local/repository/de/code/src/apps/ch.2.5/attach_methods_to_struct20 local/repository/de/code/src/apps/ch.2.5/box_example21 local/repository/de/code/src/apps/ch.2.5/embedded_method22 local/repository/de/code/src/apps/ch.2.5/method_overload23 local/repository/de/code/src/apps/ch.2.5/pass_struct_to_method24 local/repository/de/code/src/apps/ch.2.6/reflection25 local/repository/de/code/src/apps/ch.2.6/stringer_interface26 local/repository/de/code/src/apps/ch.2.6/switch_type_check27 local/repository/de/code/src/apps/ch.2.6/type_check28 local/repository/de/code/src/apps/ch.2.7/buffered_channel29 local/repository/de/code/src/apps/ch.2.7/goroutine30 local/repository/de/code/src/apps/ch.2.7/range_and_close_channel31 local/repository/de/code/src/apps/ch.2.7/select_channel32 local/repository/de/code/src/apps/ch.2.7/timeout33 local/repository/de/code/src/apps/ch.2.7/unbuffered_channel34 local/repository/de/code/src/apps/ch.3.235 local/repository/de/code/src/apps/ch.3.436 local/repository/th/code/src/apps/ch.2.6/interface37 local/repository/pt-br/code/src/apps/ch.2.6/interface38 local/repository/fa/code/src/apps/ch.2.6/interface39 local/repository/en/code/src/apps/ch.2.6/interface40 local/repository/de/code/src/apps/ch.2.6/interface
1 local/repository/de/code/src/apps/ch.1.2
2 local/repository/de/code/src/apps/ch.2.1
3 local/repository/de/code/src/apps/ch.2.2
4 local/repository/de/code/src/apps/ch.2.2/what_is_wrong_with_this
5 local/repository/de/code/src/apps/ch.2.3
6 local/repository/de/code/src/apps/ch.2.3/basic_functions
7 local/repository/de/code/src/apps/ch.2.3/hidden_print_methods
8 local/repository/de/code/src/apps/ch.2.3/import_packages
9 local/repository/de/code/src/apps/ch.2.3/import_packages/only_call_init
10 local/repository/de/code/src/apps/ch.2.3/panic_and_recover
11 local/repository/de/code/src/apps/ch.2.3/pass_by_value_and_pointer
12 local/repository/de/code/src/apps/ch.2.3/type_function
13 local/repository/de/code/src/apps/ch.2.3/variadic_functions
14 local/repository/de/code/src/apps/ch.2.4
15 local/repository/de/code/src/apps/ch.2.4/compare_age
16 local/repository/de/code/src/apps/ch.2.4/embedded_structs
17 local/repository/de/code/src/apps/ch.2.4/embedded_structs2
18 local/repository/de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict
19 local/repository/de/code/src/apps/ch.2.5/attach_methods_to_struct
20 local/repository/de/code/src/apps/ch.2.5/box_example
21 local/repository/de/code/src/apps/ch.2.5/embedded_method
22 local/repository/de/code/src/apps/ch.2.5/method_overload
23 local/repository/de/code/src/apps/ch.2.5/pass_struct_to_method
24 local/repository/de/code/src/apps/ch.2.6/reflection
25 local/repository/de/code/src/apps/ch.2.6/stringer_interface
26 local/repository/de/code/src/apps/ch.2.6/switch_type_check
27 local/repository/de/code/src/apps/ch.2.6/type_check
28 local/repository/de/code/src/apps/ch.2.7/buffered_channel
29 local/repository/de/code/src/apps/ch.2.7/goroutine
30 local/repository/de/code/src/apps/ch.2.7/range_and_close_channel
31 local/repository/de/code/src/apps/ch.2.7/select_channel
32 local/repository/de/code/src/apps/ch.2.7/timeout
33 local/repository/de/code/src/apps/ch.2.7/unbuffered_channel
34 local/repository/de/code/src/apps/ch.3.2
35 local/repository/de/code/src/apps/ch.3.4
36 local/repository/th/code/src/apps/ch.2.6/interface3333
37 local/repository/pt-br/code/src/apps/ch.2.6/interface3333
38 local/repository/fa/code/src/apps/ch.2.6/interface3333
39 local/repository/en/code/src/apps/ch.2.6/interface3333
40 local/repository/de/code/src/apps/ch.2.6/interface3333
Uses a module listed above itPart of a loopThe module itself
1 local/repository/de/code/src/apps/ch.1.22 local/repository/de/code/src/apps/ch.2.13 local/repository/de/code/src/apps/ch.2.24 local/repository/de/code/src/apps/ch.2.2/what_is_wrong_with_this5 local/repository/de/code/src/apps/ch.2.36 local/repository/de/code/src/apps/ch.2.3/basic_functions7 local/repository/de/code/src/apps/ch.2.3/hidden_print_methods8 local/repository/de/code/src/apps/ch.2.3/import_packages9 local/repository/de/code/src/apps/ch.2.3/import_packages/only_call_init10 local/repository/de/code/src/apps/ch.2.3/panic_and_recover11 local/repository/de/code/src/apps/ch.2.3/pass_by_value_and_pointer12 local/repository/de/code/src/apps/ch.2.3/type_function13 local/repository/de/code/src/apps/ch.2.3/variadic_functions14 local/repository/de/code/src/apps/ch.2.415 local/repository/de/code/src/apps/ch.2.4/compare_age16 local/repository/de/code/src/apps/ch.2.4/embedded_structs17 local/repository/de/code/src/apps/ch.2.4/embedded_structs218 local/repository/de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict19 local/repository/de/code/src/apps/ch.2.5/attach_methods_to_struct20 local/repository/de/code/src/apps/ch.2.5/box_example21 local/repository/de/code/src/apps/ch.2.5/embedded_method22 local/repository/de/code/src/apps/ch.2.5/method_overload23 local/repository/de/code/src/apps/ch.2.5/pass_struct_to_method24 local/repository/de/code/src/apps/ch.2.6/reflection25 local/repository/de/code/src/apps/ch.2.6/stringer_interface26 local/repository/de/code/src/apps/ch.2.6/switch_type_check27 local/repository/de/code/src/apps/ch.2.6/type_check28 local/repository/de/code/src/apps/ch.2.7/buffered_channel29 local/repository/de/code/src/apps/ch.2.7/goroutine30 local/repository/de/code/src/apps/ch.2.7/range_and_close_channel31 local/repository/de/code/src/apps/ch.2.7/select_channel32 local/repository/de/code/src/apps/ch.2.7/timeout33 local/repository/de/code/src/apps/ch.2.7/unbuffered_channel34 local/repository/de/code/src/apps/ch.3.235 local/repository/de/code/src/apps/ch.3.436 local/repository/th/code/src/apps/ch.2.6/interface37 local/repository/pt-br/code/src/apps/ch.2.6/interface38 local/repository/fa/code/src/apps/ch.2.6/interface39 local/repository/en/code/src/apps/ch.2.6/interface40 local/repository/de/code/src/apps/ch.2.6/interfacelocal/repository/de/code/src/apps/ch.1.21local/repository/de/code/src/apps/ch.2.12local/repository/de/code/src/apps/ch.2.23local/repository/de/code/src/apps/ch.2.2/what_is_wrong_with_this4local/repository/de/code/src/apps/ch.2.35local/repository/de/code/src/apps/ch.2.3/basic_functions6local/repository/de/code/src/apps/ch.2.3/hidden_print_methods7local/repository/de/code/src/apps/ch.2.3/import_packages8local/repository/de/code/src/apps/ch.2.3/import_packages/only_call_init9local/repository/de/code/src/apps/ch.2.3/panic_and_recover10local/repository/de/code/src/apps/ch.2.3/pass_by_value_and_pointer11local/repository/de/code/src/apps/ch.2.3/type_function12local/repository/de/code/src/apps/ch.2.3/variadic_functions13local/repository/de/code/src/apps/ch.2.414local/repository/de/code/src/apps/ch.2.4/compare_age15local/repository/de/code/src/apps/ch.2.4/embedded_structs16local/repository/de/code/src/apps/ch.2.4/embedded_structs217local/repository/de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict18local/repository/de/code/src/apps/ch.2.5/attach_methods_to_struct19local/repository/de/code/src/apps/ch.2.5/box_example20local/repository/de/code/src/apps/ch.2.5/embedded_method21local/repository/de/code/src/apps/ch.2.5/method_overload22local/repository/de/code/src/apps/ch.2.5/pass_struct_to_method23local/repository/de/code/src/apps/ch.2.6/reflection24local/repository/de/code/src/apps/ch.2.6/stringer_interface25local/repository/de/code/src/apps/ch.2.6/switch_type_check26local/repository/de/code/src/apps/ch.2.6/type_check27local/repository/de/code/src/apps/ch.2.7/buffered_channel28local/repository/de/code/src/apps/ch.2.7/goroutine29local/repository/de/code/src/apps/ch.2.7/range_and_close_channel30local/repository/de/code/src/apps/ch.2.7/select_channel31local/repository/de/code/src/apps/ch.2.7/timeout32local/repository/de/code/src/apps/ch.2.7/unbuffered_channel33local/repository/de/code/src/apps/ch.3.234local/repository/de/code/src/apps/ch.3.435local/repository/th/code/src/apps/ch.2.6/interface36local/repository/pt-br/code/src/apps/ch.2.6/interface37local/repository/fa/code/src/apps/ch.2.6/interface38local/repository/en/code/src/apps/ch.2.6/interface39local/repository/de/code/src/apps/ch.2.6/interface4033333333333333333333+241 more modules (most-connected shown)

At a glance — Code Health · 75% · Strong ·

At a glance — Architecture · 100% · Exemplary ·

At a glance — Maturity · 40% · Weak · gated by D34, M2 ·

At a glance — Readiness · 18% · Critical · gated by D8, P1, P3, P7 ·

At a glance — Security · 45% · Checked 2 of 9 · gated by D29 ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection97Medium
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (30), build.go (5), build_new.go (2).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.+7.5 ptsLowADR Quality
Resolve the 1 No automated tests finding(s) in Code Coverage.+18.2 ptsHighCode Coverage
Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (30), build.go (5), build_new.go (2).+6.6 ptsMediumKnowledge Freshness
Add a CI workflow that builds and runs the test suite on every push/PR.+6.2 ptsMediumCI/CD gates
Run what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+6.2 ptsMediumSecurity & performance tooling
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+4.0 ptsMediumArchitecture documentation
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.+3.8 ptsMediumOutbound HTTP resilience
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED.+1.4 ptsLowSecrets (history)

File quality

Per-file score 0–10 — a quality signature. Of 101 files carrying findings, judged against the Production bar: 0% slop · 71% mixed · 29% near-clean.

FileScoreBandWorst signal
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 2

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 280

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 49

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 25

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 31 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 31 dimensions across the health lenses
D1D2D3D4D5D6D8D13D15D17D20D27D28D29D34D35AX10AX2AX3AX4M1M2M3M4P1P2P3P7X2X26X3

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 323 of 331 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1d4a1-4b6c-7ebb-9742-b89cbd6321a3.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
  • D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Every one of the 39 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (13744 LoC, 506 module-visible types across 281 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P5 DR & Backup — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found. Whether there is anything here to recover could NOT be determined: persistence is detected from deployment/container manifests and from dependency manifests, and neither was readable by this pass, so a data store this code opens directly — a file, an embedded database — would not be visible to it. The blindness is this analyzer's, not a finding that the repository holds no data. You can widen what we reach: keep the deployment/container manifest or a dependency manifest in this repository — or a link to the ops repo that holds the DR evidence — so the persistence probe has something to read.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 function(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity8.7 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Prevented

15 function(s) exceeded the cognitive complexity threshold of 15; the worst was ProfilePage.GetErrors at 16.

ProfilePage.GetErrors (cognitive 16) · ×15de/code/src/apps/ch.4.2/validator/main.go:23

What to do

  1. Bring the 15 bodies over 15 down to 15 or less in Cognitive Complexity — start with ProfilePage.GetErrors (cognitive 16), ProfilePage.GetErrors (cognitive 16), ProfilePage.GetErrors (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 over-large unit(s) detected — types, modules or files that carry too much.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication6.6 / 10Adequate✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Verified

106 duplicated block group(s) detected. A further 46 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 4 of the 152 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Members sharing a duplicated core (5 members, 50+ identical tokens) · ×39de/code/src/apps/ch.2.2/main.go:29
Duplicated block (7 lines × 5) · ×10de/code/src/apps/ch.2.3/type_function/main.go:38
Duplicated block (11 lines × 5) · ×6de/code/src/apps/ch.2.3/basic_functions/main.go:16
Duplicated block (9 lines × 5) · ×6de/code/src/apps/ch.2.7/unbuffered_channel/main.go:16
Duplicated block (20 lines × 5) · ×5de/code/src/apps/ch.2.2/main.go:59

+ 50 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 39 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with REDACTED (39). — One of this dimension's main actionable groups (39 warning-level).
  2. Resolve the 10 Duplicated block (7 lines × 5) finding(s) in Code Duplication — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).
  3. Resolve the 6 Duplicated block (11 lines × 5) finding(s) in Code Duplication — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

9 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 10 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

1 deducted task-comment markers across 13798 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoCommentpt-br/code/src/apps/ch.2.2/main.go:144

What to do

  1. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundREDACTED:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability9.9 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

0 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)0.1 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.1 / 10 · rule-coverage 100% · ceiling Documented

97 finding(s): 0 critical, 0 high, 97 medium, 0 low. semgrep hit a parse error in 7 file(s) — `en/build.sh` (line 32, line 37, line 42, …), `ja/build.sh` (line 32, line 37, line 42, …), `th/build.sh` (line 32, line 37, line 42, …), `zh-tw/build.sh` (line 33, line 38, line 43, …), `zh-tw/build_new.sh` (line 38, line 43, line 45, …), … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 35 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (35). — One of this dimension's main actionable groups (35 warning-level).
  2. Resolve the 35 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (35). — One of this dimension's main actionable groups (35 warning-level).
  3. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

39 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pt-br/code/src/apps/ch.2.2/main.go. Counted over 39 of the 291 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×39pt-br/code/src/apps/ch.2.2/main.go:1
Dormant codebase

What to do

  1. Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (30), build.go (5), build_new.go (2). — One of this dimension's main actionable groups (39 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

M1 · Documentation (README)4.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

  • The root README is 98 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

What to do

  • Add a health-check endpoint (a /healthz handler) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×5) — de/code/src/apps/ch.4.5/client_upload/main.go:32, en/code/src/apps/ch.4.5/client_upload/main.go:32, fa/code/src/apps/ch.4.5/client_upload/main.go:32, …
  • `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — zh-tw/build_new.go:70, zh/build_new.go:70

What to do

  • Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/7 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `md2html` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. (×2) — zh-tw/build_new.go:20, zh/build_new.go:20
  • `postFile` calls `http.Post(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. (×5) — th/code/src/apps/ch.4.5/client_upload/main.go:18, pt-br/code/src/apps/ch.4.5/client_upload/main.go:18, fa/code/src/apps/ch.4.5/client_upload/main.go:18, …

What to do

  • Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health75%StrongSolid.
Architecture100%ExemplaryStrongest area.
Maturity40%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness18%Critical — gated by D8, P1, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security45%Checked 2 of 9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 6 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 77 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
  • D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — no CI workflow found
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — X12 reached only 0% of this repository's production lines — go (13,744 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 2 finding(s)
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (Go's `testing` package (`go test ./...`)), and run it in CI so the gap cannot reopen.
Serious — 280 finding(s)
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×39
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:29 — de/code/src/apps/ch.2.2/main.go:29-48 | en/code/src/apps/ch.2.2/main.go:29-48 | fa/code/src/apps/ch.2.2/main.go:29-48 | pt-br/code/src/apps/ch.2.2/main.go:29-48 | th/code/src/apps/ch.2.2/main.go:29-48 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:58 — de/code/src/apps/ch.2.2/main.go:58-78 | en/code/src/apps/ch.2.2/main.go:58-78 | fa/code/src/apps/ch.2.2/main.go:58-78 | pt-br/code/src/apps/ch.2.2/main.go:58-78 | th/code/src/apps/ch.2.2/main.go:58-78 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:93 — de/code/src/apps/ch.2.2/main.go:93-114 | en/code/src/apps/ch.2.2/main.go:93-114 | fa/code/src/apps/ch.2.2/main.go:93-114 | pt-br/code/src/apps/ch.2.2/main.go:93-114 | th/code/src/apps/ch.2.2/main.go:93-114 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:122 — de/code/src/apps/ch.2.2/main.go:122-141 | en/code/src/apps/ch.2.2/main.go:122-141 | fa/code/src/apps/ch.2.2/main.go:122-141 | pt-br/code/src/apps/ch.2.2/main.go:122-141 | th/code/src/apps/ch.2.2/main.go:122-141 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:164 — de/code/src/apps/ch.2.2/main.go:164-195 | en/code/src/apps/ch.2.2/main.go:164-195 | fa/code/src/apps/ch.2.2/main.go:164-195 | pt-br/code/src/apps/ch.2.2/main.go:164-195 | th/code/src/apps/ch.2.2/main.go:164-195 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:196 — de/code/src/apps/ch.2.2/main.go:196-236 | en/code/src/apps/ch.2.2/main.go:196-236 | fa/code/src/apps/ch.2.2/main.go:196-236 | pt-br/code/src/apps/ch.2.2/main.go:196-236 | th/code/src/apps/ch.2.2/main.go:196-236 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.2/main.go:237 — de/code/src/apps/ch.2.2/main.go:237-264 | en/code/src/apps/ch.2.2/main.go:237-264 | fa/code/src/apps/ch.2.2/main.go:237-264 | pt-br/code/src/apps/ch.2.2/main.go:237-264 | th/code/src/apps/ch.2.2/main.go:237-264 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.3/basic_functions/main.go:15 — de/code/src/apps/ch.2.3/basic_functions/main.go:15-26 | en/code/src/apps/ch.2.3/basic_functions/main.go:15-26 | fa/code/src/apps/ch.2.3/basic_functions/main.go:15-26 | pt-br/code/src/apps/ch.2.3/basic_functions/main.go:15-26 | th/code/src/apps/ch.2.3/basic_functions/main.go:15-26 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.3/main.go:10 — de/code/src/apps/ch.2.3/main.go:10-30 | en/code/src/apps/ch.2.3/main.go:10-30 | fa/code/src/apps/ch.2.3/main.go:10-30 | pt-br/code/src/apps/ch.2.3/main.go:10-30 | th/code/src/apps/ch.2.3/main.go:10-30 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.3/main.go:54 — de/code/src/apps/ch.2.3/main.go:54-77 | en/code/src/apps/ch.2.3/main.go:54-77 | fa/code/src/apps/ch.2.3/main.go:54-77 | pt-br/code/src/apps/ch.2.3/main.go:54-77 | th/code/src/apps/ch.2.3/main.go:54-77 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.3/main.go:78 — de/code/src/apps/ch.2.3/main.go:78-90 | en/code/src/apps/ch.2.3/main.go:78-90 | fa/code/src/apps/ch.2.3/main.go:78-90 | pt-br/code/src/apps/ch.2.3/main.go:78-90 | th/code/src/apps/ch.2.3/main.go:78-90 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.3/main.go:91 — de/code/src/apps/ch.2.3/main.go:91-126 | en/code/src/apps/ch.2.3/main.go:91-126 | fa/code/src/apps/ch.2.3/main.go:91-126 | pt-br/code/src/apps/ch.2.3/main.go:91-126 | th/code/src/apps/ch.2.3/main.go:91-126 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.3/type_function/main.go:37 — de/code/src/apps/ch.2.3/type_function/main.go:37-44 | en/code/src/apps/ch.2.3/type_function/main.go:37-44 | fa/code/src/apps/ch.2.3/type_function/main.go:37-44 | pt-br/code/src/apps/ch.2.3/type_function/main.go:37-44 | th/code/src/apps/ch.2.3/type_function/main.go:37-44 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.4/compare_age/main.go:22 — de/code/src/apps/ch.2.4/compare_age/main.go:22-43 | en/code/src/apps/ch.2.4/compare_age/main.go:22-43 | fa/code/src/apps/ch.2.4/compare_age/main.go:22-43 | pt-br/code/src/apps/ch.2.4/compare_age/main.go:22-43 | th/code/src/apps/ch.2.4/compare_age/main.go:22-43 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.4/embedded_structs/main.go:18 — de/code/src/apps/ch.2.4/embedded_structs/main.go:18-39 | en/code/src/apps/ch.2.4/embedded_structs/main.go:18-39 | fa/code/src/apps/ch.2.4/embedded_structs/main.go:18-39 | pt-br/code/src/apps/ch.2.4/embedded_structs/main.go:18-39 | th/code/src/apps/ch.2.4/embedded_structs/main.go:18-39 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.4/embedded_structs2/main.go:22 — de/code/src/apps/ch.2.4/embedded_structs2/main.go:22-39 | en/code/src/apps/ch.2.4/embedded_structs2/main.go:22-39 | fa/code/src/apps/ch.2.4/embedded_structs2/main.go:22-39 | pt-br/code/src/apps/ch.2.4/embedded_structs2/main.go:22-39 | th/code/src/apps/ch.2.4/embedded_structs2/main.go:22-39 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.4/main.go:7 — de/code/src/apps/ch.2.4/main.go:7-26 | en/code/src/apps/ch.2.4/main.go:7-26 | fa/code/src/apps/ch.2.4/main.go:7-26 | pt-br/code/src/apps/ch.2.4/main.go:7-26 | th/code/src/apps/ch.2.4/main.go:7-26 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:26 — de/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:26-36 | en/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:26-36 | fa/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:26-36 | pt-br/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:26-36 | th/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:26-36 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.6/interface/main.go:41 — de/code/src/apps/ch.2.6/interface/main.go:41-71 | en/code/src/apps/ch.2.6/interface/main.go:41-71 | fa/code/src/apps/ch.2.6/interface/main.go:41-71 | pt-br/code/src/apps/ch.2.6/interface/main.go:41-71 | th/code/src/apps/ch.2.6/interface/main.go:41-71 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.6/reflection/main.go:16 — de/code/src/apps/ch.2.6/reflection/main.go:16-29 | en/code/src/apps/ch.2.6/reflection/main.go:16-29 | fa/code/src/apps/ch.2.6/reflection/main.go:16-29 | pt-br/code/src/apps/ch.2.6/reflection/main.go:16-29 | th/code/src/apps/ch.2.6/reflection/main.go:16-29 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.6/switch_type_check/main.go:20 — de/code/src/apps/ch.2.6/switch_type_check/main.go:20-38 | en/code/src/apps/ch.2.6/switch_type_check/main.go:20-38 | fa/code/src/apps/ch.2.6/switch_type_check/main.go:20-38 | pt-br/code/src/apps/ch.2.6/switch_type_check/main.go:20-38 | th/code/src/apps/ch.2.6/switch_type_check/main.go:20-38 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.6/type_check/main.go:20 — de/code/src/apps/ch.2.6/type_check/main.go:20-37 | en/code/src/apps/ch.2.6/type_check/main.go:20-37 | fa/code/src/apps/ch.2.6/type_check/main.go:20-37 | pt-br/code/src/apps/ch.2.6/type_check/main.go:20-37 | th/code/src/apps/ch.2.6/type_check/main.go:20-37 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.7/timeout/main.go:11 — de/code/src/apps/ch.2.7/timeout/main.go:11-27 | en/code/src/apps/ch.2.7/timeout/main.go:11-27 | fa/code/src/apps/ch.2.7/timeout/main.go:11-27 | pt-br/code/src/apps/ch.2.7/timeout/main.go:11-27 | th/code/src/apps/ch.2.7/timeout/main.go:11-27 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) de/code/src/apps/ch.2.7/unbuffered_channel/main.go:15 — de/code/src/apps/ch.2.7/unbuffered_channel/main.go:15-24 | en/code/src/apps/ch.2.7/unbuffered_channel/main.go:15-24 | fa/code/src/apps/ch.2.7/unbuffered_channel/main.go:15-24 | pt-br/code/src/apps/ch.2.7/unbuffered_channel/main.go:15-24 | th/code/src/apps/ch.2.7/unbuffered_channel/main.go:15-24 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) REDACTED:28 — REDACTED:28-39 | REDACTED:28-39 | REDACTED:28-39 | REDACTED:28-39 | REDACTED:28-39 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • + 14 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 10 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 10 more in this group — see findings.md.
D2 · Cognitive Complexity · ProfilePage.GetErrors (cognitive 16) · ×15
  • ProfilePage.GetErrors (cognitive 16) de/code/src/apps/ch.4.2/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) de/code/src/apps/ch.4.4/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) de/code/src/apps/ch.4.5/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) en/code/src/apps/ch.4.2/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) en/code/src/apps/ch.4.4/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) en/code/src/apps/ch.4.5/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) fa/code/src/apps/ch.4.2/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) fa/code/src/apps/ch.4.4/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) fa/code/src/apps/ch.4.5/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) pt-br/code/src/apps/ch.4.2/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) pt-br/code/src/apps/ch.4.4/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) pt-br/code/src/apps/ch.4.5/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) th/code/src/apps/ch.4.2/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) th/code/src/apps/ch.4.4/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ProfilePage.GetErrors (cognitive 16) th/code/src/apps/ch.4.5/validator/main.go:23 — ProfilePage.GetErrors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×10
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.2.3/type_function/main.go:38 — de/code/src/apps/ch.2.3/type_function/main.go:38-44 | en/code/src/apps/ch.2.3/type_function/main.go:38-44 | fa/code/src/apps/ch.2.3/type_function/main.go:38-44 | pt-br/code/src/apps/ch.2.3/type_function/main.go:38-44 | th/code/src/apps/ch.2.3/type_function/main.go:38-44 — before extracting anything, compare `de/code/src/apps/ch.2.3/type_function/main.go` and `en/code/src/apps/ch.2.3/type_function/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 5) REDACTED:43 — REDACTED:43-49 | REDACTED:43-49 | REDACTED:43-49 | REDACTED:43-49 | REDACTED:43-49 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.2.3/import_packages/main.go:20 — de/code/src/apps/ch.2.3/import_packages/main.go:20-26 | en/code/src/apps/ch.2.3/import_packages/main.go:20-26 | fa/code/src/apps/ch.2.3/import_packages/main.go:20-26 | pt-br/code/src/apps/ch.2.3/import_packages/main.go:19-25 | th/code/src/apps/ch.2.3/import_packages/main.go:20-26 — before extracting anything, compare `de/code/src/apps/ch.2.3/import_packages/main.go` and `en/code/src/apps/ch.2.3/import_packages/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.2.3/main.go:127 — de/code/src/apps/ch.2.3/main.go:127-133 | en/code/src/apps/ch.2.3/main.go:127-133 | fa/code/src/apps/ch.2.3/main.go:127-133 | pt-br/code/src/apps/ch.2.3/main.go:127-133 | th/code/src/apps/ch.2.3/main.go:127-133 — before extracting anything, compare `de/code/src/apps/ch.2.3/main.go` and `en/code/src/apps/ch.2.3/main.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.2.7/buffered_channel/main.go:7 — de/code/src/apps/ch.2.7/buffered_channel/main.go:7-13 | en/code/src/apps/ch.2.7/buffered_channel/main.go:7-13 | fa/code/src/apps/ch.2.7/buffered_channel/main.go:7-13 | pt-br/code/src/apps/ch.2.7/buffered_channel/main.go:7-13 | th/code/src/apps/ch.2.7/buffered_channel/main.go:7-13 — before extracting anything, compare `de/code/src/apps/ch.2.7/buffered_channel/main.go` and `en/code/src/apps/ch.2.7/buffered_channel/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 5) REDACTED:25 — REDACTED:25-31 | REDACTED:25-31 | REDACTED:25-31 | REDACTED:25-31 | REDACTED:25-31 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.5.5/main.go:101 — de/code/src/apps/ch.5.5/main.go:101-107 | en/code/src/apps/ch.5.5/main.go:101-107 | fa/code/src/apps/ch.5.5/main.go:101-107 | pt-br/code/src/apps/ch.5.5/main.go:101-107 | th/code/src/apps/ch.5.5/main.go:101-107 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.5.5/main.go:109 — de/code/src/apps/ch.5.5/main.go:109-115 | en/code/src/apps/ch.5.5/main.go:109-115 | fa/code/src/apps/ch.5.5/main.go:109-115 | pt-br/code/src/apps/ch.5.5/main.go:109-115 | th/code/src/apps/ch.5.5/main.go:109-115 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.5.5/main.go:117 — de/code/src/apps/ch.5.5/main.go:117-123 | en/code/src/apps/ch.5.5/main.go:117-123 | fa/code/src/apps/ch.5.5/main.go:117-123 | pt-br/code/src/apps/ch.5.5/main.go:117-123 | th/code/src/apps/ch.5.5/main.go:117-123 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 5) de/code/src/apps/ch.5.5/main.go:125 — de/code/src/apps/ch.5.5/main.go:125-131 | en/code/src/apps/ch.5.5/main.go:125-131 | fa/code/src/apps/ch.5.5/main.go:125-131 | pt-br/code/src/apps/ch.5.5/main.go:125-131 | th/code/src/apps/ch.5.5/main.go:125-131 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×7
  • Outbound HTTP without resilience de/code/src/apps/ch.4.5/client_upload/main.go:32 — `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience en/code/src/apps/ch.4.5/client_upload/main.go:32 — `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience fa/code/src/apps/ch.4.5/client_upload/main.go:32 — `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience pt-br/code/src/apps/ch.4.5/client_upload/main.go:32 — `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience th/code/src/apps/ch.4.5/client_upload/main.go:32 — `http.Post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience zh-tw/build_new.go:70 — `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience zh/build_new.go:70 — `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
X2 · Cancellation propagation · Function without context.Context · ×7
  • Function without context.Context: md2html zh-tw/build_new.go:20 — `md2html` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
  • Function without context.Context: md2html zh/build_new.go:20 — `md2html` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
  • Function without context.Context: postFile th/code/src/apps/ch.4.5/client_upload/main.go:18 — `postFile` calls `http.Post(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
  • Function without context.Context: postFile pt-br/code/src/apps/ch.4.5/client_upload/main.go:18 — `postFile` calls `http.Post(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
  • Function without context.Context: postFile fa/code/src/apps/ch.4.5/client_upload/main.go:18 — `postFile` calls `http.Post(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
  • Function without context.Context: postFile en/code/src/apps/ch.4.5/client_upload/main.go:18 — `postFile` calls `http.Post(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
  • Function without context.Context: postFile de/code/src/apps/ch.4.5/client_upload/main.go:18 — `postFile` calls `http.Post(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×6
  • Duplicated block (11 lines × 5) de/code/src/apps/ch.2.3/basic_functions/main.go:16 — de/code/src/apps/ch.2.3/basic_functions/main.go:16-26 | en/code/src/apps/ch.2.3/basic_functions/main.go:16-26 | fa/code/src/apps/ch.2.3/basic_functions/main.go:16-26 | pt-br/code/src/apps/ch.2.3/basic_functions/main.go:16-26 | th/code/src/apps/ch.2.3/basic_functions/main.go:16-26 — before extracting anything, compare `de/code/src/apps/ch.2.3/basic_functions/main.go` and `en/code/src/apps/ch.2.3/basic_functions/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 5) REDACTED:29 — REDACTED:29-39 | REDACTED:29-39 | REDACTED:29-39 | REDACTED:29-39 | REDACTED:29-39 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 5) REDACTED:24 — REDACTED:24-34 | REDACTED:24-34 | REDACTED:24-34 | REDACTED:24-34 | REDACTED:24-34 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 5) REDACTED:30 — REDACTED:30-40 | REDACTED:30-40 | REDACTED:30-40 | REDACTED:30-40 | REDACTED:30-40 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 5) de/code/src/apps/ch.2.7/goroutine/main.go:10 — de/code/src/apps/ch.2.7/goroutine/main.go:10-20 | en/code/src/apps/ch.2.7/goroutine/main.go:10-20 | fa/code/src/apps/ch.2.7/goroutine/main.go:10-20 | pt-br/code/src/apps/ch.2.7/goroutine/main.go:10-20 | th/code/src/apps/ch.2.7/goroutine/main.go:10-20 — before extracting anything, compare `de/code/src/apps/ch.2.7/goroutine/main.go` and `en/code/src/apps/ch.2.7/goroutine/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 5) de/code/src/apps/ch.2.5/box_example/main.go:30 — de/code/src/apps/ch.2.5/box_example/main.go:30-40 | en/code/src/apps/ch.2.5/box_example/main.go:30-40 | fa/code/src/apps/ch.2.5/box_example/main.go:30-40 | pt-br/code/src/apps/ch.2.5/box_example/main.go:30-40 | th/code/src/apps/ch.2.5/box_example/main.go:30-40 — before extracting anything, compare `de/code/src/apps/ch.2.5/box_example/main.go` and `en/code/src/apps/ch.2.5/box_example/main.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×6
  • Duplicated block (9 lines × 5) de/code/src/apps/ch.2.7/unbuffered_channel/main.go:16 — de/code/src/apps/ch.2.7/unbuffered_channel/main.go:16-24 | en/code/src/apps/ch.2.7/unbuffered_channel/main.go:16-24 | fa/code/src/apps/ch.2.7/unbuffered_channel/main.go:16-24 | pt-br/code/src/apps/ch.2.7/unbuffered_channel/main.go:16-24 | th/code/src/apps/ch.2.7/unbuffered_channel/main.go:16-24 — before extracting anything, compare `de/code/src/apps/ch.2.7/unbuffered_channel/main.go` and `en/code/src/apps/ch.2.7/unbuffered_channel/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 5) REDACTED:14 — REDACTED:14-22 | REDACTED:14-22 | REDACTED:14-22 | REDACTED:14-22 | REDACTED:14-22 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 5) REDACTED:45 — REDACTED:45-53 | REDACTED:45-53 | REDACTED:45-53 | REDACTED:45-53 | REDACTED:45-53 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 5) de/code/src/apps/ch.2.2/main.go:49 — de/code/src/apps/ch.2.2/main.go:49-57 | en/code/src/apps/ch.2.2/main.go:49-57 | fa/code/src/apps/ch.2.2/main.go:49-57 | pt-br/code/src/apps/ch.2.2/main.go:49-57 | th/code/src/apps/ch.2.2/main.go:49-57 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 5) de/code/src/apps/ch.2.3/type_function/main.go:25 — de/code/src/apps/ch.2.3/type_function/main.go:25-33 | en/code/src/apps/ch.2.3/type_function/main.go:25-33 | fa/code/src/apps/ch.2.3/type_function/main.go:25-33 | pt-br/code/src/apps/ch.2.3/type_function/main.go:25-33 | th/code/src/apps/ch.2.3/type_function/main.go:25-33 — before extracting anything, compare `de/code/src/apps/ch.2.3/type_function/main.go` and `en/code/src/apps/ch.2.3/type_function/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 5) de/code/src/apps/ch.5.5/main.go:91 — de/code/src/apps/ch.5.5/main.go:91-99 | en/code/src/apps/ch.5.5/main.go:91-99 | fa/code/src/apps/ch.5.5/main.go:91-99 | pt-br/code/src/apps/ch.5.5/main.go:91-99 | th/code/src/apps/ch.5.5/main.go:91-99 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 5) · ×5
  • Duplicated block (20 lines × 5) de/code/src/apps/ch.2.2/main.go:59 — de/code/src/apps/ch.2.2/main.go:59-78 | en/code/src/apps/ch.2.2/main.go:59-78 | fa/code/src/apps/ch.2.2/main.go:59-78 | pt-br/code/src/apps/ch.2.2/main.go:59-78 | th/code/src/apps/ch.2.2/main.go:59-78 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 5) de/code/src/apps/ch.2.3/main.go:11 — de/code/src/apps/ch.2.3/main.go:11-30 | en/code/src/apps/ch.2.3/main.go:11-30 | fa/code/src/apps/ch.2.3/main.go:11-30 | pt-br/code/src/apps/ch.2.3/main.go:11-30 | th/code/src/apps/ch.2.3/main.go:11-30 — before extracting anything, compare `de/code/src/apps/ch.2.3/main.go` and `en/code/src/apps/ch.2.3/main.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 5) de/code/src/apps/ch.2.4/embedded_structs/main.go:20 — de/code/src/apps/ch.2.4/embedded_structs/main.go:20-39 | en/code/src/apps/ch.2.4/embedded_structs/main.go:20-39 | fa/code/src/apps/ch.2.4/embedded_structs/main.go:20-39 | pt-br/code/src/apps/ch.2.4/embedded_structs/main.go:20-39 | th/code/src/apps/ch.2.4/embedded_structs/main.go:20-39 — before extracting anything, compare `de/code/src/apps/ch.2.4/embedded_structs/main.go` and `en/code/src/apps/ch.2.4/embedded_structs/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 5) REDACTED:11 — REDACTED:11-30 | REDACTED:11-30 | REDACTED:11-30 | REDACTED:11-30 | REDACTED:11-30 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (20 lines × 5) de/code/src/apps/ch.2.5/box_example/main.go:54 — de/code/src/apps/ch.2.5/box_example/main.go:54-73 | en/code/src/apps/ch.2.5/box_example/main.go:54-73 | fa/code/src/apps/ch.2.5/box_example/main.go:54-73 | pt-br/code/src/apps/ch.2.5/box_example/main.go:54-73 | th/code/src/apps/ch.2.5/box_example/main.go:54-73 — before extracting anything, compare `de/code/src/apps/ch.2.5/box_example/main.go` and `en/code/src/apps/ch.2.5/box_example/main.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×5
  • Duplicated block (16 lines × 5) de/code/src/apps/ch.2.4/embedded_structs2/main.go:24 — de/code/src/apps/ch.2.4/embedded_structs2/main.go:24-39 | en/code/src/apps/ch.2.4/embedded_structs2/main.go:24-39 | fa/code/src/apps/ch.2.4/embedded_structs2/main.go:24-39 | pt-br/code/src/apps/ch.2.4/embedded_structs2/main.go:24-39 | th/code/src/apps/ch.2.4/embedded_structs2/main.go:24-39 — before extracting anything, compare `de/code/src/apps/ch.2.4/embedded_structs2/main.go` and `en/code/src/apps/ch.2.4/embedded_structs2/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 5) de/code/src/apps/ch.2.7/timeout/main.go:12 — de/code/src/apps/ch.2.7/timeout/main.go:12-27 | en/code/src/apps/ch.2.7/timeout/main.go:12-27 | fa/code/src/apps/ch.2.7/timeout/main.go:12-27 | pt-br/code/src/apps/ch.2.7/timeout/main.go:12-27 | th/code/src/apps/ch.2.7/timeout/main.go:12-27 — before extracting anything, compare `de/code/src/apps/ch.2.7/timeout/main.go` and `en/code/src/apps/ch.2.7/timeout/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 5) de/code/src/apps/ch.2.7/range_and_close_channel/main.go:9 — de/code/src/apps/ch.2.7/range_and_close_channel/main.go:9-24 | en/code/src/apps/ch.2.7/range_and_close_channel/main.go:9-24 | fa/code/src/apps/ch.2.7/range_and_close_channel/main.go:9-24 | pt-br/code/src/apps/ch.2.7/range_and_close_channel/main.go:9-24 | th/code/src/apps/ch.2.7/range_and_close_channel/main.go:9-24 — before extracting anything, compare `de/code/src/apps/ch.2.7/range_and_close_channel/main.go` and `en/code/src/apps/ch.2.7/range_and_close_channel/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 5) de/code/src/apps/ch.2.2/main.go:148 — de/code/src/apps/ch.2.2/main.go:148-163 | en/code/src/apps/ch.2.2/main.go:148-163 | fa/code/src/apps/ch.2.2/main.go:148-163 | pt-br/code/src/apps/ch.2.2/main.go:148-163 | th/code/src/apps/ch.2.2/main.go:148-163 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 5) de/code/src/apps/ch.2.5/box_example/main.go:5 — de/code/src/apps/ch.2.5/box_example/main.go:5-20 | en/code/src/apps/ch.2.5/box_example/main.go:5-20 | fa/code/src/apps/ch.2.5/box_example/main.go:5-20 | pt-br/code/src/apps/ch.2.5/box_example/main.go:5-20 | th/code/src/apps/ch.2.5/box_example/main.go:5-20 — before extracting anything, compare `de/code/src/apps/ch.2.5/box_example/main.go` and `en/code/src/apps/ch.2.5/box_example/main.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×5
  • Duplicated block (13 lines × 5) de/code/src/apps/ch.2.6/reflection/main.go:17 — de/code/src/apps/ch.2.6/reflection/main.go:17-29 | en/code/src/apps/ch.2.6/reflection/main.go:17-29 | fa/code/src/apps/ch.2.6/reflection/main.go:17-29 | pt-br/code/src/apps/ch.2.6/reflection/main.go:17-29 | th/code/src/apps/ch.2.6/reflection/main.go:17-29 — before extracting anything, compare `de/code/src/apps/ch.2.6/reflection/main.go` and `en/code/src/apps/ch.2.6/reflection/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 5) REDACTED:31 — REDACTED:31-43 | REDACTED:31-43 | REDACTED:31-43 | REDACTED:31-43 | REDACTED:31-43 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 5) de/code/src/apps/ch.2.3/variadic_functions/main.go:8 — de/code/src/apps/ch.2.3/variadic_functions/main.go:8-20 | en/code/src/apps/ch.2.3/variadic_functions/main.go:8-20 | fa/code/src/apps/ch.2.3/variadic_functions/main.go:8-20 | pt-br/code/src/apps/ch.2.3/variadic_functions/main.go:8-20 | th/code/src/apps/ch.2.3/variadic_functions/main.go:8-20 — before extracting anything, compare `de/code/src/apps/ch.2.3/variadic_functions/main.go` and `en/code/src/apps/ch.2.3/variadic_functions/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 5) de/code/src/apps/ch.2.2/main.go:265 — de/code/src/apps/ch.2.2/main.go:265-277 | en/code/src/apps/ch.2.2/main.go:265-277 | fa/code/src/apps/ch.2.2/main.go:265-277 | pt-br/code/src/apps/ch.2.2/main.go:265-277 | th/code/src/apps/ch.2.2/main.go:265-277 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 5) REDACTED:14 — REDACTED:14-26 | REDACTED:14-26 | REDACTED:14-26 | REDACTED:14-26 | REDACTED:14-26 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×5
  • Duplicated block (10 lines × 5) de/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:27 — de/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:27-36 | en/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:27-36 | fa/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:27-36 | pt-br/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:27-36 | th/code/src/apps/ch.2.5/attach_methods_to_struct/main.go:27-36 — before extracting anything, compare `de/code/src/apps/ch.2.5/attach_methods_to_struct/main.go` and `en/code/src/apps/ch.2.5/attach_methods_to_struct/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 5) de/code/src/apps/ch.5.5/main.go:43 — de/code/src/apps/ch.5.5/main.go:43-52 | en/code/src/apps/ch.5.5/main.go:43-52 | fa/code/src/apps/ch.5.5/main.go:43-52 | pt-br/code/src/apps/ch.5.5/main.go:43-52 | th/code/src/apps/ch.5.5/main.go:43-52 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 5) de/code/src/apps/ch.5.5/main.go:80 — de/code/src/apps/ch.5.5/main.go:80-89 | en/code/src/apps/ch.5.5/main.go:80-89 | fa/code/src/apps/ch.5.5/main.go:80-89 | pt-br/code/src/apps/ch.5.5/main.go:80-89 | th/code/src/apps/ch.5.5/main.go:80-89 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 5) de/code/src/apps/ch.5.5/main.go:32 — de/code/src/apps/ch.5.5/main.go:32-41 | en/code/src/apps/ch.5.5/main.go:32-41 | fa/code/src/apps/ch.5.5/main.go:32-41 | pt-br/code/src/apps/ch.5.5/main.go:32-41 | th/code/src/apps/ch.5.5/main.go:32-41 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 5) de/code/src/apps/ch.5.5/main.go:68 — de/code/src/apps/ch.5.5/main.go:68-77 | en/code/src/apps/ch.5.5/main.go:68-77 | fa/code/src/apps/ch.5.5/main.go:68-77 | pt-br/code/src/apps/ch.5.5/main.go:68-77 | th/code/src/apps/ch.5.5/main.go:68-77 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×4
  • Duplicated block (6 lines × 5) de/code/src/apps/ch.2.4/compare_age/main.go:15 — de/code/src/apps/ch.2.4/compare_age/main.go:15-20 | en/code/src/apps/ch.2.4/compare_age/main.go:15-20 | fa/code/src/apps/ch.2.4/compare_age/main.go:15-20 | pt-br/code/src/apps/ch.2.4/compare_age/main.go:15-20 | th/code/src/apps/ch.2.4/compare_age/main.go:15-20 — before extracting anything, compare `de/code/src/apps/ch.2.4/compare_age/main.go` and `en/code/src/apps/ch.2.4/compare_age/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) REDACTED:59 — REDACTED:59-64 | REDACTED:59-64 | REDACTED:59-64 | REDACTED:59-64 | REDACTED:59-64 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) de/code/src/apps/ch.5.5/main.go:54 — de/code/src/apps/ch.5.5/main.go:54-59 | en/code/src/apps/ch.5.5/main.go:54-59 | fa/code/src/apps/ch.5.5/main.go:54-59 | pt-br/code/src/apps/ch.5.5/main.go:54-59 | th/code/src/apps/ch.5.5/main.go:54-59 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) de/code/src/apps/ch.5.5/main.go:61 — de/code/src/apps/ch.5.5/main.go:61-66 | en/code/src/apps/ch.5.5/main.go:61-66 | fa/code/src/apps/ch.5.5/main.go:61-66 | pt-br/code/src/apps/ch.5.5/main.go:61-66 | th/code/src/apps/ch.5.5/main.go:61-66 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 15) · ×4
  • Duplicated block (10 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:130 — de/code/src/apps/ch.4.2/validator/main.go:130-139 | de/code/src/apps/ch.4.4/validator/main.go:130-139 | de/code/src/apps/ch.4.5/validator/main.go:130-139 | en/code/src/apps/ch.4.2/validator/main.go:130-139 | en/code/src/apps/ch.4.4/validator/main.go:130-139 | en/code/src/apps/ch.4.5/validator/main.go:130-139 | fa/code/src/apps/ch.4.2/validator/main.go:130-139 | fa/code/src/apps/ch.4.4/validator/main.go:130-139 | fa/code/src/apps/ch.4.5/validator/main.go:130-139 | pt-br/code/src/apps/ch.4.2/validator/main.go:130-139 | pt-br/code/src/apps/ch.4.4/validator/main.go:130-139 | pt-br/code/src/apps/ch.4.5/validator/main.go:130-139 | th/code/src/apps/ch.4.2/validator/main.go:130-139 | th/code/src/apps/ch.4.4/validator/main.go:130-139 | th/code/src/apps/ch.4.5/validator/main.go:130-139 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:142 — de/code/src/apps/ch.4.2/validator/main.go:142-151 | de/code/src/apps/ch.4.4/validator/main.go:142-151 | de/code/src/apps/ch.4.5/validator/main.go:142-151 | en/code/src/apps/ch.4.2/validator/main.go:142-151 | en/code/src/apps/ch.4.4/validator/main.go:142-151 | en/code/src/apps/ch.4.5/validator/main.go:142-151 | fa/code/src/apps/ch.4.2/validator/main.go:142-151 | fa/code/src/apps/ch.4.4/validator/main.go:142-151 | fa/code/src/apps/ch.4.5/validator/main.go:142-151 | pt-br/code/src/apps/ch.4.2/validator/main.go:142-151 | pt-br/code/src/apps/ch.4.4/validator/main.go:142-151 | pt-br/code/src/apps/ch.4.5/validator/main.go:142-151 | th/code/src/apps/ch.4.2/validator/main.go:142-151 | th/code/src/apps/ch.4.4/validator/main.go:142-151 | th/code/src/apps/ch.4.5/validator/main.go:142-151 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:154 — de/code/src/apps/ch.4.2/validator/main.go:154-163 | de/code/src/apps/ch.4.4/validator/main.go:154-163 | de/code/src/apps/ch.4.5/validator/main.go:154-163 | en/code/src/apps/ch.4.2/validator/main.go:154-163 | en/code/src/apps/ch.4.4/validator/main.go:154-163 | en/code/src/apps/ch.4.5/validator/main.go:154-163 | fa/code/src/apps/ch.4.2/validator/main.go:154-163 | fa/code/src/apps/ch.4.4/validator/main.go:154-163 | fa/code/src/apps/ch.4.5/validator/main.go:154-163 | pt-br/code/src/apps/ch.4.2/validator/main.go:154-163 | pt-br/code/src/apps/ch.4.4/validator/main.go:154-163 | pt-br/code/src/apps/ch.4.5/validator/main.go:154-163 | th/code/src/apps/ch.4.2/validator/main.go:154-163 | th/code/src/apps/ch.4.4/validator/main.go:154-163 | th/code/src/apps/ch.4.5/validator/main.go:154-163 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:166 — de/code/src/apps/ch.4.2/validator/main.go:166-175 | de/code/src/apps/ch.4.4/validator/main.go:166-175 | de/code/src/apps/ch.4.5/validator/main.go:166-175 | en/code/src/apps/ch.4.2/validator/main.go:166-175 | en/code/src/apps/ch.4.4/validator/main.go:166-175 | en/code/src/apps/ch.4.5/validator/main.go:166-175 | fa/code/src/apps/ch.4.2/validator/main.go:166-175 | fa/code/src/apps/ch.4.4/validator/main.go:166-175 | fa/code/src/apps/ch.4.5/validator/main.go:166-175 | pt-br/code/src/apps/ch.4.2/validator/main.go:166-175 | pt-br/code/src/apps/ch.4.4/validator/main.go:166-175 | pt-br/code/src/apps/ch.4.5/validator/main.go:166-175 | th/code/src/apps/ch.4.2/validator/main.go:166-175 | th/code/src/apps/ch.4.4/validator/main.go:166-175 | th/code/src/apps/ch.4.5/validator/main.go:166-175 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 5) · ×3
  • Duplicated block (19 lines × 5) de/code/src/apps/ch.2.2/main.go:30 — de/code/src/apps/ch.2.2/main.go:30-48 | en/code/src/apps/ch.2.2/main.go:30-48 | fa/code/src/apps/ch.2.2/main.go:30-48 | pt-br/code/src/apps/ch.2.2/main.go:30-48 | th/code/src/apps/ch.2.2/main.go:30-48 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 5) de/code/src/apps/ch.2.2/main.go:123 — de/code/src/apps/ch.2.2/main.go:123-141 | en/code/src/apps/ch.2.2/main.go:123-141 | fa/code/src/apps/ch.2.2/main.go:123-141 | pt-br/code/src/apps/ch.2.2/main.go:123-141 | th/code/src/apps/ch.2.2/main.go:123-141 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 5) de/code/src/apps/ch.2.4/main.go:8 — de/code/src/apps/ch.2.4/main.go:8-26 | en/code/src/apps/ch.2.4/main.go:8-26 | fa/code/src/apps/ch.2.4/main.go:8-26 | pt-br/code/src/apps/ch.2.4/main.go:8-26 | th/code/src/apps/ch.2.4/main.go:8-26 — before extracting anything, compare `de/code/src/apps/ch.2.4/main.go` and `en/code/src/apps/ch.2.4/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17 lines × 5) · ×3
  • Duplicated block (17 lines × 5) de/code/src/apps/ch.2.6/type_check/main.go:21 — de/code/src/apps/ch.2.6/type_check/main.go:21-37 | en/code/src/apps/ch.2.6/type_check/main.go:21-37 | fa/code/src/apps/ch.2.6/type_check/main.go:21-37 | pt-br/code/src/apps/ch.2.6/type_check/main.go:21-37 | th/code/src/apps/ch.2.6/type_check/main.go:21-37 — before extracting anything, compare `de/code/src/apps/ch.2.6/type_check/main.go` and `en/code/src/apps/ch.2.6/type_check/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 5) de/code/src/apps/ch.2.2/main.go:11 — de/code/src/apps/ch.2.2/main.go:11-27 | en/code/src/apps/ch.2.2/main.go:11-27 | fa/code/src/apps/ch.2.2/main.go:11-27 | pt-br/code/src/apps/ch.2.2/main.go:11-27 | th/code/src/apps/ch.2.2/main.go:11-27 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 5) de/code/src/apps/ch.2.6/interface/main.go:4 — de/code/src/apps/ch.2.6/interface/main.go:4-20 | en/code/src/apps/ch.2.6/interface/main.go:4-20 | fa/code/src/apps/ch.2.6/interface/main.go:4-20 | pt-br/code/src/apps/ch.2.6/interface/main.go:4-20 | th/code/src/apps/ch.2.6/interface/main.go:4-20 — before extracting anything, compare `de/code/src/apps/ch.2.6/interface/main.go` and `en/code/src/apps/ch.2.6/interface/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×3
  • Duplicated block (8 lines × 5) de/code/src/apps/ch.2.6/reflection/main.go:8 — de/code/src/apps/ch.2.6/reflection/main.go:8-15 | en/code/src/apps/ch.2.6/reflection/main.go:8-15 | fa/code/src/apps/ch.2.6/reflection/main.go:8-15 | pt-br/code/src/apps/ch.2.6/reflection/main.go:8-15 | th/code/src/apps/ch.2.6/reflection/main.go:8-15 — before extracting anything, compare `de/code/src/apps/ch.2.6/reflection/main.go` and `en/code/src/apps/ch.2.6/reflection/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 5) REDACTED:41 — REDACTED:41-48 | REDACTED:41-48 | REDACTED:41-48 | REDACTED:41-48 | REDACTED:41-48 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 5) de/code/src/apps/ch.5.5/main.go:133 — de/code/src/apps/ch.5.5/main.go:133-140 | en/code/src/apps/ch.5.5/main.go:133-140 | fa/code/src/apps/ch.5.5/main.go:133-140 | pt-br/code/src/apps/ch.5.5/main.go:133-140 | th/code/src/apps/ch.5.5/main.go:133-140 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (15 members, 50+ identical tokens) de/code/src/apps/ch.4.2/validator/main.go:23 — de/code/src/apps/ch.4.2/validator/main.go:23-42 | de/code/src/apps/ch.4.4/validator/main.go:23-42 | de/code/src/apps/ch.4.5/validator/main.go:23-42 | en/code/src/apps/ch.4.2/validator/main.go:23-42 | en/code/src/apps/ch.4.4/validator/main.go:23-42 | en/code/src/apps/ch.4.5/validator/main.go:23-42 | fa/code/src/apps/ch.4.2/validator/main.go:23-42 | fa/code/src/apps/ch.4.4/validator/main.go:23-42 | fa/code/src/apps/ch.4.5/validator/main.go:23-42 | pt-br/code/src/apps/ch.4.2/validator/main.go:23-42 | pt-br/code/src/apps/ch.4.4/validator/main.go:23-42 | pt-br/code/src/apps/ch.4.5/validator/main.go:23-42 | th/code/src/apps/ch.4.2/validator/main.go:23-42 | th/code/src/apps/ch.4.4/validator/main.go:23-42 | th/code/src/apps/ch.4.5/validator/main.go:23-42 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
  • Members sharing a duplicated core (15 members, 50+ identical tokens) de/code/src/apps/ch.4.2/validator/main.go:44 — de/code/src/apps/ch.4.2/validator/main.go:44-63 | de/code/src/apps/ch.4.4/validator/main.go:44-63 | de/code/src/apps/ch.4.5/validator/main.go:44-63 | en/code/src/apps/ch.4.2/validator/main.go:44-63 | en/code/src/apps/ch.4.4/validator/main.go:44-63 | en/code/src/apps/ch.4.5/validator/main.go:44-63 | fa/code/src/apps/ch.4.2/validator/main.go:44-63 | fa/code/src/apps/ch.4.4/validator/main.go:44-63 | fa/code/src/apps/ch.4.5/validator/main.go:44-63 | pt-br/code/src/apps/ch.4.2/validator/main.go:44-63 | pt-br/code/src/apps/ch.4.4/validator/main.go:44-63 | pt-br/code/src/apps/ch.4.5/validator/main.go:44-63 | th/code/src/apps/ch.4.2/validator/main.go:44-63 | th/code/src/apps/ch.4.4/validator/main.go:44-63 | th/code/src/apps/ch.4.5/validator/main.go:44-63 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (10 members, 50+ identical tokens) REDACTED:12 — REDACTED:12-23 | REDACTED:14-26 | REDACTED:12-23 | REDACTED:14-26 | REDACTED:12-23 | REDACTED:14-26 | REDACTED:12-23 | REDACTED:14-26 | REDACTED:12-23 | REDACTED:14-26 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) REDACTED:64 — REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 | REDACTED:64-70 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (7 members, 50+ identical tokens) en/build.go:17 — en/build.go:17-75 | ja/build.go:17-75 | th/build.go:17-75 | zh-tw/build.go:17-84 | zh-tw/build_new.go:20-107 | zh/build.go:17-84 | zh/build_new.go:20-107 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) en/build.go:97 — en/build.go:97-118 | ja/build.go:97-118 | th/build.go:97-118 | zh-tw/build.go:106-127 | zh-tw/build_new.go:129-150 | zh/build.go:106-127 | zh/build_new.go:129-150 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Duplicated block (31 lines × 5) · ×2
  • Duplicated block (31 lines × 5) de/code/src/apps/ch.2.2/main.go:165 — de/code/src/apps/ch.2.2/main.go:165-195 | en/code/src/apps/ch.2.2/main.go:165-195 | fa/code/src/apps/ch.2.2/main.go:165-195 | pt-br/code/src/apps/ch.2.2/main.go:165-195 | th/code/src/apps/ch.2.2/main.go:165-195 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (31 lines × 5) de/code/src/apps/ch.5.6/mongodb/main.go:28 — de/code/src/apps/ch.5.6/mongodb/main.go:28-58 | en/code/src/apps/ch.5.6/mongodb/main.go:28-58 | fa/code/src/apps/ch.5.6/mongodb/main.go:28-58 | pt-br/code/src/apps/ch.5.6/mongodb/main.go:28-58 | th/code/src/apps/ch.5.6/mongodb/main.go:28-58 — before extracting anything, compare `de/code/src/apps/ch.5.6/mongodb/main.go` and `en/code/src/apps/ch.5.6/mongodb/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (29 lines × 5) · ×2
  • Duplicated block (29 lines × 5) de/code/src/apps/ch.2.6/interface/main.go:43 — de/code/src/apps/ch.2.6/interface/main.go:43-71 | en/code/src/apps/ch.2.6/interface/main.go:43-71 | fa/code/src/apps/ch.2.6/interface/main.go:43-71 | pt-br/code/src/apps/ch.2.6/interface/main.go:43-71 | th/code/src/apps/ch.2.6/interface/main.go:43-71 — before extracting anything, compare `de/code/src/apps/ch.2.6/interface/main.go` and `en/code/src/apps/ch.2.6/interface/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `de/code/src/apps/ch.2.6/interface/main.go:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (29 lines × 5) de/code/src/apps/ch.5.5/main.go:142 — de/code/src/apps/ch.5.5/main.go:142-170 | en/code/src/apps/ch.5.5/main.go:142-170 | fa/code/src/apps/ch.5.5/main.go:142-170 | pt-br/code/src/apps/ch.5.5/main.go:142-170 | th/code/src/apps/ch.5.5/main.go:142-170 — before extracting anything, compare `de/code/src/apps/ch.5.5/main.go` and `en/code/src/apps/ch.5.5/main.go` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (28 lines × 10) · ×2
  • Duplicated block (28 lines × 10) de/code/src/apps/ch.5.2/main.go:28 — de/code/src/apps/ch.5.2/main.go:28-55 | de/code/src/apps/ch.5.3/main.go:24-51 | en/code/src/apps/ch.5.2/main.go:28-55 | en/code/src/apps/ch.5.3/main.go:24-51 | fa/code/src/apps/ch.5.2/main.go:28-55 | fa/code/src/apps/ch.5.3/main.go:24-51 | pt-br/code/src/apps/ch.5.2/main.go:28-55 | pt-br/code/src/apps/ch.5.3/main.go:24-51 | th/code/src/apps/ch.5.2/main.go:28-55 | th/code/src/apps/ch.5.3/main.go:24-51 — before extracting anything, compare `de/code/src/apps/ch.5.2/main.go` and `en/code/src/apps/ch.5.2/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `de/code/src/apps/ch.5.2/main.go:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (28 lines × 10) de/code/src/apps/ch.2.5/embedded_method/main.go:4 — de/code/src/apps/ch.2.5/embedded_method/main.go:4-31 | de/code/src/apps/ch.2.5/method_overload/main.go:5-36 | en/code/src/apps/ch.2.5/embedded_method/main.go:4-31 | en/code/src/apps/ch.2.5/method_overload/main.go:5-36 | fa/code/src/apps/ch.2.5/embedded_method/main.go:4-31 | fa/code/src/apps/ch.2.5/method_overload/main.go:5-36 | pt-br/code/src/apps/ch.2.5/embedded_method/main.go:4-31 | pt-br/code/src/apps/ch.2.5/method_overload/main.go:5-36 | th/code/src/apps/ch.2.5/embedded_method/main.go:4-31 | th/code/src/apps/ch.2.5/method_overload/main.go:5-36 — before extracting anything, compare `de/code/src/apps/ch.2.5/embedded_method/main.go` and `en/code/src/apps/ch.2.5/embedded_method/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23 lines × 5) · ×2
  • Duplicated block (23 lines × 5) de/code/src/apps/ch.2.3/main.go:55 — de/code/src/apps/ch.2.3/main.go:55-77 | en/code/src/apps/ch.2.3/main.go:55-77 | fa/code/src/apps/ch.2.3/main.go:55-77 | pt-br/code/src/apps/ch.2.3/main.go:55-77 | th/code/src/apps/ch.2.3/main.go:55-77 — before extracting anything, compare `de/code/src/apps/ch.2.3/main.go` and `en/code/src/apps/ch.2.3/main.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 5) de/code/src/apps/ch.4.5/client_upload/main.go:19 — de/code/src/apps/ch.4.5/client_upload/main.go:19-41 | en/code/src/apps/ch.4.5/client_upload/main.go:19-41 | fa/code/src/apps/ch.4.5/client_upload/main.go:19-41 | pt-br/code/src/apps/ch.4.5/client_upload/main.go:19-41 | th/code/src/apps/ch.4.5/client_upload/main.go:19-41 — before extracting anything, compare `de/code/src/apps/ch.4.5/client_upload/main.go` and `en/code/src/apps/ch.4.5/client_upload/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21 lines × 5) · ×2
  • Duplicated block (21 lines × 5) de/code/src/apps/ch.2.2/main.go:94 — de/code/src/apps/ch.2.2/main.go:94-114 | en/code/src/apps/ch.2.2/main.go:94-114 | fa/code/src/apps/ch.2.2/main.go:94-114 | pt-br/code/src/apps/ch.2.2/main.go:94-114 | th/code/src/apps/ch.2.2/main.go:94-114 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 5) de/code/src/apps/ch.2.4/compare_age/main.go:23 — de/code/src/apps/ch.2.4/compare_age/main.go:23-43 | en/code/src/apps/ch.2.4/compare_age/main.go:23-43 | fa/code/src/apps/ch.2.4/compare_age/main.go:23-43 | pt-br/code/src/apps/ch.2.4/compare_age/main.go:23-43 | th/code/src/apps/ch.2.4/compare_age/main.go:23-43 — before extracting anything, compare `de/code/src/apps/ch.2.4/compare_age/main.go` and `en/code/src/apps/ch.2.4/compare_age/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 5) · ×2
  • Duplicated block (18 lines × 5) de/code/src/apps/ch.2.6/switch_type_check/main.go:21 — de/code/src/apps/ch.2.6/switch_type_check/main.go:21-38 | en/code/src/apps/ch.2.6/switch_type_check/main.go:21-38 | fa/code/src/apps/ch.2.6/switch_type_check/main.go:21-38 | pt-br/code/src/apps/ch.2.6/switch_type_check/main.go:21-38 | th/code/src/apps/ch.2.6/switch_type_check/main.go:21-38 — before extracting anything, compare `de/code/src/apps/ch.2.6/switch_type_check/main.go` and `en/code/src/apps/ch.2.6/switch_type_check/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 5) de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go:7 — de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go:7-24 | en/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go:7-24 | fa/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go:7-24 | pt-br/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go:7-24 | th/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go:7-24 — before extracting anything, compare `de/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go` and `en/code/src/apps/ch.2.4/embedded_structs_with_name_conflict/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×2
  • Duplicated block (12 lines × 5) de/code/src/apps/ch.2.3/main.go:79 — de/code/src/apps/ch.2.3/main.go:79-90 | en/code/src/apps/ch.2.3/main.go:79-90 | fa/code/src/apps/ch.2.3/main.go:79-90 | pt-br/code/src/apps/ch.2.3/main.go:79-90 | th/code/src/apps/ch.2.3/main.go:79-90 — before extracting anything, compare `de/code/src/apps/ch.2.3/main.go` and `en/code/src/apps/ch.2.3/main.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 5) de/code/src/apps/ch.2.3/main.go:31 — de/code/src/apps/ch.2.3/main.go:31-42 | en/code/src/apps/ch.2.3/main.go:31-42 | fa/code/src/apps/ch.2.3/main.go:31-42 | pt-br/code/src/apps/ch.2.3/main.go:31-42 | th/code/src/apps/ch.2.3/main.go:31-42 — before extracting anything, compare `de/code/src/apps/ch.2.3/main.go` and `en/code/src/apps/ch.2.3/main.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×2
  • Duplicated block (14 lines × 5) de/code/src/apps/ch.2.5/pass_struct_to_method/main.go:5 — de/code/src/apps/ch.2.5/pass_struct_to_method/main.go:5-18 | en/code/src/apps/ch.2.5/pass_struct_to_method/main.go:5-18 | fa/code/src/apps/ch.2.5/pass_struct_to_method/main.go:5-18 | pt-br/code/src/apps/ch.2.5/pass_struct_to_method/main.go:5-18 | th/code/src/apps/ch.2.5/pass_struct_to_method/main.go:5-18 — before extracting anything, compare `de/code/src/apps/ch.2.5/pass_struct_to_method/main.go` and `en/code/src/apps/ch.2.5/pass_struct_to_method/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 5) de/code/src/apps/ch.2.2/main.go:79 — de/code/src/apps/ch.2.2/main.go:79-92 | en/code/src/apps/ch.2.2/main.go:79-92 | fa/code/src/apps/ch.2.2/main.go:79-92 | pt-br/code/src/apps/ch.2.2/main.go:79-92 | th/code/src/apps/ch.2.2/main.go:79-92 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 15) · ×2
  • Duplicated block (11 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:66 — de/code/src/apps/ch.4.2/validator/main.go:66-76 | de/code/src/apps/ch.4.4/validator/main.go:66-76 | de/code/src/apps/ch.4.5/validator/main.go:66-76 | en/code/src/apps/ch.4.2/validator/main.go:66-76 | en/code/src/apps/ch.4.4/validator/main.go:66-76 | en/code/src/apps/ch.4.5/validator/main.go:66-76 | fa/code/src/apps/ch.4.2/validator/main.go:66-76 | fa/code/src/apps/ch.4.4/validator/main.go:66-76 | fa/code/src/apps/ch.4.5/validator/main.go:66-76 | pt-br/code/src/apps/ch.4.2/validator/main.go:66-76 | pt-br/code/src/apps/ch.4.4/validator/main.go:66-76 | pt-br/code/src/apps/ch.4.5/validator/main.go:66-76 | th/code/src/apps/ch.4.2/validator/main.go:66-76 | th/code/src/apps/ch.4.4/validator/main.go:66-76 | th/code/src/apps/ch.4.5/validator/main.go:66-76 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:77 — de/code/src/apps/ch.4.2/validator/main.go:77-87 | de/code/src/apps/ch.4.4/validator/main.go:77-87 | de/code/src/apps/ch.4.5/validator/main.go:77-87 | en/code/src/apps/ch.4.2/validator/main.go:77-87 | en/code/src/apps/ch.4.4/validator/main.go:77-87 | en/code/src/apps/ch.4.5/validator/main.go:77-87 | fa/code/src/apps/ch.4.2/validator/main.go:77-87 | fa/code/src/apps/ch.4.4/validator/main.go:77-87 | fa/code/src/apps/ch.4.5/validator/main.go:77-87 | pt-br/code/src/apps/ch.4.2/validator/main.go:77-87 | pt-br/code/src/apps/ch.4.4/validator/main.go:77-87 | pt-br/code/src/apps/ch.4.5/validator/main.go:77-87 | th/code/src/apps/ch.4.2/validator/main.go:77-87 | th/code/src/apps/ch.4.4/validator/main.go:77-87 | th/code/src/apps/ch.4.5/validator/main.go:77-87 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment pt-br/code/src/apps/ch.2.2/main.go:144 — // Todo o resto é privado. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Near-duplicate member family (10 members, 40 shared lines) · ×1
  • Near-duplicate member family (10 members, 40 shared lines) de/code/src/apps/ch.5.2/main.go:17 — de/code/src/apps/ch.5.2/main.go:17-70 | de/code/src/apps/ch.5.3/main.go:14-66 | en/code/src/apps/ch.5.2/main.go:17-70 | en/code/src/apps/ch.5.3/main.go:14-66 | fa/code/src/apps/ch.5.2/main.go:17-70 | fa/code/src/apps/ch.5.3/main.go:14-66 | pt-br/code/src/apps/ch.5.2/main.go:17-70 | pt-br/code/src/apps/ch.5.3/main.go:14-66 | th/code/src/apps/ch.5.2/main.go:17-70 | th/code/src/apps/ch.5.3/main.go:14-66 — These 10 members are variants of one another: a block of 40 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Duplicated block (53 lines × 5) · ×1
  • Duplicated block (53 lines × 5) de/code/src/apps/ch.5.4/main.go:20 — de/code/src/apps/ch.5.4/main.go:20-72 | en/code/src/apps/ch.5.4/main.go:20-72 | fa/code/src/apps/ch.5.4/main.go:20-72 | pt-br/code/src/apps/ch.5.4/main.go:20-72 | th/code/src/apps/ch.5.4/main.go:20-72 — before extracting anything, compare `de/code/src/apps/ch.5.4/main.go` and `en/code/src/apps/ch.5.4/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (45 lines × 7) · ×1
  • Duplicated block (45 lines × 7) en/build.go:20 — en/build.go:20-64 | ja/build.go:20-64 | th/build.go:20-64 | zh-tw/build.go:22-66 | zh-tw/build_new.go:25-69 | zh/build.go:22-66 | zh/build_new.go:25-69 — `en/build.go` and `ja/build.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 75 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `en/build.go:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D4 · Code Duplication · Duplicated block (40 lines × 5) · ×1
  • Duplicated block (40 lines × 5) de/code/src/apps/ch.2.2/main.go:197 — de/code/src/apps/ch.2.2/main.go:197-236 | en/code/src/apps/ch.2.2/main.go:197-236 | fa/code/src/apps/ch.2.2/main.go:197-236 | pt-br/code/src/apps/ch.2.2/main.go:197-236 | th/code/src/apps/ch.2.2/main.go:197-236 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (39 lines × 5) · ×1
  • Duplicated block (39 lines × 5) de/code/src/apps/ch.5.6/redis/main.go:22 — de/code/src/apps/ch.5.6/redis/main.go:22-60 | en/code/src/apps/ch.5.6/redis/main.go:22-60 | fa/code/src/apps/ch.5.6/redis/main.go:22-60 | pt-br/code/src/apps/ch.5.6/redis/main.go:22-60 | th/code/src/apps/ch.5.6/redis/main.go:22-60 — before extracting anything, compare `de/code/src/apps/ch.5.6/redis/main.go` and `en/code/src/apps/ch.5.6/redis/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (35 lines × 5) · ×1
  • Duplicated block (35 lines × 5) de/code/src/apps/ch.2.3/main.go:92 — de/code/src/apps/ch.2.3/main.go:92-126 | en/code/src/apps/ch.2.3/main.go:92-126 | fa/code/src/apps/ch.2.3/main.go:92-126 | pt-br/code/src/apps/ch.2.3/main.go:92-126 | th/code/src/apps/ch.2.3/main.go:92-126 — before extracting anything, compare `de/code/src/apps/ch.2.3/main.go` and `en/code/src/apps/ch.2.3/main.go` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (27 lines × 5) · ×1
  • Duplicated block (27 lines × 5) de/code/src/apps/ch.2.2/main.go:238 — de/code/src/apps/ch.2.2/main.go:238-264 | en/code/src/apps/ch.2.2/main.go:238-264 | fa/code/src/apps/ch.2.2/main.go:238-264 | pt-br/code/src/apps/ch.2.2/main.go:238-264 | th/code/src/apps/ch.2.2/main.go:238-264 — before extracting anything, compare `de/code/src/apps/ch.2.2/main.go` and `en/code/src/apps/ch.2.2/main.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 246 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) REDACTED:37 — REDACTED:37-61 | REDACTED:37-61 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 86 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) REDACTED:11 — REDACTED:11-33 | REDACTED:11-33 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 86 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) REDACTED:82 — REDACTED:82-103 | REDACTED:82-103 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 86 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21 lines × 7) · ×1
  • Duplicated block (21 lines × 7) en/build.go:98 — en/build.go:98-118 | ja/build.go:98-118 | th/build.go:98-118 | zh-tw/build.go:107-127 | zh-tw/build_new.go:130-150 | zh/build.go:107-127 | zh/build_new.go:130-150 — `en/build.go` and `ja/build.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 75 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (20 lines × 15) · ×1
  • Duplicated block (20 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:44 — de/code/src/apps/ch.4.2/validator/main.go:44-63 | de/code/src/apps/ch.4.4/validator/main.go:44-63 | de/code/src/apps/ch.4.5/validator/main.go:44-63 | en/code/src/apps/ch.4.2/validator/main.go:44-63 | en/code/src/apps/ch.4.4/validator/main.go:44-63 | en/code/src/apps/ch.4.5/validator/main.go:44-63 | fa/code/src/apps/ch.4.2/validator/main.go:44-63 | fa/code/src/apps/ch.4.4/validator/main.go:44-63 | fa/code/src/apps/ch.4.5/validator/main.go:44-63 | pt-br/code/src/apps/ch.4.2/validator/main.go:44-63 | pt-br/code/src/apps/ch.4.4/validator/main.go:44-63 | pt-br/code/src/apps/ch.4.5/validator/main.go:44-63 | th/code/src/apps/ch.4.2/validator/main.go:44-63 | th/code/src/apps/ch.4.4/validator/main.go:44-63 | th/code/src/apps/ch.4.5/validator/main.go:44-63 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 15) · ×1
  • Duplicated block (19 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:24 — de/code/src/apps/ch.4.2/validator/main.go:24-42 | de/code/src/apps/ch.4.4/validator/main.go:24-42 | de/code/src/apps/ch.4.5/validator/main.go:24-42 | en/code/src/apps/ch.4.2/validator/main.go:24-42 | en/code/src/apps/ch.4.4/validator/main.go:24-42 | en/code/src/apps/ch.4.5/validator/main.go:24-42 | fa/code/src/apps/ch.4.2/validator/main.go:24-42 | fa/code/src/apps/ch.4.4/validator/main.go:24-42 | fa/code/src/apps/ch.4.5/validator/main.go:24-42 | pt-br/code/src/apps/ch.4.2/validator/main.go:24-42 | pt-br/code/src/apps/ch.4.4/validator/main.go:24-42 | pt-br/code/src/apps/ch.4.5/validator/main.go:24-42 | th/code/src/apps/ch.4.2/validator/main.go:24-42 | th/code/src/apps/ch.4.4/validator/main.go:24-42 | th/code/src/apps/ch.4.5/validator/main.go:24-42 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) REDACTED:63 — REDACTED:63-78 | REDACTED:63-78 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 86 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11–12 lines × 10) · ×1
  • Duplicated block (11–12 lines × 10) REDACTED:13 — REDACTED:13-23 | REDACTED:15-26 | REDACTED:13-23 | REDACTED:15-26 | REDACTED:13-23 | REDACTED:15-26 | REDACTED:13-23 | REDACTED:15-26 | REDACTED:13-23 | REDACTED:15-26 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 10) · ×1
  • Duplicated block (12 lines × 10) de/code/src/apps/ch.5.2/main.go:59 — de/code/src/apps/ch.5.2/main.go:59-70 | de/code/src/apps/ch.5.3/main.go:55-66 | en/code/src/apps/ch.5.2/main.go:59-70 | en/code/src/apps/ch.5.3/main.go:55-66 | fa/code/src/apps/ch.5.2/main.go:59-70 | fa/code/src/apps/ch.5.3/main.go:55-66 | pt-br/code/src/apps/ch.5.2/main.go:59-70 | pt-br/code/src/apps/ch.5.3/main.go:55-66 | th/code/src/apps/ch.5.2/main.go:59-70 | th/code/src/apps/ch.5.3/main.go:55-66 — before extracting anything, compare `de/code/src/apps/ch.5.2/main.go` and `en/code/src/apps/ch.5.2/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `de/code/src/apps/ch.5.2/main.go:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 10) · ×1
  • Duplicated block (6 lines × 10) REDACTED:65 — REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 | REDACTED:65-70 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22 lines × 5) · ×1
  • Duplicated block (22 lines × 5) de/code/src/apps/ch.2.3/panic_and_recover/main.go:10 — de/code/src/apps/ch.2.3/panic_and_recover/main.go:10-31 | en/code/src/apps/ch.2.3/panic_and_recover/main.go:10-31 | fa/code/src/apps/ch.2.3/panic_and_recover/main.go:10-31 | pt-br/code/src/apps/ch.2.3/panic_and_recover/main.go:10-31 | th/code/src/apps/ch.2.3/panic_and_recover/main.go:10-31 — before extracting anything, compare `de/code/src/apps/ch.2.3/panic_and_recover/main.go` and `en/code/src/apps/ch.2.3/panic_and_recover/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D4 · Code Duplication · Duplicated block (25 lines × 5) · ×1
  • Duplicated block (25 lines × 5) de/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go:7 — de/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go:7-31 | en/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go:7-31 | fa/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go:7-31 | pt-br/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go:7-31 | th/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go:7-31 — before extracting anything, compare `de/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go` and `en/code/src/apps/ch.2.3/pass_by_value_and_pointer/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (32 lines × 5) · ×1
  • Duplicated block (32 lines × 5) de/code/src/apps/ch.2.5/method_overload/main.go:5 — de/code/src/apps/ch.2.5/method_overload/main.go:5-36 | en/code/src/apps/ch.2.5/method_overload/main.go:5-36 | fa/code/src/apps/ch.2.5/method_overload/main.go:5-36 | pt-br/code/src/apps/ch.2.5/method_overload/main.go:5-36 | th/code/src/apps/ch.2.5/method_overload/main.go:5-36 — before extracting anything, compare `de/code/src/apps/ch.2.5/method_overload/main.go` and `en/code/src/apps/ch.2.5/method_overload/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 5) · ×1
  • Duplicated block (15 lines × 5) de/code/src/apps/ch.2.6/stringer_interface/main.go:8 — de/code/src/apps/ch.2.6/stringer_interface/main.go:8-22 | en/code/src/apps/ch.2.6/stringer_interface/main.go:8-22 | fa/code/src/apps/ch.2.6/stringer_interface/main.go:8-22 | pt-br/code/src/apps/ch.2.6/stringer_interface/main.go:8-22 | th/code/src/apps/ch.2.6/stringer_interface/main.go:8-22 — before extracting anything, compare `de/code/src/apps/ch.2.6/stringer_interface/main.go` and `en/code/src/apps/ch.2.6/stringer_interface/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24 lines × 5) · ×1
  • Duplicated block (24 lines × 5) de/code/src/apps/ch.2.7/select_channel/main.go:7 — de/code/src/apps/ch.2.7/select_channel/main.go:7-30 | en/code/src/apps/ch.2.7/select_channel/main.go:7-30 | fa/code/src/apps/ch.2.7/select_channel/main.go:7-30 | pt-br/code/src/apps/ch.2.7/select_channel/main.go:7-30 | th/code/src/apps/ch.2.7/select_channel/main.go:7-30 — before extracting anything, compare `de/code/src/apps/ch.2.7/select_channel/main.go` and `en/code/src/apps/ch.2.7/select_channel/main.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) REDACTED:34 — REDACTED:34-38 | REDACTED:34-38 | REDACTED:34-38 | REDACTED:34-38 | REDACTED:34-38 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 10) · ×1
  • Duplicated block (10 lines × 10) REDACTED:50 — REDACTED:50-59 | REDACTED:45-54 | REDACTED:50-59 | REDACTED:45-54 | REDACTED:50-59 | REDACTED:45-54 | REDACTED:50-59 | REDACTED:45-54 | REDACTED:50-59 | REDACTED:45-54 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 15) · ×1
  • Duplicated block (8 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:90 — de/code/src/apps/ch.4.2/validator/main.go:90-97 | de/code/src/apps/ch.4.4/validator/main.go:90-97 | de/code/src/apps/ch.4.5/validator/main.go:90-97 | en/code/src/apps/ch.4.2/validator/main.go:90-97 | en/code/src/apps/ch.4.4/validator/main.go:90-97 | en/code/src/apps/ch.4.5/validator/main.go:90-97 | fa/code/src/apps/ch.4.2/validator/main.go:90-97 | fa/code/src/apps/ch.4.4/validator/main.go:90-97 | fa/code/src/apps/ch.4.5/validator/main.go:90-97 | pt-br/code/src/apps/ch.4.2/validator/main.go:90-97 | pt-br/code/src/apps/ch.4.4/validator/main.go:90-97 | pt-br/code/src/apps/ch.4.5/validator/main.go:90-97 | th/code/src/apps/ch.4.2/validator/main.go:90-97 | th/code/src/apps/ch.4.4/validator/main.go:90-97 | th/code/src/apps/ch.4.5/validator/main.go:90-97 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 15) · ×1
  • Duplicated block (13 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:108 — de/code/src/apps/ch.4.2/validator/main.go:108-120 | de/code/src/apps/ch.4.4/validator/main.go:108-120 | de/code/src/apps/ch.4.5/validator/main.go:108-120 | en/code/src/apps/ch.4.2/validator/main.go:108-120 | en/code/src/apps/ch.4.4/validator/main.go:108-120 | en/code/src/apps/ch.4.5/validator/main.go:108-120 | fa/code/src/apps/ch.4.2/validator/main.go:108-120 | fa/code/src/apps/ch.4.4/validator/main.go:108-120 | fa/code/src/apps/ch.4.5/validator/main.go:108-120 | pt-br/code/src/apps/ch.4.2/validator/main.go:108-120 | pt-br/code/src/apps/ch.4.4/validator/main.go:108-120 | pt-br/code/src/apps/ch.4.5/validator/main.go:108-120 | th/code/src/apps/ch.4.2/validator/main.go:108-120 | th/code/src/apps/ch.4.4/validator/main.go:108-120 | th/code/src/apps/ch.4.5/validator/main.go:108-120 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 15) · ×1
  • Duplicated block (7 lines × 15) de/code/src/apps/ch.4.2/validator/main.go:121 — de/code/src/apps/ch.4.2/validator/main.go:121-127 | de/code/src/apps/ch.4.4/validator/main.go:121-127 | de/code/src/apps/ch.4.5/validator/main.go:121-127 | en/code/src/apps/ch.4.2/validator/main.go:121-127 | en/code/src/apps/ch.4.4/validator/main.go:121-127 | en/code/src/apps/ch.4.5/validator/main.go:121-127 | fa/code/src/apps/ch.4.2/validator/main.go:121-127 | fa/code/src/apps/ch.4.4/validator/main.go:121-127 | fa/code/src/apps/ch.4.5/validator/main.go:121-127 | pt-br/code/src/apps/ch.4.2/validator/main.go:121-127 | pt-br/code/src/apps/ch.4.4/validator/main.go:121-127 | pt-br/code/src/apps/ch.4.5/validator/main.go:121-127 | th/code/src/apps/ch.4.2/validator/main.go:121-127 | th/code/src/apps/ch.4.4/validator/main.go:121-127 | th/code/src/apps/ch.4.5/validator/main.go:121-127 — before extracting anything, compare `de/code/src/apps/ch.4.2/validator/main.go` and `de/code/src/apps/ch.4.4/validator/main.go` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 10) · ×1
  • Duplicated block (9 lines × 10) REDACTED:48 — REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 | REDACTED:48-56 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 10) · ×1
  • Duplicated block (7 lines × 10) de/code/src/mymath/sqrt.go:6 — de/code/src/mymath/sqrt.go:6-12 | en/code/src/mymath/sqrt.go:6-12 | en/src/1.2/sqrt.go:5-11 | es/code/src/mymath/sqrt.go:6-12 | fa/code/src/mymath/sqrt.go:6-12 | ja/src/1.2/sqrt.go:5-11 | pt-br/code/src/mymath/sqrt.go:6-12 | th/code/src/mymath/sqrt.go:6-12 | th/src/1.2/sqrt.go:5-11 | zh-tw/src/1.2/sqrt.go:5-11 — before extracting anything, compare `de/code/src/mymath/sqrt.go` and `en/code/src/mymath/sqrt.go` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×1
  • Duplicated block (9 lines × 7) en/build.go:77 — en/build.go:77-85 | ja/build.go:77-85 | th/build.go:77-85 | zh-tw/build.go:86-94 | zh-tw/build_new.go:109-117 | zh/build.go:86-94 | zh/build_new.go:109-117 — `en/build.go` and `ja/build.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 75 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
Minor — 49 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×39
  • Orphaned file pt-br/code/src/apps/ch.2.2/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file th/code/src/apps/ch.2.2/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fa/code/src/apps/ch.2.2/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file en/code/src/apps/ch.2.2/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file de/code/src/apps/ch.2.2/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file th/code/src/apps/ch.4.5/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file th/code/src/apps/ch.4.4/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file th/code/src/apps/ch.4.2/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pt-br/code/src/apps/ch.4.5/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pt-br/code/src/apps/ch.4.4/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pt-br/code/src/apps/ch.4.2/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fa/code/src/apps/ch.4.5/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fa/code/src/apps/ch.4.4/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fa/code/src/apps/ch.4.2/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file en/code/src/apps/ch.4.5/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file en/code/src/apps/ch.4.4/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file en/code/src/apps/ch.4.2/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file de/code/src/apps/ch.4.5/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file de/code/src/apps/ch.4.4/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file de/code/src/apps/ch.4.2/validator/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file th/code/src/apps/ch.5.5/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file pt-br/code/src/apps/ch.5.5/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fa/code/src/apps/ch.5.5/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file en/code/src/apps/ch.5.5/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file de/code/src/apps/ch.5.5/main.go:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 14 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate de/code/src/apps/ch.4.2/validator/main.go:159 — `siblings != nil && !doSlicesIntersect(siblings, strs)` appears character-identically in 15 files — de/code/src/apps/ch.4.2/validator/main.go, de/code/src/apps/ch.4.4/validator/main.go, de/code/src/apps/ch.4.5/validator/main.go, en/code/src/apps/ch.4.2/validator/main.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate zh-tw/a_href.py:7 — `(dirs[-1]=="l") and (dirs[0].isnumeric())` appears character-identically in 2 files — zh-tw/a_href.py, zh/a_href.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found REDACTED:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 1).
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 39 of 39 significant files have no living knowledge — the codebase as a whole is dormant, not 39 separate risks. Counted over 39 of the 291 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
M1 · Documentation (README) · Thin README · ×1
  • Thin README README.md:1 — The root README is 98 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
X2 · Cancellation propagation · Not all functions that make a request accept a context.Context · ×1
  • Not all functions that make a request accept a context.Context — Only 0/7 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7dff21222b5842c18b59bacbc308daa7/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7dff21222b5842c18b59bacbc308daa7/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .97artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a1d4a1-4b6c-7ebb-9742-b89cbd6321a3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md