Public report of kubernetes-sigs/cluster-api-provider-aws, published 17 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). 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, 17 November 2026, 03:48 UTC · Survey ID cd_ace373423a8f46c698d8df394a942852
kubernetes-sigs/cluster-api-provider-aws
Measured 17 November 2026, 03:48 UTC, at code version 31b1f8c
First survey, so nothing to compare with yet
CAI scoreAt risk
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 medium codebase: 70,577 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Security and Compliance, 57.9
Findings by how serious they are
20 critical1037 serious276 minor
15 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 03:48 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
59of 59 dimensions measured by tools.
1257of 1333 findings point to an exact file and line, so you can open each one in the code. The other 76 concern the repository as a whole, such as missing documentation.
59dimensions across 6 lenses, read from 70,577 lines of product code in 5 projects.
kubernetes-sigs/cluster-api-provider-aws is rated At risk because critical security findings are open. Its score is held back in part because it has pipeline steps that run downloads without checking them. It scores 62.5 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 57.9, is the weakest lens and counts most in the score. The best first step is pinning the third-party scripts, worth about 3.7 points. Fixing the product with no limit on what it can connect to comes next, worth about 1.7 points. Raising Security and Compliance to 70 would lift the score to about 65.9.
Six pipeline steps run downloads nobody checks. Four settings leave the servers or containers unsafe, and three known security holes in the packages the code depends on can be used by attackers. Checking each download against a checksum, correcting the unsafe settings and updating the vulnerable packages would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 70,577 lines, about €180,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 forThe 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.
If Security and Compliance rose from 57.9 to 70, the lowest score rated Strong, the score would rise from 62.5 to about 65.9.
Code composition: what the lines of code are
Product code 45%Tests 55%
Rebuild cost: about €180,000 · Estimate
Cost to rebuild
€59,000 to €300,000, for 983 to 3,119 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, 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.9 at a score of 63. 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.
Size
Medium: 70,577 lines of product code
What it is not
Not 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
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script).
Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
4 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (6 files) · Code Coverage (163 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: rosamachinepool_controller.go, rosacontrolplane_controller.go and awsmachinetemplate_controller.go
What to do: Add tests to these files and have a second person review every change to them, starting with rosamachinepool_controller.go, rosacontrolplane_controller.go and awsmachinetemplate_controller.go.
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Security and Compliance, at 57.9 (Adequate). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Of all the actions in this report, it raises the score most for the work it takes: about 3.7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 13,835 lines over the last 90 days, which is about 56,109 lines a year. At that pace, the extra work comes to an estimated 8.1 to 48.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
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.
133 modules, with 163 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 93 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.
1 pair of types, where a type in io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami uses a type in io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases.
io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami uses io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases, so a change to io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases can break io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami, while a change to io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami can't break io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases.
Position
Below the diagonal: io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 uses a type in io/cluster-api-provider-aws/v2/iam/api/v1beta1.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 uses io/cluster-api-provider-aws/v2/iam/api/v1beta1, so a change to io/cluster-api-provider-aws/v2/iam/api/v1beta1 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 can't break io/cluster-api-provider-aws/v2/iam/api/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 uses a module listed above it, which is the healthy direction.
8 pairs of types, where a type in io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2, while a change to io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud, while a change to io/cluster-api-provider-aws/v2/pkg/cloud can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud uses io/cluster-api-provider-aws/v2/pkg/cloud/throttle, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/throttle can break io/cluster-api-provider-aws/v2/pkg/cloud, while a change to io/cluster-api-provider-aws/v2/pkg/cloud can't break io/cluster-api-provider-aws/v2/pkg/cloud/throttle.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/cloud, while a change to io/cluster-api-provider-aws/v2/pkg/cloud can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/identity uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/identity, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/identity can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/identity uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/identity uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/sts.
io/cluster-api-provider-aws/v2/pkg/cloud/identity uses io/cluster-api-provider-aws/v2/pkg/cloud/services/sts, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/sts can break io/cluster-api-provider-aws/v2/pkg/cloud/identity, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/identity can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/sts.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/identity uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/identity uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/cloud/identity, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/identity can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/identity uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/eks/addons uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/eks/addons, while a change to io/cluster-api-provider-aws/v2/pkg/eks/addons can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/eks/addons uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/eks/identityprovider uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/eks/identityprovider, while a change to io/cluster-api-provider-aws/v2/pkg/eks/identityprovider can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/eks/identityprovider uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/eks/identityprovider uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/eks/identityprovider, while a change to io/cluster-api-provider-aws/v2/pkg/eks/identityprovider can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/eks/identityprovider uses a module listed above it, which is the healthy direction.
17→23 io/cluster-api-provider-aws/v2/pkg/rosa uses io/cluster-api-provider-aws/v2/pkg/cloud/scopepart of a loop✕
Connections
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/rosa uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/rosa uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/rosa, while a change to io/cluster-api-provider-aws/v2/pkg/rosa can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami uses a type in io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases.
io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami uses io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases, so a change to io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases can break io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami, while a change to io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami can't break io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami/k8sreleases.
Position
Below the diagonal: io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami uses a type in io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami.
io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami uses io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami, so a change to io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami can break io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami, while a change to io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami can't break io/cluster-api-provider-aws/hack/tools/release-tools/internal/ami.
Position
Below the diagonal: io/cluster-api-provider-aws/hack/tools/release-tools/cmd/ami uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses a type in io/cluster-api-provider-aws/v2/iam/api/v1beta1.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses io/cluster-api-provider-aws/v2/iam/api/v1beta1, so a change to io/cluster-api-provider-aws/v2/iam/api/v1beta1 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 can't break io/cluster-api-provider-aws/v2/iam/api/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1, so a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 can't break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1alpha1 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses a type in io/cluster-api-provider-aws/v2/iam/api/v1beta1.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses io/cluster-api-provider-aws/v2/iam/api/v1beta1, so a change to io/cluster-api-provider-aws/v2/iam/api/v1beta1 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap can't break io/cluster-api-provider-aws/v2/iam/api/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses a type in io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1.
io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1, so a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1 can break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap, while a change to io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap can't break io/cluster-api-provider-aws/v2/cmd/clusterawsadm/api/bootstrap/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/cmd/clusterawsadm/cloudformation/bootstrap uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/api/v1beta2 uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/exp/api/v1beta2, while a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/api/v1beta2 uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io/cluster-api-provider-aws/v2/exp/api/v1beta2 uses a type in io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
io/cluster-api-provider-aws/v2/exp/api/v1beta2 uses io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 can break io/cluster-api-provider-aws/v2/exp/api/v1beta2, while a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can't break io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/api/v1beta2 uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/converters uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/converters, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/converters can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/converters uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/converters uses a type in io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/converters uses io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/converters, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/converters can't break io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/converters uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/converters uses a type in io/cluster-api-provider-aws/v2/pkg/eks/identityprovider.
io/cluster-api-provider-aws/v2/pkg/cloud/converters uses io/cluster-api-provider-aws/v2/pkg/eks/identityprovider, so a change to io/cluster-api-provider-aws/v2/pkg/eks/identityprovider can break io/cluster-api-provider-aws/v2/pkg/cloud/converters, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/converters can't break io/cluster-api-provider-aws/v2/pkg/eks/identityprovider.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/converters uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/converters uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/converters, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/converters can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/converters uses a module listed above it, which is the healthy direction.
97 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a type in io/cluster-api-provider-aws/v2/api/v1beta2. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/pkg/cloud/services/sts, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/sts can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/sts.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/pkg/cloud/throttle, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/throttle can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/pkg/cloud/throttle.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
13 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a type in io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a type in io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
40 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a type in io/cluster-api-provider-aws/v2/pkg/cloud. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/pkg/cloud/identity, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/identity can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/pkg/cloud/identity.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/pkg/rosa, so a change to io/cluster-api-provider-aws/v2/pkg/rosa can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/pkg/rosa.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/scope uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/scope, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/scope uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a type in io/cluster-api-provider-aws/v2/pkg/logger.
io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/controlplane/rosa/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/rosa/controllers can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a type in io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 can break io/cluster-api-provider-aws/v2/controlplane/rosa/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/rosa/controllers can't break io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses io/cluster-api-provider-aws/v2/pkg/rosa, so a change to io/cluster-api-provider-aws/v2/pkg/rosa can break io/cluster-api-provider-aws/v2/controlplane/rosa/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/rosa/controllers can't break io/cluster-api-provider-aws/v2/pkg/rosa.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a type in io/cluster-api-provider-aws/v2/exp/api/v1beta2.
io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/controlplane/rosa/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/rosa/controllers can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/controlplane/rosa/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/rosa/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/rosa/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth uses a type in io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth uses io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth can't break io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/instancestate uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses a type in io/cluster-api-provider-aws/v2/pkg/cloud.
io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/secretsmanager uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/controllers uses a type in io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/controllers, while a change to io/cluster-api-provider-aws/v2/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/exp/controllers uses a type in io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2 can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/controlplane/rosa/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/pkg/rosa, so a change to io/cluster-api-provider-aws/v2/pkg/rosa can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/pkg/rosa.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/exp/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/exp/controllers, while a change to io/cluster-api-provider-aws/v2/exp/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/exp/controllers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a type in io/cluster-api-provider-aws/v2/pkg/logger.
io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a type in io/cluster-api-provider-aws/v2/pkg/cloud.
io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a type in io/cluster-api-provider-aws/v2/exp/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/autoscaling uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/iam/api/v1beta1, so a change to io/cluster-api-provider-aws/v2/iam/api/v1beta1 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/iam/api/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/sts.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/cloud/services/sts, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/sts can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/sts.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a type in io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/controlplane/eks/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/eks/addons, so a change to io/cluster-api-provider-aws/v2/pkg/eks/addons can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/eks/addons.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a type in io/cluster-api-provider-aws/v2/pkg/eks/identityprovider.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/eks/identityprovider, so a change to io/cluster-api-provider-aws/v2/pkg/eks/identityprovider can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/eks/identityprovider.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses a type in io/cluster-api-provider-aws/v2/iam/api/v1beta1.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses io/cluster-api-provider-aws/v2/iam/api/v1beta1, so a change to io/cluster-api-provider-aws/v2/iam/api/v1beta1 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam can't break io/cluster-api-provider-aws/v2/iam/api/v1beta1.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth.
io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth can break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/eks/iam uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/network, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/network can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/network, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/network can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/network, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/network can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/pkg/cloud/services/network, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/network can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/network uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/securitygroup uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a type in io/cluster-api-provider-aws/v2/api/v1beta2.
io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/controlplane/eks/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/controllers can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses io/cluster-api-provider-aws/v2/pkg/logger, so a change to io/cluster-api-provider-aws/v2/pkg/logger can break io/cluster-api-provider-aws/v2/controlplane/eks/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/controllers can't break io/cluster-api-provider-aws/v2/pkg/logger.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/scope.
io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/controlplane/eks/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/controlplane/eks/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth.
io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth can break io/cluster-api-provider-aws/v2/controlplane/eks/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/iamauth.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/eks.
io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses io/cluster-api-provider-aws/v2/pkg/cloud/services/eks, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/eks can break io/cluster-api-provider-aws/v2/controlplane/eks/controllers, while a change to io/cluster-api-provider-aws/v2/controlplane/eks/controllers can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/eks.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/controlplane/eks/controllers uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/exp/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/exp/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/exp/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/ssm.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/network.
io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses io/cluster-api-provider-aws/v2/pkg/cloud/services/network, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/network can break io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/network.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/ec2 uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/elb, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/elb can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/elb, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/elb can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses io/cluster-api-provider-aws/v2/pkg/cloud/scope, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/scope can break io/cluster-api-provider-aws/v2/pkg/cloud/services/elb, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/elb can't break io/cluster-api-provider-aws/v2/pkg/cloud/scope.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services.
io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses io/cluster-api-provider-aws/v2/pkg/cloud/services, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services can break io/cluster-api-provider-aws/v2/pkg/cloud/services/elb, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/elb can't break io/cluster-api-provider-aws/v2/pkg/cloud/services.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/network.
io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses io/cluster-api-provider-aws/v2/pkg/cloud/services/network, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/network can break io/cluster-api-provider-aws/v2/pkg/cloud/services/elb, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/elb can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/network.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/elb uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses io/cluster-api-provider-aws/v2/api/v1beta2, so a change to io/cluster-api-provider-aws/v2/api/v1beta2 can break io/cluster-api-provider-aws/v2/pkg/cloud/services/gc, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/gc can't break io/cluster-api-provider-aws/v2/api/v1beta2.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses io/cluster-api-provider-aws/v2/pkg/cloud/services/common, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/common can break io/cluster-api-provider-aws/v2/pkg/cloud/services/gc, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/gc can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/common.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses a module listed above it, which is the healthy direction.
io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses io/cluster-api-provider-aws/v2/pkg/cloud, so a change to io/cluster-api-provider-aws/v2/pkg/cloud can break io/cluster-api-provider-aws/v2/pkg/cloud/services/gc, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/gc can't break io/cluster-api-provider-aws/v2/pkg/cloud.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses a type in io/cluster-api-provider-aws/v2/pkg/cloud/services/elb.
io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses io/cluster-api-provider-aws/v2/pkg/cloud/services/elb, so a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/elb can break io/cluster-api-provider-aws/v2/pkg/cloud/services/gc, while a change to io/cluster-api-provider-aws/v2/pkg/cloud/services/gc can't break io/cluster-api-provider-aws/v2/pkg/cloud/services/elb.
Position
Below the diagonal: io/cluster-api-provider-aws/v2/pkg/cloud/services/gc uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 68.5 · Adequate · gated by D2, D4 ·
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 category
Findings
Severity
A02:2025 — Security Misconfiguration
45
High / Critical
A03:2025 — Software Supply Chain Failures
28
High / Critical
A05:2025 — Injection
18
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Resolve the 37 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (10), REDACTED (4), REDACTED (2).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Resolve the 5 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with manager_credentials_patch.yaml, REDACTED, manager_probes.yaml.
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 — 20
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 — 1037
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 — 276
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
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 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 59 dimensions across the health lenses
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
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, 1257 of 1333 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Config/default/kustomizeconfig.yaml:3, config/default/manager_iam_patch.yaml:3 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
AXR1 Runtime accessibility — 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. Render strategy: boot via ToolchainServer (.). `go` is not on PATH — this repository boots from its toolchain's own run entry point (package main in . starts an HTTP listener), so the tier cannot start it without that toolchain No runtime accessibility evidence was produced for this scan. This is a statement about THIS RUN's environment, not about the application: nothing here says the app is inaccessible, only that it was never rendered.
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, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java 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, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust 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.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin or Rust 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, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP or Rust 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.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
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, Kotlin source, and Rust 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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
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.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
74 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Service.ReconcileLaunchTemplate at 58. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being converters.AMITypeToSDK at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: pkg/cloud/converters/eks.go (converters.AMITypeToSDK at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Service.ReconcileLaunchTemplate (cyclomatic 58), Service.CreateInstance (cyclomatic 41), AWSMachineReconciler.reconcileNormal (cyclomatic 40). — 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 8 together lifts Cyclomatic Complexity from 6.1 to about 7.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 128 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with Service.ReconcileLaunchTemplate (cognitive 82), Service.reconcileSubnets (cognitive 81), AWSCluster.validateControlPlaneLBs (cognitive 68). — 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 4 together lifts Cognitive Complexity from 3.7 to about 4.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 10Strong✓ 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 TooManyMethods finding(s) in God Classes — start with service.go (4), managedcontrolplane.go, cluster.go. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 MethodTooLong finding(s) in God Classes — start with cluster_api_controller.go (2), instances.go (2), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with loadbalancer.go, rosacontrolplane_controller.go, instances.go. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication3.3 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
188 duplicated block group(s) detected. 16.8 % of the production lines (11,885 of 70,577) are in a reported copy. A further 138 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 141 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 19 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with loadbalancer.go (4), eksconfig_controller.go (2), rosacluster_controller.go (2). — One of this dimension's main actionable groups (19 warning-level).
Resolve the 14 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with launchtemplate.go (2), groupversion_info.go (2), awscluster_controller.go (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with eksconfig_controller.go, disable.go, awsmanagedcontrolplane_controller.go. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
4 production modules (Go+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
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.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with eksconfig_controller.go, nodeadmconfig_controller.go, awsmachinetemplate_controller.go. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage7.1 / 10Strong✓ 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.
Line coverage 35.4% — 223 file(s) below 50%. Measured from the Go suite (sigs.k8s.io/cluster-api-provider-aws/v2: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made; sigs.k8s.io/cluster-api-provider-aws/hack/tools/release-tools: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
Resolve the 223 Low coverage finding(s) in Code Coverage — start with types.go (8), REDACTED (5), service.go (5). — One of this dimension's main actionable groups (223 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
61 outdated, 1 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 98 of 98 direct requirement(s) were graded against proxy.golang.org (0 not served there, 4 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
Dependency pinned to a stale untagged commit: github.com/google/goexpect
Outdated: github.com/alessio/shellescape · ×61
What to do
Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 7 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 1 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (6 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with instances.go, rosamachinepool_controller.go, rosacontrolplane_controller.go. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with identity.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is bootstrap/eks/controllers/nodeadmconfig_controller.go. Counted over 262 of the 460 production source files in this repository: 194 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
93 deducted task-comment markers across 70577 LoC (0.1/KLoC) → score 9.7. 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.
Resolve the 89 TodoComment finding(s) in Explicit Debt — start with instances_test.go (20), cluster.go (5), upgrade_test.go (4). — One of this dimension's main actionable groups (89 warning-level).
Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with launchtemplate.go (2), awsmachinepool_controller.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with helpers.go. — 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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
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.
0 of 5 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
10 naming inconsistencies among 496 declarations measured against a convention their peers follow.
`DualStackDnsSuffix` spells `Dns` where 23 names in the project spell it `DNS` · ×2pkg/cloud/endpoints/partition.go:41
`ClassicElbAttributes` spells `Elb` where 49 names in the project spell it `ELB`api/v1beta2/network_types.go:336
`makeEksEncryptionConfigs` spells `Eks` where 63 names in the project spell it `EKS`pkg/cloud/services/eks/cluster.go:303
`makeEksLogging` spells `Eks` where 63 names in the project spell it `EKS`pkg/cloud/services/eks/cluster.go:388
`GetQueueUrl` spells `Url` where 14 names in the project spell it `URL`pkg/cloud/services/instancestate/service.go:42
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 `DualStackDnsSuffix` spells `Dns` where 23 names in the project spell it… finding(s) in Naming Consistency — start with partition.go (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `ClassicElbAttributes` spells `Elb` where 49 names in the project spell… finding(s) in Naming Consistency — start with network_types.go. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `makeEksEncryptionConfigs` spells `Eks` where 63 names in the project… finding(s) in Naming Consistency — start with cluster.go. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency8.3 / 10Strong✓ Tool-verified
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
20 API inconsistencies among 1164 exposed members measured against a convention their peers follow.
`Subnets.ToMap` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`)api/v1beta2/network_types.go:779
`EKSConfig.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take onebootstrap/eks/webhooks/eksconfig_webhook.go:34
`EKSConfigTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take onebootstrap/eks/webhooks/eksconfigtemplate_webhook.go:34
`AWSManagedControlPlane.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take onecontrolplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:64
`AWSManagedControlPlaneTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take onecontrolplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:43
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 `Subnets.ToMap` returns a map (`map[K]V`) where its 3 siblings return a… finding(s) in Internal API Consistency — start with network_types.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 `EKSConfig.SetupWebhookWithManager` takes no context.Context; its 4… finding(s) in Internal API Consistency — start with eksconfig_webhook.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 `EKSConfigTemplate.SetupWebhookWithManager` takes no context.Context;… finding(s) in Internal API Consistency — start with eksconfigtemplate_webhook.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 5 build units (Go, Python) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionREDACTED:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
35 % of calls cross a namespace and 4 % 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.
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.
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
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
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).
18 finding(s): 0 critical, 11 high, 5 medium, 2 low. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 6 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 37 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (10), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (37 warning-level).
Resolve the 2 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
145 of 266 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pkg/cloud/services/eks/nodegroup.go. Counted over 266 of the 460 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3pkg/cloud/services/eks/nodegroup.go:1
Concentrated knowledge decay
What to do
Resolve the 142 Orphaned file finding(s) in Knowledge Freshness — start with types.go (9), conditions_consts.go (5), service.go (4). — One of this dimension's main actionable groups (142 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with nodegroup.go, vpc.go, autoscalinggroup.go. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay 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.
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.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with defaults.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
1/7 workload(s) run every container under a seccomp profile; 0/7 declare an AppArmor/SELinux profile.
No seccomp profile · ×5config/default/manager_credentials_patch.yaml:2
What to do
Resolve the 5 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with manager_credentials_patch.yaml, REDACTED, manager_probes.yaml. — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.
Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No admission-control policy finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.page` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/book/theme/css/general.css:48
`details.collapse-code summary:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/book/theme/css/general.css:406
`.js .page-wrapper` moves (`transition: margin-left 0.3s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/book/theme/css/general.css:55
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
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.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`ClusterScoper` declares 16 methods: `Name`, `Namespace`, `InfraClusterName`, `Region`, `KubernetesClusterName`, `InfraCluster`, `ClusterObj`, `UnstructuredControlPlane`, `IdentityRef`, `ListOptionsLabelSelector`, `APIServerPort`, `AdditionalTags`, `SetFailureDomain`, `PatchObject`, `Close`, `MaxWaitDuration`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/cloud/interfaces.go:52
`EC2API` declares 71 methods: `AllocateAddress`, `AllocateHosts`, `AssociateAddress`, `AssociateRouteTable`, `AssociateVpcCidrBlock`, `AttachInternetGateway`, `AuthorizeSecurityGroupIngress`, `CreateCarrierGateway`, `CreateEgressOnlyInternetGateway`, `CreateInternetGateway`, `CreateLaunchTemplate`, `CreateLaunchTemplateVersion`, `CreateNatGateway`, `CreateRouteTable`, `CreateRoute`, `CreateSecurityGroup`, `CreateSubnet`, `CreateTags`, `CreateVpc`, `CreateVpcEndpoint`, `DeleteCarrierGateway`, `DeleteEgressOnlyInternetGateway`, `DeleteInternetGateway`, `DeleteLaunchTemplate`, `DeleteLaunchTemplateVersions`, `DeleteNatGateway`, `DeleteNetworkInterface`, `DeleteRouteTable`, `DeleteSecurityGroup`, `DeleteSubnet`, `DeleteTags`, `DeleteVpc`, `DeleteVpcEndpoints`, `DescribeAddresses`, `DescribeAvailabilityZones`, `DescribeCarrierGateways`, `DescribeDhcpOptions`, `DescribeEgressOnlyInternetGateways`, `DescribeHosts`, `DescribeImages`, and 31 more. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/cloud/services/common/common.go:27
`EKSAPI` declares 48 methods: `CreateCluster`, `DeleteCluster`, `DescribeCluster`, `UpdateClusterConfig`, `UpdateClusterVersion`, `DescribeUpdate`, `AssociateEncryptionConfig`, `ListClusters`, `CreateNodegroup`, `DeleteNodegroup`, `DescribeNodegroup`, `UpdateNodegroupConfig`, `UpdateNodegroupVersion`, `DescribeAddon`, `CreateAddon`, `UpdateAddon`, `ListAddons`, `DescribeAddonConfiguration`, `DescribeAddonVersions`, `DeleteAddon`, `ListIdentityProviderConfigs`, `DescribeIdentityProviderConfig`, `AssociateIdentityProviderConfig`, `CreateFargateProfile`, `DeleteFargateProfile`, `DescribeFargateProfile`, `TagResource`, `UntagResource`, `DisassociateIdentityProviderConfig`, `ListAccessEntries`, `DescribeAccessEntry`, `CreateAccessEntry`, `UpdateAccessEntry`, `DeleteAccessEntry`, `ListAssociatedAccessPolicies`, `AssociateAccessPolicy`, `DisassociateAccessPolicy`, `ListPodIdentityAssociations`, `DescribePodIdentityAssociation`, `CreatePodIdentityAssociation`, and 8 more. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/cloud/services/eks/service.go:35
`ELBV2API` declares 23 methods: `AddTags`, `CreateListener`, `CreateLoadBalancer`, `CreateTargetGroup`, `DeleteListener`, `DeleteLoadBalancer`, `DeleteTargetGroup`, `DeregisterTargets`, `DescribeListeners`, `DescribeLoadBalancerAttributes`, `DescribeLoadBalancers`, `DescribeTags`, `DescribeTargetGroups`, `DescribeTargetHealth`, `ModifyListener`, `ModifyLoadBalancerAttributes`, `ModifyTargetGroupAttributes`, `RegisterTargets`, `RemoveTags`, `SetSecurityGroups`, `SetSubnets`, `DescribeLoadBalancersPages`, `WaitUntilLoadBalancerAvailable`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/cloud/services/elb/service.go:67
`ASGInterface` declares 16 methods: `ASGIfExists`, `GetASGByName`, `CreateASG`, `UpdateASG`, `CancelASGInstanceRefresh`, `StartASGInstanceRefresh`, `CanStartASGInstanceRefresh`, `UpdateResourceTags`, `DeleteASGAndWait`, `SuspendProcesses`, `ResumeProcesses`, `SubnetIDs`, `DescribeLifecycleHooks`, `CreateLifecycleHook`, `UpdateLifecycleHook`, `DeleteLifecycleHook`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/cloud/services/interfaces.go:73
`EC2Interface` declares 29 methods: `InstanceIfExists`, `TerminateInstance`, `CreateInstance`, `GetRunningInstanceByTags`, `GetAdditionalSecurityGroupsIDs`, `GetCoreSecurityGroups`, `GetInstanceSecurityGroups`, `UpdateInstanceSecurityGroups`, `UpdateResourceTags`, `ModifyInstanceMetadataOptions`, `ModifySourceDestCheck`, `TerminateInstanceAndWait`, `DetachSecurityGroupsFromNetworkInterface`, `DiscoverLaunchTemplateAMI`, `GetLaunchTemplate`, `GetLaunchTemplateID`, `GetLaunchTemplateLatestVersion`, `CreateLaunchTemplate`, `CreateLaunchTemplateVersion`, `PruneLaunchTemplateVersions`, `DeleteLaunchTemplate`, `LaunchTemplateNeedsUpdate`, `DeleteBastion`, `ReconcileBastion`, `ReconcileElasticIPFromPublicPool`, `ReleaseElasticIP`, `AllocateDedicatedHost`, `ReleaseDedicatedHost`, `DescribeDedicatedHost`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/cloud/services/interfaces.go:94
`OCMClient` declares 32 methods: `AckVersionGate`, `AddHTPasswdUser`, `CreateNodePool`, `CreateIdentityProvider`, `CreateCluster`, `CreateUser`, `DeleteCluster`, `DeleteNodePool`, `DeleteUser`, `GetAvailableChannels`, `GetCluster`, `GetControlPlaneUpgradePolicies`, `GetHTPasswdUserList`, `GetHypershiftNodePoolUpgrade`, `GetIdentityProviders`, `GetMissingGateAgreementsHypershift`, `GetNodePool`, `GetNodePools`, `GetPolicies`, `GetUser`, `ScheduleHypershiftControlPlaneUpgrade`, `ScheduleNodePoolUpgrade`, `UpdateNodePool`, `UpdateCluster`, `ValidateHypershiftVersion`, `SetLogForwarder`, `UpdateLogForwarder`, `DeleteLogForwarder`, `GetLogForwarders`, `UpdateClusterDeletionProtection`, `GetIngresses`, `UpdateIngress`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pkg/rosa/ocmclient.go:37
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.
What to do
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.
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.
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.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `docs/triage-party`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `uv`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `uv` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.Get(` 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. (×3) — cmd/clusterawsadm/ami/helper.go:73, cmd/clusterawsadm/ami/helper.go:149, cmd/clusterawsadm/ami/helper.go:171
`requests.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. (×2) — hack/boskos.py:61, hack/boskos.py:72
`http.DefaultClient` 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. — pkg/cloud/services/eks/service.go:129
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.
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://code.jquery.com/jquery-3.5.1.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — docs/book/theme/head.hbs:5
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
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 2/4 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.
`LatestPatchRelease` calls `http.Get(…)` 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, …)`. — cmd/clusterawsadm/ami/helper.go:67
`latestStableRelease` calls `http.Get(…)` 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, …)`. — cmd/clusterawsadm/ami/helper.go:148
What to do
Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
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.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for … range` leaves the slice or map it is walking alone — Go raises nothing, but the walk and the collection part: a range evaluates its slice once, so an element appended in the body is never visited and a removal by reslicing (`s = append(s[:i], s[i+1:]...)`, `slices.Delete`) shifts the next element under the index, which is then skipped while the last is read twice; a reslice, a reassignment or a sort leaves every later `s[i]` naming another element; and a map's order is unspecified, so deleting another key (or clearing the map) changes from run to run which entries the loop still sees.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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.
`r, ok := obj.(*infrav1.AWSCluster)` failed on this branch, so `r` is the zero value of `*infrav1.AWSCluster` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — webhooks/awscluster_webhook.go:65, webhooks/awscluster_webhook.go:272
`r, ok := newObj.(*infrav1.AWSCluster)` failed on this branch, so `r` is the zero value of `*infrav1.AWSCluster` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — webhooks/awscluster_webhook.go:97
`r, ok := obj.(*infrav1.AWSClusterControllerIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterControllerIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — webhooks/awsclustercontrolleridentity_webhook.go:58, webhooks/awsclustercontrolleridentity_webhook.go:119
`r, ok := newObj.(*infrav1.AWSClusterControllerIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterControllerIdentity` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — webhooks/awsclustercontrolleridentity_webhook.go:87
`r, ok := obj.(*infrav1.AWSClusterRoleIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterRoleIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — webhooks/awsclusterroleidentity_webhook.go:56, webhooks/awsclusterroleidentity_webhook.go:113
`r, ok := newObj.(*infrav1.AWSClusterRoleIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterRoleIdentity` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — webhooks/awsclusterroleidentity_webhook.go:84
`r, ok := obj.(*infrav1.AWSClusterStaticIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterStaticIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — webhooks/awsclusterstaticidentity_webhook.go:56, webhooks/awsclusterstaticidentity_webhook.go:107
`r, ok := newObj.(*infrav1.AWSClusterStaticIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterStaticIdentity` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — webhooks/awsclusterstaticidentity_webhook.go:79
`r, ok := obj.(*infrav1.AWSClusterTemplate)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterTemplate` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — webhooks/awsclustertemplate_webhook.go:54, webhooks/awsclustertemplate_webhook.go:65
`r, ok := newObj.(*infrav1.AWSClusterTemplate)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterTemplate` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — webhooks/awsclustertemplate_webhook.go:80
`r, ok := obj.(*infrav1.AWSMachine)` failed on this branch, so `r` is the zero value of `*infrav1.AWSMachine` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — REDACTED:72, REDACTED:459
`r, ok := newObj.(*infrav1.AWSMachine)` failed on this branch, so `r` is the zero value of `*infrav1.AWSMachine` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — REDACTED:96
`if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — pkg/cloud/throttle/throttle.go:98, pkg/cloud/services/instancestate/rule.go:220, pkg/cloud/services/instancestate/rule.go:225, …
`firstTime, _ := time.Parse(createDateTimestampFormat, aws.ToString(i[k].CreationDate))` writes the call's error to `_` and then uses `firstTime` as if the call succeeded. When `time.Parse` fails, `firstTime` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `firstTime` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — pkg/cloud/services/ec2/ami.go:275
`secondTime, _ := time.Parse(createDateTimestampFormat, aws.ToString(i[j].CreationDate))` writes the call's error to `_` and then uses `secondTime` as if the call succeeded. When `time.Parse` fails, `secondTime` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `secondTime` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — pkg/cloud/services/ec2/ami.go:276
`userData, _ := userdata.NewBastion(&userdata.BastionInput{})` writes the call's error to `_` and then uses `userData` as if the call succeeded. When `userdata.NewBastion` fails, `userData` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `userData` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — pkg/cloud/services/ec2/bastion.go:173
`a, _ := parseSemver(minors[i])` writes the call's error to `_` and then uses `a` as if the call succeeded. When `parseSemver` fails, `a` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `a` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:254
`b, _ := parseSemver(minors[j])` writes the call's error to `_` and then uses `b` as if the call succeeded. When `parseSemver` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:255
`a, _ := parseSemver(patches[i])` writes the call's error to `_` and then uses `a` as if the call succeeded. When `parseSemver` fails, `a` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `a` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:273
`b, _ := parseSemver(patches[j])` writes the call's error to `_` and then uses `b` as if the call succeeded. When `parseSemver` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:274
`r, ok := obj.(*expinfrav1.AWSFargateProfile)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSFargateProfile` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — exp/webhooks/awsfargateprofile_webhook.go:65, exp/webhooks/awsfargateprofile_webhook.go:158
`r, ok := newObj.(*expinfrav1.AWSFargateProfile)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSFargateProfile` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — exp/webhooks/awsfargateprofile_webhook.go:89
`r, ok := obj.(*expinfrav1.AWSMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — exp/webhooks/awsmachinepool_webhook.go:198, exp/webhooks/awsmachinepool_webhook.go:304
`r, ok := newObj.(*expinfrav1.AWSMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — exp/webhooks/awsmachinepool_webhook.go:271
`r, ok := obj.(*expinfrav1.AWSManagedMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSManagedMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. (×2) — exp/webhooks/awsmanagedmachinepool_webhook.go:155, exp/webhooks/awsmanagedmachinepool_webhook.go:291
`r, ok := newObj.(*expinfrav1.AWSManagedMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSManagedMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead. — exp/webhooks/awsmanagedmachinepool_webhook.go:198
`r, ok := obj.(*expinfrav1.ROSAMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.ROSAMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead. — exp/webhooks/rosamachinepool_webhook.go:41
What to do
Lost error (reports the zero value of a failed type assertion)
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`Info` at line 233 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — main.go:233
`Info` at line 136 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — pkg/logger/logger.go:136
`Info` at line 138 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — pkg/logger/logger.go:138
`Info` at line 346 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — controllers/rosacluster_controller.go:346
`Info` at line 351 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog. — controllers/rosacluster_controller.go:351
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Capped 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 — 22 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 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 image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
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.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
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
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — `go` is not on PATH — this repository boots from its toolchain's own run entry point (package main in . starts an HTTP listener), so the tier cannot start it without that toolchain No runtime accessibility evidence was produced for this scan. This is a statement about THIS RUN's environment, not about the application: nothing here says the app is inaccessible, only that it was never rendered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
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 — ~87537 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
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.
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 — None of 4 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
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.
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.
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, Scala, Rust and Java, 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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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 data present for 391 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 1% of this repository's production lines — go (70,083 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
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
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.
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.
TodoComment test/e2e/suites/unmanaged/unmanaged_functional_test.go:210— // // TODO: @sedefsavas: Requires env var logic to be removed — 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.
TodoComment test/e2e/suites/unmanaged/unmanaged_functional_test.go:431— // TODO @randomvariable: Await more resources — 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.
TodoComment test/e2e/suites/managed/eks_upgrade_to_nodeadm_test.go:79— // TODO (richardcase) - change in the future when upgrades to machinepools work — 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.
TodoComment test/e2e/suites/managed/upgrade_test.go:73— // TODO (richardcase) - change in the future when upgrades to machinepools work — 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.
TodoComment test/e2e/suites/managed/machine_pool.go:104— // TODO (richardcase): should this be a separate spec? — 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.
TodoComment test/e2e/suites/managed/upgrade_test.go:80— // TODO: should cluster be returned from the ManagedClusterSpec as a convenience — 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.
TodoComment test/e2e/suites/managed/upgrade_test.go:89— // TODO (richardcase) - uncomment when we use machine pools again — 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.
TodoComment test/e2e/suites/managed/upgrade_test.go:122— // TODO (richardcase): add test for the node group upgrade — 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.
TodoComment test/e2e/suites/conformance/conformance_test.go:44— // TODO @randomvariable: Replace with CAPI e2e framework ClusterUpgradeConformanceSpec. — 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.
TodoComment test/e2e/shared/aws.go:595— // TODO: why is there a break here? Don't we want to clean up everything? — 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.
TodoComment test/e2e/shared/aws.go:603— // TODO: remove once test infra accounts are fixed. — 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.
TodoComment test/e2e/shared/common.go:302— // TODO: This is commented out as it assumes kubeadm and errors if its not there — 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.
TodoComment test/e2e/shared/temp.go:120— // TODO: this is the reason why we can't use this at present for the EKS tests — 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.
TodoComment pkg/rosa/client.go:164— // TODO: once the ENV variable fallback is gone, we can no longer ignore non-existent secret here — 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.
TodoComment pkg/rosa/client.go:181— // TODO: the ENV variables are to be removed with the next code release — 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.
TodoComment pkg/rosa/awshelpers/helpers.go:27— // TODO: Remove once ROSA dependency is bumped to include this function (added in commit e14522438). — 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.
TodoComment pkg/rosa/awshelpers/helpers.go:34— // TODO: Remove once ROSA dependency is bumped to include this function (added in commit e14522438). — 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.
TodoComment pkg/cloud/services/securitygroup/securitygroups.go:125— // TODO(vincepri): validate / update security group if necessary. — 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.
TodoComment pkg/cloud/services/s3/s3.go:138— // TODO Switch to aws-sdk-go-v2 which has NewListObjectsV2Paginator (as part of https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/2225)
TodoComment pkg/cloud/services/s3/s3.go:417— // TODO: This will fail if bucket is shared with other cluster. — 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.
TodoComment pkg/cloud/services/network/routetables.go:73— // TODO(vincepri): check that everything is in order, e.g. routes match the subnet type. — 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.
TodoComment REDACTED:369— // TODO: this might need to be the last instead of the first.. — 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.
TodoComment pkg/cloud/services/iamauth/configmap_test.go:174— //TODO: we may need to do a better match — 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.
TodoComment pkg/cloud/services/iamauth/configmap_test.go:307— //TODO: we may need to do a better match — 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.
TodoComment pkg/cloud/services/elb/loadbalancer.go:513— // TODO: remove when security groups on NLBs is supported in all regions. — 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.
X3 · Exception handling· Lost error (reports the zero value of a failed type assertion) · ×28
Lost error (reports the zero value of a failed type assertion) webhooks/awscluster_webhook.go:65— `r, ok := obj.(*infrav1.AWSCluster)` failed on this branch, so `r` is the zero value of `*infrav1.AWSCluster` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awscluster_webhook.go:97— `r, ok := newObj.(*infrav1.AWSCluster)` failed on this branch, so `r` is the zero value of `*infrav1.AWSCluster` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awscluster_webhook.go:272— `r, ok := obj.(*infrav1.AWSCluster)` failed on this branch, so `r` is the zero value of `*infrav1.AWSCluster` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclustercontrolleridentity_webhook.go:58— `r, ok := obj.(*infrav1.AWSClusterControllerIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterControllerIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclustercontrolleridentity_webhook.go:87— `r, ok := newObj.(*infrav1.AWSClusterControllerIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterControllerIdentity` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclustercontrolleridentity_webhook.go:119— `r, ok := obj.(*infrav1.AWSClusterControllerIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterControllerIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclusterroleidentity_webhook.go:56— `r, ok := obj.(*infrav1.AWSClusterRoleIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterRoleIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclusterroleidentity_webhook.go:84— `r, ok := newObj.(*infrav1.AWSClusterRoleIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterRoleIdentity` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclusterroleidentity_webhook.go:113— `r, ok := obj.(*infrav1.AWSClusterRoleIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterRoleIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclusterstaticidentity_webhook.go:56— `r, ok := obj.(*infrav1.AWSClusterStaticIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterStaticIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclusterstaticidentity_webhook.go:79— `r, ok := newObj.(*infrav1.AWSClusterStaticIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterStaticIdentity` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclusterstaticidentity_webhook.go:107— `r, ok := obj.(*infrav1.AWSClusterStaticIdentity)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterStaticIdentity` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclustertemplate_webhook.go:54— `r, ok := obj.(*infrav1.AWSClusterTemplate)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterTemplate` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclustertemplate_webhook.go:65— `r, ok := obj.(*infrav1.AWSClusterTemplate)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterTemplate` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) webhooks/awsclustertemplate_webhook.go:80— `r, ok := newObj.(*infrav1.AWSClusterTemplate)` failed on this branch, so `r` is the zero value of `*infrav1.AWSClusterTemplate` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) REDACTED:72— `r, ok := obj.(*infrav1.AWSMachine)` failed on this branch, so `r` is the zero value of `*infrav1.AWSMachine` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) REDACTED:96— `r, ok := newObj.(*infrav1.AWSMachine)` failed on this branch, so `r` is the zero value of `*infrav1.AWSMachine` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) REDACTED:459— `r, ok := obj.(*infrav1.AWSMachine)` failed on this branch, so `r` is the zero value of `*infrav1.AWSMachine` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsfargateprofile_webhook.go:65— `r, ok := obj.(*expinfrav1.AWSFargateProfile)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSFargateProfile` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsfargateprofile_webhook.go:89— `r, ok := newObj.(*expinfrav1.AWSFargateProfile)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSFargateProfile` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsfargateprofile_webhook.go:158— `r, ok := obj.(*expinfrav1.AWSFargateProfile)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSFargateProfile` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsmachinepool_webhook.go:198— `r, ok := obj.(*expinfrav1.AWSMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsmachinepool_webhook.go:271— `r, ok := newObj.(*expinfrav1.AWSMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `newObj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsmachinepool_webhook.go:304— `r, ok := obj.(*expinfrav1.AWSMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) exp/webhooks/awsmanagedmachinepool_webhook.go:155— `r, ok := obj.(*expinfrav1.AWSManagedMachinePool)` failed on this branch, so `r` is the zero value of `*expinfrav1.AWSManagedMachinePool` here, and that is what is reported: the value that did not fit is lost. Report `obj` itself (and `%T` of it) instead.
Duplicated block (7 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:78— bootstrap/eks/controllers/eksconfig_controller.go:78-84 | bootstrap/eks/controllers/nodeadmconfig_controller.go:75-81 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) pkg/cloud/scope/machinepool.go:153— pkg/cloud/scope/machinepool.go:153-159 | pkg/cloud/scope/managednodegroup.go:357-363 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/scope/machinepool.go:153` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) pkg/cloud/scope/managednodegroup.go:88— pkg/cloud/scope/managednodegroup.go:88-94 | pkg/cloud/scope/rosacontrolplane.go:68-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/scope/managednodegroup.go:88` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: `pkg/cloud/scope/rosacontrolplane.go:68` is reached only past a guard at line 51 that tests `params.Cluster` and leaves the function early, and `pkg/cloud/scope/managednodegroup.go:88` reads `params.Cluster` with no such check. What separates these copies is not which lines they run but which PRECONDITION they enforce, so one of them is operating on state the other one refuses. Decide which is intended BEFORE unifying them — extract the shared part and whichever copy is missing the check keeps running unchecked, and if the guard is the correct behaviour then that hole is already live.
Duplicated block (7 lines × 2) pkg/cloud/services/elb/loadbalancer.go:440— pkg/cloud/services/elb/loadbalancer.go:440-446 | pkg/cloud/services/elb/loadbalancer.go:1247-1253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) pkg/cloud/services/elb/loadbalancer.go:744— pkg/cloud/services/elb/loadbalancer.go:744-751 | pkg/cloud/services/elb/loadbalancer.go:855-861 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) pkg/cloud/services/instancestate/rule.go:145— pkg/cloud/services/instancestate/rule.go:145-153 | pkg/cloud/services/instancestate/rule.go:202-208 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/instancestate/rule.go:145` 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 (7 lines × 2) controllers/awsmachinetemplate_controller.go:418— controllers/awsmachinetemplate_controller.go:418-424 | controllers/awsmachinetemplate_controller.go:433-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) pkg/rosa/ocmrole/ocmrole.go:204— pkg/rosa/ocmrole/ocmrole.go:204-210 | pkg/rosa/ocmrole/ocmrole.go:229-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/rosa/ocmrole/ocmrole.go:204` it begins part-way through the construct above it, 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 (7 lines × 2) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:77— controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:77-83 | pkg/cloud/services/eks/cluster.go:772-778 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) exp/instancestate/awsinstancestate_controller.go:232— exp/instancestate/awsinstancestate_controller.go:232-238 | pkg/cloud/services/instancestate/queue.go:106-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) hack/tools/release-tools/cmd/ami/detect_k8s_release.go:109— hack/tools/release-tools/cmd/ami/detect_k8s_release.go:109-115 | hack/tools/release-tools/cmd/ami/find_missing_ami.go:202-208 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) controllers/rosacluster_controller.go:163— controllers/rosacluster_controller.go:163-170 | controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:176-182 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/rosacluster_controller.go:163` 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 (7 lines × 2) pkg/cloud/services/elb/loadbalancer.go:573— pkg/cloud/services/elb/loadbalancer.go:573-579 | pkg/cloud/services/elb/loadbalancer.go:1557-1563 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/elb/loadbalancer.go:573` it begins part-way through the construct above it, 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 (7 lines × 2) exp/controllers/rosaocmroleconfig_controller.go:114— exp/controllers/rosaocmroleconfig_controller.go:114-120 | exp/controllers/rosaroleconfig_controller.go:127-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:88— bootstrap/eks/controllers/eksconfig_controller.go:88-94 | bootstrap/eks/controllers/nodeadmconfig_controller.go:85-91 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:88` 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 (7 lines × 2) pkg/cloud/services/gc/loadbalancer.go:216— pkg/cloud/services/gc/loadbalancer.go:216-222 | pkg/cloud/services/gc/loadbalancer.go:245-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/gc/loadbalancer.go:216` 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 (7 lines × 2) controllers/rosacluster_controller.go:97— controllers/rosacluster_controller.go:97-103 | exp/controllers/awsmanagedmachinepool_controller.go:121-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/rosacluster_controller.go:97` it begins part-way through the construct above it, 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) pkg/cloud/services/awsnode/cni.go:244— pkg/cloud/services/awsnode/cni.go:244-250 | pkg/cloud/services/awsnode/cni.go:252-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/awsnode/cni.go:244` it begins part-way through the construct above it, 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 (7 lines × 2) pkg/cloud/services/ec2/instances.go:432— pkg/cloud/services/ec2/instances.go:432-438 | pkg/cloud/services/ec2/instances.go:442-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:405— bootstrap/eks/controllers/eksconfig_controller.go:405-414 | bootstrap/eks/controllers/nodeadmconfig_controller.go:328-337 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:405` 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 (10 lines × 2) cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:102— cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:102-111 | cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:149-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) controllers/awsmanagedcluster_controller.go:97— controllers/awsmanagedcluster_controller.go:97-106 | controllers/rosacluster_controller.go:117-126 — before extracting anything, compare `controllers/awsmanagedcluster_controller.go` and `controllers/rosacluster_controller.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) pkg/cloud/scope/managedcontrolplane.go:75— pkg/cloud/scope/managedcontrolplane.go:75-84 | pkg/cloud/scope/rosacontrolplane.go:51-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) pkg/cloud/services/ec2/launchtemplate.go:146— pkg/cloud/services/ec2/launchtemplate.go:146-155 | pkg/cloud/services/ec2/launchtemplate.go:166-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/ec2/launchtemplate.go:146` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) pkg/cloud/services/ec2/launchtemplate.go:1204— pkg/cloud/services/ec2/launchtemplate.go:1204-1213 | pkg/cloud/services/ec2/launchtemplate.go:1218-1227 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/ec2/launchtemplate.go:1204` 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 (10 lines × 2) pkg/cloud/services/eks/roles.go:254— pkg/cloud/services/eks/roles.go:254-263 | pkg/cloud/services/eks/roles.go:366-375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/roles.go:254` it begins part-way through the construct above it, 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 (10 lines × 2) api/v1beta1/awsidentity_types.go:181— api/v1beta1/awsidentity_types.go:181-190 | api/v1beta2/awsidentity_types.go:184-193 — `api/v1beta1/awsidentity_types.go` and `api/v1beta2/awsidentity_types.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 2 separate duplicated blocks between them, totalling at least 169 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.
Duplicated block (10 lines × 2) api/v1beta2/groupversion_info.go:27— api/v1beta2/groupversion_info.go:27-36 | exp/api/v1beta2/groupversion_info.go:27-36 — before extracting anything, compare `api/v1beta2/groupversion_info.go` and `exp/api/v1beta2/groupversion_info.go` as WHOLE FILES: 96% 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 (10 lines × 2) controlplane/eks/api/v1beta2/groupversion_info.go:27— controlplane/eks/api/v1beta2/groupversion_info.go:27-36 | controlplane/rosa/api/v1beta2/groupversion_info.go:27-36 — before extracting anything, compare `controlplane/eks/api/v1beta2/groupversion_info.go` and `controlplane/rosa/api/v1beta2/groupversion_info.go` as WHOLE FILES: 88% 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 (10 lines × 2) controllers/awscluster_controller.go:118— controllers/awscluster_controller.go:118-127 | controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:77-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) pkg/cloud/scope/machine.go:339— pkg/cloud/scope/machine.go:339-348 | pkg/cloud/scope/machinepool.go:163-172 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) exp/controllers/rosaocmroleconfig_controller.go:396— exp/controllers/rosaocmroleconfig_controller.go:396-405 | exp/controllers/rosaroleconfig_controller.go:558-567 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) controllers/awscluster_controller.go:459— controllers/awscluster_controller.go:459-468 | controllers/awsmachine_controller.go:1236-1245 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/awscluster_controller.go:459` 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D30 · Dependency Vulnerabilities· Medium CVE · ×13
Duplicated block (11 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:300— bootstrap/eks/controllers/eksconfig_controller.go:300-310 | bootstrap/eks/controllers/nodeadmconfig_controller.go:290-300 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:300` 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 (11 lines × 2) cmd/clusterawsadm/cmd/gc/disable.go:74— cmd/clusterawsadm/cmd/gc/disable.go:74-84 | cmd/clusterawsadm/cmd/gc/enable.go:75-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/gc/disable.go:74` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:231— controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:231-241 | controlplane/rosa/controllers/rosacontrolplane_controller.go:205-215 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) exp/webhooks/awsmanagedmachinepool_webhook.go:169— exp/webhooks/awsmanagedmachinepool_webhook.go:169-179 | exp/webhooks/awsmanagedmachinepool_webhook.go:214-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `exp/webhooks/awsmanagedmachinepool_webhook.go:169` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `exp/webhooks/awsmanagedmachinepool_webhook.go:181` calls `Validate` and `exp/webhooks/awsmanagedmachinepool_webhook.go:226` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) pkg/cloud/scope/clients.go:157— pkg/cloud/scope/clients.go:157-167 | pkg/cloud/scope/clients.go:178-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/scope/clients.go:157` 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 (11 lines × 2) pkg/cloud/services/ec2/launchtemplate.go:561— pkg/cloud/services/ec2/launchtemplate.go:561-571 | pkg/cloud/services/ec2/launchtemplate.go:1185-1195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) pkg/cloud/services/network/vpc.go:100— pkg/cloud/services/network/vpc.go:100-110 | pkg/cloud/services/network/vpc.go:158-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/network/vpc.go:100` it begins part-way through the construct above it, 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 (11 lines × 2) pkg/cloud/services/secretsmanager/secret.go:77— pkg/cloud/services/secretsmanager/secret.go:77-87 | pkg/cloud/services/ssm/secret.go:85-95 — `pkg/cloud/services/secretsmanager/secret.go` and `pkg/cloud/services/ssm/secret.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 35 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 `pkg/cloud/services/secretsmanager/secret.go:77` 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 (11 lines × 2) cmd/clusterawsadm/cmd/controller/credentials/common.go:23— cmd/clusterawsadm/cmd/controller/credentials/common.go:23-39 | cmd/clusterawsadm/cmd/controller/rollout/common.go:24-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) controlplane/rosa/controllers/rosacontrolplane_controller.go:1664— controlplane/rosa/controllers/rosacontrolplane_controller.go:1664-1674 | exp/controllers/rosanetwork_controller.go:313-323 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) pkg/cloud/services/ec2/instances.go:1469— pkg/cloud/services/ec2/instances.go:1469-1479 | pkg/cloud/services/ec2/launchtemplate.go:1305-1315 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) pkg/rosa/ocmrole/ocmrole.go:192— pkg/rosa/ocmrole/ocmrole.go:192-202 | pkg/rosa/ocmrole/ocmrole.go:216-227 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/rosa/ocmrole/ocmrole.go:192` it begins part-way through the construct above it, 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 (11 lines × 2) pkg/cloud/services/eks/nodegroup.go:56— pkg/cloud/services/eks/nodegroup.go:56-66 | pkg/cloud/services/eks/nodegroup.go:263-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/nodegroup.go:56` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) controllers/awscluster_controller.go:172— controllers/awscluster_controller.go:172-180 | controllers/awsmanagedcluster_controller.go:72-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `controllers/awscluster_controller.go:169` calls `Default` and `controllers/awsmanagedcluster_controller.go:69` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) controllers/awsmanagedcluster_controller.go:128— controllers/awsmanagedcluster_controller.go:128-135 | controllers/rosacluster_controller.go:163-170 — before extracting anything, compare `controllers/awsmanagedcluster_controller.go` and `controllers/rosacluster_controller.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/awsmanagedcluster_controller.go:128` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `controllers/awsmanagedcluster_controller.go:127` calls `WithEventFilter`, `ResourceIsNotExternallyManaged`, `GetScheme` and `controllers/rosacluster_controller.go:162` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) controlplane/rosa/controllers/rosacontrolplane_controller.go:123— controlplane/rosa/controllers/rosacontrolplane_controller.go:123-130 | exp/controllers/rosanetwork_controller.go:329-336 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `controlplane/rosa/controllers/rosacontrolplane_controller.go:123` 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 (8 lines × 2) exp/controllers/awsfargatepool_controller.go:90— exp/controllers/awsfargatepool_controller.go:90-97 | exp/controllers/awsmanagedmachinepool_controller.go:129-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `exp/controllers/awsfargatepool_controller.go:90` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: `exp/controllers/awsmanagedmachinepool_controller.go:129` is reached only past a guard at line 125 that tests `r.Client` and leaves the function early, and `exp/controllers/awsfargatepool_controller.go:90` reads `r.Client` with no such check. What separates these copies is not which lines they run but which PRECONDITION they enforce, so one of them is operating on state the other one refuses. Decide which is intended BEFORE unifying them — extract the shared part and whichever copy is missing the check keeps running unchecked, and if the guard is the correct behaviour then that hole is already live.
Duplicated block (8 lines × 2) exp/controllers/awsmanagedmachinepool_controller.go:185— exp/controllers/awsmanagedmachinepool_controller.go:185-192 | exp/controllers/rosamachinepool_controller.go:217-224 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `exp/controllers/awsmanagedmachinepool_controller.go:185` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) pkg/cloud/services/iamauth/reconcile.go:120— pkg/cloud/services/iamauth/reconcile.go:120-127 | pkg/cloud/services/iamauth/reconcile.go:154-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/iamauth/reconcile.go:120` 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 (8 lines × 2) pkg/cloud/services/securitygroup/securitygroups.go:1004— pkg/cloud/services/securitygroup/securitygroups.go:1004-1011 | pkg/cloud/services/securitygroup/securitygroups.go:1026-1033 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/securitygroup/securitygroups.go:1004` it begins part-way through the construct above it, 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 (8 lines × 2) webhooks/awsclustercontrolleridentity_webhook.go:63— webhooks/awsclustercontrolleridentity_webhook.go:63-70 | webhooks/awsclustercontrolleridentity_webhook.go:100-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `webhooks/awsclustercontrolleridentity_webhook.go:63` it begins part-way through the construct above it, 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 (8 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:101— bootstrap/eks/controllers/eksconfig_controller.go:101-108 | bootstrap/eks/controllers/nodeadmconfig_controller.go:98-105 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:101` it begins part-way through the construct above it, 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 (8 lines × 2) pkg/cloud/scope/machinepool.go:142— pkg/cloud/scope/machinepool.go:142-149 | pkg/cloud/scope/managednodegroup.go:346-353 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/scope/machinepool.go:142` 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 (8 lines × 2) pkg/cloud/scope/rosamachinepool.go:212— pkg/cloud/scope/rosamachinepool.go:212-219 | pkg/cloud/scope/rosanetwork.go:129-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) pkg/cloud/scope/fargate.go:68— pkg/cloud/scope/fargate.go:68-75 | pkg/cloud/scope/managednodegroup.go:87-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/scope/fargate.go:68` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) pkg/cloud/services/eks/fargate.go:308— pkg/cloud/services/eks/fargate.go:308-315 | pkg/cloud/services/eks/nodegroup.go:131-138 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/fargate.go:308` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
TooManyMethods: Service pkg/cloud/services/network/service.go:28— TooManyMethods — 83 methods, declared across 12 files: network/routetables.go (18), network/eips.go (13), network/vpc.go (12), REDACTED (10), +8 more file(s). The bar is 30 methods; this is 53 over it, 2.77× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Service pkg/cloud/services/ec2/service.go:31— TooManyMethods — 64 methods, declared across 7 files: ec2/instances.go (27), ec2/launchtemplate.go (18), ec2/dedicatedhosts.go (7), ec2/ami.go (4), +3 more file(s). The bar is 30 methods; this is 34 over it, 2.13× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ManagedControlPlaneScope pkg/cloud/scope/managedcontrolplane.go:117— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Service pkg/cloud/services/eks/service.go:100— TooManyMethods — 55 methods, declared across 11 files: eks/cluster.go (16), eks/accessentry.go (8), eks/config.go (8), eks/addons.go (5), +7 more file(s). The bar is 30 methods; this is 25 over it, 1.83× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ClusterScope pkg/cloud/scope/cluster.go:97— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Service pkg/cloud/services/elb/service.go:36— TooManyMethods — 45 methods, declared across 2 files: elb/loadbalancer.go (44), elb/eip.go (1). The bar is 30 methods; this is 15 over it, 1.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MachineScope pkg/cloud/scope/machine.go:92— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AWSMachineReconciler controllers/awsmachine_controller.go:87— TooManyMethods — 41 methods, declared across 4 files: controllers/awsmachine_controller.go (32), controllers/awsmachine_annotations.go (4), controllers/awsmachine_tags.go (3), controllers/awsmachine_security_groups.go (2). The bar is 30 methods; this is 11 over it, 1.37× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ManagedMachinePoolScope pkg/cloud/scope/managednodegroup.go:126— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Template cmd/clusterawsadm/cloudformation/bootstrap/template.go:58— TooManyMethods — 32 methods, declared across 13 files: bootstrap/cluster_api_controller.go (7), bootstrap/cluster_api_node.go (5), bootstrap/user.go (3), bootstrap/cloud_provider_integration_control_plane.go (2), +9 more file(s). The bar is 30 methods; this is 2 over it, 1.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MachinePoolScope pkg/cloud/scope/machinepool.go:47— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ocmclient pkg/rosa/ocmclient.go:31— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. Most of these members implement rosa.OCMClient (32 of 32 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
MethodTooLong: Service.ReconcileLaunchTemplate pkg/cloud/services/ec2/launchtemplate.go:68— MethodTooLong — ReconcileLaunchTemplate runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Template.ControllersPolicyEKS cmd/clusterawsadm/cloudformation/bootstrap/cluster_api_controller.go:348— MethodTooLong — ControllersPolicyEKS runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Service.CreateInstance pkg/cloud/services/ec2/instances.go:121— MethodTooLong — CreateInstance runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Service.getSecurityGroupIngressRules pkg/cloud/services/securitygroup/securitygroups.go:580— MethodTooLong — getSecurityGroupIngressRules runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AWSMachineReconciler.reconcileNormal controllers/awsmachine_controller.go:534— MethodTooLong — reconcileNormal runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Service.createSubnet REDACTED:520— MethodTooLong — createSubnet runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ROSAControlPlaneReconciler.reconcileNormal controlplane/rosa/controllers/rosacontrolplane_controller.go:273— MethodTooLong — reconcileNormal runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Service.reconcileSubnets REDACTED:51— MethodTooLong — reconcileSubnets runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AWSMachinePoolReconciler.reconcileNormal exp/controllers/awsmachinepool_controller.go:276— MethodTooLong — reconcileNormal runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Service.runInstance pkg/cloud/services/ec2/instances.go:593— MethodTooLong — runInstance runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Template.ControllersPolicy cmd/clusterawsadm/cloudformation/bootstrap/cluster_api_controller.go:78— MethodTooLong — ControllersPolicy runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Template.RenderCloudFormation cmd/clusterawsadm/cloudformation/bootstrap/template.go:77— MethodTooLong — RenderCloudFormation runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (5 lines × 2) controllers/awscluster_controller.go:182— controllers/awscluster_controller.go:182-186 | controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:241-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) pkg/cloud/services/ec2/instances.go:836— pkg/cloud/services/ec2/instances.go:836-840 | pkg/cloud/services/ec2/instances.go:1193-1198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/ec2/instances.go:836` 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 (5 lines × 2) pkg/cloud/services/elb/loadbalancer.go:771— pkg/cloud/services/elb/loadbalancer.go:771-775 | pkg/cloud/services/elb/loadbalancer.go:877-881 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/elb/loadbalancer.go:771` it begins part-way through the construct above it, 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 (5 lines × 2) pkg/cloud/services/elb/loadbalancer.go:1637— pkg/cloud/services/elb/loadbalancer.go:1637-1641 | pkg/cloud/services/elb/loadbalancer.go:1677-1681 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/elb/loadbalancer.go:1637` 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 (5 lines × 2) api/v1beta1/tags.go:238— api/v1beta1/tags.go:238-242 | api/v1beta2/tags.go:242-246 — `api/v1beta1/tags.go` and `api/v1beta2/tags.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 62 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.
Duplicated block (5 lines × 2) REDACTED:36— REDACTED:36-40 | pkg/cloud/services/userdata/utils.go:40-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Check import visibility before settling on that home: `REDACTED` sits under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
Duplicated block (5 lines × 2) cmd/clusterawsadm/cmd/eks/addons/list_available.go:44— cmd/clusterawsadm/cmd/eks/addons/list_available.go:44-48 | cmd/clusterawsadm/cmd/eks/addons/list_installed.go:44-48 — before extracting anything, compare `cmd/clusterawsadm/cmd/eks/addons/list_available.go` and `cmd/clusterawsadm/cmd/eks/addons/list_installed.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/eks/addons/list_available.go:44` it begins part-way through the construct above it, 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 (5 lines × 2) main.go:323— main.go:323-327 | main.go:518-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main.go:323` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `main.go:322` calls `GetEventRecorderFor` and `main.go:517` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) REDACTED:100— REDACTED:100-104 | REDACTED:106-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) controllers/awsmachine_controller.go:1165— controllers/awsmachine_controller.go:1165-1169 | controllers/awsmachine_controller.go:1190-1194 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/awsmachine_controller.go:1165` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) exp/webhooks/awsmachinepool_webhook.go:208— exp/webhooks/awsmachinepool_webhook.go:208-212 | exp/webhooks/awsmachinepool_webhook.go:277-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `exp/webhooks/awsmachinepool_webhook.go:206` calls `validateRootVolume`, `validateNonRootVolumes` and `exp/webhooks/awsmachinepool_webhook.go:276` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:432— bootstrap/eks/controllers/eksconfig_controller.go:432-440 | bootstrap/eks/controllers/nodeadmconfig_controller.go:355-363 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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 × 2) cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:90— cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:90-98 | cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:137-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:90` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:83` calls `Examples` and `cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:132` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) controlplane/eks/REDACTED:65— controlplane/eks/REDACTED:65-73 | controlplane/eks/REDACTED:164-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `controlplane/eks/REDACTED:65` it begins part-way through the construct above it, 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 (9 lines × 2) pkg/cloud/services/network/vpc.go:334— pkg/cloud/services/network/vpc.go:334-342 | pkg/cloud/services/network/vpc.go:361-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/network/vpc.go:334` 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) controlplane/eks/api/v1beta1/validate.go:27— controlplane/eks/api/v1beta1/validate.go:27-35 | controlplane/eks/api/v1beta2/validate.go:27-35 — `controlplane/eks/api/v1beta1/validate.go` and `controlplane/eks/api/v1beta2/validate.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 67 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.
Duplicated block (9 lines × 2) exp/api/v1beta1/types.go:240— exp/api/v1beta1/types.go:240-248 | exp/api/v1beta2/types.go:357-365 — `exp/api/v1beta1/types.go` and `exp/api/v1beta2/types.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 125 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.
Duplicated block (9 lines × 2) pkg/cloud/scope/machinepool.go:175— pkg/cloud/scope/machinepool.go:175-183 | pkg/cloud/scope/managednodegroup.go:275-283 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) pkg/cloud/services/secretsmanager/secret.go:124— pkg/cloud/services/secretsmanager/secret.go:124-132 | pkg/cloud/services/ssm/secret.go:127-135 — `pkg/cloud/services/secretsmanager/secret.go` and `pkg/cloud/services/ssm/secret.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 35 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.
Duplicated block (9 lines × 2) pkg/rosa/ocmrole/ocmrole.go:243— pkg/rosa/ocmrole/ocmrole.go:243-251 | pkg/rosa/ocmrole/ocmrole.go:277-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/rosa/ocmrole/ocmrole.go:243` it begins part-way through the construct above it, 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 (6 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:199— bootstrap/eks/controllers/eksconfig_controller.go:199-204 | bootstrap/eks/controllers/nodeadmconfig_controller.go:208-213 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:199` 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 (6 lines × 2) pkg/cloud/scope/cluster.go:139— pkg/cloud/scope/cluster.go:139-144 | pkg/cloud/scope/managedcontrolplane.go:195-200 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `pkg/cloud/scope/cluster.go:147` calls `SecurityGroupOverrides` and `pkg/cloud/scope/managedcontrolplane.go:203` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) pkg/cloud/scope/cluster.go:421— pkg/cloud/scope/cluster.go:421-426 | pkg/cloud/scope/managedcontrolplane.go:482-487 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) pkg/cloud/scope/machine.go:198— pkg/cloud/scope/machine.go:198-203 | pkg/cloud/scope/machinepool.go:199-204 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) REDACTED:145— REDACTED:145-150 | REDACTED:151-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:145` it begins part-way through the construct above it, 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 (6 lines × 2) cmd/clusterawsadm/cloudformation/service/service.go:141— cmd/clusterawsadm/cloudformation/service/service.go:141-146 | cmd/clusterawsadm/cloudformation/service/service.go:163-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cloudformation/service/service.go:141` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) pkg/cloud/services/network/vpc.go:349— pkg/cloud/services/network/vpc.go:349-354 | pkg/cloud/services/network/vpc.go:376-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/network/vpc.go:349` it begins part-way through the construct above it, 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 (6 lines × 2) main.go:338— main.go:338-343 | main.go:443-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main.go:338` 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 (6 lines × 2) REDACTED:77— REDACTED:77-82 | webhooks/awsmachinetemplate_webhook.go:241-246 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
FileTooLong: elb/loadbalancer.go pkg/cloud/services/elb/loadbalancer.go— FileTooLong — 1207 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: Service (44 blocks, 75-1897). The bar is 500 significant lines; this is 707 over it, 2.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: controllers/rosacontrolplane_controller.go controlplane/rosa/controllers/rosacontrolplane_controller.go— FileTooLong — 1052 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: ROSAControlPlaneReconciler (22 blocks, 104-1714). The bar is 500 significant lines; this is 552 over it, 2.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ec2/instances.go pkg/cloud/services/ec2/instances.go— FileTooLong — 877 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: Service (27 blocks, 53-1566). The bar is 500 significant lines; this is 377 over it, 1.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: controllers/awsmachine_controller.go controllers/awsmachine_controller.go— FileTooLong — 822 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: AWSMachineReconciler (33 blocks, 87-1390). The bar is 500 significant lines; this is 322 over it, 1.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ec2/launchtemplate.go pkg/cloud/services/ec2/launchtemplate.go— FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: Service (18 blocks, 68-1253). The bar is 500 significant lines; this is 218 over it, 1.44× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: securitygroup/securitygroups.go pkg/cloud/services/securitygroup/securitygroups.go— FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: Service (25 blocks, 60-1080). The bar is 500 significant lines; this is 144 over it, 1.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: eks/cluster.go pkg/cloud/services/eks/cluster.go— FileTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: Service (16 blocks, 49-923). The bar is 500 significant lines; this is 118 over it, 1.24× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ./main.go main.go— FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (13 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:416— bootstrap/eks/controllers/eksconfig_controller.go:416-428 | bootstrap/eks/controllers/nodeadmconfig_controller.go:339-351 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:416` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) controlplane/eks/REDACTED:37— controlplane/eks/REDACTED:37-49 | controlplane/eks/REDACTED:136-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `controlplane/eks/REDACTED:37` it begins part-way through the construct above it, 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 (13 lines × 2) controlplane/rosa/controllers/rosacontrolplane_controller.go:277— controlplane/rosa/controllers/rosacontrolplane_controller.go:277-289 | exp/controllers/rosamachinepool_controller.go:236-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `controlplane/rosa/controllers/rosacontrolplane_controller.go:277` it begins part-way through the construct above it, 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) pkg/cloud/services/network/secondarycidr.go:33— pkg/cloud/services/network/secondarycidr.go:33-45 | pkg/cloud/services/network/secondarycidr.go:87-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/network/secondarycidr.go:33` 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 (13 lines × 2) pkg/cloud/scope/rosacontrolplane.go:167— pkg/cloud/scope/rosacontrolplane.go:167-179 | pkg/cloud/scope/rosaroleconfig.go:147-159 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) exp/controllers/rosaocmroleconfig_controller.go:409— exp/controllers/rosaocmroleconfig_controller.go:409-421 | exp/controllers/rosaroleconfig_controller.go:571-583 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) cmd/clusterawsadm/cmd/eks/addons/list_available.go:122— cmd/clusterawsadm/cmd/eks/addons/list_available.go:122-134 | cmd/clusterawsadm/cmd/eks/addons/list_installed.go:126-138 — before extracting anything, compare `cmd/clusterawsadm/cmd/eks/addons/list_available.go` and `cmd/clusterawsadm/cmd/eks/addons/list_installed.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×7
Discarded error (assigned to `_`, then its result used) pkg/cloud/services/ec2/ami.go:275— `firstTime, _ := time.Parse(createDateTimestampFormat, aws.ToString(i[k].CreationDate))` writes the call's error to `_` and then uses `firstTime` as if the call succeeded. When `time.Parse` fails, `firstTime` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `firstTime` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) pkg/cloud/services/ec2/ami.go:276— `secondTime, _ := time.Parse(createDateTimestampFormat, aws.ToString(i[j].CreationDate))` writes the call's error to `_` and then uses `secondTime` as if the call succeeded. When `time.Parse` fails, `secondTime` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `secondTime` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) pkg/cloud/services/ec2/bastion.go:173— `userData, _ := userdata.NewBastion(&userdata.BastionInput{})` writes the call's error to `_` and then uses `userData` as if the call succeeded. When `userdata.NewBastion` fails, `userData` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `userData` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:254— `a, _ := parseSemver(minors[i])` writes the call's error to `_` and then uses `a` as if the call succeeded. When `parseSemver` fails, `a` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `a` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:255— `b, _ := parseSemver(minors[j])` writes the call's error to `_` and then uses `b` as if the call succeeded. When `parseSemver` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:273— `a, _ := parseSemver(patches[i])` writes the call's error to `_` and then uses `a` as if the call succeeded. When `parseSemver` fails, `a` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `a` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) hack/tools/release-tools/internal/ami/k8sreleases/detect_k8s_release.go:274— `b, _ := parseSemver(patches[j])` writes the call's error to `_` and then uses `b` as if the call succeeded. When `parseSemver` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×6
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×6
Edited copy of a member (8 corresponding lines) api/v1beta1/network_types.go:319— api/v1beta1/network_types.go:319-326 | api/v1beta2/network_types.go:831-841 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) cmd/clusterawsadm/api/ami/v1beta1/scheme/scheme.go:32— cmd/clusterawsadm/api/ami/v1beta1/scheme/scheme.go:32-39 | cmd/clusterawsadm/api/bootstrap/v1alpha1/scheme/scheme.go:32-39 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) controlplane/rosa/webhooks/rosacontrolplane_webhook.go:172— controlplane/rosa/webhooks/rosacontrolplane_webhook.go:172-179 | exp/webhooks/rosamachinepool_webhook.go:133-143 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) cmd/clusterawsadm/printers/printers.go:97— cmd/clusterawsadm/printers/printers.go:97-104 | hack/tools/release-tools/printer/printer.go:114-121 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) api/v1beta1/network_types.go:287— api/v1beta1/network_types.go:287-294 | api/v1beta2/network_types.go:779-786 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) controllers/awsmachine_annotations.go:42— controllers/awsmachine_annotations.go:42-54 | pkg/annotations/annotations.go:25-32 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (19 lines × 2) bootstrap/eks/internal/userdata/node.go:111— bootstrap/eks/internal/userdata/node.go:111-129 | bootstrap/eks/internal/userdata/nodeadm.go:209-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) cmd/clusterawsadm/cmd/ami/common/copy.go:52— cmd/clusterawsadm/cmd/ami/common/copy.go:52-70 | cmd/clusterawsadm/cmd/ami/common/encryptedcopy.go:69-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/ami/common/copy.go:52` 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 (19 lines × 2) controllers/awsmachinetemplate_controller.go:512— controllers/awsmachinetemplate_controller.go:512-530 | controllers/awsmachinetemplate_controller.go:537-555 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/awsmachinetemplate_controller.go:512` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) controlplane/eks/api/v1beta1/types.go:50— controlplane/eks/api/v1beta1/types.go:50-68 | controlplane/eks/api/v1beta2/types.go:51-69 — `controlplane/eks/api/v1beta1/types.go` and `controlplane/eks/api/v1beta2/types.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 150 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.
Duplicated block (19 lines × 2) pkg/cloud/services/eks/addons.go:106— pkg/cloud/services/eks/addons.go:106-124 | pkg/cloud/services/eks/addons.go:149-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/addons.go:106` 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 (19 lines × 2) api/v1beta1/network_types.go:490— api/v1beta1/network_types.go:490-508 | api/v1beta2/network_types.go:1065-1083 — `api/v1beta1/network_types.go` and `api/v1beta2/network_types.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 132 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.
Duplicated block (14 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:110— bootstrap/eks/controllers/eksconfig_controller.go:110-123 | bootstrap/eks/controllers/nodeadmconfig_controller.go:107-120 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:110` it begins part-way through the construct above it, 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) controllers/awsmanagedcluster_controller.go:170— controllers/awsmanagedcluster_controller.go:170-183 | controllers/rosacluster_controller.go:205-218 — before extracting anything, compare `controllers/awsmanagedcluster_controller.go` and `controllers/rosacluster_controller.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/awsmanagedcluster_controller.go:170` it begins part-way through the construct above it, 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 (14 lines × 2) controlplane/rosa/webhooks/rosacontrolplane_webhook.go:55— controlplane/rosa/webhooks/rosacontrolplane_webhook.go:55-68 | controlplane/rosa/webhooks/rosacontrolplane_webhook.go:125-138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) pkg/cloud/services/iamauth/crd.go:36— pkg/cloud/services/iamauth/crd.go:36-49 | pkg/cloud/services/iamauth/crd.go:72-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/iamauth/crd.go:36` 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 (14 lines × 2) pkg/cloud/services/eks/cluster.go:978— pkg/cloud/services/eks/cluster.go:978-991 | pkg/cloud/services/eks/cluster.go:992-1005 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/cluster.go:978` it begins part-way through the construct above it, 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 (14 lines × 2) controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:525— controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:525-538 | controlplane/rosa/controllers/rosacontrolplane_controller.go:1686-1699 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:525` it begins part-way through the construct above it, 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 (12 lines × 2) pkg/cloud/services/ec2/instances.go:919— pkg/cloud/services/ec2/instances.go:919-930 | pkg/cloud/services/ec2/instances.go:936-947 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) REDACTED:441— REDACTED:441-452 | REDACTED:468-479 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) pkg/cloud/services/elb/loadbalancer.go:1099— pkg/cloud/services/elb/loadbalancer.go:1099-1110 | pkg/cloud/services/elb/loadbalancer.go:1124-1135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/elb/loadbalancer.go:1099` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) api/v1beta1/groupversion_info.go:27— api/v1beta1/groupversion_info.go:27-38 | exp/api/v1beta1/groupversion_info.go:27-38 — before extracting anything, compare `api/v1beta1/groupversion_info.go` and `exp/api/v1beta1/groupversion_info.go` as WHOLE FILES: 96% 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 (12 lines × 2) api/v1beta1/tags.go:58— api/v1beta1/tags.go:58-69 | api/v1beta2/tags.go:51-62 — `api/v1beta1/tags.go` and `api/v1beta2/tags.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 62 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.
Duplicated block (12 lines × 2) hack/tools/ami/delete_amis.py:110— hack/tools/ami/delete_amis.py:110-121 | hack/tools/ami/list_amis.py:70-81 — before extracting anything, compare `hack/tools/ami/delete_amis.py` and `hack/tools/ami/list_amis.py` as WHOLE FILES: 89% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Outbound HTTP without resilience cmd/clusterawsadm/ami/helper.go:73— `http.Get(` 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 cmd/clusterawsadm/ami/helper.go:149— `http.Get(` 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 cmd/clusterawsadm/ami/helper.go:171— `http.Get(` 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 hack/boskos.py:61— `requests.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 hack/boskos.py:72— `requests.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 pkg/cloud/services/eks/service.go:129— `http.DefaultClient` 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.
Hotspot: pkg/cloud/services/ec2/instances.go pkg/cloud/services/ec2/instances.go:121— pkg/cloud/services/ec2/instances.go changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in Service.CreateInstance at line 121. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 14:14:21 +00:00' --until='2026-11-16 14:14:21 +00:00' --full-history --no-merges -- pkg/cloud/services/ec2/instances.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: exp/controllers/rosamachinepool_controller.go exp/controllers/rosamachinepool_controller.go:523— exp/controllers/rosamachinepool_controller.go changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in controllers.nodePoolBuilder at line 523. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 14:14:21 +00:00' --until='2026-11-16 14:14:21 +00:00' --full-history --no-merges -- exp/controllers/rosamachinepool_controller.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: controlplane/rosa/controllers/rosacontrolplane_controller.go controlplane/rosa/controllers/rosacontrolplane_controller.go:273— controlplane/rosa/controllers/rosacontrolplane_controller.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in ROSAControlPlaneReconciler.reconcileNormal at line 273. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 14:14:21 +00:00' --until='2026-11-16 14:14:21 +00:00' --full-history --no-merges -- controlplane/rosa/controllers/rosacontrolplane_controller.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: controllers/awsmachinetemplate_controller.go controllers/awsmachinetemplate_controller.go:283— controllers/awsmachinetemplate_controller.go changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AWSMachineTemplateReconciler.getNodeInfo at line 283. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 14:14:21 +00:00' --until='2026-11-16 14:14:21 +00:00' --full-history --no-merges -- controllers/awsmachinetemplate_controller.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: pkg/cloud/services/ec2/launchtemplate.go pkg/cloud/services/ec2/launchtemplate.go:1075— pkg/cloud/services/ec2/launchtemplate.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Service.DiscoverLaunchTemplateAMI at line 1075. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 14:14:21 +00:00' --until='2026-11-16 14:14:21 +00:00' --full-history --no-merges -- pkg/cloud/services/ec2/launchtemplate.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×5
Edited copy of a member (21 corresponding lines) REDACTED:174— REDACTED:174-194 | webhooks/awsmachinetemplate_webhook.go:120-141 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) pkg/cloud/services/securitygroup/securitygroups.go:996— pkg/cloud/services/securitygroup/securitygroups.go:996-1016 | pkg/cloud/services/securitygroup/securitygroups.go:1018-1038 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) cmd/clusterawsadm/cmd/eks/addons/list_available.go:33— cmd/clusterawsadm/cmd/eks/addons/list_available.go:33-53 | cmd/clusterawsadm/cmd/eks/addons/list_installed.go:33-53 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) pkg/eks/identityprovider/procedures.go:43— pkg/eks/identityprovider/procedures.go:43-67 | pkg/eks/identityprovider/procedures.go:80-100 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) pkg/cloud/services/iamauth/configmap.go:47— pkg/cloud/services/iamauth/configmap.go:47-67 | pkg/cloud/services/iamauth/configmap.go:69-89 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×5
Edited copy of a member (15 corresponding lines) pkg/cloud/services/iamauth/reconcile.go:181— pkg/cloud/services/iamauth/reconcile.go:181-195 | pkg/cloud/services/iamauth/reconcile.go:197-211 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) pkg/cloud/services/awsnode/cni.go:172— pkg/cloud/services/awsnode/cni.go:172-186 | pkg/cloud/services/ec2/instances.go:532-554 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) exp/controllers/awsmachinepool_controller.go:708— exp/controllers/awsmachinepool_controller.go:708-722 | exp/controllers/awsmanagedmachinepool_controller.go:311-328 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) controllers/awsmachine_annotations.go:59— controllers/awsmachine_annotations.go:59-73 | pkg/cloud/services/ec2/launchtemplate.go:377-391 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) pkg/cloud/converters/eks.go:185— pkg/cloud/converters/eks.go:185-201 | pkg/cloud/converters/eks.go:204-218 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) REDACTED:55— REDACTED:55-67 | REDACTED:69-81 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) iam/api/v1beta1/types.go:112— iam/api/v1beta1/types.go:112-124 | iam/api/v1beta1/types.go:133-145 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) pkg/cloud/services/secretsmanager/secret.go:90— pkg/cloud/services/secretsmanager/secret.go:90-105 | pkg/cloud/services/secretsmanager/secret.go:108-120 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) cmd/clusterawsadm/api/ami/v1beta1/register.go:26— cmd/clusterawsadm/api/ami/v1beta1/register.go:26-38 | cmd/clusterawsadm/api/bootstrap/v1beta1/register.go:26-38 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) pkg/cloud/scope/managedcontrolplane.go:58— pkg/cloud/scope/managedcontrolplane.go:58-70 | pkg/cloud/scope/managednodegroup.go:48-63 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×5
Edited copy of a member (12 corresponding lines) exp/controlleridentitycreator/awscontrolleridentity_controller.go:132— exp/controlleridentitycreator/awscontrolleridentity_controller.go:132-147 | exp/controllers/awsfargatepool_controller.go:53-64 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) pkg/eks/addons/procedures.go:49— pkg/eks/addons/procedures.go:49-61 | pkg/eks/addons/procedures.go:229-240 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) REDACTED:107— REDACTED:107-118 | REDACTED:120-131 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) cmd/clusterawsadm/cloudformation/bootstrap/managed_nodegroup.go:26— cmd/clusterawsadm/cloudformation/bootstrap/managed_nodegroup.go:26-38 | cmd/clusterawsadm/cloudformation/bootstrap/fargate.go:26-37 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) bootstrap/eks/api/v1beta1/groupversion_info.go:27— bootstrap/eks/api/v1beta1/groupversion_info.go:27-38 | controlplane/eks/api/v1beta1/groupversion_info.go:27-38 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Swallowed exception (caught, then discarded) pkg/cloud/throttle/throttle.go:98— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) pkg/cloud/services/instancestate/rule.go:220— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) pkg/cloud/services/instancestate/rule.go:225— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) pkg/cloud/services/instancestate/rule.go:241— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) pkg/cloud/scope/machine.go:142— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
TooManyFields: RosaControlPlaneSpec controlplane/rosa/api/v1beta2/rosacontrolplane_types.go:132— TooManyFields — 38 stored fields. The bar is 30 stored fields; this is 8 over it, 1.27× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: AWSMachineSpec api/v1beta2/awsmachine_types.go:80— TooManyFields — 37 stored fields. The bar is 30 stored fields; this is 7 over it, 1.23× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Instance api/v1beta2/types.go:190— TooManyFields — 37 stored fields. The bar is 30 stored fields; this is 7 over it, 1.23× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: AWSManagedControlPlaneSpec controlplane/eks/api/v1beta2/awsmanagedcontrolplane_types.go:36— TooManyFields — 35 stored fields beside 1 method. The bar is 30 stored fields; this is 5 over it, 1.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) controllers/awsmanagedcluster_controller.go:118— controllers/awsmanagedcluster_controller.go:118-151 | controllers/rosacluster_controller.go:153-186 | controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:168-197 | controlplane/rosa/controllers/rosacontrolplane_controller.go:116-176 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:86— controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:86-125 | controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:128-206 | controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:57-88 | controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:91-166 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) pkg/cloud/converters/tags.go:115— pkg/cloud/converters/tags.go:115-131 | pkg/cloud/converters/tags.go:134-150 | pkg/cloud/converters/tags.go:153-169 | pkg/cloud/converters/tags.go:183-199 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) pkg/cloud/services/network/egress_only_gateways.go:176— pkg/cloud/services/network/egress_only_gateways.go:176-187 | pkg/cloud/services/network/gateways.go:173-184 | pkg/cloud/services/network/natgateways.go:245-256 | pkg/cloud/services/network/vpc.go:668-679 — These 4 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 4 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 4 times.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×4
Edited copy of a member (33 corresponding lines) pkg/cloud/services/secretsmanager/secret.go:55— pkg/cloud/services/secretsmanager/secret.go:55-87 | pkg/cloud/services/ssm/secret.go:56-95 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) pkg/cloud/services/instancestate/rule.go:180— pkg/cloud/services/instancestate/rule.go:180-212 | pkg/cloud/services/instancestate/rule.go:216-255 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) pkg/cloud/services/elb/loadbalancer.go:125— pkg/cloud/services/elb/loadbalancer.go:125-157 | pkg/cloud/services/elb/loadbalancer.go:619-653 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) pkg/cloud/services/eks/fargate.go:48— pkg/cloud/services/eks/fargate.go:48-88 | pkg/cloud/services/eks/fargate.go:165-197 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) exp/webhooks/awsmachinepool_webhook.go:195— exp/webhooks/awsmachinepool_webhook.go:195-227 | REDACTED:69-90 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) pkg/cloud/services/eks/cluster.go:546— pkg/cloud/services/eks/cluster.go:546-567 | pkg/cloud/services/eks/nodegroup.go:630-652 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) pkg/eks/addons/procedures.go:75— pkg/eks/addons/procedures.go:75-96 | pkg/eks/addons/procedures.go:145-171 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) cmd/clusterawsadm/cmd/bootstrap/iam/root.go:26— cmd/clusterawsadm/cmd/bootstrap/iam/root.go:26-47 | cmd/clusterawsadm/cmd/controller/controller.go:29-50 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×4
Edited copy of a member (14 corresponding lines) pkg/cloud/services/eks/service.go:119— pkg/cloud/services/eks/service.go:119-139 | pkg/cloud/services/eks/service.go:154-167 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) pkg/cloud/scope/machinepool.go:280— pkg/cloud/scope/machinepool.go:280-293 | pkg/cloud/scope/managednodegroup.go:217-230 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) pkg/cloud/services/elb/loadbalancer.go:1598— pkg/cloud/services/elb/loadbalancer.go:1598-1611 | pkg/cloud/services/elb/loadbalancer.go:1613-1626 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) pkg/cloud/services/iamauth/configmap.go:177— pkg/cloud/services/iamauth/configmap.go:177-190 | pkg/cloud/services/iamauth/configmap.go:192-205 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) pkg/cloud/services/eks/fargate.go:305— pkg/cloud/services/eks/fargate.go:305-315 | pkg/cloud/services/eks/nodegroup.go:128-138 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) api/v1beta1/network_types.go:359— api/v1beta1/network_types.go:359-369 | api/v1beta2/network_types.go:893-903 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) pkg/cloud/services/elb/loadbalancer.go:1959— pkg/cloud/services/elb/loadbalancer.go:1959-1969 | pkg/cloud/services/gc/loadbalancer.go:268-278 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) exp/controllers/rosaocmroleconfig_controller.go:51— exp/controllers/rosaocmroleconfig_controller.go:51-61 | exp/controllers/rosaroleconfig_controller.go:61-74 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
FixmeComment pkg/cloud/services/ec2/launchtemplate.go:973— // FIXME(dlipovetsky): This will include the core security groups as well, making the — 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.
FixmeComment pkg/cloud/services/ec2/launchtemplate.go:1013— // FIXME(dlipovetsky): This check should account for changed userdata, but does not yet do so. — 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.
FixmeComment exp/controllers/awsmachinepool_controller.go:358— // FIXME(dlipovetsky,sedefsavas): If the controller terminates, or the StartASGInstanceRefresh returns an error, — 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· Edited copy of a member (39 corresponding lines) · ×3
Edited copy of a member (39 corresponding lines) pkg/cloud/services/elb/loadbalancer.go:1628— pkg/cloud/services/elb/loadbalancer.go:1628-1666 | pkg/cloud/services/elb/loadbalancer.go:1668-1706 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) pkg/cloud/scope/cluster.go:56— pkg/cloud/scope/cluster.go:56-94 | pkg/cloud/scope/managedcontrolplane.go:74-114 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) exp/controllers/awsfargatepool_controller.go:182— exp/controllers/awsfargatepool_controller.go:182-223 | exp/controllers/rosamachinepool_controller.go:671-709 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×3
Edited copy of a member (35 corresponding lines) bootstrap/eks/controllers/eksconfig_controller.go:299— bootstrap/eks/controllers/eksconfig_controller.go:299-333 | bootstrap/eks/controllers/nodeadmconfig_controller.go:289-325 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) pkg/cloud/services/iamauth/crd.go:35— pkg/cloud/services/iamauth/crd.go:35-69 | pkg/cloud/services/iamauth/crd.go:71-105 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) api/v1beta1/network_types.go:242— api/v1beta1/network_types.go:242-276 | api/v1beta2/network_types.go:622-704 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×3
Edited copy of a member (27 corresponding lines) pkg/cloud/services/network/carriergateways.go:85— pkg/cloud/services/network/carriergateways.go:85-111 | pkg/cloud/services/network/egress_only_gateways.go:86-119 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) exp/webhooks/awsmachinepool_webhook.go:66— exp/webhooks/awsmachinepool_webhook.go:66-92 | REDACTED:343-369 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) cmd/clusterawsadm/cloudformation/service/service.go:77— cmd/clusterawsadm/cloudformation/service/service.go:77-108 | cmd/clusterawsadm/cloudformation/service/service.go:111-137 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) pkg/cloud/services/gc/loadbalancer.go:211— pkg/cloud/services/gc/loadbalancer.go:211-237 | pkg/cloud/services/gc/loadbalancer.go:240-265 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) exp/webhooks/awsmachinepool_webhook.go:268— exp/webhooks/awsmachinepool_webhook.go:268-293 | exp/webhooks/rosamachinepool_webhook.go:38-67 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) controllers/awsmachine_tags.go:42— controllers/awsmachine_tags.go:42-67 | pkg/cloud/services/ec2/launchtemplate.go:347-374 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) pkg/cloud/services/network/routetables.go:246— pkg/cloud/services/network/routetables.go:246-264 | REDACTED:499-518 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) pkg/cloud/scope/clients.go:135— pkg/cloud/scope/clients.go:135-153 | pkg/cloud/scope/clients.go:156-174 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) api/v1beta1/tags.go:251— api/v1beta1/tags.go:251-269 | api/v1beta2/tags.go:255-275 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) cmd/clusterawsadm/api/bootstrap/v1alpha1/defaults.go:97— cmd/clusterawsadm/api/bootstrap/v1alpha1/defaults.go:97-106 | cmd/clusterawsadm/api/bootstrap/v1beta1/defaults.go:112-121 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) pkg/cloud/services/autoscaling/autoscalinggroup.go:482— pkg/cloud/services/autoscaling/autoscalinggroup.go:482-491 | pkg/cloud/services/autoscaling/autoscalinggroup.go:494-503 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) webhooks/awsmachinetemplate_webhook.go:107— webhooks/awsmachinetemplate_webhook.go:107-118 | REDACTED:478-487 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (40 lines × 2) cmd/clusterawsadm/api/bootstrap/v1alpha1/defaults.go:54— cmd/clusterawsadm/api/bootstrap/v1alpha1/defaults.go:54-93 | cmd/clusterawsadm/api/bootstrap/v1beta1/defaults.go:65-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (40 lines × 2) controlplane/eks/api/v1beta1/conditions_consts.go:21— controlplane/eks/api/v1beta1/conditions_consts.go:21-60 | controlplane/eks/api/v1beta2/conditions_consts.go:21-60 — `controlplane/eks/api/v1beta1/conditions_consts.go` and `controlplane/eks/api/v1beta2/conditions_consts.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 1 separate duplicated blocks between them, totalling at least 40 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.
Duplicated block (40 lines × 2) exp/api/v1beta1/types.go:154— exp/api/v1beta1/types.go:154-193 | exp/api/v1beta2/types.go:206-245 — `exp/api/v1beta1/types.go` and `exp/api/v1beta2/types.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 125 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 `exp/api/v1beta1/types.go:154` it begins part-way through the construct above it, 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 (15 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:379— bootstrap/eks/controllers/eksconfig_controller.go:379-393 | bootstrap/eks/controllers/nodeadmconfig_controller.go:446-460 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:379` 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 (15 lines × 2) exp/REDACTED:67— exp/REDACTED:67-81 | exp/REDACTED:136-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) pkg/cloud/services/secretsmanager/secret.go:57— pkg/cloud/services/secretsmanager/secret.go:57-71 | pkg/cloud/services/ssm/secret.go:58-72 — `pkg/cloud/services/secretsmanager/secret.go` and `pkg/cloud/services/ssm/secret.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 35 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.
Duplicated block (7 lines × 3) cmd/clusterawsadm/cmd/gc/configure.go:74— cmd/clusterawsadm/cmd/gc/configure.go:74-80 | cmd/clusterawsadm/cmd/gc/disable.go:73-79 | cmd/clusterawsadm/cmd/gc/enable.go:74-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/gc/configure.go:74` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cmd/clusterawsadm/cmd/gc/configure.go:81` calls `Flags`, `StringSliceVar` and `cmd/clusterawsadm/cmd/gc/disable.go:81` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) pkg/cloud/services/iamauth/reconcile.go:137— pkg/cloud/services/iamauth/reconcile.go:137-143 | pkg/cloud/services/iamauth/reconcile.go:183-189 | pkg/cloud/services/iamauth/reconcile.go:199-205 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) pkg/cloud/scope/cluster.go:314— pkg/cloud/scope/cluster.go:314-320 | pkg/cloud/scope/fargate.go:138-144 | pkg/cloud/scope/managedcontrolplane.go:305-311 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) pkg/cloud/services/awsnode/cni.go:49— pkg/cloud/services/awsnode/cni.go:49-53 | pkg/cloud/services/iamauth/reconcile.go:39-43 | pkg/cloud/services/kubeproxy/reconcile.go:41-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) main.go:338— main.go:338-343 | main.go:397-401 | main.go:443-448 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main.go:338` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `main.go:337` calls `GetEventRecorderFor` and `main.go:396` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) main.go:277— main.go:277-281 | main.go:287-291 | main.go:526-530 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main.go:277` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `main.go:276` calls `GetEventRecorderFor` and `main.go:525` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) pkg/cloud/services/network/service.go:34— pkg/cloud/services/network/service.go:34-39 | pkg/cloud/services/secretsmanager/service.go:46-51 | pkg/cloud/services/ssm/service.go:48-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 3) pkg/cloud/services/eks/cluster.go:595— pkg/cloud/services/eks/cluster.go:595-600 | pkg/cloud/services/eks/cluster.go:636-643 | pkg/cloud/services/eks/cluster.go:667-672 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/cluster.go:595` it begins part-way through the construct above it, 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) exp/webhooks/awsmachinepool_webhook.go:98— exp/webhooks/awsmachinepool_webhook.go:98-103 | REDACTED:428-433 | webhooks/awsmachinetemplate_webhook.go:86-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `exp/webhooks/awsmachinepool_webhook.go:98` 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.
Low cohesion: EKSConfigReconciler (LCOM4 5) bootstrap/eks/controllers/eksconfig_controller.go:60— EKSConfigReconciler's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NodeadmConfigReconciler (LCOM4 5) bootstrap/eks/controllers/nodeadmconfig_controller.go:57— NodeadmConfigReconciler's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AWSMachineTemplateReconciler (LCOM4 5) controllers/awsmachinetemplate_controller.go:67— AWSMachineTemplateReconciler's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×2
Focus outline removed in CSS without a :focus replacement docs/book/theme/css/general.css:48— `.page` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/book/theme/css/general.css:406— `details.collapse-code summary:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
IngressRule.Equals (cognitive 16) api/v1beta1/network_types.go:511— IngressRule.Equals has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3, boolean chains 2, match/switch 1 (nesting depth added 3). 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.
IngressRule.Equals (cognitive 16) api/v1beta2/network_types.go:1086— IngressRule.Equals has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3, boolean chains 2, match/switch 1 (nesting depth added 3). 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.
ClassTooLong: AWSMachineReconciler controllers/awsmachine_controller.go:87— ClassTooLong — 761 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods, 33 blocks, lines 87-1390. The bar is 400 significant lines; this is 361 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ROSAControlPlaneReconciler controlplane/rosa/controllers/rosacontrolplane_controller.go:104— ClassTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods, 22 blocks, lines 104-1714. The bar is 400 significant lines; this is 341 over it, 1.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FunctionTooLong: main.main main.go:137— FunctionTooLong — main runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: controllers.buildOCMClusterSpec controlplane/rosa/controllers/rosacontrolplane_controller.go:1357— FunctionTooLong — buildOCMClusterSpec runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×2
Edited copy of a member (45 corresponding lines) pkg/cloud/services/network/vpc.go:569— pkg/cloud/services/network/vpc.go:569-618 | pkg/cloud/services/network/vpc.go:622-666 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (45 corresponding lines) cmd/clusterawsadm/api/bootstrap/v1alpha1/defaults.go:50— cmd/clusterawsadm/api/bootstrap/v1alpha1/defaults.go:50-94 | cmd/clusterawsadm/api/bootstrap/v1beta1/defaults.go:61-109 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×2
Edited copy of a member (60 corresponding lines) api/v1beta1/network_types.go:511— api/v1beta1/network_types.go:511-570 | api/v1beta2/network_types.go:1086-1145 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (60 corresponding lines) api/v1beta1/tags.go:141— api/v1beta1/tags.go:141-200 | api/v1beta2/tags.go:134-204 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×2
Edited copy of a member (40 corresponding lines) bootstrap/eks/REDACTED:28— bootstrap/eks/REDACTED:28-69 | bootstrap/eks/REDACTED:97-136 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) controlplane/eks/api/v1beta1/conditions_consts.go:21— controlplane/eks/api/v1beta1/conditions_consts.go:21-60 | controlplane/eks/api/v1beta2/conditions_consts.go:21-67 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×2
Edited copy of a member (36 corresponding lines) hack/tools/ami/delete_amis.py:99— hack/tools/ami/delete_amis.py:99-141 | hack/tools/ami/list_amis.py:62-97 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) pkg/cloud/scope/machine.go:54— pkg/cloud/scope/machine.go:54-89 | pkg/cloud/scope/machinepool.go:80-122 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×2
Edited copy of a member (41 corresponding lines) exp/webhooks/awsmanagedmachinepool_webhook.go:152— exp/webhooks/awsmanagedmachinepool_webhook.go:152-192 | exp/webhooks/awsmanagedmachinepool_webhook.go:195-235 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (41 corresponding lines) api/v1beta1/network_types.go:439— api/v1beta1/network_types.go:439-479 | api/v1beta2/network_types.go:997-1054 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) cmd/clusterawsadm/cloudformation/service/service.go:139— cmd/clusterawsadm/cloudformation/service/service.go:139-159 | cmd/clusterawsadm/cloudformation/service/service.go:161-180 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) pkg/cloud/services/eks/fargate.go:199— pkg/cloud/services/eks/fargate.go:199-218 | pkg/cloud/services/eks/nodegroup.go:46-66 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) pkg/cloud/services/network/carriergateways.go:130— pkg/cloud/services/network/carriergateways.go:130-146 | pkg/cloud/services/network/gateways.go:155-171 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) api/v1beta1/awsclustertemplate_conversion.go:27— api/v1beta1/awsclustertemplate_conversion.go:27-43 | exp/REDACTED:205-222 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) bootstrap/eks/controllers/eksconfig_controller.go:404— bootstrap/eks/controllers/eksconfig_controller.go:404-428 | bootstrap/eks/controllers/nodeadmconfig_controller.go:327-351 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) hack/tools/ami/delete_amis.py:11— hack/tools/ami/delete_amis.py:11-40 | hack/tools/ami/list_amis.py:11-35 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) pkg/cloud/scope/clients.go:198— pkg/cloud/scope/clients.go:198-215 | pkg/cloud/scope/clients.go:240-255 | pkg/cloud/scope/clients.go:321-336 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) webhooks/awsclustercontrolleridentity_webhook.go:55— webhooks/awsclustercontrolleridentity_webhook.go:55-76 | webhooks/awsclusterroleidentity_webhook.go:53-73 | webhooks/awsclusterstaticidentity_webhook.go:53-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) pkg/cloud/services/ec2/launchtemplate.go:521— pkg/cloud/services/ec2/launchtemplate.go:521-545 | pkg/cloud/services/ec2/launchtemplate.go:819-836 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:503— controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:503-520 | controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:526-543 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (63 lines × 2) controllers/awsmachine_tags.go:90— controllers/awsmachine_tags.go:90-152 | pkg/cloud/services/ec2/launchtemplate.go:426-488 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (63 lines × 2) controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.go:216— controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.go:216-278 | controlplane/eks/api/v1beta2/awsmanagedcontrolplane_types.go:351-413 — `controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.go` and `controlplane/eks/api/v1beta2/awsmanagedcontrolplane_types.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 1 separate duplicated blocks between them, totalling at least 63 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 `controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.go:216` 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 (52 lines × 2) api/v1beta1/conditions_consts.go:21— api/v1beta1/conditions_consts.go:21-72 | api/v1beta2/conditions_consts.go:21-72 — `api/v1beta1/conditions_consts.go` and `api/v1beta2/conditions_consts.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 2 separate duplicated blocks between them, totalling at least 96 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 `api/v1beta1/conditions_consts.go:21` 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 (52 lines × 2) api/v1beta1/network_types.go:513— api/v1beta1/network_types.go:513-564 | api/v1beta2/network_types.go:1088-1139 — `api/v1beta1/network_types.go` and `api/v1beta2/network_types.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 132 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 `api/v1beta1/network_types.go:513` 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 transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (33 lines × 2) pkg/cloud/services/elb/loadbalancer.go:455— pkg/cloud/services/elb/loadbalancer.go:455-487 | pkg/cloud/services/elb/loadbalancer.go:1262-1294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/elb/loadbalancer.go:455` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (33 lines × 2) bootstrap/eks/api/v1beta1/eksconfigtemplate_types.go:24— bootstrap/eks/api/v1beta1/eksconfigtemplate_types.go:24-57 | bootstrap/eks/api/v1beta2/eksconfigtemplate_types.go:24-56 — `bootstrap/eks/api/v1beta1/eksconfigtemplate_types.go` and `bootstrap/eks/api/v1beta2/eksconfigtemplate_types.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 1 separate duplicated blocks between them, totalling at least 34 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.
Duplicated block (29 lines × 2) controlplane/eks/api/v1beta1/validate.go:39— controlplane/eks/api/v1beta1/validate.go:39-67 | controlplane/eks/api/v1beta2/validate.go:39-67 — `controlplane/eks/api/v1beta1/validate.go` and `controlplane/eks/api/v1beta2/validate.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 67 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.
Duplicated block (29 lines × 2) controlplane/eks/api/v1beta1/validate.go:71— controlplane/eks/api/v1beta1/validate.go:71-99 | controlplane/eks/api/v1beta2/validate.go:71-99 — `controlplane/eks/api/v1beta1/validate.go` and `controlplane/eks/api/v1beta2/validate.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 67 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.
Duplicated block (25 lines × 2) exp/controllers/awsmanagedmachinepool_controller.go:344— exp/controllers/awsmanagedmachinepool_controller.go:344-368 | exp/controllers/rosamachinepool_controller.go:685-709 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `exp/controllers/awsmanagedmachinepool_controller.go:344` 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 (25 lines × 2) pkg/cloud/services/iamauth/crd.go:109— pkg/cloud/services/iamauth/crd.go:109-133 | pkg/cloud/services/iamauth/crd.go:137-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/iamauth/crd.go:109` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–24 lines × 2) cmd/clusterawsadm/cmd/ami/common/copy.go:77— cmd/clusterawsadm/cmd/ami/common/copy.go:77-99 | cmd/clusterawsadm/cmd/ami/common/encryptedcopy.go:96-119 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/ami/common/copy.go:77` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cmd/clusterawsadm/cmd/ami/common/encryptedcopy.go:120` calls `addKmsKeyIDFlag` and `cmd/clusterawsadm/cmd/ami/common/copy.go:100` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23–24 lines × 2) pkg/cloud/services/eks/config.go:118— pkg/cloud/services/eks/config.go:118-141 | pkg/cloud/services/eks/config.go:175-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:266— bootstrap/eks/controllers/eksconfig_controller.go:266-286 | bootstrap/eks/controllers/nodeadmconfig_controller.go:369-389 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:266` 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 (21 lines × 2) pkg/cloud/services/ec2/instances.go:777— pkg/cloud/services/ec2/instances.go:777-797 | pkg/cloud/services/ec2/launchtemplate.go:734-754 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/ec2/instances.go:777` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) exp/webhooks/awsmachinepool_webhook.go:98— exp/webhooks/awsmachinepool_webhook.go:98-117 | webhooks/awsmachinetemplate_webhook.go:86-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `exp/webhooks/awsmachinepool_webhook.go:98` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (20 lines × 2) hack/tools/ami/delete_amis.py:44— hack/tools/ami/delete_amis.py:44-63 | hack/tools/ami/list_amis.py:39-58 — before extracting anything, compare `hack/tools/ami/delete_amis.py` and `hack/tools/ami/list_amis.py` as WHOLE FILES: 89% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) exp/controllers/awsfargatepool_controller.go:184— exp/controllers/awsfargatepool_controller.go:184-200 | exp/controllers/awsmanagedmachinepool_controller.go:332-348 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) api/v1beta1/awscluster_conversion.go:92— api/v1beta1/awscluster_conversion.go:92-108 | api/v1beta1/awscluster_conversion.go:115-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `api/v1beta1/awscluster_conversion.go:92` it begins part-way through the construct above it, 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 (16 lines × 2) cmd/clusterawsadm/cloudformation/service/service.go:78— cmd/clusterawsadm/cloudformation/service/service.go:78-93 | cmd/clusterawsadm/cloudformation/service/service.go:112-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cloudformation/service/service.go:78` 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 (16 lines × 2) pkg/cloud/services/network/vpc.go:603— pkg/cloud/services/network/vpc.go:603-618 | pkg/cloud/services/network/vpc.go:651-666 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/network/vpc.go:603` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
X2 · Cancellation propagation· Function without context.Context · ×2
Function without context.Context: LatestPatchRelease cmd/clusterawsadm/ami/helper.go:67— `LatestPatchRelease` calls `http.Get(…)` 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: latestStableRelease cmd/clusterawsadm/ami/helper.go:148— `latestStableRelease` calls `http.Get(…)` 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, …)`.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard docs/book/theme/css/general.css:55— `.js .page-wrapper` moves (`transition: margin-left 0.3s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Service.ReconcileLaunchTemplate (cyclomatic 58) pkg/cloud/services/ec2/launchtemplate.go:68— Service.ReconcileLaunchTemplate has cyclomatic complexity 58 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.CreateInstance (cyclomatic 41) pkg/cloud/services/ec2/instances.go:121— Service.CreateInstance has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachineReconciler.reconcileNormal (cyclomatic 40) controllers/awsmachine_controller.go:534— AWSMachineReconciler.reconcileNormal has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.reconcileSubnets (cyclomatic 40) REDACTED:51— Service.reconcileSubnets has cyclomatic complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.createSubnet (cyclomatic 37) REDACTED:520— Service.createSubnet has cyclomatic complexity 37 (threshold 15). Of this number, 27 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSCluster.ConvertTo (cyclomatic 36) api/v1beta1/awscluster_conversion.go:28— AWSCluster.ConvertTo has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSCluster.validateNetwork (cyclomatic 32) webhooks/awscluster_webhook.go:319— AWSCluster.validateNetwork has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.runInstance (cyclomatic 31) pkg/cloud/services/ec2/instances.go:593— Service.runInstance has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
controllers.buildOCMClusterSpec (cyclomatic 30) controlplane/rosa/controllers/rosacontrolplane_controller.go:1357— controllers.buildOCMClusterSpec has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ROSAControlPlaneReconciler.reconcileNormal (cyclomatic 30) controlplane/rosa/controllers/rosacontrolplane_controller.go:273— ROSAControlPlaneReconciler.reconcileNormal has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.SDKToLaunchTemplate (cyclomatic 30) pkg/cloud/services/ec2/launchtemplate.go:910— Service.SDKToLaunchTemplate has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSCluster.validateControlPlaneLBs (cyclomatic 30) webhooks/awscluster_webhook.go:403— AWSCluster.validateControlPlaneLBs has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachinePoolReconciler.reconcileNormal (cyclomatic 29) exp/controllers/awsmachinepool_controller.go:276— AWSMachinePoolReconciler.reconcileNormal has cyclomatic complexity 29 (threshold 15). Of this number, 25 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
main.main (cyclomatic 29) main.go:137— main.main has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ROSAControlPlaneReconciler.reconcileExternalAuthProviders (cyclomatic 27) controlplane/rosa/controllers/rosacontrolplane_controller.go:984— ROSAControlPlaneReconciler.reconcileExternalAuthProviders has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ROSAControlPlane.validateRosaRoleConfig (cyclomatic 27) controlplane/rosa/webhooks/rosacontrolplane_webhook.go:240— ROSAControlPlane.validateRosaRoleConfig has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.ReconcileSecurityGroups (cyclomatic 27) pkg/cloud/services/securitygroup/securitygroups.go:60— Service.ReconcileSecurityGroups has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ocmrole.checkRoleExists (cyclomatic 27) pkg/rosa/ocmrole/ocmrole.go:163— ocmrole.checkRoleExists has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachineReconciler.reconcileDelete (cyclomatic 26) controllers/awsmachine_controller.go:331— AWSMachineReconciler.reconcileDelete has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.getSecurityGroupIngressRules (cyclomatic 26) pkg/cloud/services/securitygroup/securitygroups.go:580— Service.getSecurityGroupIngressRules has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.findSubnet (cyclomatic 25) pkg/cloud/services/ec2/instances.go:355— Service.findSubnet has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSCluster.ValidateUpdate (cyclomatic 25) webhooks/awscluster_webhook.go:94— AWSCluster.ValidateUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.ReconcileCNI (cyclomatic 24) pkg/cloud/services/awsnode/cni.go:46— Service.ReconcileCNI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ROSAControlPlaneReconciler.updateOCMClusterSpec (cyclomatic 23) controlplane/rosa/controllers/rosacontrolplane_controller.go:867— ROSAControlPlaneReconciler.updateOCMClusterSpec has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.DeleteNetwork (cyclomatic 23) pkg/cloud/services/network/network.go:103— Service.DeleteNetwork has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.reconcileVPC (cyclomatic 23) pkg/cloud/services/network/vpc.go:49— Service.reconcileVPC has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachineTemplateReconciler.Reconcile (cyclomatic 22) controllers/awsmachinetemplate_controller.go:118— AWSMachineTemplateReconciler.Reconcile has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
webhooks.validateNetwork (cyclomatic 22) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:584— webhooks.validateNetwork has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
controllers.nodePoolBuilder (cyclomatic 22) exp/controllers/rosamachinepool_controller.go:523— controllers.nodePoolBuilder has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ROSAMachinePoolReconciler.reconcileNormal (cyclomatic 22) exp/controllers/rosamachinepool_controller.go:229— ROSAMachinePoolReconciler.reconcileNormal has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NodeadmConfigReconciler.joinWorker (cyclomatic 21) bootstrap/eks/controllers/nodeadmconfig_controller.go:151— NodeadmConfigReconciler.joinWorker has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.reconcileCluster (cyclomatic 21) pkg/cloud/services/eks/cluster.go:49— Service.reconcileCluster has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
userdata.NewNodeadmUserdata (cyclomatic 20) bootstrap/eks/internal/userdata/nodeadm.go:167— userdata.NewNodeadmUserdata has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ROSAMachinePoolReconciler.Reconcile (cyclomatic 20) exp/controllers/rosamachinepool_controller.go:118— ROSAMachinePoolReconciler.Reconcile has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.reconcileVPCEndpoints (cyclomatic 20) pkg/cloud/services/network/vpc.go:197— Service.reconcileVPCEndpoints has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ocmrole.GetOrCreateOCMRole (cyclomatic 20) pkg/rosa/ocmrole/ocmrole.go:74— ocmrole.GetOrCreateOCMRole has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
main.setupReconcilersAndWebhooks (cyclomatic 19) main.go:363— main.setupReconcilersAndWebhooks has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NodegroupService.createNodegroup (cyclomatic 19) pkg/cloud/services/eks/nodegroup.go:193— NodegroupService.createNodegroup has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NodegroupService.reconcileNodegroupVersion (cyclomatic 19) pkg/cloud/services/eks/nodegroup.go:320— NodegroupService.reconcileNodegroupVersion has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.getAPIServerLBSpec (cyclomatic 19) pkg/cloud/services/elb/loadbalancer.go:370— Service.getAPIServerLBSpec has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
boilerplate.file_passes (cyclomatic 19) hack/boilerplate/boilerplate.py:72— boilerplate.file_passes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EKSConfigReconciler.joinWorker (cyclomatic 18) bootstrap/eks/controllers/eksconfig_controller.go:154— EKSConfigReconciler.joinWorker has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSMachineReconciler.Reconcile (cyclomatic 18) controllers/awsmachine_controller.go:165— AWSMachineReconciler.Reconcile has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSMachineTemplateReconciler.getNodeInfo (cyclomatic 18) controllers/awsmachinetemplate_controller.go:283— AWSMachineTemplateReconciler.getNodeInfo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSManagedControlPlane.ConvertTo (cyclomatic 18) controlplane/eks/REDACTED:28— AWSManagedControlPlane.ConvertTo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSManagedControlPlane.ConvertFrom (cyclomatic 18) controlplane/eks/REDACTED:133— AWSManagedControlPlane.ConvertFrom has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachinePoolReconciler.Reconcile (cyclomatic 18) exp/controllers/awsmachinepool_controller.go:124— AWSMachinePoolReconciler.Reconcile has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSMachinePoolReconciler.updatePool (cyclomatic 18) exp/controllers/awsmachinepool_controller.go:567— AWSMachinePoolReconciler.updatePool has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.DiscoverLaunchTemplateAMI (cyclomatic 18) pkg/cloud/services/ec2/launchtemplate.go:1075— Service.DiscoverLaunchTemplateAMI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.createVPC (cyclomatic 18) pkg/cloud/services/network/vpc.go:424— Service.createVPC has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachineTemplate.validateHostAllocation (cyclomatic 18) webhooks/awsmachinetemplate_webhook.go:176— AWSMachineTemplate.validateHostAllocation has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AWSMachineTemplateReconciler.getKubernetesVersion (cyclomatic 17) controllers/awsmachinetemplate_controller.go:405— AWSMachineTemplateReconciler.getKubernetesVersion has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSManagedControlPlaneReconciler.reconcileNormal (cyclomatic 17) controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:309— AWSManagedControlPlaneReconciler.reconcileNormal has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ec2.getInstanceMarketOptionsRequest (cyclomatic 17) pkg/cloud/services/ec2/instances.go:1328— ec2.getInstanceMarketOptionsRequest has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.createCluster (cyclomatic 17) pkg/cloud/services/eks/cluster.go:434— Service.createCluster has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NodegroupService.reconcileNodegroupConfig (cyclomatic 17) pkg/cloud/services/eks/nodegroup.go:440— NodegroupService.reconcileNodegroupConfig has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.reconcileTargetGroupsAndListeners (cyclomatic 17) pkg/cloud/services/elb/loadbalancer.go:1710— Service.reconcileTargetGroupsAndListeners has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.reconcileRules (cyclomatic 17) pkg/cloud/services/instancestate/rule.go:44— Service.reconcileRules has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.getDefaultSubnets (cyclomatic 17) REDACTED:295— Service.getDefaultSubnets has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.ensureManagedVPCAttributes (cyclomatic 17) pkg/cloud/services/network/vpc.go:322— Service.ensureManagedVPCAttributes has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AWSMachine.validateHostAllocationUpdate (cyclomatic 17) REDACTED:539— AWSMachine.validateHostAllocationUpdate has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
S3Bucket.Validate (cyclomatic 16) api/v1beta2/s3bucket.go:34— S3Bucket.Validate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EKSConfigReconciler.Reconcile (cyclomatic 16) bootstrap/eks/controllers/eksconfig_controller.go:73— EKSConfigReconciler.Reconcile has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NodeadmConfigReconciler.Reconcile (cyclomatic 16) bootstrap/eks/controllers/nodeadmconfig_controller.go:70— NodeadmConfigReconciler.Reconcile has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSManagedControlPlaneReconciler.Reconcile (cyclomatic 16) controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:216— AWSManagedControlPlaneReconciler.Reconcile has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSMachinePool.ConvertTo (cyclomatic 16) exp/REDACTED:28— AWSMachinePool.ConvertTo has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSManagedMachinePoolReconciler.Reconcile (cyclomatic 16) exp/controllers/awsmanagedmachinepool_controller.go:96— AWSManagedMachinePoolReconciler.Reconcile has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ROSAOCMRoleConfigReconciler.reconcileDelete (cyclomatic 16) exp/controllers/rosaocmroleconfig_controller.go:283— ROSAOCMRoleConfigReconciler.reconcileDelete has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ROSARoleConfigReconciler.Reconcile (cyclomatic 16) exp/controllers/rosaroleconfig_controller.go:123— ROSARoleConfigReconciler.Reconcile has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
main.setupEKSReconcilersAndWebhooks (cyclomatic 16) main.go:480— main.setupEKSReconcilersAndWebhooks has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.SDKToAutoScalingGroup (cyclomatic 16) pkg/cloud/services/autoscaling/autoscalinggroup.go:46— Service.SDKToAutoScalingGroup has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Service.shouldEnablePrimaryIpv6 (cyclomatic 16) pkg/cloud/services/ec2/instances.go:1508— Service.shouldEnablePrimaryIpv6 has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IAMService.EnsureTagsAndPolicy (cyclomatic 16) REDACTED:234— IAMService.EnsureTagsAndPolicy has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Service.describeVpcSubnets (cyclomatic 16) REDACTED:432— Service.describeVpcSubnets has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Deprecated module: github.com/aws/aws-sdk-go-v2/feature/s3/manager — `github.com/aws/aws-sdk-go-v2/feature/s3/manager` is required at v1.23.10 in REDACTED, and its author has DEPRECATED the module: "superceded by feature/s3/transfermanager. See https://github.com/aws/aws-sdk-go-v2/discussions/3306" A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×1
Dependency pinned to a stale untagged commit: github.com/google/goexpect — Direct dependency `github.com/google/goexpect` is required at `v0.0.0-20210430020637-ab937bf7fd6f` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2021-04-30, 5.5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/google/goexpect` and has not moved this requirement in 5.5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/google/goexpect` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Repeated repair: pkg/cloud/identity/identity.go pkg/cloud/identity/identity.go:68— pkg/cloud/identity/identity.go changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is identity.GetAssumeRoleCredentialsCache at line 68), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: digest the provider gob payload instead of appending to it”; “fix: include region in role principal hash”; “fix: include source provider in role principal hash”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 14:14:21 +00:00' --until='2026-11-16 14:14:21 +00:00' --full-history --no-merges -- pkg/cloud/identity/identity.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
HackComment pkg/rosa/helpers.go:56— // Hack to always display the correct terms and conditions message — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Service.ReconcileLaunchTemplate (cognitive 82) pkg/cloud/services/ec2/launchtemplate.go:68— Service.ReconcileLaunchTemplate has cognitive complexity 82 (threshold 15). Drivers by points: if/else 39 (72 pts), boolean chains 8, match/switch 1 (2 pts) (nesting depth added 34). 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.
Service.reconcileSubnets (cognitive 81) REDACTED:51— Service.reconcileSubnets has cognitive complexity 81 (threshold 15). Drivers by points: if/else 30 (68 pts), loops 5 (10 pts), boolean chains 3 (nesting depth added 43). Of this number, 78 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
AWSCluster.validateControlPlaneLBs (cognitive 68) webhooks/awscluster_webhook.go:403— AWSCluster.validateControlPlaneLBs has cognitive complexity 68 (threshold 15). Drivers by points: if/else 25 (62 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 39). 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.
AWSCluster.ConvertTo (cognitive 62) api/v1beta1/awscluster_conversion.go:28— AWSCluster.ConvertTo has cognitive complexity 62 (threshold 15). Drivers by points: if/else 29 (54 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 27). 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.
Service.CreateInstance (cognitive 59) pkg/cloud/services/ec2/instances.go:121— Service.CreateInstance has cognitive complexity 59 (threshold 15). Drivers by points: if/else 32 (51 pts), loops 2 (4 pts), boolean chains 3, match/switch 1 (nesting depth added 21). 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.
AWSMachineReconciler.reconcileNormal (cognitive 57) controllers/awsmachine_controller.go:534— AWSMachineReconciler.reconcileNormal has cognitive complexity 57 (threshold 15). Drivers by points: if/else 33 (53 pts), boolean chains 3, match/switch 1 (nesting depth added 20). 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.
Service.createSubnet (cognitive 57) REDACTED:520— Service.createSubnet has cognitive complexity 57 (threshold 15). Drivers by points: if/else 27 (46 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 22). Of this number, 35 points are the body's own statements and 22 belong to 5 function literals inside it that branch. 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.
ROSAControlPlaneReconciler.reconcileNormal (cognitive 53) controlplane/rosa/controllers/rosacontrolplane_controller.go:273— ROSAControlPlaneReconciler.reconcileNormal has cognitive complexity 53 (threshold 15). Drivers by points: if/else 26 (49 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 24). 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.
AWSCluster.validateNetwork (cognitive 52) webhooks/awscluster_webhook.go:319— AWSCluster.validateNetwork has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (43 pts), boolean chains 6, loops 3 (nesting depth added 22). 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.
ROSAControlPlaneReconciler.reconcileExternalAuthProviders (cognitive 51) controlplane/rosa/controllers/rosacontrolplane_controller.go:984— ROSAControlPlaneReconciler.reconcileExternalAuthProviders has cognitive complexity 51 (threshold 15). Drivers by points: if/else 25 (47 pts), loops 3 (4 pts) (nesting depth added 23). 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.
Service.ReconcileSecurityGroups (cognitive 49) pkg/cloud/services/securitygroup/securitygroups.go:60— Service.ReconcileSecurityGroups has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (44 pts), loops 3, boolean chains 2 (nesting depth added 23). Of this number, 40 points are the body's own statements and 9 belong to 3 function literals inside it that branch. 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.
ocmrole.checkRoleExists (cognitive 49) pkg/rosa/ocmrole/ocmrole.go:163— ocmrole.checkRoleExists has cognitive complexity 49 (threshold 15). Drivers by points: if/else 23 (48 pts), match/switch 1 (nesting depth added 25). 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.
controllers.buildOCMClusterSpec (cognitive 47) controlplane/rosa/controllers/rosacontrolplane_controller.go:1357— controllers.buildOCMClusterSpec has cognitive complexity 47 (threshold 15). Drivers by points: if/else 27 (41 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 17). 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.
Service.runInstance (cognitive 47) pkg/cloud/services/ec2/instances.go:593— Service.runInstance has cognitive complexity 47 (threshold 15). Drivers by points: if/else 25 (35 pts), loops 5 (11 pts), boolean chains 1 (nesting depth added 16). 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.
Service.findSubnet (cognitive 46) pkg/cloud/services/ec2/instances.go:355— Service.findSubnet has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (36 pts), boolean chains 5, loops 2 (4 pts), match/switch 1 (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AWSMachineReconciler.reconcileDelete (cognitive 45) controllers/awsmachine_controller.go:331— AWSMachineReconciler.reconcileDelete has cognitive complexity 45 (threshold 15). Drivers by points: if/else 19 (39 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 22). 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.
Service.getSecurityGroupIngressRules (cognitive 45) pkg/cloud/services/securitygroup/securitygroups.go:580— Service.getSecurityGroupIngressRules has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (37 pts), loops 3 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 25). 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.
Service.ReconcileCNI (cognitive 43) pkg/cloud/services/awsnode/cni.go:46— Service.ReconcileCNI has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (37 pts), loops 4 (6 pts) (nesting depth added 20). 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.
Service.reconcileVPC (cognitive 41) pkg/cloud/services/network/vpc.go:49— Service.reconcileVPC has cognitive complexity 41 (threshold 15). Drivers by points: if/else 23 (41 pts) (nesting depth added 18). Of this number, 36 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
main.main (cognitive 40) main.go:137— main.main has cognitive complexity 40 (threshold 15). Drivers by points: if/else 28 (40 pts) (nesting depth added 12). Of this number, 37 points are the body's own statements and 3 belong to 2 function literals inside it that branch. 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.
Service.SDKToLaunchTemplate (cognitive 37) pkg/cloud/services/ec2/launchtemplate.go:910— Service.SDKToLaunchTemplate has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 13). 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.
Service.reconcileTargetGroupsAndListeners (cognitive 37) pkg/cloud/services/elb/loadbalancer.go:1710— Service.reconcileTargetGroupsAndListeners has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (31 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 21). 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.
AWSMachinePoolReconciler.reconcileNormal (cognitive 36) exp/controllers/awsmachinepool_controller.go:276— AWSMachinePoolReconciler.reconcileNormal has cognitive complexity 36 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 1, loops 1 (nesting depth added 8). Of this number, 32 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Service.reconcileVPCEndpoints (cognitive 36) pkg/cloud/services/network/vpc.go:197— Service.reconcileVPCEndpoints has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (29 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 17). 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.
ami.List (cognitive 35) cmd/clusterawsadm/ami/list.go:45— ami.List has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 4 (8 pts) (nesting depth added 18). 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.
ROSAMachinePoolReconciler.reconcileNormal (cognitive 35) exp/controllers/rosamachinepool_controller.go:229— ROSAMachinePoolReconciler.reconcileNormal has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (33 pts), boolean chains 2 (nesting depth added 14). 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.
Service.getAPIServerLBSpec (cognitive 32) pkg/cloud/services/elb/loadbalancer.go:370— Service.getAPIServerLBSpec has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 4 (9 pts), boolean chains 4, jumps 1 (nesting depth added 12). 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.
AWSMachinePoolReconciler.updatePool (cognitive 31) exp/controllers/awsmachinepool_controller.go:567— AWSMachinePoolReconciler.updatePool has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 5 (10 pts), boolean chains 1 (nesting depth added 14). 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.
controllers.nodePoolBuilder (cognitive 30) exp/controllers/rosamachinepool_controller.go:523— controllers.nodePoolBuilder has cognitive complexity 30 (threshold 15). Drivers by points: if/else 21 (28 pts), loops 1 (2 pts) (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.
Service.describeVpcSubnets (cognitive 30) REDACTED:432— Service.describeVpcSubnets has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 15). 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.
webhooks.validateNetwork (cognitive 28) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:584— webhooks.validateNetwork has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 9). 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.
boilerplate.file_passes (cognitive 28) hack/boilerplate/boilerplate.py:72— boilerplate.file_passes has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 3 (6 pts), boolean chains 1, error handling 1 (nesting depth added 10). 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.
ROSAControlPlaneReconciler.updateOCMClusterSpec (cognitive 27) controlplane/rosa/controllers/rosacontrolplane_controller.go:867— ROSAControlPlaneReconciler.updateOCMClusterSpec has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (20 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Service.reconcileV2LB (cognitive 27) pkg/cloud/services/elb/loadbalancer.go:159— Service.reconcileV2LB has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 1 (nesting depth added 12). 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.
Service.updateNatGatewayIPs (cognitive 27) pkg/cloud/services/network/natgateways.go:109— Service.updateNatGatewayIPs has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 2, loops 2 (nesting depth added 14). Of this number, 23 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
Service.DeleteNetwork (cognitive 27) pkg/cloud/services/network/network.go:103— Service.DeleteNetwork has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23 (27 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
userdata.NewNodeadmUserdata (cognitive 26) bootstrap/eks/internal/userdata/nodeadm.go:167— userdata.NewNodeadmUserdata has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 1 (nesting depth added 10). 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.
ROSAClusterReconciler.syncROSAClusterNodePools (cognitive 26) controllers/rosacluster_controller.go:310— ROSAClusterReconciler.syncROSAClusterNodePools has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 14). 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.
main.setupReconcilersAndWebhooks (cognitive 26) main.go:363— main.setupReconcilersAndWebhooks has cognitive complexity 26 (threshold 15). Drivers by points: if/else 19 (26 pts) (nesting depth added 7). 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.
endpoints.ParseFlag (cognitive 26) pkg/cloud/endpoints/endpoints.go:72— endpoints.ParseFlag has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 2 (3 pts) (nesting depth added 15). 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.
Service.getInstanceAddresses (cognitive 26) pkg/cloud/services/ec2/instances.go:1050— Service.getInstanceAddresses has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 15). 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.
Service.shouldEnablePrimaryIpv6 (cognitive 26) pkg/cloud/services/ec2/instances.go:1508— Service.shouldEnablePrimaryIpv6 has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 10). 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.
Service.reconcileRouteTables (cognitive 26) pkg/cloud/services/network/routetables.go:44— Service.reconcileRouteTables has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (4 pts) (nesting depth added 14). Of this number, 21 points are the body's own statements and 5 belong to 2 function literals inside it that branch. 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.
Service.createVPC (cognitive 26) pkg/cloud/services/network/vpc.go:424— Service.createVPC has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). 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.
AWSCluster.ValidateUpdate (cognitive 26) webhooks/awscluster_webhook.go:94— AWSCluster.ValidateUpdate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 7, loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Service.reconcileClassicLoadBalancer (cognitive 25) pkg/cloud/services/elb/loadbalancer.go:655— Service.reconcileClassicLoadBalancer has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (25 pts) (nesting depth added 13). 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.
Service.getAPIServerClassicELBSpec (cognitive 25) pkg/cloud/services/elb/loadbalancer.go:1206— Service.getAPIServerClassicELBSpec has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (7 pts), boolean chains 4, jumps 1 (nesting depth added 9). 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.
NodeadmConfigReconciler.joinWorker (cognitive 24) bootstrap/eks/controllers/nodeadmconfig_controller.go:151— NodeadmConfigReconciler.joinWorker has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AWSManagedControlPlane.ConvertTo (cognitive 24) controlplane/eks/REDACTED:28— AWSManagedControlPlane.ConvertTo has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 1 (2 pts) (nesting depth added 7). 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.
AWSManagedControlPlane.ConvertFrom (cognitive 24) controlplane/eks/REDACTED:133— AWSManagedControlPlane.ConvertFrom has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 1 (2 pts) (nesting depth added 7). 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.
Service.ensureManagedVPCAttributes (cognitive 24) pkg/cloud/services/network/vpc.go:322— Service.ensureManagedVPCAttributes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 4 (nesting depth added 6). 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.
Service.DeleteBucket (cognitive 24) pkg/cloud/services/s3/s3.go:121— Service.DeleteBucket has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (6 pts), loops 2 (5 pts) (nesting depth added 14). 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.
S3Bucket.Validate (cognitive 23) api/v1beta2/s3bucket.go:34— S3Bucket.Validate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 2 (3 pts), boolean chains 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.
webhooks.validateEKSAddons (cognitive 23) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:280— webhooks.validateEKSAddons has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). 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.
ROSAMachinePoolReconciler.Reconcile (cognitive 23) exp/controllers/rosamachinepool_controller.go:118— ROSAMachinePoolReconciler.Reconcile has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 4 (nesting depth added 4). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Service.DiscoverLaunchTemplateAMI (cognitive 23) pkg/cloud/services/ec2/launchtemplate.go:1075— Service.DiscoverLaunchTemplateAMI has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 1 (nesting depth added 7). 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.
Service.reconcileCluster (cognitive 23) pkg/cloud/services/eks/cluster.go:49— Service.reconcileCluster has cognitive complexity 23 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Service.reconcileRules (cognitive 23) pkg/cloud/services/instancestate/rule.go:44— Service.reconcileRules has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 1, loops 1 (nesting depth added 6). 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.
AWSCluster.validateControlPlaneLoadBalancerUpdate (cognitive 23) webhooks/awscluster_webhook.go:194— AWSCluster.validateControlPlaneLoadBalancerUpdate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 5 (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.
scope.buildProvidersForRef (cognitive 22) pkg/cloud/scope/session.go:236— scope.buildProvidersForRef has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 1 (nesting depth added 11). 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.
IAMService.EnsureTagsAndPolicy (cognitive 22) REDACTED:234— IAMService.EnsureTagsAndPolicy has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 2, boolean chains 1 (nesting depth added 7). 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.
AWSMachineTemplateReconciler.getNodeInfo (cognitive 21) controllers/awsmachinetemplate_controller.go:283— AWSMachineTemplateReconciler.getNodeInfo has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 3, match/switch 1 (nesting depth added 5). 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.
AWSControllerIdentityReconciler.Reconcile (cognitive 21) exp/controlleridentitycreator/awscontrolleridentity_controller.go:50— AWSControllerIdentityReconciler.Reconcile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 2 (nesting depth added 7). 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.
Service.SDKToInstance (cognitive 21) pkg/cloud/services/ec2/instances.go:968— Service.SDKToInstance has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 6). 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.
Service.createCluster (cognitive 21) pkg/cloud/services/eks/cluster.go:434— Service.createCluster has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 2, loops 1 (nesting depth added 3). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Service.getManagedPodIdentityAssociations (cognitive 21) pkg/cloud/services/eks/pod_identities.go:86— Service.getManagedPodIdentityAssociations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (3 pts) (nesting depth added 13). 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.
NodegroupService.createNodegroup (cognitive 21) pkg/cloud/services/eks/nodegroup.go:193— NodegroupService.createNodegroup has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NodegroupService.reconcileNodegroupIAMRole (cognitive 21) pkg/cloud/services/eks/roles.go:173— NodegroupService.reconcileNodegroupIAMRole has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (21 pts) (nesting depth added 7). 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.
Service.getDefaultSubnets (cognitive 21) REDACTED:295— Service.getDefaultSubnets has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (20 pts), loops 1 (nesting depth added 5). 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.
AWSManagedControlPlane.validateAccessEntries (cognitive 20) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:383— AWSManagedControlPlane.validateAccessEntries has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, loops 2 (3 pts) (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.
AWSMachinePoolReconciler.Reconcile (cognitive 20) exp/controllers/awsmachinepool_controller.go:124— AWSMachinePoolReconciler.Reconcile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 1, match/switch 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ROSARoleConfigReconciler.Reconcile (cognitive 20) exp/controllers/rosaroleconfig_controller.go:123— ROSARoleConfigReconciler.Reconcile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (18 pts), loops 1 (2 pts) (nesting depth added 5). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
webhooks.validateLifecycleHooks (cognitive 20) exp/webhooks/validation.go:27— webhooks.validateLifecycleHooks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, loops 1 (nesting depth added 6). 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.
NodegroupService.reconcileNodegroup (cognitive 20) pkg/cloud/services/eks/nodegroup.go:513— NodegroupService.reconcileNodegroup has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (19 pts), match/switch 1 (nesting depth added 5). 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.
Service.getSubnetTagParams (cognitive 20) REDACTED:744— Service.getSubnetTagParams has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 1 (2 pts), boolean chains 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.
AWSMachine.validateIgnitionProxy (cognitive 20) REDACTED:244— AWSMachine.validateIgnitionProxy has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), 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.
AWSMachineTemplateReconciler.Reconcile (cognitive 19) controllers/awsmachinetemplate_controller.go:118— AWSMachineTemplateReconciler.Reconcile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSManagedControlPlaneReconciler.reconcileNormal (cognitive 19) controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:309— AWSManagedControlPlaneReconciler.reconcileNormal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (18 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AWSManagedMachinePool.ConvertTo (cognitive 19) exp/REDACTED:114— AWSManagedMachinePool.ConvertTo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 1 (nesting depth added 6). 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.
ROSAOCMRoleConfigReconciler.reconcileDelete (cognitive 19) exp/controllers/rosaocmroleconfig_controller.go:283— ROSAOCMRoleConfigReconciler.reconcileDelete has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 2 (nesting depth added 2). Of this number, 11 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AwsInstanceStateReconciler.watchQueuesForInstanceEvents (cognitive 19) exp/instancestate/awsinstancestate_controller.go:125— AwsInstanceStateReconciler.watchQueuesForInstanceEvents has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts) (nesting depth added 10). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 137). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
main.setupEKSReconcilersAndWebhooks (cognitive 19) main.go:480— main.setupEKSReconcilersAndWebhooks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
asg.ReconcileLifecycleHooks (cognitive 19) pkg/cloud/services/autoscaling/lifecyclehook.go:163— asg.ReconcileLifecycleHooks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts) (nesting depth added 9). 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.
Service.ReconcileBastion (cognitive 19) pkg/cloud/services/ec2/bastion.go:49— Service.ReconcileBastion has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (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.
Service.reconcileControlPlaneIAMRole (cognitive 19) pkg/cloud/services/eks/roles.go:73— Service.reconcileControlPlaneIAMRole has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). 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.
NodegroupService.reconcileNodegroupVersion (cognitive 19) pkg/cloud/services/eks/nodegroup.go:320— NodegroupService.reconcileNodegroupVersion has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 4). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
ocmrole.GetOrCreateOCMRole (cognitive 19) pkg/rosa/ocmrole/ocmrole.go:74— ocmrole.GetOrCreateOCMRole has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ami.assertNoDuplicateFlags (cognitive 19) hack/tools/release-tools/cmd/ami/detect_k8s_release.go:151— ami.assertNoDuplicateFlags has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 11). 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.
EKSConfigReconciler.Reconcile (cognitive 18) bootstrap/eks/controllers/eksconfig_controller.go:73— EKSConfigReconciler.Reconcile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NodeadmConfigReconciler.Reconcile (cognitive 18) bootstrap/eks/controllers/nodeadmconfig_controller.go:70— NodeadmConfigReconciler.Reconcile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
addons.listAvailableAddons (cognitive 18) cmd/clusterawsadm/cmd/eks/addons/list_available.go:55— addons.listAvailableAddons has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 7 (8 pts) (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AWSClusterReconciler.reconcileNormal (cognitive 18) controllers/awscluster_controller.go:357— AWSClusterReconciler.reconcileNormal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2 (3 pts) (nesting depth added 5). 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.
AWSMachineReconciler.Reconcile (cognitive 18) controllers/awsmachine_controller.go:165— AWSMachineReconciler.Reconcile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AWSManagedControlPlane.validatePodIdentityAssociations (cognitive 18) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:662— AWSManagedControlPlane.validatePodIdentityAssociations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (2 pts) (nesting depth added 11). 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.
Service.reconcileAccessEntries (cognitive 18) pkg/cloud/services/eks/accessentry.go:32— Service.reconcileAccessEntries has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 2 (nesting depth added 6). 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.
Service.reconcilePodIdentityAssociations (cognitive 18) pkg/cloud/services/eks/pod_identities.go:34— Service.reconcilePodIdentityAssociations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 2 (nesting depth added 6). 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.
FargateService.reconcileFargateIAMRole (cognitive 18) pkg/cloud/services/eks/roles.go:295— FargateService.reconcileFargateIAMRole has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1 (nesting depth added 6). 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.
Service.filterProviderOwnedLB (cognitive 18) pkg/cloud/services/gc/loadbalancer.go:211— Service.filterProviderOwnedLB has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 11). 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. This shape REPEATS in the file: one other method here (Service.filterProviderOwnedLBV2) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Service.filterProviderOwnedLBV2 (cognitive 18) pkg/cloud/services/gc/loadbalancer.go:240— Service.filterProviderOwnedLBV2 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 11). 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. This shape REPEATS in the file: one other method here (Service.filterProviderOwnedLB) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
boilerplate.get_files (cognitive 18) hack/boilerplate/boilerplate.py:170— boilerplate.get_files has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 4 (8 pts), boolean chains 1 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
EKSConfigReconciler.joinWorker (cognitive 17) bootstrap/eks/controllers/eksconfig_controller.go:154— EKSConfigReconciler.joinWorker has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 4, match/switch 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSManagedControlPlaneReconciler.Reconcile (cognitive 17) controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:216— AWSManagedControlPlaneReconciler.Reconcile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2 (nesting depth added 3). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
controllers.deleteOrphanedAWSMachines (cognitive 17) exp/controllers/awsmachinepool_machines.go:117— controllers.deleteOrphanedAWSMachines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2, boolean chains 1 (nesting depth added 7). 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.
ROSAOCMRoleConfigReconciler.reconcileOCMRole (cognitive 17) exp/controllers/rosaocmroleconfig_controller.go:169— ROSAOCMRoleConfigReconciler.reconcileOCMRole has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1 (nesting depth added 6). 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.
Service.createLaunchTemplateData (cognitive 17) pkg/cloud/services/ec2/launchtemplate.go:617— Service.createLaunchTemplateData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
eks.getASGTagUpdates (cognitive 17) pkg/cloud/services/eks/tags.go:82— eks.getASGTagUpdates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 9). 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.
Service.getManagedAccessEntries (cognitive 17) pkg/cloud/services/eks/accessentry.go:74— Service.getManagedAccessEntries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (nesting depth added 10). 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.
NodegroupService.reconcileNodegroupConfig (cognitive 17) pkg/cloud/services/eks/nodegroup.go:440— NodegroupService.reconcileNodegroupConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.createTargetGroup (cognitive 17) pkg/cloud/services/elb/loadbalancer.go:1833— Service.createTargetGroup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 pts) (nesting depth added 6). 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.
Service.describeSecurityGroupOverridesByID (cognitive 17) pkg/cloud/services/securitygroup/securitygroups.go:254— Service.describeSecurityGroupOverridesByID has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (5 pts) (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.
Service.processIngressRulesSGs (cognitive 17) pkg/cloud/services/securitygroup/securitygroups.go:1040— Service.processIngressRulesSGs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), boolean chains 2 (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.
plan.Create (cognitive 17) pkg/eks/addons/plan.go:51— plan.Create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (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.
ocmrole.createRole (cognitive 17) pkg/rosa/ocmrole/ocmrole.go:320— ocmrole.createRole has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 6). 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.
AWSMachineReconciler.securityGroupsChanged (cognitive 16) controllers/awsmachine_security_groups.go:80— AWSMachineReconciler.securityGroupsChanged has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 6 (7 pts) (nesting depth added 6). 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.
AWSMachineTemplateReconciler.getKubernetesVersion (cognitive 16) controllers/awsmachinetemplate_controller.go:405— AWSMachineTemplateReconciler.getKubernetesVersion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, loops 3 (nesting depth added 3). 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.
ROSAControlPlane.validateRosaRoleConfig (cognitive 16) controlplane/rosa/webhooks/rosacontrolplane_webhook.go:240— ROSAControlPlane.validateRosaRoleConfig has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AWSMachinePool.ConvertTo (cognitive 16) exp/REDACTED:28— AWSMachinePool.ConvertTo has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
controllers.createAWSMachinesIfNotExists (cognitive 16) exp/controllers/awsmachinepool_machines.go:25— controllers.createAWSMachinesIfNotExists has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 6). 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.
ROSARoleConfigReconciler.reconcileOIDC (cognitive 16) exp/controllers/rosaroleconfig_controller.go:307— ROSARoleConfigReconciler.reconcileOIDC has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 5). 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.
Service.SDKToAutoScalingGroup (cognitive 16) pkg/cloud/services/autoscaling/autoscalinggroup.go:46— Service.SDKToAutoScalingGroup has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, loops 3 (6 pts), match/switch 2 (4 pts) (nesting depth added 5). 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.
Service.SubnetIDs (cognitive 16) pkg/cloud/services/autoscaling/autoscalinggroup.go:524— Service.SubnetIDs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (6 pts), match/switch 1 (2 pts) (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.
Service.eksAMILookup (cognitive 16) pkg/cloud/services/ec2/ami.go:384— Service.eksAMILookup has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 5). 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.
eks.clusterUpdatingStateRetryable (cognitive 16) pkg/cloud/services/eks/cluster.go:973— eks.clusterUpdatingStateRetryable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (16 pts) (nesting depth added 6). 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.
IAMService.EnsurePoliciesAttached (cognitive 16) REDACTED:134— IAMService.EnsurePoliciesAttached has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (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.
IAMService.FindAndVerifyOIDCProvider (cognitive 16) REDACTED:467— IAMService.FindAndVerifyOIDCProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (nesting depth added 4). 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.
Service.reconcileAccessPolicies (cognitive 16) pkg/cloud/services/eks/accessentry.go:241— Service.reconcileAccessPolicies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 2 (nesting depth added 4). 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.
Service.updatePodIdentityAssociation (cognitive 16) pkg/cloud/services/eks/pod_identities.go:136— Service.updatePodIdentityAssociation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (nesting depth added 4). 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.
Service.ReconcileLoadbalancers (cognitive 16) pkg/cloud/services/elb/loadbalancer.go:75— Service.ReconcileLoadbalancers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 7). 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.
Service.filterByOwnedTag (cognitive 16) pkg/cloud/services/elb/loadbalancer.go:1496— Service.filterByOwnedTag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
Service.reconcileNatGateways (cognitive 16) pkg/cloud/services/network/natgateways.go:43— Service.reconcileNatGateways has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 1 (2 pts) (nesting depth added 6). 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.
Service.getNatGatewayForSubnet (cognitive 16) pkg/cloud/services/network/natgateways.go:366— Service.getNatGatewayForSubnet has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, loops 2 (nesting depth added 4). 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.
ami.FindMissingAMIs (cognitive 16) hack/tools/release-tools/internal/ami/find_missing_ami.go:69— ami.FindMissingAMIs has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 1 (5 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D22 · Internal API Consistency· `Subnets.ToMap` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) · ×1
`Subnets.ToMap` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) api/v1beta2/network_types.go:779— 3 of 4 collection-returning members of `Subnets` return a slice (`[]T`) (3 of 4). Siblings: Subnets.IDs (api/v1beta2/network_types.go:789); Subnets.IDsWithEdge (api/v1beta2/network_types.go:805); Subnets.GetUniqueZones (api/v1beta2/network_types.go:893). Return a slice (`[]T`). [rule A4]
D22 · Internal API Consistency· `EKSConfig.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`EKSConfig.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one bootstrap/eks/webhooks/eksconfig_webhook.go:34— 4 of 5 fallible operations of `EKSConfig` take a `ctx context.Context` (4 of 5). Siblings: EKSConfig.ValidateCreate (bootstrap/eks/webhooks/eksconfig_webhook.go:48); EKSConfig.ValidateUpdate (bootstrap/eks/webhooks/eksconfig_webhook.go:53); EKSConfig.ValidateDelete (bootstrap/eks/webhooks/eksconfig_webhook.go:58); EKSConfig.Default (bootstrap/eks/webhooks/eksconfig_webhook.go:63). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `EKSConfigTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`EKSConfigTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one bootstrap/eks/webhooks/eksconfigtemplate_webhook.go:34— 4 of 5 fallible operations of `EKSConfigTemplate` take a `ctx context.Context` (4 of 5). Siblings: EKSConfigTemplate.ValidateCreate (bootstrap/eks/webhooks/eksconfigtemplate_webhook.go:48); EKSConfigTemplate.ValidateUpdate (bootstrap/eks/webhooks/eksconfigtemplate_webhook.go:53); EKSConfigTemplate.ValidateDelete (bootstrap/eks/webhooks/eksconfigtemplate_webhook.go:58); EKSConfigTemplate.Default (bootstrap/eks/webhooks/eksconfigtemplate_webhook.go:63). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSManagedControlPlane.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSManagedControlPlane.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:64— 4 of 5 fallible operations of `AWSManagedControlPlane` take a `ctx context.Context` (4 of 5). Siblings: AWSManagedControlPlane.ValidateCreate (controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:86); AWSManagedControlPlane.ValidateUpdate (controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:128); AWSManagedControlPlane.ValidateDelete (controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:209); AWSManagedControlPlane.Default (controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:694). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSManagedControlPlaneTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSManagedControlPlaneTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:43— 4 of 5 fallible operations of `AWSManagedControlPlaneTemplate` take a `ctx context.Context` (4 of 5). Siblings: AWSManagedControlPlaneTemplate.ValidateCreate (controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:57); AWSManagedControlPlaneTemplate.ValidateUpdate (controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:91); AWSManagedControlPlaneTemplate.ValidateDelete (controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:169); AWSManagedControlPlaneTemplate.Default (controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:181). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `ROSAControlPlane.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`ROSAControlPlane.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one controlplane/rosa/webhooks/rosacontrolplane_webhook.go:40— 4 of 5 fallible operations of `ROSAControlPlane` take a `ctx context.Context` (4 of 5). Siblings: ROSAControlPlane.ValidateCreate (controlplane/rosa/webhooks/rosacontrolplane_webhook.go:54); ROSAControlPlane.ValidateUpdate (controlplane/rosa/webhooks/rosacontrolplane_webhook.go:119); ROSAControlPlane.ValidateDelete (controlplane/rosa/webhooks/rosacontrolplane_webhook.go:168); ROSAControlPlane.Default (controlplane/rosa/webhooks/rosacontrolplane_webhook.go:357). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSFargateProfile.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSFargateProfile.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one exp/webhooks/awsfargateprofile_webhook.go:46— 4 of 5 fallible operations of `AWSFargateProfile` take a `ctx context.Context` (4 of 5). Siblings: AWSFargateProfile.Default (exp/webhooks/awsfargateprofile_webhook.go:62); AWSFargateProfile.ValidateUpdate (exp/webhooks/awsfargateprofile_webhook.go:86); AWSFargateProfile.ValidateCreate (exp/webhooks/awsfargateprofile_webhook.go:155); AWSFargateProfile.ValidateDelete (exp/webhooks/awsfargateprofile_webhook.go:174). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSMachinePool.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSMachinePool.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one exp/webhooks/awsmachinepool_webhook.go:43— 4 of 5 fallible operations of `AWSMachinePool` take a `ctx context.Context` (4 of 5). Siblings: AWSMachinePool.ValidateCreate (exp/webhooks/awsmachinepool_webhook.go:195); AWSMachinePool.ValidateUpdate (exp/webhooks/awsmachinepool_webhook.go:268); AWSMachinePool.ValidateDelete (exp/webhooks/awsmachinepool_webhook.go:296); AWSMachinePool.Default (exp/webhooks/awsmachinepool_webhook.go:301). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSManagedMachinePool.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSManagedMachinePool.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one exp/webhooks/awsmanagedmachinepool_webhook.go:50— 4 of 5 fallible operations of `AWSManagedMachinePool` take a `ctx context.Context` (4 of 5). Siblings: AWSManagedMachinePool.ValidateCreate (exp/webhooks/awsmanagedmachinepool_webhook.go:152); AWSManagedMachinePool.ValidateUpdate (exp/webhooks/awsmanagedmachinepool_webhook.go:195); AWSManagedMachinePool.ValidateDelete (exp/webhooks/awsmanagedmachinepool_webhook.go:238); AWSManagedMachinePool.Default (exp/webhooks/awsmanagedmachinepool_webhook.go:288). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `ROSAMachinePool.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`ROSAMachinePool.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one exp/webhooks/rosamachinepool_webhook.go:24— 4 of 5 fallible operations of `ROSAMachinePool` take a `ctx context.Context` (4 of 5). Siblings: ROSAMachinePool.ValidateCreate (exp/webhooks/rosamachinepool_webhook.go:38); ROSAMachinePool.ValidateUpdate (exp/webhooks/rosamachinepool_webhook.go:70); ROSAMachinePool.ValidateDelete (exp/webhooks/rosamachinepool_webhook.go:129); ROSAMachinePool.Default (exp/webhooks/rosamachinepool_webhook.go:184). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `ROSANetwork.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`ROSANetwork.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one exp/webhooks/rosanetwork_webhook.go:21— 4 of 5 fallible operations of `ROSANetwork` take a `ctx context.Context` (4 of 5). Siblings: ROSANetwork.ValidateCreate (exp/webhooks/rosanetwork_webhook.go:35); ROSANetwork.ValidateUpdate (exp/webhooks/rosanetwork_webhook.go:62); ROSANetwork.ValidateDelete (exp/webhooks/rosanetwork_webhook.go:67); ROSANetwork.Default (exp/webhooks/rosanetwork_webhook.go:72). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `ROSARoleConfig.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`ROSARoleConfig.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one exp/webhooks/rosaroleconfig_webhook.go:22— 4 of 5 fallible operations of `ROSARoleConfig` take a `ctx context.Context` (4 of 5). Siblings: ROSARoleConfig.ValidateCreate (exp/webhooks/rosaroleconfig_webhook.go:36); ROSARoleConfig.ValidateUpdate (exp/webhooks/rosaroleconfig_webhook.go:68); ROSARoleConfig.ValidateDelete (exp/webhooks/rosaroleconfig_webhook.go:73); ROSARoleConfig.Default (exp/webhooks/rosaroleconfig_webhook.go:78). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `NetworkScope.SecurityGroups` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) · ×1
`NetworkScope.SecurityGroups` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) pkg/cloud/scope/network.go:39— 3 of 4 collection-returning members of `NetworkScope` return a slice (`[]T`) (3 of 4). Siblings: NetworkScope.SecondaryCidrBlocks (pkg/cloud/scope/network.go:44); NetworkScope.AllSecondaryCidrBlocks (pkg/cloud/scope/network.go:47); NetworkScope.GetNatGatewaysIPs (pkg/cloud/scope/network.go:61). Return a slice (`[]T`). [rule A4]
D22 · Internal API Consistency· `AWSCluster.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSCluster.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one webhooks/awscluster_webhook.go:43— 4 of 5 fallible operations of `AWSCluster` take a `ctx context.Context` (4 of 5). Siblings: AWSCluster.ValidateCreate (webhooks/awscluster_webhook.go:62); AWSCluster.ValidateDelete (webhooks/awscluster_webhook.go:89); AWSCluster.ValidateUpdate (webhooks/awscluster_webhook.go:94); AWSCluster.Default (webhooks/awscluster_webhook.go:269). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSClusterControllerIdentity.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSClusterControllerIdentity.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one webhooks/awsclustercontrolleridentity_webhook.go:47— 4 of 5 fallible operations of `AWSClusterControllerIdentity` take a `ctx context.Context` (4 of 5). Siblings: AWSClusterControllerIdentity.ValidateCreate (webhooks/awsclustercontrolleridentity_webhook.go:55); AWSClusterControllerIdentity.ValidateDelete (webhooks/awsclustercontrolleridentity_webhook.go:79); AWSClusterControllerIdentity.ValidateUpdate (webhooks/awsclustercontrolleridentity_webhook.go:84); AWSClusterControllerIdentity.Default (webhooks/awsclustercontrolleridentity_webhook.go:116). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSClusterRoleIdentity.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSClusterRoleIdentity.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one webhooks/awsclusterroleidentity_webhook.go:45— 4 of 5 fallible operations of `AWSClusterRoleIdentity` take a `ctx context.Context` (4 of 5). Siblings: AWSClusterRoleIdentity.ValidateCreate (webhooks/awsclusterroleidentity_webhook.go:53); AWSClusterRoleIdentity.ValidateDelete (webhooks/awsclusterroleidentity_webhook.go:76); AWSClusterRoleIdentity.ValidateUpdate (webhooks/awsclusterroleidentity_webhook.go:81); AWSClusterRoleIdentity.Default (webhooks/awsclusterroleidentity_webhook.go:110). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSClusterStaticIdentity.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSClusterStaticIdentity.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one webhooks/awsclusterstaticidentity_webhook.go:45— 4 of 5 fallible operations of `AWSClusterStaticIdentity` take a `ctx context.Context` (4 of 5). Siblings: AWSClusterStaticIdentity.ValidateCreate (webhooks/awsclusterstaticidentity_webhook.go:53); AWSClusterStaticIdentity.ValidateDelete (webhooks/awsclusterstaticidentity_webhook.go:71); AWSClusterStaticIdentity.ValidateUpdate (webhooks/awsclusterstaticidentity_webhook.go:76); AWSClusterStaticIdentity.Default (webhooks/awsclusterstaticidentity_webhook.go:104). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSClusterTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSClusterTemplate.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one webhooks/awsclustertemplate_webhook.go:43— 4 of 5 fallible operations of `AWSClusterTemplate` take a `ctx context.Context` (4 of 5). Siblings: AWSClusterTemplate.Default (webhooks/awsclustertemplate_webhook.go:51); AWSClusterTemplate.ValidateCreate (webhooks/awsclustertemplate_webhook.go:62); AWSClusterTemplate.ValidateUpdate (webhooks/awsclustertemplate_webhook.go:77); AWSClusterTemplate.ValidateDelete (webhooks/awsclustertemplate_webhook.go:92). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSMachine.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one · ×1
`AWSMachine.SetupWebhookWithManager` takes no context.Context; its 4 sibling operations take one REDACTED:50— 4 of 5 fallible operations of `AWSMachine` take a `ctx context.Context` (4 of 5). Siblings: AWSMachine.ValidateCreate (REDACTED:69); AWSMachine.ValidateUpdate (REDACTED:93); AWSMachine.ValidateDelete (REDACTED:450); AWSMachine.Default (REDACTED:456). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `AWSMachineTemplate.SetupWebhookWithManager` takes no context.Context; its 3 sibling operations take one · ×1
`AWSMachineTemplate.SetupWebhookWithManager` takes no context.Context; its 3 sibling operations take one webhooks/awsmachinetemplate_webhook.go:36— 3 of 4 fallible operations of `AWSMachineTemplate` take a `ctx context.Context` (3 of 4). Siblings: AWSMachineTemplate.ValidateCreate (webhooks/awsmachinetemplate_webhook.go:220); AWSMachineTemplate.ValidateUpdate (webhooks/awsmachinetemplate_webhook.go:254); AWSMachineTemplate.ValidateDelete (webhooks/awsmachinetemplate_webhook.go:287). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
Change coupling: defaults.go ↔ loadbalancer.go api/v1beta2/defaults.go:1— `api/v1beta2/defaults.go` and `pkg/cloud/services/elb/loadbalancer.go` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c72f25d8` Support a secondary control plane load balancer; `681762da` Update docs/book/src/topics/network-load-balancer-with-awscluster.md; `652e97ac` Add ability to use NLBs as control plane load-balancers — run `git show` on any of them.
Near-duplicate member pair (36 shared lines) bootstrap/eks/controllers/eksconfig_controller.go:73— bootstrap/eks/controllers/eksconfig_controller.go:73-152 | bootstrap/eks/controllers/nodeadmconfig_controller.go:70-149 — These two members are variants of one another: 36 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (23 shared lines) pkg/cloud/services/elb/loadbalancer.go:740— pkg/cloud/services/elb/loadbalancer.go:740-786 | pkg/cloud/services/elb/loadbalancer.go:853-893 — These two members are variants of one another: 23 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) controlplane/rosa/controllers/rosacontrolplane_controller.go:116— controlplane/rosa/controllers/rosacontrolplane_controller.go:116-176 | exp/controllers/rosamachinepool_controller.go:56-108 | exp/controllers/rosanetwork_controller.go:326-363 | exp/controllers/rosaocmroleconfig_controller.go:63-102 | exp/controllers/rosaroleconfig_controller.go:76-115 — 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.
D4 · Code Duplication· Edited copy of a member (88 corresponding lines) · ×1
Edited copy of a member (88 corresponding lines) controlplane/eks/REDACTED:28— controlplane/eks/REDACTED:28-130 | controlplane/eks/REDACTED:133-220 — These two members are one piece of code written twice and then edited apart: 88 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (100 corresponding lines) · ×1
Edited copy of a member (100 corresponding lines) exp/controllers/awsmanagedmachinepool_controller.go:96— exp/controllers/awsmanagedmachinepool_controller.go:96-195 | exp/controllers/rosamachinepool_controller.go:118-227 — These two members are one piece of code written twice and then edited apart: 100 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (95 corresponding lines) · ×1
Edited copy of a member (95 corresponding lines) controllers/awsmachine_controller.go:165— controllers/awsmachine_controller.go:165-259 | exp/controllers/awsmachinepool_controller.go:124-229 — These two members are one piece of code written twice and then edited apart: 95 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (81 corresponding lines) · ×1
Edited copy of a member (81 corresponding lines) cmd/clusterawsadm/cmd/eks/addons/list_available.go:55— cmd/clusterawsadm/cmd/eks/addons/list_available.go:55-135 | cmd/clusterawsadm/cmd/eks/addons/list_installed.go:55-139 — These two members are one piece of code written twice and then edited apart: 81 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (62 corresponding lines) · ×1
Edited copy of a member (62 corresponding lines) pkg/cloud/services/eks/roles.go:173— pkg/cloud/services/eks/roles.go:173-244 | pkg/cloud/services/eks/roles.go:295-356 — These two members are one piece of code written twice and then edited apart: 62 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) pkg/cloud/services/elb/loadbalancer.go:563— pkg/cloud/services/elb/loadbalancer.go:563-614 | pkg/cloud/services/elb/loadbalancer.go:1547-1596 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) pkg/cloud/services/s3/s3.go:192— pkg/cloud/services/s3/s3.go:192-240 | pkg/cloud/services/s3/s3.go:243-291 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (285 corresponding lines) · ×1
Edited copy of a member (285 corresponding lines) controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.go:27— controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.go:27-311 | controlplane/eks/api/v1beta2/awsmanagedcontrolplane_types.go:27-464 — These two members are one piece of code written twice and then edited apart: 285 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 41+ corresponding lines) · ×1
Edited copies of one member (3 members, 41+ corresponding lines) pkg/cloud/services/network/carriergateways.go:39— pkg/cloud/services/network/carriergateways.go:39-83 | pkg/cloud/services/network/egress_only_gateways.go:39-84 | pkg/cloud/services/network/gateways.go:39-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (59 corresponding lines) · ×1
Edited copy of a member (59 corresponding lines) controllers/awsmachine_controller.go:1278— controllers/awsmachine_controller.go:1278-1337 | exp/controllers/awsmachinepool_controller.go:766-824 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) pkg/cloud/services/eks/roles.go:246— pkg/cloud/services/eks/roles.go:246-293 | pkg/cloud/services/eks/roles.go:358-400 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) pkg/cloud/services/eks/config.go:115— pkg/cloud/services/eks/config.go:115-165 | pkg/cloud/services/eks/config.go:167-218 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (70 corresponding lines) · ×1
Edited copy of a member (70 corresponding lines) cmd/clusterawsadm/cmd/ami/common/copy.go:33— cmd/clusterawsadm/cmd/ami/common/copy.go:33-102 | cmd/clusterawsadm/cmd/ami/common/encryptedcopy.go:37-123 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) controlplane/rosa/webhooks/rosacontrolplane_webhook.go:54— controlplane/rosa/webhooks/rosacontrolplane_webhook.go:54-104 | controlplane/rosa/webhooks/rosacontrolplane_webhook.go:119-165 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (155 corresponding lines) · ×1
Edited copy of a member (155 corresponding lines) api/v1beta1/conditions_consts.go:21— api/v1beta1/conditions_consts.go:21-175 | api/v1beta2/conditions_consts.go:21-201 — These two members are one piece of code written twice and then edited apart: 155 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 55+ corresponding lines) · ×1
Edited copies of one member (3 members, 55+ corresponding lines) cmd/clusterawsadm/cmd/gc/configure.go:30— cmd/clusterawsadm/cmd/gc/configure.go:30-86 | cmd/clusterawsadm/cmd/gc/disable.go:30-84 | cmd/clusterawsadm/cmd/gc/enable.go:30-85 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 55 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) bootstrap/eks/controllers/eksconfig_controller.go:263— bootstrap/eks/controllers/eksconfig_controller.go:263-295 | bootstrap/eks/controllers/nodeadmconfig_controller.go:366-397 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) REDACTED:489— REDACTED:489-520 | REDACTED:539-580 | webhooks/awsmachinetemplate_webhook.go:176-213 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:72— cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:72-125 | cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:127-172 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (178 corresponding lines) · ×1
Edited copy of a member (178 corresponding lines) cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:29— cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:29-206 | cmd/clusterawsadm/api/bootstrap/v1beta1/types.go:29-238 — These two members are one piece of code written twice and then edited apart: 178 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) bootstrap/eks/controllers/eksconfig_controller.go:371— bootstrap/eks/controllers/eksconfig_controller.go:371-401 | bootstrap/eks/controllers/nodeadmconfig_controller.go:437-468 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) exp/controllers/rosaocmroleconfig_controller.go:384— exp/controllers/rosaocmroleconfig_controller.go:384-422 | exp/controllers/rosaroleconfig_controller.go:547-584 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) pkg/cloud/services/eks/cluster.go:569— pkg/cloud/services/eks/cluster.go:569-606 | pkg/cloud/services/eks/cluster.go:652-679 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 39+ corresponding lines) · ×1
Edited copies of one member (4 members, 39+ corresponding lines) controllers/awsmanagedcluster_controller.go:153— controllers/awsmanagedcluster_controller.go:153-198 | controllers/rosacluster_controller.go:188-233 | controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:515-553 | controlplane/rosa/controllers/rosacontrolplane_controller.go:1676-1714 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 39 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) controllers/awsmachine_controller.go:1096— controllers/awsmachine_controller.go:1096-1118 | controllers/awsmachine_controller.go:1152-1174 | controllers/awsmachine_controller.go:1176-1200 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) webhooks/awsclustercontrolleridentity_webhook.go:84— webhooks/awsclustercontrolleridentity_webhook.go:84-113 | webhooks/awsclusterroleidentity_webhook.go:81-107 | webhooks/awsclusterstaticidentity_webhook.go:76-101 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) pkg/cloud/scope/machine.go:283— pkg/cloud/scope/machine.go:283-300 | pkg/cloud/scope/machinepool.go:141-159 | pkg/cloud/scope/managednodegroup.go:345-363 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) pkg/cloud/services/ec2/instances.go:775— pkg/cloud/services/ec2/instances.go:775-803 | pkg/cloud/services/ec2/launchtemplate.go:732-760 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 30+ corresponding lines) · ×1
Edited copies of one member (4 members, 30+ corresponding lines) pkg/cloud/scope/rosacontrolplane.go:50— pkg/cloud/scope/rosacontrolplane.go:50-86 | pkg/cloud/scope/rosanetwork.go:56-85 | pkg/cloud/scope/rosaocmroleconfig.go:59-91 | pkg/cloud/scope/rosaroleconfig.go:59-91 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) exp/webhooks/awsmachinepool_webhook.go:94— exp/webhooks/awsmachinepool_webhook.go:94-117 | REDACTED:424-447 | webhooks/awsmachinetemplate_webhook.go:51-78 | webhooks/awsmachinetemplate_webhook.go:80-105 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) pkg/cloud/services/securitygroup/securitygroups.go:498— pkg/cloud/services/securitygroup/securitygroups.go:498-511 | pkg/cloud/services/securitygroup/securitygroups.go:513-527 | pkg/cloud/services/securitygroup/securitygroups.go:529-543 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) pkg/cloud/scope/clients.go:63— pkg/cloud/scope/clients.go:63-84 | pkg/cloud/scope/clients.go:87-108 | pkg/cloud/scope/clients.go:111-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:34— cmd/clusterawsadm/cmd/bootstrap/iam/cloudformation.go:34-70 | cmd/clusterawsadm/cmd/bootstrap/iam/config.go:31-64 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) bootstrap/eks/controllers/eksconfig_controller.go:337— bootstrap/eks/controllers/eksconfig_controller.go:337-349 | bootstrap/eks/controllers/eksconfig_controller.go:353-367 | bootstrap/eks/controllers/nodeadmconfig_controller.go:401-414 | bootstrap/eks/controllers/nodeadmconfig_controller.go:418-433 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 38+ corresponding lines) · ×1
Edited copies of one member (4 members, 38+ corresponding lines) cmd/clusterawsadm/api/ami/v1beta1/types.go:62— cmd/clusterawsadm/api/ami/v1beta1/types.go:62-99 | cmd/clusterawsadm/cmd/eks/addons/types.go:50-88 | cmd/clusterawsadm/cmd/eks/addons/types.go:117-167 | cmd/clusterawsadm/resource/type.go:39-80 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 38 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (106 corresponding lines) · ×1
Edited copy of a member (106 corresponding lines) exp/api/v1beta1/awsfargateprofile_types.go:32— exp/api/v1beta1/awsfargateprofile_types.go:32-137 | exp/api/v1beta2/awsfargateprofile_types.go:29-163 — These two members are one piece of code written twice and then edited apart: 106 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) pkg/cloud/services/elb/loadbalancer.go:1087— pkg/cloud/services/elb/loadbalancer.go:1087-1110 | pkg/cloud/services/elb/loadbalancer.go:1113-1135 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) cmd/clusterawsadm/cmd/controller/credentials/update_credentials.go:28— cmd/clusterawsadm/cmd/controller/credentials/update_credentials.go:28-63 | cmd/clusterawsadm/cmd/controller/credentials/zero_credentials.go:27-56 | cmd/clusterawsadm/cmd/controller/rollout/rollout.go:33-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) pkg/cloud/converters/tags.go:58— pkg/cloud/converters/tags.go:58-76 | pkg/cloud/services/autoscaling/autoscalinggroup.go:505-521 | REDACTED:178-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 16+ corresponding lines) · ×1
Edited copies of one member (5 members, 16+ corresponding lines) pkg/cloud/scope/clients.go:45— pkg/cloud/scope/clients.go:45-60 | pkg/cloud/scope/clients.go:218-237 | pkg/cloud/scope/clients.go:258-273 | pkg/cloud/scope/clients.go:276-296 | pkg/cloud/scope/clients.go:299-318 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) cmd/clusterawsadm/cloudformation/bootstrap/cluster_api_controller.go:60— cmd/clusterawsadm/cloudformation/bootstrap/cluster_api_controller.go:60-75 | cmd/clusterawsadm/cloudformation/bootstrap/control_plane.go:25-40 | cmd/clusterawsadm/cloudformation/bootstrap/node.go:25-39 | cmd/clusterawsadm/cloudformation/bootstrap/user.go:34-48 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) REDACTED:362— REDACTED:362-383 | REDACTED:386-404 | REDACTED:407-425 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 9+ corresponding lines) · ×1
Edited copies of one member (5 members, 9+ corresponding lines) pkg/rosa/externalauthproviders.go:36— pkg/rosa/externalauthproviders.go:36-44 | pkg/rosa/externalauthproviders.go:47-57 | pkg/rosa/externalauthproviders.go:60-73 | pkg/rosa/externalauthproviders.go:76-87 | pkg/rosa/externalauthproviders.go:104-112 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) pkg/cloud/scope/fargate.go:171— pkg/cloud/scope/fargate.go:171-188 | pkg/cloud/scope/managednodegroup.go:234-251 | pkg/cloud/scope/managednodegroup.go:255-272 | pkg/cloud/scope/rosamachinepool.go:192-209 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) cmd/clusterawsadm/cmd/ami/ami.go:29— cmd/clusterawsadm/cmd/ami/ami.go:29-50 | cmd/clusterawsadm/cmd/bootstrap/bootstrap.go:30-50 | cmd/clusterawsadm/cmd/gc/gc.go:25-40 | cmd/clusterawsadm/cmd/resource/resource.go:28-45 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) api/v1beta1/awsmachine_conversion.go:78— api/v1beta1/awsmachine_conversion.go:78-87 | bootstrap/eks/REDACTED:72-80 | exp/REDACTED:91-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) bootstrap/eks/REDACTED:139— bootstrap/eks/REDACTED:139-147 | exp/REDACTED:172-180 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) api/v1beta1/network_types.go:297— api/v1beta1/network_types.go:297-303 | api/v1beta2/network_types.go:805-811 | controlplane/rosa/controllers/rosacontrolplane_controller.go:698-704 | pkg/cloud/converters/eks.go:67-74 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) pkg/cloud/services/eks/addons.go:220— pkg/cloud/services/eks/addons.go:220-226 | pkg/cloud/services/eks/cluster.go:947-953 | pkg/cloud/services/eks/nodegroup.go:655-660 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) pkg/cloud/services/secretsmanager/cloudinit.go:26— pkg/cloud/services/secretsmanager/cloudinit.go:26-33 | pkg/cloud/services/ssm/cloudinit.go:27-33 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) controllers/rosacluster_controller.go:53— controllers/rosacluster_controller.go:53-61 | exp/controllers/rosamachinepool_controller.go:48-53 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (156–159 lines × 2) api/v1beta1/awsidentity_types.go:24— api/v1beta1/awsidentity_types.go:24-179 | api/v1beta2/awsidentity_types.go:24-182 — `api/v1beta1/awsidentity_types.go` and `api/v1beta2/awsidentity_types.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 2 separate duplicated blocks between them, totalling at least 169 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.
Duplicated block (96 lines × 2) api/v1beta1/types.go:77— api/v1beta1/types.go:77-172 | api/v1beta2/types.go:127-222 — `api/v1beta1/types.go` and `api/v1beta2/types.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 2 separate duplicated blocks between them, totalling at least 177 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 `api/v1beta1/types.go:77` it begins part-way through the construct above it, 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 (81 lines × 2) api/v1beta1/types.go:213— api/v1beta1/types.go:213-293 | api/v1beta2/types.go:535-615 — `api/v1beta1/types.go` and `api/v1beta2/types.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 2 separate duplicated blocks between them, totalling at least 177 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 `api/v1beta1/types.go:213` 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 (78 lines × 2) exp/api/v1beta1/awsmanagedmachinepool_types.go:157— exp/api/v1beta1/awsmanagedmachinepool_types.go:157-234 | exp/api/v1beta2/awsmanagedmachinepool_types.go:224-301 — `exp/api/v1beta1/awsmanagedmachinepool_types.go` and `exp/api/v1beta2/awsmanagedmachinepool_types.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 1 separate duplicated blocks between them, totalling at least 78 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 `exp/api/v1beta1/awsmanagedmachinepool_types.go:157` 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 (77 lines × 2) exp/api/v1beta1/awsfargateprofile_types.go:61— exp/api/v1beta1/awsfargateprofile_types.go:61-137 | exp/api/v1beta2/awsfargateprofile_types.go:87-163 — `exp/api/v1beta1/awsfargateprofile_types.go` and `exp/api/v1beta2/awsfargateprofile_types.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 1 separate duplicated blocks between them, totalling at least 77 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 `exp/api/v1beta1/awsfargateprofile_types.go:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (71–74 lines × 2) controlplane/eks/api/v1beta1/types.go:87— controlplane/eks/api/v1beta1/types.go:87-160 | controlplane/eks/api/v1beta2/types.go:145-215 — `controlplane/eks/api/v1beta1/types.go` and `controlplane/eks/api/v1beta2/types.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 150 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 `controlplane/eks/api/v1beta1/types.go:87` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `controlplane/eks/api/v1beta2/types.go:219` calls `AddonResolution` and `controlplane/eks/api/v1beta1/types.go:161` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (73 lines × 2) cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:88— cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:88-160 | cmd/clusterawsadm/api/bootstrap/v1beta1/types.go:96-168 — `cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go` and `cmd/clusterawsadm/api/bootstrap/v1beta1/types.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 2 separate duplicated blocks between them, totalling at least 129 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 `cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:88` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (68 lines × 2) api/v1beta1/awscluster_types.go:72— api/v1beta1/awscluster_types.go:72-139 | api/v1beta2/awscluster_types.go:84-151 — `api/v1beta1/awscluster_types.go` and `api/v1beta2/awscluster_types.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 1 separate duplicated blocks between them, totalling at least 68 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 `api/v1beta1/awscluster_types.go:72` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (60–61 lines × 2) api/v1beta1/network_types.go:372— api/v1beta1/network_types.go:372-431 | api/v1beta2/network_types.go:929-989 — `api/v1beta1/network_types.go` and `api/v1beta2/network_types.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 132 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.
Duplicated block (57 lines × 2) controlplane/eks/api/v1beta1/types.go:161— controlplane/eks/api/v1beta1/types.go:161-217 | controlplane/eks/api/v1beta2/types.go:220-276 — `controlplane/eks/api/v1beta1/types.go` and `controlplane/eks/api/v1beta2/types.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 150 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 `controlplane/eks/api/v1beta1/types.go:161` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `controlplane/eks/api/v1beta2/types.go:211` calls `AddonResolution` and `controlplane/eks/api/v1beta1/types.go:153` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (56 lines × 2) cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:29— cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:29-84 | cmd/clusterawsadm/api/bootstrap/v1beta1/types.go:29-84 — `cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go` and `cmd/clusterawsadm/api/bootstrap/v1beta1/types.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 2 separate duplicated blocks between them, totalling at least 129 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 `cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:29` 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 (48 lines × 2) exp/api/v1beta1/conditions_consts.go:57— exp/api/v1beta1/conditions_consts.go:57-104 | exp/api/v1beta2/conditions_consts.go:75-122 — `exp/api/v1beta1/conditions_consts.go` and `exp/api/v1beta2/conditions_consts.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 1 separate duplicated blocks between them, totalling at least 48 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 `exp/api/v1beta1/conditions_consts.go:57` it begins part-way through the construct above it, 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 (45 lines × 2) api/v1beta1/tags.go:89— api/v1beta1/tags.go:89-133 | api/v1beta2/tags.go:82-126 — `api/v1beta1/tags.go` and `api/v1beta2/tags.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 62 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 `api/v1beta1/tags.go:89` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (44 lines × 2) api/v1beta1/conditions_consts.go:131— api/v1beta1/conditions_consts.go:131-174 | api/v1beta2/conditions_consts.go:154-197 — `api/v1beta1/conditions_consts.go` and `api/v1beta2/conditions_consts.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 2 separate duplicated blocks between them, totalling at least 96 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 `api/v1beta1/conditions_consts.go:131` it begins part-way through the construct above it, 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 (26 lines × 2) cmd/clusterawsadm/cmd/eks/addons/list_available.go:56— cmd/clusterawsadm/cmd/eks/addons/list_available.go:56-81 | cmd/clusterawsadm/cmd/eks/addons/list_installed.go:56-81 — before extracting anything, compare `cmd/clusterawsadm/cmd/eks/addons/list_available.go` and `cmd/clusterawsadm/cmd/eks/addons/list_installed.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) exp/controllers/awsmanagedmachinepool_controller.go:100— exp/controllers/awsmanagedmachinepool_controller.go:100-121 | exp/controllers/rosamachinepool_controller.go:122-143 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `exp/controllers/awsmanagedmachinepool_controller.go:100` 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 (17–22 lines × 2) REDACTED:490— REDACTED:490-506 | REDACTED:540-561 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:490` 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 (31 lines × 2) pkg/cloud/services/s3/s3.go:210— pkg/cloud/services/s3/s3.go:210-240 | pkg/cloud/services/s3/s3.go:261-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/s3/s3.go:210` 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 (18 lines × 2) api/v1beta1/bastion.go:28— api/v1beta1/bastion.go:28-45 | api/v1beta2/bastion.go:28-45 — `api/v1beta1/bastion.go` and `api/v1beta2/bastion.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 1 separate duplicated blocks between them, totalling at least 18 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.
Duplicated block (15 lines × 3) pkg/cloud/services/eks/cluster.go:626— pkg/cloud/services/eks/cluster.go:626-640 | pkg/cloud/services/eks/cluster.go:812-826 | pkg/cloud/services/eks/cluster.go:901-915 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/eks/cluster.go:626` it begins part-way through the construct above it, 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 (11–13 lines × 2) REDACTED:510— REDACTED:510-520 | REDACTED:568-580 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:510` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:507` calls `Forbidden`, `NewPath` and `REDACTED:565` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 4) pkg/cloud/converters/tags.go:120— pkg/cloud/converters/tags.go:120-131 | pkg/cloud/converters/tags.go:139-150 | pkg/cloud/converters/tags.go:158-169 | pkg/cloud/converters/tags.go:188-199 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/converters/tags.go:120` 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 (9–11 lines × 2) bootstrap/eks/controllers/eksconfig_controller.go:155— bootstrap/eks/controllers/eksconfig_controller.go:155-165 | bootstrap/eks/controllers/nodeadmconfig_controller.go:152-160 — before extracting anything, compare `bootstrap/eks/controllers/eksconfig_controller.go` and `bootstrap/eks/controllers/nodeadmconfig_controller.go` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `bootstrap/eks/controllers/eksconfig_controller.go:155` 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 (10–11 lines × 2) pkg/cloud/services/elb/loadbalancer.go:777— pkg/cloud/services/elb/loadbalancer.go:777-786 | pkg/cloud/services/elb/loadbalancer.go:883-893 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/elb/loadbalancer.go:777` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) cmd/clusterawsadm/cmd/gc/configure.go:58— cmd/clusterawsadm/cmd/gc/configure.go:58-67 | cmd/clusterawsadm/cmd/gc/disable.go:57-66 | cmd/clusterawsadm/cmd/gc/enable.go:58-67 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cmd/clusterawsadm/cmd/gc/configure.go:58` 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 (9–10 lines × 2) exp/controllers/rosaocmroleconfig_controller.go:137— exp/controllers/rosaocmroleconfig_controller.go:137-146 | exp/controllers/rosaroleconfig_controller.go:149-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `exp/controllers/rosaocmroleconfig_controller.go:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 4) pkg/cloud/services/network/egress_only_gateways.go:179— pkg/cloud/services/network/egress_only_gateways.go:179-187 | pkg/cloud/services/network/gateways.go:176-184 | pkg/cloud/services/network/natgateways.go:248-256 | pkg/cloud/services/network/vpc.go:671-679 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/services/network/egress_only_gateways.go:179` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 5) webhooks/awsclustercontrolleridentity_webhook.go:68— webhooks/awsclustercontrolleridentity_webhook.go:68-76 | webhooks/awsclusterroleidentity_webhook.go:65-73 | webhooks/awsclusterroleidentity_webhook.go:99-107 | webhooks/awsclusterstaticidentity_webhook.go:60-68 | webhooks/awsclusterstaticidentity_webhook.go:93-101 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `webhooks/awsclustercontrolleridentity_webhook.go:68` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) exp/controllers/rosamachinepool_controller.go:67— exp/controllers/rosamachinepool_controller.go:67-74 | exp/controllers/rosanetwork_controller.go:329-336 | exp/controllers/rosaocmroleconfig_controller.go:69-76 | exp/controllers/rosaroleconfig_controller.go:82-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `exp/controllers/rosamachinepool_controller.go:67` 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 (5 lines × 4) REDACTED:632— REDACTED:632-636 | REDACTED:653-657 | REDACTED:677-681 | REDACTED:693-697 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:632` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (38 lines × 2) api/v1beta1/awsclustertemplate_types.go:26— api/v1beta1/awsclustertemplate_types.go:26-63 | api/v1beta2/awsclustertemplate_types.go:26-64 — `api/v1beta1/awsclustertemplate_types.go` and `api/v1beta2/awsclustertemplate_types.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 1 separate duplicated blocks between them, totalling at least 39 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.
Duplicated block (14 lines × 3) api/v1beta1/awscluster_conversion.go:222— api/v1beta1/awscluster_conversion.go:222-235 | api/v1beta1/awsclustertemplate_conversion.go:46-59 | api/v1beta1/awsmachine_conversion.go:158-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 12) api/v1beta2/awscluster_types.go:451— api/v1beta2/awscluster_types.go:451-456 | api/v1beta2/awsmachine_types.go:559-564 | api/v1beta2/awsmachinetemplate_types.go:155-160 | api/v1beta2/awsmanagedcluster_types.go:113-118 | bootstrap/eks/api/v1beta2/eksconfig_types.go:167-172 | bootstrap/eks/api/v1beta2/nodeadmconfig_types.go:200-205 | controlplane/eks/api/v1beta2/awsmanagedcontrolplane_types.go:485-490 | controlplane/rosa/api/v1beta2/rosacontrolplane_types.go:1069-1074 | exp/api/v1beta2/awsmachinepool_types.go:342-347 | exp/api/v1beta2/awsmanagedmachinepool_types.go:363-368 | exp/api/v1beta2/rosacluster_types.go:109-114 | exp/api/v1beta2/rosamachinepool_types.go:343-348 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times.
Duplicated block (6 lines × 10) bootstrap/eks/webhooks/eksconfig_webhook.go:34— bootstrap/eks/webhooks/eksconfig_webhook.go:34-39 | bootstrap/eks/webhooks/eksconfigtemplate_webhook.go:34-39 | controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:64-69 | controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:43-48 | exp/webhooks/awsfargateprofile_webhook.go:46-51 | exp/webhooks/awsmachinepool_webhook.go:43-48 | exp/webhooks/awsmanagedmachinepool_webhook.go:50-55 | exp/webhooks/rosamachinepool_webhook.go:24-29 | exp/webhooks/rosanetwork_webhook.go:21-26 | exp/webhooks/rosaroleconfig_webhook.go:22-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:37` calls `WithName` and `bootstrap/eks/webhooks/eksconfig_webhook.go:28` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (75 lines × 2) exp/api/v1beta1/types.go:29— exp/api/v1beta1/types.go:29-103 | exp/api/v1beta2/types.go:28-103 — `exp/api/v1beta1/types.go` and `exp/api/v1beta2/types.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 125 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 `exp/api/v1beta1/types.go:29` it begins part-way through the construct above it, 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 (37 lines × 2) api/v1beta1/awsmachinetemplate_types.go:36— api/v1beta1/awsmachinetemplate_types.go:36-72 | api/v1beta2/awsmachinetemplate_types.go:97-134 — `api/v1beta1/awsmachinetemplate_types.go` and `api/v1beta2/awsmachinetemplate_types.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 1 separate duplicated blocks between them, totalling at least 38 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.
Duplicated block (11 lines × 3) pkg/cloud/scope/fargate.go:57— pkg/cloud/scope/fargate.go:57-67 | pkg/cloud/scope/managedcontrolplane.go:79-89 | pkg/cloud/scope/managednodegroup.go:75-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/cloud/scope/fargate.go:57` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: `pkg/cloud/scope/managedcontrolplane.go:79` is reached only past a guard at line 75 that tests `params.Cluster` and leaves the function early, and `pkg/cloud/scope/fargate.go:57` reads `params.Cluster` with no such check. What separates these copies is not which lines they run but which PRECONDITION they enforce, so one of them is operating on state the other one refuses. Decide which is intended BEFORE unifying them — extract the shared part and whichever copy is missing the check keeps running unchecked, and if the guard is the correct behaviour then that hole is already live.
Duplicated block (7 lines × 4) controllers/awsmanagedcluster_controller.go:128— controllers/awsmanagedcluster_controller.go:128-135 | controllers/rosacluster_controller.go:163-170 | controlplane/eks/controllers/awsmanagedcontrolplane_controller.go:176-182 | controlplane/rosa/controllers/rosacontrolplane_controller.go:154-161 — before extracting anything, compare `controllers/awsmanagedcluster_controller.go` and `controllers/rosacluster_controller.go` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `controllers/awsmanagedcluster_controller.go:128` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `controllers/awsmanagedcluster_controller.go:127` calls `WithEventFilter`, `ResourceIsNotExternallyManaged`, `GetScheme` and `controllers/rosacluster_controller.go:162` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 9) main.go:277— main.go:277-281 | main.go:287-291 | main.go:323-327 | main.go:338-342 | main.go:397-401 | main.go:443-447 | main.go:518-522 | main.go:526-530 | main.go:536-540 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main.go:277` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `main.go:276` calls `GetEventRecorderFor` and `main.go:396` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:103— controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:103-108 | controlplane/eks/webhooks/awsmanagedcontrolplane_webhook.go:149-154 | controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:69-74 | controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.go:111-116 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Third-party script without Subresource Integrity docs/book/theme/head.hbs:5— `https://code.jquery.com/jquery-3.5.1.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup.
Orphaned file api/v1beta1/network_types.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 exp/api/v1beta2/types.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 exp/api/v1beta2/awsmanagedmachinepool_types.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 bootstrap/eks/controllers/eksconfig_controller.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 cmd/clusterawsadm/cloudformation/bootstrap/cluster_api_controller.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 pkg/cloud/scope/cluster.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 pkg/cloud/endpoints/endpoints.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 REDACTED: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 pkg/cloud/scope/managednodegroup.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 exp/controllers/awsmanagedmachinepool_controller.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 controlplane/eks/api/v1beta1/awsmanagedcontrolplane_types.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 exp/api/v1beta2/awsmachinepool_types.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 exp/webhooks/awsmachinepool_webhook.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 pkg/cloud/scope/machine.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 pkg/cloud/scope/machinepool.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 api/v1beta1/awsmachine_types.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 pkg/internal/rate/rate.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 api/v1beta1/awscluster_types.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 exp/webhooks/awsmanagedmachinepool_webhook.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 pkg/cloud/services/eks/fargate.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 controlplane/eks/webhooks/awsmanagedcontrolplanetemplate_webhook.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 exp/api/v1beta1/types.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 pkg/cloud/services/common/common.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 exp/api/v1beta1/awsmanagedmachinepool_types.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 cmd/clusterawsadm/api/bootstrap/v1beta1/types.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.
Duplicated predicate exp/webhooks/awsmachinepool_webhook.go:186— `!feature.Gates.Enabled(feature.BootstrapFormatIgnition) && w.ignitionEnabled(r)` appears character-identically in 2 files — exp/webhooks/awsmachinepool_webhook.go, webhooks/awsmachinetemplate_webhook.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 api/v1beta1/bastion.go:30— `b.DisableIngressRules && len(b.AllowedCIDRBlocks) > 0` appears character-identically in 2 files — api/v1beta1/bastion.go, api/v1beta2/bastion.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 api/v1beta1/network_types.go:112— `b.Name != "" && !Tags(b.Tags).HasOwned(clusterName)` appears character-identically in 2 files — api/v1beta1/network_types.go, api/v1beta2/network_types.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 controllers/awsmachine_controller.go:1283— `cluster.Spec.ControlPlaneRef.IsDefined() && cluster.Spec.ControlPlaneRef.Kind == AWSManagedControlPlaneRefKind` appears character-identically in 2 files — controllers/awsmachine_controller.go, controllers/awsmachinetemplate_controller.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 bootstrap/eks/controllers/eksconfig_controller.go:158— `config.Status.DataSecretName != nil && configOwner.GetKind() == kindMachine` appears character-identically in 2 files — bootstrap/eks/controllers/eksconfig_controller.go, bootstrap/eks/controllers/nodeadmconfig_controller.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 bootstrap/eks/controllers/nodeadmconfig_controller.go:161— `err != nil && !apierrors.IsNotFound(err)` appears character-identically in 6 files — bootstrap/eks/controllers/nodeadmconfig_controller.go, controllers/awsmachine_controller.go, controlplane/rosa/controllers/rosacontrolplane_controller.go, pkg/cloud/services/eks/oidc.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 api/v1beta1/network_types.go:552— `i.Description != o.Description || i.Protocol != o.Protocol` appears character-identically in 2 files — api/v1beta1/network_types.go, api/v1beta2/network_types.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 api/v1beta1/network_types.go:564— `i.FromPort == o.FromPort && i.ToPort == o.ToPort` appears character-identically in 2 files — api/v1beta1/network_types.go, api/v1beta2/network_types.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 pkg/cloud/services/ec2/instances.go:1329— `i.MarketType != "" && i.MarketType == infrav1.MarketTypeCapacityBlock && i.SpotMarketOptions != nil` appears character-identically in 2 files — pkg/cloud/services/ec2/instances.go, pkg/cloud/services/ec2/launchtemplate.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 pkg/cloud/services/ec2/instances.go:1338— `i.SpotMarketOptions != nil && i.MarketType == ""` appears character-identically in 2 files — pkg/cloud/services/ec2/instances.go, pkg/cloud/services/ec2/launchtemplate.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 exp/webhooks/awsmachinepool_webhook.go:98— `infrav1.VolumeTypesProvisioned.Has(string(volume.Type)) && volume.IOPS == 0` appears character-identically in 3 files — exp/webhooks/awsmachinepool_webhook.go, REDACTED, webhooks/awsmachinetemplate_webhook.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 REDACTED:482— `len(additionalSecurityGroup.Filters) > 0 && additionalSecurityGroup.ID != nil` appears character-identically in 2 files — REDACTED, webhooks/awsmachinetemplate_webhook.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 hack/tools/release-tools/cmd/ami/detect_k8s_release.go:111— `normalized == printer.TypeTable || normalized == ""` appears character-identically in 2 files — hack/tools/release-tools/cmd/ami/detect_k8s_release.go, hack/tools/release-tools/cmd/ami/find_missing_ami.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 api/v1beta1/tags.go:42— `ok && ResourceLifecycle(value) == ResourceLifecycleOwned` appears character-identically in 2 files — api/v1beta1/tags.go, api/v1beta2/tags.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 pkg/cloud/services/network/secondarycidr.go:83— `s.scope.VPC().IsUnmanaged(s.scope.Name()) || s.scope.VPC().ID == ""` appears character-identically in 2 files — pkg/cloud/services/network/secondarycidr.go, pkg/cloud/services/network/vpc.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 pkg/cloud/services/ec2/instances.go:184— `scope.IsEKSManaged() && imageLookupFormat == "" && imageLookupOrg == "" && imageLookupBaseOS == ""` appears character-identically in 2 files — pkg/cloud/services/ec2/instances.go, pkg/cloud/services/ec2/launchtemplate.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 exp/api/v1beta1/types.go:245— `t.Effect == other.Effect && t.Key == other.Key && t.Value == other.Value` appears character-identically in 2 files — exp/api/v1beta1/types.go, exp/api/v1beta2/types.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 api/v1beta1/network_types.go:228— `v.ID != "" && !v.Tags.HasOwned(clusterName)` appears character-identically in 2 files — api/v1beta1/network_types.go, api/v1beta2/network_types.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 pkg/cloud/services/ec2/instances.go:986— `v.IamInstanceProfile != nil && v.IamInstanceProfile.Arn != nil` appears character-identically in 2 files — pkg/cloud/services/ec2/instances.go, pkg/cloud/services/ec2/launchtemplate.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 exp/webhooks/awsmachinepool_webhook.go:317— `w.ignitionEnabled(r) && r.Spec.Ignition.StorageType == ""` appears character-identically in 2 files — exp/webhooks/awsmachinepool_webhook.go, REDACTED. 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 exp/webhooks/awsmachinepool_webhook.go:322— `w.ignitionEnabled(r) && r.Spec.Ignition.Version == "" && r.Spec.Ignition.StorageType != infrav1.IgnitionStorageTypeOptionUnencryptedUserData` appears character-identically in 2 files — exp/webhooks/awsmachinepool_webhook.go, REDACTED. 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 hack/tools/ami/delete_amis.py:60— `tag["Key"] == "kubernetes_version" and version_contains in tag["Value"]` appears character-identically in 2 files — hack/tools/ami/delete_amis.py, hack/tools/ami/list_amis.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.
Fat interface: ClusterScoper (16 methods) pkg/cloud/interfaces.go:52— `ClusterScoper` declares 16 methods: `Name`, `Namespace`, `InfraClusterName`, `Region`, `KubernetesClusterName`, `InfraCluster`, `ClusterObj`, `UnstructuredControlPlane`, `IdentityRef`, `ListOptionsLabelSelector`, `APIServerPort`, `AdditionalTags`, `SetFailureDomain`, `PatchObject`, `Close`, `MaxWaitDuration`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: EC2API (71 methods) pkg/cloud/services/common/common.go:27— `EC2API` declares 71 methods: `AllocateAddress`, `AllocateHosts`, `AssociateAddress`, `AssociateRouteTable`, `AssociateVpcCidrBlock`, `AttachInternetGateway`, `AuthorizeSecurityGroupIngress`, `CreateCarrierGateway`, `CreateEgressOnlyInternetGateway`, `CreateInternetGateway`, `CreateLaunchTemplate`, `CreateLaunchTemplateVersion`, `CreateNatGateway`, `CreateRouteTable`, `CreateRoute`, `CreateSecurityGroup`, `CreateSubnet`, `CreateTags`, `CreateVpc`, `CreateVpcEndpoint`, `DeleteCarrierGateway`, `DeleteEgressOnlyInternetGateway`, `DeleteInternetGateway`, `DeleteLaunchTemplate`, `DeleteLaunchTemplateVersions`, `DeleteNatGateway`, `DeleteNetworkInterface`, `DeleteRouteTable`, `DeleteSecurityGroup`, `DeleteSubnet`, `DeleteTags`, `DeleteVpc`, `DeleteVpcEndpoints`, `DescribeAddresses`, `DescribeAvailabilityZones`, `DescribeCarrierGateways`, `DescribeDhcpOptions`, `DescribeEgressOnlyInternetGateways`, `DescribeHosts`, `DescribeImages`, and 31 more. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: EKSAPI (48 methods) pkg/cloud/services/eks/service.go:35— `EKSAPI` declares 48 methods: `CreateCluster`, `DeleteCluster`, `DescribeCluster`, `UpdateClusterConfig`, `UpdateClusterVersion`, `DescribeUpdate`, `AssociateEncryptionConfig`, `ListClusters`, `CreateNodegroup`, `DeleteNodegroup`, `DescribeNodegroup`, `UpdateNodegroupConfig`, `UpdateNodegroupVersion`, `DescribeAddon`, `CreateAddon`, `UpdateAddon`, `ListAddons`, `DescribeAddonConfiguration`, `DescribeAddonVersions`, `DeleteAddon`, `ListIdentityProviderConfigs`, `DescribeIdentityProviderConfig`, `AssociateIdentityProviderConfig`, `CreateFargateProfile`, `DeleteFargateProfile`, `DescribeFargateProfile`, `TagResource`, `UntagResource`, `DisassociateIdentityProviderConfig`, `ListAccessEntries`, `DescribeAccessEntry`, `CreateAccessEntry`, `UpdateAccessEntry`, `DeleteAccessEntry`, `ListAssociatedAccessPolicies`, `AssociateAccessPolicy`, `DisassociateAccessPolicy`, `ListPodIdentityAssociations`, `DescribePodIdentityAssociation`, `CreatePodIdentityAssociation`, and 8 more. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ELBV2API (23 methods) pkg/cloud/services/elb/service.go:67— `ELBV2API` declares 23 methods: `AddTags`, `CreateListener`, `CreateLoadBalancer`, `CreateTargetGroup`, `DeleteListener`, `DeleteLoadBalancer`, `DeleteTargetGroup`, `DeregisterTargets`, `DescribeListeners`, `DescribeLoadBalancerAttributes`, `DescribeLoadBalancers`, `DescribeTags`, `DescribeTargetGroups`, `DescribeTargetHealth`, `ModifyListener`, `ModifyLoadBalancerAttributes`, `ModifyTargetGroupAttributes`, `RegisterTargets`, `RemoveTags`, `SetSecurityGroups`, `SetSubnets`, `DescribeLoadBalancersPages`, `WaitUntilLoadBalancerAvailable`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ASGInterface (16 methods) pkg/cloud/services/interfaces.go:73— `ASGInterface` declares 16 methods: `ASGIfExists`, `GetASGByName`, `CreateASG`, `UpdateASG`, `CancelASGInstanceRefresh`, `StartASGInstanceRefresh`, `CanStartASGInstanceRefresh`, `UpdateResourceTags`, `DeleteASGAndWait`, `SuspendProcesses`, `ResumeProcesses`, `SubnetIDs`, `DescribeLifecycleHooks`, `CreateLifecycleHook`, `UpdateLifecycleHook`, `DeleteLifecycleHook`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: EC2Interface (29 methods) pkg/cloud/services/interfaces.go:94— `EC2Interface` declares 29 methods: `InstanceIfExists`, `TerminateInstance`, `CreateInstance`, `GetRunningInstanceByTags`, `GetAdditionalSecurityGroupsIDs`, `GetCoreSecurityGroups`, `GetInstanceSecurityGroups`, `UpdateInstanceSecurityGroups`, `UpdateResourceTags`, `ModifyInstanceMetadataOptions`, `ModifySourceDestCheck`, `TerminateInstanceAndWait`, `DetachSecurityGroupsFromNetworkInterface`, `DiscoverLaunchTemplateAMI`, `GetLaunchTemplate`, `GetLaunchTemplateID`, `GetLaunchTemplateLatestVersion`, `CreateLaunchTemplate`, `CreateLaunchTemplateVersion`, `PruneLaunchTemplateVersions`, `DeleteLaunchTemplate`, `LaunchTemplateNeedsUpdate`, `DeleteBastion`, `ReconcileBastion`, `ReconcileElasticIPFromPublicPool`, `ReleaseElasticIP`, `AllocateDedicatedHost`, `ReleaseDedicatedHost`, `DescribeDedicatedHost`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: OCMClient (32 methods) pkg/rosa/ocmclient.go:37— `OCMClient` declares 32 methods: `AckVersionGate`, `AddHTPasswdUser`, `CreateNodePool`, `CreateIdentityProvider`, `CreateCluster`, `CreateUser`, `DeleteCluster`, `DeleteNodePool`, `DeleteUser`, `GetAvailableChannels`, `GetCluster`, `GetControlPlaneUpgradePolicies`, `GetHTPasswdUserList`, `GetHypershiftNodePoolUpgrade`, `GetIdentityProviders`, `GetMissingGateAgreementsHypershift`, `GetNodePool`, `GetNodePools`, `GetPolicies`, `GetUser`, `ScheduleHypershiftControlPlaneUpgrade`, `ScheduleNodePoolUpgrade`, `UpdateNodePool`, `UpdateCluster`, `ValidateHypershiftVersion`, `SetLogForwarder`, `UpdateLogForwarder`, `DeleteLogForwarder`, `GetLogForwarders`, `UpdateClusterDeletionProtection`, `GetIngresses`, `UpdateIngress`. Counted over the exported method specs the interface itself declares, once per name; an embedded interface is a role it composes, judged on its own declaration, and is not counted here. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
No seccomp profile config/default/manager_credentials_patch.yaml:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile config/default/manager_probes.yaml:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile config/default/manager_pull_policy.yaml:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile config/default/manager_webhook_patch.yaml:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
Interpolated log message defeats structured logging main.go:233— `Info` at line 233 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
Interpolated log message defeats structured logging pkg/logger/logger.go:136— `Info` at line 136 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
Interpolated log message defeats structured logging pkg/logger/logger.go:138— `Info` at line 138 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
Interpolated log message defeats structured logging controllers/rosacluster_controller.go:346— `Info` at line 346 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
Interpolated log message defeats structured logging controllers/rosacluster_controller.go:351— `Info` at line 351 is handed a message assembled at the call — `fmt.Sprintf` with values, or a string concatenated with a value — so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values as attributes instead: `slog.Info("order moved", "order_id", orderID, "status", status)` with log/slog, `logger.Info("order moved", zap.String("order_id", orderID))` with zap, `log.WithFields(log.Fields{"order_id": orderID}).Info("order moved")` with logrus, or `log.Info().Str("order_id", orderID).Msg("order moved")` with zerolog.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file pkg/cloud/services/eks/nodegroup.go:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file pkg/cloud/services/network/vpc.go:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file pkg/cloud/services/autoscaling/autoscalinggroup.go:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D21 · Naming Consistency· `DualStackDnsSuffix` spells `Dns` where 23 names in the project spell it `DNS` · ×2
`DualStackDnsSuffix` spells `Dns` where 23 names in the project spell it `DNS` pkg/cloud/endpoints/partition.go:41— 23 of 25 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `DNS` (23 of 25; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `DNS`). Peers: v1beta1.WaitForDNSNameReason (api/v1beta1/conditions_consts.go:119); v1beta1.WaitForDNSNameResolveReason (api/v1beta1/conditions_consts.go:121); sigs.k8s.io/cluster-api-provider-aws/v2/api/v1beta2.AWSLoadBalancerDNSResolutionCheck (api/v1beta2/awscluster_types.go:188); v1beta2.AWSLoadBalancerDNSResolutionCheckNone (api/v1beta2/awscluster_types.go:192); v1beta2.AWSLoadBalancerDNSResolutionCheckEnabled (api/v1beta2/awscluster_types.go:196). Rename to `DualStackDNSSuffix`. [rule N6]
`DualStackDnsSuffix` spells `Dns` where 23 names in the project spell it `DNS` pkg/cloud/endpoints/partition.go:53— 23 of 25 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `DNS` (23 of 25; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `DNS`). Peers: v1beta1.WaitForDNSNameReason (api/v1beta1/conditions_consts.go:119); v1beta1.WaitForDNSNameResolveReason (api/v1beta1/conditions_consts.go:121); sigs.k8s.io/cluster-api-provider-aws/v2/api/v1beta2.AWSLoadBalancerDNSResolutionCheck (api/v1beta2/awscluster_types.go:188); v1beta2.AWSLoadBalancerDNSResolutionCheckNone (api/v1beta2/awscluster_types.go:192); v1beta2.AWSLoadBalancerDNSResolutionCheckEnabled (api/v1beta2/awscluster_types.go:196). Rename to `DualStackDNSSuffix`. [rule N6]
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: exp/api/v1beta2/v1beta2_condition_consts.go, api/v1beta2/v1beta2_condition_consts.go, bootstrap/eks/api/v1beta2/v1beta2_condition_consts.go, controlplane/eks/api/v1beta2/v1beta2_condition_consts.go, controlplane/rosa/api/v1beta2/v1beta2_condition_consts.go. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (10 single-owned of 262 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 262 of the 460 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: pkg/cloud/identity/identity.go, pkg/cloud/services/gc/cleanup.go, cmd/clusterawsadm/cmd/ami/list/list.go, pkg/cloud/services/network/enis.go, bootstrap/eks/controllers/nodeadmconfig_controller.go.
D21 · Naming Consistency· `ClassicElbAttributes` spells `Elb` where 49 names in the project spell it `ELB` · ×1
`ClassicElbAttributes` spells `Elb` where 49 names in the project spell it `ELB` api/v1beta2/network_types.go:336— 49 of 50 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `ELB` (49 of 50; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `ELB`). Peers: NetworkStatus.APIServerELB (api/v1beta1/network_types.go:31); sigs.k8s.io/cluster-api-provider-aws/v2/api/v1beta1.ClassicELBScheme (api/v1beta1/network_types.go:35); v1beta1.ClassicELBSchemeInternetFacing (api/v1beta1/network_types.go:40); v1beta1.ClassicELBSchemeInternal (api/v1beta1/network_types.go:44); v1beta1.ClassicELBSchemeIncorrectInternetFacing (api/v1beta1/network_types.go:47). Rename to `ClassicELBAttributes`. [rule N6]
D21 · Naming Consistency· `makeEksEncryptionConfigs` spells `Eks` where 63 names in the project spell it `EKS` · ×1
`makeEksEncryptionConfigs` spells `Eks` where 63 names in the project spell it `EKS` pkg/cloud/services/eks/cluster.go:303— 63 of 65 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `EKS` (63 of 65; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `EKS`). Peers: v1beta1.SecurityGroupEKSNodeAdditional (api/v1beta1/network_types.go:405); v1beta2.SecurityGroupEKSNodeAdditional (api/v1beta2/network_types.go:963); EKSConfigReconciler.ClusterToEKSConfigs (bootstrap/eks/controllers/eksconfig_controller.go:371); EKSConfig.EnableUserEKSConsolePolicy (cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:102); EKSConfig.EnableUserEKSConsolePolicy (cmd/clusterawsadm/api/bootstrap/v1beta1/types.go:110). Rename to `makeEKSEncryptionConfigs`. [rule N6]
D21 · Naming Consistency· `makeEksLogging` spells `Eks` where 63 names in the project spell it `EKS` · ×1
`makeEksLogging` spells `Eks` where 63 names in the project spell it `EKS` pkg/cloud/services/eks/cluster.go:388— 63 of 65 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `EKS` (63 of 65; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `EKS`). Peers: v1beta1.SecurityGroupEKSNodeAdditional (api/v1beta1/network_types.go:405); v1beta2.SecurityGroupEKSNodeAdditional (api/v1beta2/network_types.go:963); EKSConfigReconciler.ClusterToEKSConfigs (bootstrap/eks/controllers/eksconfig_controller.go:371); EKSConfig.EnableUserEKSConsolePolicy (cmd/clusterawsadm/api/bootstrap/v1alpha1/types.go:102); EKSConfig.EnableUserEKSConsolePolicy (cmd/clusterawsadm/api/bootstrap/v1beta1/types.go:110). Rename to `makeEKSLogging`. [rule N6]
D21 · Naming Consistency· `GetQueueUrl` spells `Url` where 14 names in the project spell it `URL` · ×1
`GetQueueUrl` spells `Url` where 14 names in the project spell it `URL` pkg/cloud/services/instancestate/service.go:42— 14 of 15 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `URL` (14 of 15; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `URL`). Peers: S3Bucket.PresignedURLDuration (api/v1beta2/awscluster_types.go:388); ami.latestStableReleaseURL (cmd/clusterawsadm/ami/helper.go:38); OIDCIdentityProviderConfig.IssuerURL (controlplane/eks/api/v1beta1/types.go:257); OIDCIdentityProviderConfig.IssuerURL (controlplane/eks/api/v1beta2/types.go:372); RosaControlPlaneStatus.ConsoleURL (controlplane/rosa/api/v1beta2/rosacontrolplane_types.go:994). Rename to `GetQueueURL`. [rule N6]
D21 · Naming Consistency· `LaunchTemplateNeedsUpdateReasonIamInstanceProfile` spells `Iam` where 59 names in the project spell it `IAM` · ×1
`LaunchTemplateNeedsUpdateReasonIamInstanceProfile` spells `Iam` where 59 names in the project spell it `IAM` pkg/cloud/services/interfaces.go:52— 59 of 60 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `IAM` (59 of 60; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `IAM`). Peers: S3Bucket.ControlPlaneIAMInstanceProfile (api/v1beta1/awscluster_types.go:214); S3Bucket.NodesIAMInstanceProfiles (api/v1beta1/awscluster_types.go:218); sigs.k8s.io/cluster-api-provider-aws/v2/api/v1beta2.AdditionalIAMRole (api/v1beta2/awscluster_types.go:343); S3Bucket.ControlPlaneIAMInstanceProfile (api/v1beta2/awscluster_types.go:364); S3Bucket.NodesIAMInstanceProfiles (api/v1beta2/awscluster_types.go:369). Rename to `LaunchTemplateNeedsUpdateReasonIAMInstanceProfile`. [rule N6]
D21 · Naming Consistency· `htpasswdIDPId` spells `Id` where 290 names in the project spell it `ID` · ×1
`htpasswdIDPId` spells `Id` where 290 names in the project spell it `ID` pkg/rosa/ocmclient.go:50— 290 of 292 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `ID` (290 of 292; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `ID`). Peers: AWSClusterRoleIdentitySpec.ExternalID (api/v1beta1/awsidentity_types.go:145); AWSMachineSpec.ProviderID (api/v1beta1/awsmachine_types.go:48); AWSMachineSpec.InstanceID (api/v1beta1/awsmachine_types.go:51); IPv6.PoolID (api/v1beta1/network_types.go:176); IPv6.EgressOnlyInternetGatewayID (api/v1beta1/network_types.go:180). Rename to `htpasswdIDPID`. [rule N6]
D21 · Naming Consistency· `ConvertToRosaOcmClient` spells `Ocm` where 19 names in the project spell it `OCM` · ×1
`ConvertToRosaOcmClient` spells `Ocm` where 19 names in the project spell it `OCM` pkg/rosa/ocmclient.go:215— 19 of 20 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `OCM` (19 of 20; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `OCM`). Peers: ROSAClusterReconciler.NewOCMClient (controllers/rosacluster_controller.go:60); ROSAControlPlaneReconciler.NewOCMClient (controlplane/rosa/controllers/rosacontrolplane_controller.go:108); ROSAControlPlaneReconciler.updateOCMCluster (controlplane/rosa/controllers/rosacontrolplane_controller.go:847); ROSAControlPlaneReconciler.updateOCMClusterSpec (controlplane/rosa/controllers/rosacontrolplane_controller.go:867); controllers.buildOCMClusterSpec (controlplane/rosa/controllers/rosacontrolplane_controller.go:1357). Rename to `ConvertToRosaOCMClient`. [rule N6]
D21 · Naming Consistency· `AwsSdkVersion` spells `Sdk` where 27 names in the project spell it `SDK` · ×1
`AwsSdkVersion` spells `Sdk` where 27 names in the project spell it `SDK` version/version.go:45— 27 of 28 names in project sigs.k8s.io/cluster-api-provider-aws/v2 spell the token `SDK` (27 of 28; unit: names in project sigs.k8s.io/cluster-api-provider-aws/v2 containing `SDK`). Peers: converters.AddonSDKToAddonState (pkg/cloud/converters/eks.go:42); converters.TaintToSDK (pkg/cloud/converters/eks.go:77); converters.TaintsToSDK (pkg/cloud/converters/eks.go:90); converters.TaintsFromSDK (pkg/cloud/converters/eks.go:105); converters.TaintEffectToSDK (pkg/cloud/converters/eks.go:123). Rename to `AwsSDKVersion`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion REDACTED:1— `(repository root)` (69370 LoC, 829 module-visible types across 124 directories) overshoots its size bounds. 1 of 5 build unit(s) (Go, Python) overshoot their size bounds, lowering Project Cohesion to 6.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Concentrated knowledge decay — 145 of 266 significant files have no living knowledge, while the repository is still being changed at a low rate (141 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 145 separate risks. Counted over 266 of the 460 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
D42 · Runtime Threat Enforcement· No admission-control policy · ×1
No admission-control policy — No policy-enforcement gate (Kyverno / OPA Gatekeeper / PodSecurity admission) is committed. Admission control keeps workloads that violate your security baseline from ever reaching the cluster.
Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `docs/triage-party`.
P3 · Security & performance tooling· Dependabot does not watch uv · ×1
Dependabot does not watch uv REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `uv`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
No security response headers detected netlify.toml:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
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 2/4 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.
Outdated: github.com/alessio/shellescape — `github.com/alessio/shellescape` is required at v1.4.2 in REDACTED, but v1.6.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/alessio/shellescape@v1.6.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/amazon-vpc-cni-k8s — `github.com/aws/amazon-vpc-cni-k8s` is required at v1.22.4 in REDACTED, but v1.23.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/amazon-vpc-cni-k8s@v1.23.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2 — `github.com/aws/aws-sdk-go-v2` is required at v1.47.1 in REDACTED, but v1.48.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2@v1.48.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/config — `github.com/aws/aws-sdk-go-v2/config` is required at v1.33.6 in REDACTED, but v1.33.19 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/config@v1.33.19 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/credentials — `github.com/aws/aws-sdk-go-v2/credentials` is required at v1.20.6 in REDACTED, but v1.21.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/credentials@v1.21.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/autoscaling — `github.com/aws/aws-sdk-go-v2/service/autoscaling` is required at v1.78.1 in REDACTED, but v1.82.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/autoscaling@v1.82.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/cloudformation — `github.com/aws/aws-sdk-go-v2/service/cloudformation` is required at v1.81.1 in REDACTED, but v1.84.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/cloudformation@v1.84.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/cloudtrail — `github.com/aws/aws-sdk-go-v2/service/cloudtrail` is required at v1.65.1 in REDACTED, but v1.65.12 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/cloudtrail@v1.65.12 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/configservice — `github.com/aws/aws-sdk-go-v2/service/configservice` is required at v1.74.1 in REDACTED, but v1.75.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/configservice@v1.75.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/ec2 — `github.com/aws/aws-sdk-go-v2/service/ec2` is required at v1.336.1 in REDACTED, but v1.348.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/ec2@v1.348.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/ecrpublic — `github.com/aws/aws-sdk-go-v2/service/ecrpublic` is required at v1.47.1 in REDACTED, but v1.47.12 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/ecrpublic@v1.47.12 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/efs — `github.com/aws/aws-sdk-go-v2/service/efs` is required at v1.49.1 in REDACTED, but v1.51.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/efs@v1.51.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/eks — `github.com/aws/aws-sdk-go-v2/service/eks` is required at v1.101.0 in REDACTED, but v1.105.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/eks@v1.105.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing — `github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing` is required at v1.41.1 in REDACTED, but v1.42.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing@v1.42.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 — `github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2` is required at v1.63.1 in REDACTED, but v1.64.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2@v1.64.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/eventbridge — `github.com/aws/aws-sdk-go-v2/service/eventbridge` is required at v1.55.0 in REDACTED, but v1.55.11 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/eventbridge@v1.55.11 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/iam — `github.com/aws/aws-sdk-go-v2/service/iam` is required at v1.64.1 in REDACTED, but v1.66.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/iam@v1.66.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi — `github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi` is required at v1.41.1 in REDACTED, but v1.42.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi@v1.42.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/s3 — `github.com/aws/aws-sdk-go-v2/service/s3` is required at v1.113.4 in REDACTED, but v1.114.10 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/s3@v1.114.10 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/secretsmanager — `github.com/aws/aws-sdk-go-v2/service/secretsmanager` is required at v1.50.1 in REDACTED, but v1.51.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/secretsmanager@v1.51.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/servicequotas — `github.com/aws/aws-sdk-go-v2/service/servicequotas` is required at v1.43.1 in REDACTED, but v1.43.12 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/servicequotas@v1.43.12 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/sqs — `github.com/aws/aws-sdk-go-v2/service/sqs` is required at v1.52.1 in REDACTED, but v1.53.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/sqs@v1.53.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/ssm — `github.com/aws/aws-sdk-go-v2/service/ssm` is required at v1.78.1 in REDACTED, but v1.83.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/ssm@v1.83.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/aws-sdk-go-v2/service/sts — `github.com/aws/aws-sdk-go-v2/service/sts` is required at v1.51.1 in REDACTED, but v1.52.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/aws-sdk-go-v2/service/sts@v1.52.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/aws/constructs-go/constructs/v3 — `github.com/aws/constructs-go/constructs/v3` is required at v3.3.87 in docs/triage-party/REDACTED, but v3.4.344 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/aws/constructs-go/constructs/v3@v3.4.344 && go mod tidy` and commit the updated REDACTED and go.sum.
+ 36 more in this group — see findings.md.
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.
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.
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.
Run 01a1e79e-ac37-73a8-8906-cab16940bf1c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 20 · Warnings: 1037 · Recommendations: 215 · Info: 61 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 03:48 UTC.
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.