Public report of openshift/cluster-node-tuning-operator, published 16 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, 16 November 2026, 22:02 UTC · Survey ID cd_0bb4851b273c4320b1de9f1a049debe2
openshift/cluster-node-tuning-operator
Measured 16 November 2026, 22:01 UTC, at code version aa0cdf2
Code coverage is not measured: Go suite (CouldNotMeasureRanButNoData).
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A small codebase: 18,351 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 57.2
Findings by how serious they are
11 critical244 serious26 minor
26 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
16 November 2026, 22:01 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
42of 42 dimensions measured by tools.
272of 281 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
42dimensions across 5 lenses, read from 18,351 lines of product code in 1 project.
openshift/cluster-node-tuning-operator falls short of our standard for production because we found no working pipeline that builds or tests changes to the code. It scores 66.5 out of 100 and is rated Adequate, and all 11 of its critical findings are security problems.
Production Readiness, at 57.2, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 8.1 points. Raising Production Readiness to 70 would lift the score to about 72.6.
Seven settings leave the servers or containers unsafe. Two pipeline steps run downloads nobody checks, and one automatic update takes new releases before a bad one can be spotted. Correcting the unsafe settings, checking each download against a checksum and setting a waiting period for automatic updates would close these risks. Reading outside data into plain values would fix the place where outside data is turned straight into objects.
The product code is 18,351 lines, about €65,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 Production Readiness rose from 57.2 to 70, the lowest score rated Strong, the score would rise from 66.5 to about 72.6.
Code composition: what the lines of code are
Product code 34%Tests 66%
Rebuild cost: about €65,000 · Estimate
Cost to rebuild
€22,000 to €110,000, for 362 to 1,148 hours of work, about 0.4 person-years for one engineer
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 67. 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
Small: 18,351 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
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 8.1 points · Medium effort · CI/CD gates
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go.
Raises the score by about 1.9 points · Low effort · ADR Quality
3
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €65,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 57.2 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a CI workflow that builds and runs the test suite on every push/PR. Of all the actions in this report, it raises the score most for the work it takes: about 8.1 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.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 5,412 lines over the last 90 days, which is about 21,949 lines a year. At that pace, the extra work comes to an estimated 3.5 to 20.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.
48 modules, with 40 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 8 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 com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components can break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, while a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/manifests uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/manifests uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/manifests, while a change to com/openshift/cluster-node-tuning-operator/pkg/manifests can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/manifests uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/serialize uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/serialize uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/serialize, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/serialize can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/toleration.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/serialize uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/util uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/util uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/util, while a change to com/openshift/cluster-node-tuning-operator/pkg/util can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/util uses a module listed above it, which is the healthy direction.
12 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/operator uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/operator uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/operator, while a change to com/openshift/cluster-node-tuning-operator/pkg/operator can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/operator uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/operator uses a type in com/openshift/cluster-node-tuning-operator/pkg/client.
com/openshift/cluster-node-tuning-operator/pkg/operator uses com/openshift/cluster-node-tuning-operator/pkg/client, so a change to com/openshift/cluster-node-tuning-operator/pkg/client can break com/openshift/cluster-node-tuning-operator/pkg/operator, while a change to com/openshift/cluster-node-tuning-operator/pkg/operator can't break com/openshift/cluster-node-tuning-operator/pkg/client.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/operator uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/operator uses a type in com/openshift/cluster-node-tuning-operator/pkg/util.
com/openshift/cluster-node-tuning-operator/pkg/operator uses com/openshift/cluster-node-tuning-operator/pkg/util, so a change to com/openshift/cluster-node-tuning-operator/pkg/util can break com/openshift/cluster-node-tuning-operator/pkg/operator, while a change to com/openshift/cluster-node-tuning-operator/pkg/operator can't break com/openshift/cluster-node-tuning-operator/pkg/util.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/operator uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/machineconfig uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/profile uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/runtimeclass uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/runtimeclass uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/runtimeclass, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/runtimeclass can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/runtimeclass uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/tuned uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/resources uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/cmd uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/cmd uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/cmd, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/cmd can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/profilecreator/cmd uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/utils/testing uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/utils/testing uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/utils/testing, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/utils/testing can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/utils/testing uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/tuned uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/tuned uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/tuned, while a change to com/openshift/cluster-node-tuning-operator/pkg/tuned can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/tuned uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/tuned uses a type in com/openshift/cluster-node-tuning-operator/pkg/client.
com/openshift/cluster-node-tuning-operator/pkg/tuned uses com/openshift/cluster-node-tuning-operator/pkg/client, so a change to com/openshift/cluster-node-tuning-operator/pkg/client can break com/openshift/cluster-node-tuning-operator/pkg/tuned, while a change to com/openshift/cluster-node-tuning-operator/pkg/tuned can't break com/openshift/cluster-node-tuning-operator/pkg/client.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/tuned uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/tuned uses a type in com/openshift/cluster-node-tuning-operator/pkg/util.
com/openshift/cluster-node-tuning-operator/pkg/tuned uses com/openshift/cluster-node-tuning-operator/pkg/util, so a change to com/openshift/cluster-node-tuning-operator/pkg/util can break com/openshift/cluster-node-tuning-operator/pkg/tuned, while a change to com/openshift/cluster-node-tuning-operator/pkg/tuned can't break com/openshift/cluster-node-tuning-operator/pkg/util.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/tuned uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render, while a change to com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render, while a change to com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/tuned/cmd/render uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components/manifestset.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/cmd/render uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller can't break com/openshift/cluster-node-tuning-operator/pkg/apis/tuned/v1.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/components.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status uses a type in com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status uses com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2, so a change to com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2 can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status can't break com/openshift/cluster-node-tuning-operator/pkg/apis/performanceprofile/v2.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status uses a type in com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status.
com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status uses com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status, so a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status can break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status, while a change to com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status can't break com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/status.
Position
Below the diagonal: com/openshift/cluster-node-tuning-operator/pkg/performanceprofile/controller/performanceprofile/hypershift/status uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 71.9 · Adequate · gated by D2 ·
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
58
High / Critical
A05:2025 — Injection
9
High / Critical
A03:2025 — Software Supply Chain Failures
1
Medium
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 — 11
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 — 244
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 — 26
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 26
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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, 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 — 42 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, 272 of 281 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.
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.
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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (18351 LoC, 151 module-visible types across 49 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
D32 Data Compliance (PII/GDPR) — 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. `pkg/generated/listers/tuned/v1/profile.go`, `pkg/generated/listers/tuned/v1/tuned.go`, `pkg/tuned/cmd/render/render.go` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 93 commits in the last 90 days, yet 27 of 51 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
AXB2 Runtime readiness — 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. An image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository. (rule: registry). The renderer reported: docker build failed (exit 1) — -------------------- ERROR: failed to solve: registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.26-openshift-5.1: failed to resolve source metadata for registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.26-openshift-5.1: failed to do request: Head "https://registry.ci.openshift.org/v2/openshift/release/manifests/rhel-9-release-golang-1.26-openshift-5.1": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
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 REDACTED (REDACTED). docker build failed (exit 1) — -------------------- ERROR: failed to solve: registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.26-openshift-5.1: failed to resolve source metadata for registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.26-openshift-5.1: failed to do request: Head "https://registry.ci.openshift.org/v2/openshift/release/manifests/rhel-9-release-golang-1.26-openshift-5.1": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
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 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 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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async 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, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust 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.
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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
X13 Undrained process stream — 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, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java 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.
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.
X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X22 Contradicted release guard — 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# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's Go 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.
X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, 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.
X24 Document value interpolated into markup unescaped — 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, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python 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.
X25 Inert configuration knob — 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, Scala, PHP, Erlang, Python, Dart, Ruby and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby 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.
Repo exclusion declarations: 5 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
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.
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.
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 Secret Scanning: Secret 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.
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.
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.
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.
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".
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.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 27 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with tuned.NewNodePerformance (cyclomatic 51), Controller.sync (cyclomatic 50), machineconfig.getIgnitionConfig (cyclomatic 41). — 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 27 together lifts Cyclomatic Complexity from 5.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 48 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with tuned.NewNodePerformance (cognitive 92), Controller.sync (cognitive 75), machineconfig.getIgnitionConfig (cognitive 74). — 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 6 together lifts Cognitive Complexity from 2.0 to about 3.2/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.5 / 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.
Resolve the 3 FileTooLong finding(s) in God Classes — start with controller.go (2), machineconfig.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 FunctionTooLong finding(s) in God Classes — start with machineconfig.go, tuned.go, render.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with controller.go (2), status.go. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
47 duplicated block group(s) detected. 12.5 % of the production lines (2,286 of 18,351) are in a reported copy. A further 25 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (26 corresponding lines) · ×2pkg/performanceprofile/profilecreator/mustgather.go:108
Edited copy of a member (23 corresponding lines) · ×2pkg/performanceprofile/controller/performanceprofile_controller.go:170
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with performanceprofile_controller.go (3), performanceprofile_conversion.go, hypershift.go. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with machineconfig.go, REDACTED, performanceprofile_controller.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with performanceprofile_conversion.go (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with performanceprofile_controller.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_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.
2 outdated, 0 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 40 of 40 direct requirement(s) were graded against proxy.golang.org (0 not served there, 9 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/coreos/go-systemd
Outdated: gopkg.in/ini.v1 · ×2
What to do
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 143 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. A further 1 module(s) are not known to the public Go module index (private modules, or pins the public proxy never served) and are outside this verdict.
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.
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.
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is pkg/tuned/controller.go. Counted over 51 of the 100 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.
21 deducted task-comment markers across 18351 LoC (0.1/KLoC) → score 9.8. 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 20 TodoComment finding(s) in Explicit Debt — start with llc.go (5), REDACTED (2), v1.go (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with devices.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.
1 of 1 documentation facets pass in full. 12 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundcmd/performance-profile-creator/main.go:17
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency10.0 / 10Exemplary○ Nothing flagged
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.
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.
39 % of calls cross a namespace and 1 % go through an interface, but 59 % of collaborators are co-located — so following a call takes several hops. 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: Secret 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.
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).
9 finding(s): 0 critical, 4 high, 4 medium, 1 low. semgrep hit a parse error in 3 file(s) — `pkg/generated/listers/tuned/v1/profile.go` (lines 39–40, line 41, line 44, …), `pkg/generated/listers/tuned/v1/tuned.go` (lines 39–40, line 41, line 44, …), `pkg/tuned/cmd/render/render.go` (line 359) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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).
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 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 44 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (22), REDACTED (15), REDACTED (3). — One of this dimension's main actionable groups (44 warning-level).
Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 7 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d31_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.
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.
0/3 workload(s) run every container under a seccomp profile; 0/3 declare an AppArmor/SELinux profile.
No seccomp profile · ×3REDACTED:2
What to do
Resolve the 3 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, 50-operator-ibm-cloud-managed.yaml, REDACTED. — One of this dimension's main actionable groups (3 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).
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 1 platform declaration(s) and 0 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.
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.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
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 `gitsubmodule`, 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:17
What to do
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
Dependabot is configured but does not watch `gitsubmodule` — 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.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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.
`execCmd` hands values from a goroutine to the body waiting on it through `out`, a variable — the goroutine writes it with `out += …` on line 267, and the body touches it at line 301. Those two spans provably run concurrently: this body waits on `chReader`, which nothing but the goroutine raises, so the goroutine cannot be the flow that is waiting for it. The touch comes after the goroutine is started and BEFORE the body waits on `chReader`, so the Go memory model orders nothing between it and the goroutine's write. A goroutine's closure captures `out` by reference, so every goroutine and the body use ONE variable, and a plain variable has no synchronisation of its own: by the Go memory model a write concurrent with any other access to it is a data race (the race detector reports it), a racing `++` loses updates, and a racing read sees a stale or torn value. `chReader` is a channel, which orders the handoff's signal and takes no exclusion over the variable's own state. Hand the values over the channel itself instead of beside it, or guard every access to `out` on both sides with one `sync.Mutex`. — pkg/tuned/tuned_parser.go:267
What to do
In Go, hand values from a goroutine to the body waiting on it over a channel the body receives from, rather than through a map or slice beside a `sync.WaitGroup` or a signal channel — or hold one `sync.Mutex` over every access to the shared map or slice on both sides. The wait orders the signal; it takes no exclusion over the map's or slice's own state.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — 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.
`object, ok := o.(metav1.Object)` failed on this branch, so `object` is the zero value of `metav1.Object` here, and that is what is reported: the value that did not fit is lost. Report `o` itself (and `%T` of it) instead. (×2) — pkg/tuned/controller.go:1517, pkg/operator/controller.go:1247
`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. (×3) — REDACTED:47, REDACTED:44, pkg/performanceprofile/controller/performanceprofile/components/utils.go:57
What to do
Lost error (reports the zero value of a failed type assertion)
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 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 — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 68 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
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.
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 — docker build failed (exit 1) — -------------------- ERROR: failed to solve: registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.26-openshift-5.1: failed to resolve source metadata for registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.26-openshift-5.1: failed to do request: Head "https://registry.ci.openshift.org/v2/openshift/release/manifests/rhel-9-release-golang-1.26-openshift-5.1": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped 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 — ~35569 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.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
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, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the Go half could not be measured — the Go suite ran but its cover profiles carried none of the module's own source. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
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 only 1 of the 3 signals this lens looks for (1 event-sourced shape(s) (event folds / event-recording aggregates))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 Go aggregate(s) recording domain events (own events-slice append / raise-record))
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 — no CI workflow found
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go source (service entry point: REDACTED:68 (http.Server {))
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async 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
X12 Unreachable branch — 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
X13 Undrained process stream — 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
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X17 Uncapped recursion over a caller-supplied document — not 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
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
X2 Cancellation propagation — 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
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: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — 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
X23 Unguarded diagnostic materialisation — 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
X24 Document value interpolated into markup unescaped — 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
X25 Inert configuration knob — 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
X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — 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/performanceprofile/functests/utils/resources/resources.go:8— // TODO: handle init containers vs application containers — 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/performanceprofile/functests/utils/cgroup/v2/v2.go:91— // TODO — 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/performanceprofile/functests/utils/cgroup/v1/v1.go:88— // TODO — 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/performanceprofile/functests/utils/cgroup/v1/v1.go:113— // TODO — 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/performanceprofile/functests/13_llc/llc.go:1611— // TODO — 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/performanceprofile/functests/utils/baseload/baseload.go:12— // TODO: Currently this package only calculates CPU-based load. To support other — 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/performanceprofile/functests/5_latency_testing/5_latency_testing_suite_test.go:35— // TODO get commonly used variables from one shared file that defines constants — 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/performanceprofile/functests/5_latency_testing/latency_testing.go:21— // TODO get commonly used variables from one shared file that defines constants — 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/performanceprofile/functests/2_performance_update/updating_profile.go:463— // TODO - This test case is highly specific to MCP. — 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/performanceprofile/functests/1_performance/cpu_management.go:132— // TODO: adjust the test to consider having shared CPUs — 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/performanceprofile/functests/13_llc/llc.go:1419— // TODO log what? — 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/performanceprofile/functests/13_llc/llc.go:1445— // TODO log what? — 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/performanceprofile/functests/13_llc/llc.go:1423— // TODO: to be really safe we should add SMT level cpus — 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/performanceprofile/functests/13_llc/llc.go:1633— // TODO: we assume all L3 Groups are equal in size. — 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/performanceprofile/profilecreator/cmd/root.go:455— // TODO: Get the name from MCP if not specified in the command line arguments — 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:52— // TODO: we should merge all create, get and delete methods — 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/performanceprofile/controller/performanceprofile/components/consts.go:10— // TODO: change it back to longer name once https://bugzilla.redhat.com/show_bug.cgi?id=1787907 fixed
TodoComment pkg/operator/hypershift.go:33— // TODO remove once HyperShift has switched to using new key. — 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/generated/informers/externalversions/generic.go:51— // TODO extend this to unknown resources with a client pool — 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/apis/performanceprofile/v2/performanceprofile_validation.go:124— // TODO(user): fill in your validation logic upon object deletion. — 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.
Duplicated block (6 lines × 2) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:29— pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:29-34 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:201-206 — 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/apis/performanceprofile/v2/performanceprofile_conversion.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 (6 lines × 2) pkg/performanceprofile/controller/performanceprofile/hypershift/hypershift.go:233— pkg/performanceprofile/controller/performanceprofile/hypershift/hypershift.go:233-238 | pkg/performanceprofile/controller/performanceprofile/hypershift/hypershift.go:243-248 — 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 (6 lines × 2) pkg/performanceprofile/controller/performanceprofile_controller.go:620— pkg/performanceprofile/controller/performanceprofile_controller.go:620-625 | pkg/performanceprofile/controller/performanceprofile_controller.go:629-634 — 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/performanceprofile/controller/performanceprofile_controller.go:620` 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 × 2) pkg/performanceprofile/controller/performanceprofile_controller.go:666— pkg/performanceprofile/controller/performanceprofile_controller.go:666-671 | pkg/performanceprofile/controller/performanceprofile_controller.go:675-680 — 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/performanceprofile/controller/performanceprofile_controller.go:666` 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 × 2) pkg/performanceprofile/controller/performanceprofile_controller.go:197— pkg/performanceprofile/controller/performanceprofile_controller.go:197-202 | pkg/performanceprofile/controller/performanceprofile_controller.go:220-225 — 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/performanceprofile/controller/performanceprofile_controller.go:197` 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/operator/controller.go:1450— pkg/operator/controller.go:1450-1455 | pkg/operator/controller.go:1462-1467 — 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/operator/controller.go:1450` 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.
FileTooLong: tuned/controller.go pkg/tuned/controller.go— FileTooLong — 1023 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 523 over it, 2.05× 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.
FileTooLong: operator/controller.go pkg/operator/controller.go— FileTooLong — 921 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: Controller (26 blocks, 66-1543). The bar is 500 significant lines; this is 421 over it, 1.84× 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: machineconfig/machineconfig.go pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go— FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2 over it, 1.00× 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.
FunctionTooLong: machineconfig.getIgnitionConfig pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:188— FunctionTooLong — getIgnitionConfig runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: tuned.NewNodePerformance pkg/performanceprofile/controller/performanceprofile/components/tuned/tuned.go:61— FunctionTooLong — NewNodePerformance runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: render.render pkg/tuned/cmd/render/render.go:108— FunctionTooLong — render runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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: Controller.sync pkg/operator/controller.go:215— MethodTooLong — sync runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: Controller.computeStatus pkg/operator/status.go:225— MethodTooLong — computeStatus runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: Controller.syncProfile pkg/operator/controller.go:591— MethodTooLong — syncProfile 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 (12 lines × 2) pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:705— pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:705-716 | pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:741-752 — 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/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:705` 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) REDACTED:68— REDACTED:68-79 | REDACTED:146-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.
Duplicated block (12 lines × 2) pkg/performanceprofile/controller/performanceprofile_controller.go:132— pkg/performanceprofile/controller/performanceprofile_controller.go:132-143 | pkg/performanceprofile/controller/performanceprofile_controller.go:263-274 — 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/performanceprofile/controller/performanceprofile_controller.go:132` 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 (11 lines × 2) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:82— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:82-92 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:187-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. Read the line range as the matched WINDOW rather than a finished unit: at `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:82` 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:88— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:88-98 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:112-122 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:88` 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:193— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:193-203 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:272-282 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:193` 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.
Swallowed exception (caught, then discarded) REDACTED:47— `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) REDACTED:44— `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/performanceprofile/controller/performanceprofile/components/utils.go:57— `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.
ClassTooLong: Controller pkg/operator/controller.go:66— ClassTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods, 26 blocks, lines 66-1543. The bar is 400 significant lines; this is 408 over it, 2.02× 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: Controller pkg/tuned/controller.go:202— ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods, 24 blocks, lines 202-1621. The bar is 400 significant lines; this is 111 over it, 1.28× 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.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) pkg/performanceprofile/profilecreator/mustgather.go:108— pkg/performanceprofile/profilecreator/mustgather.go:108-133 | pkg/performanceprofile/profilecreator/mustgather.go:136-163 — 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) pkg/clusteroperator/status.go:11— pkg/clusteroperator/status.go:11-36 | pkg/tuned/status.go:12-37 — 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 (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) pkg/performanceprofile/controller/performanceprofile_controller.go:170— pkg/performanceprofile/controller/performanceprofile_controller.go:170-192 | pkg/performanceprofile/controller/performanceprofile_controller.go:311-333 — 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.
Edited copy of a member (23 corresponding lines) pkg/operator/mc.go:47— pkg/operator/mc.go:47-69 | pkg/operator/mc.go:73-97 — 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.
Duplicated block (20 lines × 2) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:14— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:14-33 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:14-33 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:14` 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 (20 lines × 2) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:120— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:120-139 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:186-205 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.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 (16 lines × 2) pkg/operator/controller.go:1233— pkg/operator/controller.go:1233-1248 | pkg/tuned/controller.go:1503-1518 — 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 `pkg/operator/controller.go:1233` 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) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:142— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:142-157 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:216-231 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.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 (9 lines × 2) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:108— pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:108-116 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:268-276 — 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/apis/performanceprofile/v2/performanceprofile_conversion.go:108` 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/operator/controller.go:864— pkg/operator/controller.go:864-872 | pkg/operator/controller.go:1016-1026 — 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/operator/controller.go:864` 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:29— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:29-36 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:135-142 — 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.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 (8 lines × 2) pkg/performanceprofile/controller/performanceprofile_controller.go:411— pkg/performanceprofile/controller/performanceprofile_controller.go:411-418 | pkg/performanceprofile/controller/performanceprofile_controller.go:450-458 — 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/performanceprofile/controller/performanceprofile_controller.go:411` 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 before the matched lines, `pkg/performanceprofile/controller/performanceprofile_controller.go:410` calls `GetNamespace` and `pkg/performanceprofile/controller/performanceprofile_controller.go:448` 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 (7 lines × 2) pkg/performanceprofile/controller/performanceprofile_controller.go:86— pkg/performanceprofile/controller/performanceprofile_controller.go:86-93 | pkg/performanceprofile/controller/performanceprofile_controller.go:246-252 — 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/performanceprofile/controller/performanceprofile_controller.go:86` 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 (7 lines × 2) pkg/operator/hypershift.go:232— pkg/operator/hypershift.go:232-238 | pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:305-311 — 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 (13 lines × 2) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:301— pkg/apis/performanceprofile/v2/performanceprofile_validation.go:301-313 | pkg/apis/performanceprofile/v2/performanceprofile_validation.go:349-361 — 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/apis/performanceprofile/v2/performanceprofile_validation.go:301` 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) pkg/performanceprofile/controller/performanceprofile/components/handler/handler.go:44— pkg/performanceprofile/controller/performanceprofile/components/handler/handler.go:44-56 | pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:94-106 — 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 `pkg/performanceprofile/controller/performanceprofile/components/handler/handler.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. 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· Lost error (reports the zero value of a failed type assertion) · ×2
Lost error (reports the zero value of a failed type assertion) pkg/tuned/controller.go:1517— `object, ok := o.(metav1.Object)` failed on this branch, so `object` is the zero value of `metav1.Object` here, and that is what is reported: the value that did not fit is lost. Report `o` itself (and `%T` of it) instead.
Lost error (reports the zero value of a failed type assertion) pkg/operator/controller.go:1247— `object, ok := o.(metav1.Object)` failed on this branch, so `object` is the zero value of `metav1.Object` here, and that is what is reported: the value that did not fit is lost. Report `o` itself (and `%T` of it) instead.
tuned.NewNodePerformance (cyclomatic 51) pkg/performanceprofile/controller/performanceprofile/components/tuned/tuned.go:61— tuned.NewNodePerformance has cyclomatic complexity 51 (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.
Controller.sync (cyclomatic 50) pkg/operator/controller.go:215— Controller.sync has cyclomatic complexity 50 (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.
machineconfig.getIgnitionConfig (cyclomatic 41) pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:188— machineconfig.getIgnitionConfig 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.
PerformanceProfile.ConvertTo (cyclomatic 40) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:13— PerformanceProfile.ConvertTo 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.
PerformanceProfile.ConvertFrom (cyclomatic 37) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:185— PerformanceProfile.ConvertFrom has cyclomatic complexity 37 (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.
Controller.syncProfile (cyclomatic 36) pkg/operator/controller.go:591— Controller.syncProfile 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.
tuned.expandTuneDBuiltin (cyclomatic 32) pkg/tuned/tuned_parser.go:418— tuned.expandTuneDBuiltin has cyclomatic complexity 32 (threshold 15). Of this number, 30 points are the body's own statements and 2 belong 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.
render.render (cyclomatic 31) pkg/performanceprofile/cmd/render/render.go:82— render.render 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.
handler.Apply (cyclomatic 30) pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:75— handler.Apply has cyclomatic complexity 30 (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.
kubeletconfig.setKubeletConfigForCPUAndMemoryManagers (cyclomatic 29) pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig/kubeletconfig.go:122— kubeletconfig.setKubeletConfigForCPUAndMemoryManagers has cyclomatic complexity 29 (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.
render.render (cyclomatic 28) pkg/tuned/cmd/render/render.go:108— render.render has cyclomatic complexity 28 (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.
handler.Apply (cyclomatic 25) pkg/performanceprofile/controller/performanceprofile/components/handler/handler.go:35— handler.Apply 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.
Controller.changeSyncerTuneD (cyclomatic 25) pkg/tuned/controller.go:975— Controller.changeSyncerTuneD 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.
PerformanceProfile.ConvertTo (cyclomatic 24) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:13— PerformanceProfile.ConvertTo 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. This shape REPEATS in the file: one other method here (PerformanceProfile.ConvertFrom) 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.
PerformanceProfile.ConvertFrom (cyclomatic 24) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:119— PerformanceProfile.ConvertFrom 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. This shape REPEATS in the file: one other method here (PerformanceProfile.ConvertTo) 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.
PerformanceProfile.validateHugePages (cyclomatic 22) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:367— PerformanceProfile.validateHugePages 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.
metrics.RunServer (cyclomatic 21) REDACTED:177— metrics.RunServer has cyclomatic complexity 21 (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.
ProfileCalculator.calculateProfile (cyclomatic 21) pkg/operator/profilecalculator.go:190— ProfileCalculator.calculateProfile has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong 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.
main.operatorRun (cyclomatic 20) cmd/cluster-node-tuning-operator/main.go:119— main.operatorRun has cyclomatic complexity 20 (threshold 15). 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, 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.
Controller.computeStatus (cyclomatic 20) pkg/operator/status.go:225— Controller.computeStatus 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.
PerformanceProfileReconciler.Reconcile (cyclomatic 20) pkg/performanceprofile/controller/performanceprofile_controller.go:520— PerformanceProfileReconciler.Reconcile 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.
ProfileCalculator.calculateProfileHyperShift (cyclomatic 19) pkg/operator/profilecalculator.go:342— ProfileCalculator.calculateProfileHyperShift has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong 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.
Controller.syncMachineConfigHyperShift (cyclomatic 18) pkg/operator/controller.go:932— Controller.syncMachineConfigHyperShift has cyclomatic complexity 18 (threshold 15). Of this number, 17 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.
tuned.TunedRun (cyclomatic 17) pkg/tuned/run.go:120— tuned.TunedRun has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 129). 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.
tuned.execCmd (cyclomatic 17) pkg/tuned/tuned_parser.go:220— tuned.execCmd has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 273, 251). The decisions are inside those literals, 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 literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
profilecreator.CalculateCPUSets (cyclomatic 16) pkg/performanceprofile/profilecreator/profilecreator.go:118— profilecreator.CalculateCPUSets 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.
profilecreator.getOvsDpdkCPUs (cyclomatic 16) pkg/performanceprofile/profilecreator/profilecreator.go:200— profilecreator.getOvsDpdkCPUs has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong 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.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×1
Dependency pinned to a stale untagged commit: github.com/coreos/go-systemd — Direct dependency `github.com/coreos/go-systemd` is required at `v0.0.0-20191104093116-d3cd4ed1dbcf` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2019-11-04, 7 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/coreos/go-systemd` and has not moved this requirement in 7 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/coreos/go-systemd` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
FixmeComment test/e2e/performanceprofile/functests/9_reboot/devices.go:39— // FIXME — 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.
tuned.NewNodePerformance (cognitive 92) pkg/performanceprofile/controller/performanceprofile/components/tuned/tuned.go:61— tuned.NewNodePerformance has cognitive complexity 92 (threshold 15). Drivers by points: if/else 41 (81 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 42). 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.
Controller.sync (cognitive 75) pkg/operator/controller.go:215— Controller.sync has cognitive complexity 75 (threshold 15). Drivers by points: if/else 39 (69 pts), boolean chains 2, jumps 2, match/switch 2 (nesting depth added 30). 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.
machineconfig.getIgnitionConfig (cognitive 74) pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:188— machineconfig.getIgnitionConfig has cognitive complexity 74 (threshold 15). Drivers by points: if/else 38 (69 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 32). 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.
PerformanceProfile.ConvertTo (cognitive 72) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:13— PerformanceProfile.ConvertTo has cognitive complexity 72 (threshold 15). Drivers by points: if/else 34 (60 pts), loops 5 (12 pts) (nesting depth added 33). 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.
PerformanceProfile.ConvertFrom (cognitive 68) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:185— PerformanceProfile.ConvertFrom has cognitive complexity 68 (threshold 15). Drivers by points: if/else 32 (56 pts), loops 5 (12 pts) (nesting depth added 31). 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.
kubeletconfig.setKubeletConfigForCPUAndMemoryManagers (cognitive 64) pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig/kubeletconfig.go:122— kubeletconfig.setKubeletConfigForCPUAndMemoryManagers has cognitive complexity 64 (threshold 15). Drivers by points: if/else 25 (61 pts), boolean chains 3 (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Controller.syncProfile (cognitive 54) pkg/operator/controller.go:591— Controller.syncProfile has cognitive complexity 54 (threshold 15). Drivers by points: if/else 26 (49 pts), boolean chains 4, match/switch 1 (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.
render.render (cognitive 51) pkg/performanceprofile/cmd/render/render.go:82— render.render has cognitive complexity 51 (threshold 15). Drivers by points: if/else 19 (39 pts), loops 5 (7 pts), match/switch 2 (5 pts) (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.
tuned.expandTuneDBuiltin (cognitive 51) pkg/tuned/tuned_parser.go:418— tuned.expandTuneDBuiltin has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (31 pts), boolean chains 8, jumps 5, loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 24). Of this number, 49 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.
Controller.changeSyncerTuneD (cognitive 47) pkg/tuned/controller.go:975— Controller.changeSyncerTuneD has cognitive complexity 47 (threshold 15). Drivers by points: if/else 21 (42 pts), boolean chains 5 (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.
Controller.computeStatus (cognitive 43) pkg/operator/status.go:225— Controller.computeStatus has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (37 pts), boolean chains 2, loops 1 (2 pts), match/switch 2 (nesting depth added 21). 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.
PerformanceProfile.ConvertTo (cognitive 38) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:13— PerformanceProfile.ConvertTo has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (29 pts), loops 4 (9 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. This shape REPEATS in the file: one other method here (PerformanceProfile.ConvertFrom) 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.
PerformanceProfile.ConvertFrom (cognitive 38) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:119— PerformanceProfile.ConvertFrom has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (29 pts), loops 4 (9 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. This shape REPEATS in the file: one other method here (PerformanceProfile.ConvertTo) 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.
metrics.RunServer (cognitive 37) REDACTED:177— metrics.RunServer has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (30 pts), boolean chains 4, match/switch 1 (2 pts), loops 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.
cmd.makeClusterData (cognitive 37) pkg/performanceprofile/profilecreator/cmd/root.go:258— cmd.makeClusterData has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 4 (9 pts) (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.
ProfileCalculator.calculateProfile (cognitive 36) pkg/operator/profilecalculator.go:190— ProfileCalculator.calculateProfile has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 3, loops 2 (nesting depth added 15). Of this number, 19 points are the body's own statements and 17 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.
Controller.syncHostedClusterTuneds (cognitive 35) pkg/operator/hypershift.go:44— Controller.syncHostedClusterTuneds has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 2, boolean chains 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
handler.Apply (cognitive 35) pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:75— handler.Apply has cognitive complexity 35 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 1 (nesting depth added 8). 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.
profilecreator.updateExtendedCPUInfo (cognitive 34) pkg/performanceprofile/profilecreator/profilecreator.go:576— profilecreator.updateExtendedCPUInfo has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 5 (8 pts), boolean chains 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.
render.render (cognitive 34) pkg/tuned/cmd/render/render.go:108— render.render has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23 (30 pts), loops 4 (nesting depth added 7). 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.
PerformanceProfileReconciler.Reconcile (cognitive 32) pkg/performanceprofile/controller/performanceprofile_controller.go:520— PerformanceProfileReconciler.Reconcile has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (32 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.
main.operatorRun (cognitive 30) cmd/cluster-node-tuning-operator/main.go:119— main.operatorRun has cognitive complexity 30 (threshold 15). Drivers by points: if/else 20 (30 pts) (nesting depth added 10). Of this number, 28 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.
ProfileCalculator.calculateProfileHyperShift (cognitive 29) pkg/operator/profilecalculator.go:342— ProfileCalculator.calculateProfileHyperShift has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 2, loops 2 (nesting depth added 10). Of this number, 20 points are the body's own statements and 9 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.
PerformanceProfile.validateCPUs (cognitive 27) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:174— PerformanceProfile.validateCPUs has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (26 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.
handler.Apply (cognitive 27) pkg/performanceprofile/controller/performanceprofile/components/handler/handler.go:35— handler.Apply has cognitive complexity 27 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 1, loops 1 (nesting depth added 5). 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.
operator.tunedProfilesGet (cognitive 26) pkg/operator/profilecalculator.go:741— operator.tunedProfilesGet has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 4 (8 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.
profilecreator.GetMCPSelector (cognitive 25) pkg/performanceprofile/profilecreator/mcp.go:15— profilecreator.GetMCPSelector has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 4 (7 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.
profilecreator.getOfflinedCPUs (cognitive 25) pkg/performanceprofile/profilecreator/profilecreator.go:267— profilecreator.getOfflinedCPUs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 12). Of this number, 24 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.
tuned.TunedRun (cognitive 25) pkg/tuned/run.go:120— tuned.TunedRun has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3, loops 1 (nesting depth added 10). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 129). 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.
Controller.syncMachineConfigHyperShift (cognitive 24) pkg/operator/controller.go:932— Controller.syncMachineConfigHyperShift has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2, loops 2 (nesting depth added 7). Of this number, 23 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.
PerformanceProfile.validateHugePages (cognitive 21) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:367— PerformanceProfile.validateHugePages has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 7, loops 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.
tuned.execCmd (cognitive 21) pkg/tuned/tuned_parser.go:220— tuned.execCmd has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 3, loops 1 (nesting depth added 8). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 251, 273). The decisions are inside those literals, 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 literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
main.dedupExpectedContent (cognitive 20) cmd/gather-sysinfo/gather-sysinfo.go:175— main.dedupExpectedContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 5 (7 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.
Controller.run (cognitive 20) pkg/operator/controller.go:1399— Controller.run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (20 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.
status.GetTunedProfilesMessage (cognitive 20) pkg/performanceprofile/controller/performanceprofile/status/status.go:208— status.GetTunedProfilesMessage has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 3, 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.
profilecreator.getOvsDpdkCPUs (cognitive 20) pkg/performanceprofile/profilecreator/profilecreator.go:200— profilecreator.getOvsDpdkCPUs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 5). Of this number, 14 points are the body's own statements and 6 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.
PerformanceProfile.validateWorkloadHints (cognitive 19) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:643— PerformanceProfile.validateWorkloadHints has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6 (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.
ProfileCalculator.getPoolsForNode (cognitive 19) pkg/operator/mc.go:149— ProfileCalculator.getPoolsForNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 2, match/switch 1 (2 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.
metrics.buildServer (cognitive 18) REDACTED:68— metrics.buildServer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 100). 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.
Controller.syncMachineConfig (cognitive 18) pkg/operator/controller.go:776— Controller.syncMachineConfig has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (18 pts) (nesting depth added 5). Of this number, 17 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.
profilecreator.getPoolsForNode (cognitive 18) pkg/performanceprofile/profilecreator/mcp.go:118— profilecreator.getPoolsForNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2, match/switch 1 (2 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.
profilecreator.ensureSameTopology (cognitive 18) pkg/performanceprofile/profilecreator/profilecreator.go:516— profilecreator.ensureSameTopology has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), 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.
Controller.removeResources (cognitive 17) pkg/operator/controller.go:1347— Controller.removeResources has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1, 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.
Controller.getObjFromTunedConfigMap (cognitive 17) pkg/operator/hypershift.go:120— Controller.getObjFromTunedConfigMap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), 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.
cpuAccumulator.AddCoresWithFilter (cognitive 17) pkg/performanceprofile/profilecreator/profilecreator.go:385— cpuAccumulator.AddCoresWithFilter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (3 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.
tuned.retryLoop (cognitive 17) pkg/tuned/controller.go:1623— tuned.retryLoop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 7). Of this number, 12 points are the body's own statements and 5 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.
Controller.changeWatcher (cognitive 17) pkg/tuned/controller.go:1529— Controller.changeWatcher has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, match/switch 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.
util.SplitKernelArgumentsWithout (cognitive 17) pkg/util/kernel.go:55— util.SplitKernelArgumentsWithout has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), 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.
PerformanceProfile.validateNet (cognitive 16) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:610— PerformanceProfile.validateNet has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, 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.
Controller.informerEventHandler (cognitive 16) pkg/operator/controller.go:1203— Controller.informerEventHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 1234, 1205, 1219). The decisions are inside those literals, 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 literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
profilecreator.GetNodesForPool (cognitive 16) pkg/performanceprofile/profilecreator/mcp.go:67— profilecreator.GetNodesForPool has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 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.
cmd.makeClusterInfoFromClusterData (cognitive 16) pkg/performanceprofile/profilecreator/cmd/info.go:93— cmd.makeClusterInfoFromClusterData has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (6 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.
cmd.listNodesForPool (cognitive 16) pkg/performanceprofile/profilecreator/cmd/root.go:545— cmd.listNodesForPool has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (3 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.
TooManyMethods: Controller pkg/operator/controller.go:66— TooManyMethods — 38 methods, declared across 4 files: operator/controller.go (25), operator/hypershift.go (6), operator/status.go (6), operator/validator.go (1). The bar is 30 methods; this is 8 over it, 1.27× 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.
D4 · Code Duplication· Near-duplicate member family (4 members, 51 shared lines) · ×1
Near-duplicate member family (4 members, 51 shared lines) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:13— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:13-116 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:119-221 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:13-182 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:185-344 — These 4 members are variants of one another: a block of 51 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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 (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) pkg/operator/controller.go:1203— pkg/operator/controller.go:1203-1258 | pkg/tuned/controller.go:1465-1523 — These two members are one piece of code written twice and then edited apart: 56 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 (236 corresponding lines) · ×1
Edited copy of a member (236 corresponding lines) pkg/apis/performanceprofile/v1/performanceprofile_types.go:27— pkg/apis/performanceprofile/v1/performanceprofile_types.go:27-262 | pkg/apis/performanceprofile/v2/performanceprofile_types.go:27-294 — These two members are one piece of code written twice and then edited apart: 236 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 (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) pkg/operator/mc.go:149— pkg/operator/mc.go:149-215 | pkg/performanceprofile/profilecreator/mcp.go:118-182 — These two members are one piece of code written twice and then edited apart: 65 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) pkg/operator/controller.go:1261— pkg/operator/controller.go:1261-1289 | pkg/operator/controller.go:1292-1321 — 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 copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:271— pkg/apis/performanceprofile/v2/performanceprofile_validation.go:271-313 | pkg/apis/performanceprofile/v2/performanceprofile_validation.go:319-361 — 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) pkg/operator/controller.go:180— pkg/operator/controller.go:180-213 | pkg/tuned/controller.go:302-335 — 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 copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) pkg/operator/controller.go:1053— pkg/operator/controller.go:1053-1088 | pkg/operator/controller.go:1091-1128 — 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) pkg/performanceprofile/profilecreator/ghwhandler.go:94— pkg/performanceprofile/profilecreator/ghwhandler.go:94-117 | pkg/performanceprofile/profilecreator/ghwhandler.go:129-143 — 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 copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) REDACTED:66— REDACTED:66-89 | REDACTED:227-250 | REDACTED:317-342 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) pkg/performanceprofile/profilecreator/mustgather.go:86— pkg/performanceprofile/profilecreator/mustgather.go:86-105 | pkg/performanceprofile/profilecreator/mustgather.go:166-188 | pkg/performanceprofile/profilecreator/profilecreator.go:654-670 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) pkg/performanceprofile/cmd/render/cmd.go:41— pkg/performanceprofile/cmd/render/cmd.go:41-62 | pkg/tuned/cmd/operand/cmd.go:37-57 | pkg/tuned/cmd/render/cmd.go:36-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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 (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) REDACTED:103— REDACTED:103-119 | REDACTED:182-198 | REDACTED:252-272 | REDACTED:344-360 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 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 (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:559— pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:559-580 | pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:637-656 — 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 (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) pkg/performanceprofile/controller/performanceprofile/hypershift/hypershift.go:232— pkg/performanceprofile/controller/performanceprofile/hypershift/hypershift.go:232-240 | pkg/performanceprofile/controller/performanceprofile/hypershift/hypershift.go:242-250 — 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 copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) pkg/operator/profilecalculator.go:789— pkg/operator/profilecalculator.go:789-805 | pkg/tuned/controller.go:586-599 — 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) · ×1
Edited copy of a member (11 corresponding lines) pkg/performanceprofile/cmd/render/render.go:68— pkg/performanceprofile/cmd/render/render.go:68-78 | pkg/tuned/cmd/render/render.go:51-61 — 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) pkg/operator/mc.go:248— pkg/operator/mc.go:248-257 | pkg/performanceprofile/profilecreator/mcp.go:103-112 — 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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) pkg/util/strings_map.go:16— pkg/util/strings_map.go:16-28 | pkg/util/strings_slice.go:35-47 — 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 (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) pkg/operator/controller.go:767— pkg/operator/controller.go:767-774 | pkg/operator/profilecalculator.go:589-596 — 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) cmd/gather-sysinfo/gather-sysinfo.go:131— cmd/gather-sysinfo/gather-sysinfo.go:131-137 | pkg/performanceprofile/profilecreator/cmd/root.go:250-256 — 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.
Duplicated block (160–167 lines × 2) pkg/apis/performanceprofile/v1/performanceprofile_types.go:103— pkg/apis/performanceprofile/v1/performanceprofile_types.go:103-262 | pkg/apis/performanceprofile/v2/performanceprofile_types.go:128-294 — `pkg/apis/performanceprofile/v1/performanceprofile_types.go` and `pkg/apis/performanceprofile/v2/performanceprofile_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 267 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/apis/performanceprofile/v1/performanceprofile_types.go:103` 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 (61–65 lines × 2) pkg/apis/performanceprofile/v1/performanceprofile_types.go:30— pkg/apis/performanceprofile/v1/performanceprofile_types.go:30-94 | pkg/apis/performanceprofile/v2/performanceprofile_types.go:59-119 — `pkg/apis/performanceprofile/v1/performanceprofile_types.go` and `pkg/apis/performanceprofile/v2/performanceprofile_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 267 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/apis/performanceprofile/v1/performanceprofile_types.go:30` 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 (42 lines × 2) pkg/operator/profilecalculator.go:278— pkg/operator/profilecalculator.go:278-319 | pkg/operator/profilecalculator.go:421-462 — 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/operator/profilecalculator.go:278` 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 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 (29 lines × 4) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:51— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:51-79 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:156-184 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:70-98 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:230-258 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:51` 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) pkg/operator/mc.go:164— pkg/operator/mc.go:164-189 | pkg/performanceprofile/profilecreator/mcp.go:134-159 — 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 `pkg/operator/mc.go:164` 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 (25 lines × 2) pkg/clusteroperator/status.go:41— pkg/clusteroperator/status.go:41-65 | pkg/tuned/status.go:42-66 — 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 (21 lines × 2) pkg/clusteroperator/status.go:16— pkg/clusteroperator/status.go:16-36 | pkg/tuned/status.go:17-37 — 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 `pkg/clusteroperator/status.go:16` 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–20 lines × 2) pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:138— pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:138-157 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:298-316 — 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/apis/performanceprofile/v2/performanceprofile_conversion.go:138` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:316` calls `To` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:157` 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 (16 lines × 4) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:101— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:101-116 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:206-221 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:167-182 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:329-344 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:101` 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 (15 lines × 3) pkg/performanceprofile/cmd/render/cmd.go:48— pkg/performanceprofile/cmd/render/cmd.go:48-62 | pkg/tuned/cmd/operand/cmd.go:43-57 | pkg/tuned/cmd/render/cmd.go:42-56 — 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 `pkg/performanceprofile/cmd/render/cmd.go:48` 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 (15 lines × 2) pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:76— pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:76-90 | pkg/performanceprofile/controller/performanceprofile/hypershift/status/writer.go:32-46 — 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–12 lines × 2) pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:842— pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:842-853 | pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:859-868 — 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/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go:842` 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 (11–12 lines × 2) pkg/performanceprofile/profilecreator/mustgather.go:94— pkg/performanceprofile/profilecreator/mustgather.go:94-105 | pkg/performanceprofile/profilecreator/mustgather.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/performanceprofile/profilecreator/mustgather.go:94` 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (11 lines × 3) REDACTED:68— REDACTED:68-78 | REDACTED:146-156 | REDACTED:319-329 — 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.
Duplicated block (17 lines × 2) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:36— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:36-52 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:55-71 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.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 (6–7 lines × 2) pkg/performanceprofile/profilecreator/ghwhandler.go:105— pkg/performanceprofile/profilecreator/ghwhandler.go:105-111 | pkg/performanceprofile/profilecreator/ghwhandler.go:134-139 — 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/performanceprofile/profilecreator/ghwhandler.go:105` 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 × 4) pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:87— pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:87-92 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:192-197 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:111-116 | pkg/apis/performanceprofile/v2/performanceprofile_conversion.go:271-276 — `pkg/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go` and `pkg/apis/performanceprofile/v2/performanceprofile_conversion.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 9 separate duplicated blocks between them, totalling at least 146 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/apis/performanceprofile/v1alpha1/performanceprofile_conversion.go:87` 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 × 3) pkg/performanceprofile/cmd/render/cmd.go:103— pkg/performanceprofile/cmd/render/cmd.go:103-107 | pkg/tuned/cmd/operand/cmd.go:64-68 | pkg/tuned/cmd/render/cmd.go:86-90 — 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 (35 lines × 3) pkg/apis/performanceprofile/v1/performanceprofile_types.go:228— pkg/apis/performanceprofile/v1/performanceprofile_types.go:228-262 | pkg/apis/performanceprofile/v1alpha1/performanceprofile_types.go:127-161 | pkg/apis/performanceprofile/v2/performanceprofile_types.go:260-294 — `pkg/apis/performanceprofile/v1/performanceprofile_types.go` and `pkg/apis/performanceprofile/v1alpha1/performanceprofile_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 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 (14 lines × 2) pkg/apis/performanceprofile/v2/performanceprofile_validation.go:286— pkg/apis/performanceprofile/v2/performanceprofile_validation.go:286-299 | pkg/apis/performanceprofile/v2/performanceprofile_validation.go:334-347 — 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/apis/performanceprofile/v2/performanceprofile_validation.go:286` 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 (13 lines × 3) REDACTED:107— REDACTED:107-119 | REDACTED:186-198 | REDACTED:348-360 — 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 `REDACTED:107` 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 × 2) pkg/operator/controller.go:1206— pkg/operator/controller.go:1206-1215 | pkg/operator/controller.go:1220-1230 — 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 (6 lines × 3) pkg/operator/controller.go:1211— pkg/operator/controller.go:1211-1216 | pkg/operator/controller.go:1225-1231 | pkg/operator/controller.go:1249-1254 — 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.
Low cohesion: PerformanceProfileReconciler (LCOM4 4) pkg/performanceprofile/controller/performanceprofile_controller.go:71— PerformanceProfileReconciler's methods fall into 4 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 4 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.
Coverage not measured — Go suite — Coverage NOT MEASURED: the Go half could not be measured — the Go suite ran but its cover profiles carried none of the module's own source. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Collection crosses a callback boundary unsynchronised pkg/tuned/tuned_parser.go:267— `execCmd` hands values from a goroutine to the body waiting on it through `out`, a variable — the goroutine writes it with `out += …` on line 267, and the body touches it at line 301. Those two spans provably run concurrently: this body waits on `chReader`, which nothing but the goroutine raises, so the goroutine cannot be the flow that is waiting for it. The touch comes after the goroutine is started and BEFORE the body waits on `chReader`, so the Go memory model orders nothing between it and the goroutine's write. A goroutine's closure captures `out` by reference, so every goroutine and the body use ONE variable, and a plain variable has no synchronisation of its own: by the Go memory model a write concurrent with any other access to it is a data race (the race detector reports it), a racing `++` loses updates, and a racing read sees a stale or torn value. `chReader` is a channel, which orders the handoff's signal and takes no exclusion over the variable's own state. Hand the values over the channel itself instead of beside it, or guard every access to `out` on both sides with one `sync.Mutex`.
Duplicated predicate pkg/clusteroperator/status.go:19— `condition.Status == c.Status && condition.Reason == c.Reason && condition.Message == c.Message` appears character-identically in 2 files — pkg/clusteroperator/status.go, pkg/tuned/status.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/clusteroperator/status.go:50— `conditionA.Type == conditionB.Type && conditionA.Status == conditionB.Status && conditionA.Reason == conditionB.Reason && conditionA.Message…` appears character-identically in 2 files — pkg/clusteroperator/status.go, pkg/tuned/status.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/performanceprofile/controller/performanceprofile/hypershift/components/handler.go:316— `err != nil && !k8serrors.IsNotFound(err)` appears character-identically in 2 files — pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.go, pkg/performanceprofile/controller/performanceprofile/hypershift/status/status.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/performanceprofile/controller/performanceprofile/components/handler/handler.go:88— `mcMutated != nil || kcMutated != nil || performanceTunedNeedsUpdate || runtimeClassMutated != nil` appears character-identically in 2 files — pkg/performanceprofile/controller/performanceprofile/components/handler/handler.go, pkg/performanceprofile/controller/performanceprofile/hypershift/components/handler.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/performanceprofile/controller/performanceprofile/components/kubeletconfig/kubeletconfig.go:160— `profile.Spec.CPU != nil && profile.Spec.CPU.Reserved != nil` appears character-identically in 2 files — pkg/performanceprofile/controller/performanceprofile/components/kubeletconfig/kubeletconfig.go, pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.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/operator/mc.go:164— `selector.Empty() || !selector.Matches(labels.Set(node.Labels))` appears character-identically in 2 files — pkg/operator/mc.go, pkg/performanceprofile/profilecreator/mcp.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.
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 manifests/50-operator-ibm-cloud-managed.yaml:3— 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:3— 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 7 significant file(s) lose their only recent owner: pkg/tuned/controller.go, pkg/operator/controller.go, pkg/operator/status.go, REDACTED, pkg/apis/tuned/v1/tuned_types.go, pkg/sync/bootcmdline.go, pkg/operator/validator.go. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 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 (9 single-owned of 51 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; 51 of the 100 production source files in this repository met that bar). They are anonymized user #2 (2 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/performanceprofile/controller/performanceprofile/components/kubeletconfig/kubeletconfig.go, pkg/apis/performanceprofile/v2/performanceprofile_conversion.go.
No ADRs found cmd/performance-profile-creator/main.go:17— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `cmd/performance-profile-creator/main.go` makes this repository a deployable product (line 17).
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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling· Dependabot does not watch gitsubmodule · ×1
Dependabot does not watch gitsubmodule REDACTED:17— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, 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.
Silent fallback default on error pkg/performanceprofile/controller/performanceprofile/components/utils.go:57— `CPUListToMaskList` turns a non-nil `err` into `return "", nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
Outdated: gopkg.in/ini.v1 — `gopkg.in/ini.v1` is required at v1.67.3 in REDACTED, but v1.68.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get gopkg.in/ini.v1@v1.68.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: sigs.k8s.io/controller-runtime — `sigs.k8s.io/controller-runtime` is required at v0.25.2 in REDACTED, but v0.25.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get sigs.k8s.io/controller-runtime@v0.25.3 && go mod tidy` and commit the updated REDACTED and go.sum.
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. semgrep could not parse 3 file(s) — `pkg/generated/listers/tuned/v1/profile.go`, `pkg/generated/listers/tuned/v1/tuned.go`, `pkg/tuned/cmd/render/render.go` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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 01a1e661-3af1-70b4-afdc-c896a5c2ed05 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 11 · Warnings: 244 · Recommendations: 24 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 22:01 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.