Public report of pulumi/pulumi-kubernetes, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 01:01 UTC · Survey ID cd_d8ff15eeeec44708b8b4c3c86e044e50
pulumi/pulumi-kubernetes
Measured 17 November 2026, 00:59 UTC, at code version 596bd58
Code coverage is not measured: Suite not runnable in-image.
Test reliability is not measured: No test run produced results.
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 medium codebase: 23,762 lines of product code in 16 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Security and Compliance, 33.2
Findings by how serious they are
40 critical501 serious117 minor
7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 00:59 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 ▸
44of 44 dimensions measured by tools.
624of 658 findings point to an exact file and line, so you can open each one in the code. The other 34 concern the repository as a whole, such as missing documentation.
44dimensions across 6 lenses, read from 23,762 lines of product code in 16 projects.
pulumi/pulumi-kubernetes falls short of our standard for production because it has unsafe settings in infrastructure or container files and pipeline steps that install packages without pinning their versions. It scores 51.1 out of 100 and is rated Adequate, and all 40 of its critical findings are security problems.
Security and Compliance, at 33.2, is the weakest lens and counts most in the score. The best first step is fixing the runtime or framework that no longer gets security updates, worth about 2.6 points. Fixing the five secrets exposed to more of the pipeline than needed would lift Security and Compliance itself, worth about 1.3 points. Raising Security and Compliance to 70 would lift the score to about 65.9.
Eleven settings leave the servers or containers unsafe. Eight pipeline steps install packages that can change without warning, and seven secrets can leak from the build pipeline. Correcting the unsafe settings, pinning what the pipeline installs and limiting each secret to its own step would close these risks. Pinning each tool to an exact version would fix the four pipeline tools referenced by a changeable name, and updating the vulnerable packages would deal with the three packages with a known security hole.
The product code is 23,762 lines, about €67,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 33.2 to 70, the lowest score rated Strong, the score would rise from 51.1 to about 65.9.
Code composition: what the lines of code are
Product code 35%Tests 65%
Rebuild cost: about €67,000 · Estimate
Cost to rebuild
€22,000 to €110,000, for 371 to 1,177 hours of work, about 0.5 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.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 23,762 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
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Pulumi.Kubernetes.csproj.
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 €67,000 to build again, about 0.5 person-years of work. Its weakest lens is Security and Compliance, at 33.2 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life. Of all the actions in this report, it raises the score most for the work it takes: about 2.6 points for low effort, because it clears the 1 Platform End-of-Life findings. 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.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 12% on every change. The history of the code shows how much it changes: about 5,540 lines over the last 90 days, which is about 22,468 lines a year. At that pace, the extra work comes to an estimated 3 to 17.7 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.
852 modules, with 1472 dependencies between them. One loop runs through 5 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 812 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.
com.pulumi.kubernetes.admissionregistration.v1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.admissionregistration.v1, while a change to com.pulumi.kubernetes.admissionregistration.v1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.admissionregistration.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.admissionregistration.v1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.admissionregistration.v1, while a change to com.pulumi.kubernetes.admissionregistration.v1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.admissionregistration.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.admissionregistration.v1alpha1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.admissionregistration.v1alpha1, while a change to com.pulumi.kubernetes.admissionregistration.v1alpha1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.admissionregistration.v1alpha1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.admissionregistration.v1alpha1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.admissionregistration.v1alpha1, while a change to com.pulumi.kubernetes.admissionregistration.v1alpha1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.admissionregistration.v1alpha1 uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in com.pulumi.kubernetes.core.v1.inputs uses a type in com.pulumi.kubernetes.meta.v1.inputs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.pulumi.kubernetes.core.v1.inputs uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.core.v1.inputs, while a change to com.pulumi.kubernetes.core.v1.inputs can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.core.v1.inputs uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in com.pulumi.kubernetes.core.v1.outputs uses a type in com.pulumi.kubernetes.meta.v1.outputs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.pulumi.kubernetes.core.v1.outputs uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.core.v1.outputs, while a change to com.pulumi.kubernetes.core.v1.outputs can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.core.v1.outputs uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients.
Position
Below the diagonal: github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition uses a module listed above it, which is the healthy direction.
9→40 github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/awaitpart of a loop✕
Connections
1 pair of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/provider/resource uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/provider/resource uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/provider/resource, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/provider/resource can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients.
Position
Below the diagonal: github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/provider/resource uses a module listed above it, which is the healthy direction.
sdk.nodejs.apps.v1.deploymentList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.apps.v1.deploymentList, while a change to sdk.nodejs.apps.v1.deploymentList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.apps.v1.deploymentList uses a module listed above it, which is the healthy direction.
sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList, while a change to sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList uses a module listed above it, which is the healthy direction.
sdk.nodejs.flowcontrol.v1.flowSchema uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.flowcontrol.v1.flowSchema, while a change to sdk.nodejs.flowcontrol.v1.flowSchema can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.flowcontrol.v1.flowSchema uses a module listed above it, which is the healthy direction.
sdk.nodejs.flowcontrol.v1.flowSchemaList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.flowcontrol.v1.flowSchemaList, while a change to sdk.nodejs.flowcontrol.v1.flowSchemaList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.flowcontrol.v1.flowSchemaList uses a module listed above it, which is the healthy direction.
sdk.nodejs.flowcontrol.v1.flowSchemaPatch uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.flowcontrol.v1.flowSchemaPatch, while a change to sdk.nodejs.flowcontrol.v1.flowSchemaPatch can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.flowcontrol.v1.flowSchemaPatch uses a module listed above it, which is the healthy direction.
sdk.nodejs.flowcontrol.v1.priorityLevelConfiguration uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.flowcontrol.v1.priorityLevelConfiguration, while a change to sdk.nodejs.flowcontrol.v1.priorityLevelConfiguration can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.flowcontrol.v1.priorityLevelConfiguration uses a module listed above it, which is the healthy direction.
sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList, while a change to sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList uses a module listed above it, which is the healthy direction.
sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationPatch uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationPatch, while a change to sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationPatch can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationPatch uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.deviceClassList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.deviceClassList, while a change to sdk.nodejs.resource.v1.deviceClassList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.deviceClassList uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceClaim uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceClaim, while a change to sdk.nodejs.resource.v1.resourceClaim can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceClaim uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceClaimList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceClaimList, while a change to sdk.nodejs.resource.v1.resourceClaimList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceClaimList uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceClaimPatch uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceClaimPatch, while a change to sdk.nodejs.resource.v1.resourceClaimPatch can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceClaimPatch uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceClaimTemplate uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceClaimTemplate, while a change to sdk.nodejs.resource.v1.resourceClaimTemplate can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceClaimTemplate uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceClaimTemplateList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceClaimTemplateList, while a change to sdk.nodejs.resource.v1.resourceClaimTemplateList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceClaimTemplateList uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceClaimTemplatePatch uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceClaimTemplatePatch, while a change to sdk.nodejs.resource.v1.resourceClaimTemplatePatch can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceClaimTemplatePatch uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceSlice uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceSlice, while a change to sdk.nodejs.resource.v1.resourceSlice can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceSlice uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceSliceList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceSliceList, while a change to sdk.nodejs.resource.v1.resourceSliceList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceSliceList uses a module listed above it, which is the healthy direction.
sdk.nodejs.resource.v1.resourceSlicePatch uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.resource.v1.resourceSlicePatch, while a change to sdk.nodejs.resource.v1.resourceSlicePatch can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.resource.v1.resourceSlicePatch uses a module listed above it, which is the healthy direction.
sdk.nodejs.scheduling.v1alpha1.workloadList uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.scheduling.v1alpha1.workloadList, while a change to sdk.nodejs.scheduling.v1alpha1.workloadList can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.scheduling.v1alpha1.workloadList uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.batch.v1.inputs uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.batch.v1.inputs, while a change to com.pulumi.kubernetes.batch.v1.inputs can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.batch.v1.inputs uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.batch.v1.inputs uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.batch.v1.inputs, while a change to com.pulumi.kubernetes.batch.v1.inputs can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.batch.v1.inputs uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.batch.v1.outputs uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.batch.v1.outputs, while a change to com.pulumi.kubernetes.batch.v1.outputs can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.batch.v1.outputs uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.batch.v1.outputs uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.batch.v1.outputs, while a change to com.pulumi.kubernetes.batch.v1.outputs can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.batch.v1.outputs uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.events.v1, while a change to com.pulumi.kubernetes.events.v1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.events.v1, while a change to com.pulumi.kubernetes.events.v1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1 uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.events.v1, while a change to com.pulumi.kubernetes.events.v1 can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1 uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.events.v1, while a change to com.pulumi.kubernetes.events.v1 can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1beta1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.events.v1beta1, while a change to com.pulumi.kubernetes.events.v1beta1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1beta1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.events.v1beta1, while a change to com.pulumi.kubernetes.events.v1beta1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1beta1 uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.events.v1beta1, while a change to com.pulumi.kubernetes.events.v1beta1 can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.events.v1beta1 uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.events.v1beta1, while a change to com.pulumi.kubernetes.events.v1beta1 can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.events.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.resource.v1alpha1, while a change to com.pulumi.kubernetes.resource.v1alpha1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.resource.v1alpha1, while a change to com.pulumi.kubernetes.resource.v1alpha1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha1 uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.resource.v1alpha1, while a change to com.pulumi.kubernetes.resource.v1alpha1 can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha1 uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.resource.v1alpha1, while a change to com.pulumi.kubernetes.resource.v1alpha1 can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha2 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.resource.v1alpha2, while a change to com.pulumi.kubernetes.resource.v1alpha2 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha2 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha2 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.resource.v1alpha2, while a change to com.pulumi.kubernetes.resource.v1alpha2 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha2 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha2 uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.resource.v1alpha2, while a change to com.pulumi.kubernetes.resource.v1alpha2 can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha2 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.resource.v1alpha2 uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.resource.v1alpha2, while a change to com.pulumi.kubernetes.resource.v1alpha2 can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.resource.v1alpha2 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.storage.v1, while a change to com.pulumi.kubernetes.storage.v1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.storage.v1, while a change to com.pulumi.kubernetes.storage.v1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1 uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.storage.v1, while a change to com.pulumi.kubernetes.storage.v1 can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1 uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.storage.v1, while a change to com.pulumi.kubernetes.storage.v1 can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1beta1 uses com.pulumi.kubernetes.meta.v1.inputs, so a change to com.pulumi.kubernetes.meta.v1.inputs can break com.pulumi.kubernetes.storage.v1beta1, while a change to com.pulumi.kubernetes.storage.v1beta1 can't break com.pulumi.kubernetes.meta.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1beta1 uses com.pulumi.kubernetes.meta.v1.outputs, so a change to com.pulumi.kubernetes.meta.v1.outputs can break com.pulumi.kubernetes.storage.v1beta1, while a change to com.pulumi.kubernetes.storage.v1beta1 can't break com.pulumi.kubernetes.meta.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1beta1 uses com.pulumi.kubernetes.core.v1.inputs, so a change to com.pulumi.kubernetes.core.v1.inputs can break com.pulumi.kubernetes.storage.v1beta1, while a change to com.pulumi.kubernetes.storage.v1beta1 can't break com.pulumi.kubernetes.core.v1.inputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1beta1 uses a module listed above it, which is the healthy direction.
com.pulumi.kubernetes.storage.v1beta1 uses com.pulumi.kubernetes.core.v1.outputs, so a change to com.pulumi.kubernetes.core.v1.outputs can break com.pulumi.kubernetes.storage.v1beta1, while a change to com.pulumi.kubernetes.storage.v1beta1 can't break com.pulumi.kubernetes.core.v1.outputs.
Position
Below the diagonal: com.pulumi.kubernetes.storage.v1beta1 uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition.
Position
Below the diagonal: github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging uses a module listed above it, which is the healthy direction.
38→40 github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/awaitpart of a loop✕
Connections
1 pair of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
189 pairs of types, where a type in sdk.nodejs.yaml.yaml uses a type in sdk.nodejs.types.output. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
sdk.nodejs.yaml.yaml uses sdk.nodejs.types.output, so a change to sdk.nodejs.types.output can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.types.output.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.apps.v1.deploymentList, so a change to sdk.nodejs.apps.v1.deploymentList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.apps.v1.deploymentList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList, so a change to sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.autoscaling.v1.horizontalPodAutoscalerList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.flowcontrol.v1.flowSchemaList, so a change to sdk.nodejs.flowcontrol.v1.flowSchemaList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.flowcontrol.v1.flowSchemaList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList, so a change to sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.flowcontrol.v1.priorityLevelConfigurationList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.resource.v1.deviceClassList, so a change to sdk.nodejs.resource.v1.deviceClassList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.resource.v1.deviceClassList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.resource.v1.resourceClaimList, so a change to sdk.nodejs.resource.v1.resourceClaimList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.resource.v1.resourceClaimList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.resource.v1.resourceClaimTemplateList, so a change to sdk.nodejs.resource.v1.resourceClaimTemplateList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.resource.v1.resourceClaimTemplateList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.resource.v1.resourceSliceList, so a change to sdk.nodejs.resource.v1.resourceSliceList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.resource.v1.resourceSliceList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
sdk.nodejs.yaml.yaml uses sdk.nodejs.scheduling.v1alpha1.workloadList, so a change to sdk.nodejs.scheduling.v1alpha1.workloadList can break sdk.nodejs.yaml.yaml, while a change to sdk.nodejs.yaml.yaml can't break sdk.nodejs.scheduling.v1alpha1.workloadList.
Position
Below the diagonal: sdk.nodejs.yaml.yaml uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/clients.
Position
Below the diagonal: github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await/condition.
Position
Below the diagonal: github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses a type in github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging.
github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging, so a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging can break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await, while a change to github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await can't break github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/logging.
Position
Below the diagonal: github.com/pulumi/pulumi-kubernetes/provider/v4/pkg/await uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 68.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
298
High / Critical
A05:2025 — Injection
48
High / Critical
A03:2025 — Software Supply Chain Failures
26
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Top priorities: Resolve the 222 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (40), REDACTED (40), REDACTED (22); Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Pulumi.Kubernetes.csproj; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Pulumi.Kubernetes.csproj.
Per-file score 0–10 — a quality signature. Of 90 files carrying findings, judged against the Production bar: 16% slop · 56% mixed · 28% near-clean.
File
Score
Band
Worst signal
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
1.6
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
3.0
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.3
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.9
Mixed
Static Analysis (SAST): Medium: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 40
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 — 501
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 — 117
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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 44 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 — 44 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, 624 of 658 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.
D8 Code Coverage — 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. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`go test -short -v -coverprofile="coverage.txt" -coverpkg`), uploaded by `codecov/codecov-action` and a Codecov configuration (codecov.yml) shows that coverage is collected and tracked in your own CI. The suite could not be built/run in-image, so the number could not be read here — it is excluded from the score rather than treated as unmeasured-by-the-team. To have it measured, make the suite runnable without services we do not provision (a database, a broker). For context only, test code is ≈ 100% of production LoC (43,506 test / 23,762 production) — a rough proxy, NOT a coverage measurement. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
D11 Test Reliability — 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — 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. The 4 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .go (23,526 lines, 99% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 36 task marker(s) (TODO/FIXME/HACK/XXX) across 23 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
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.
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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D24 Comment Value — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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: 75 commits in the last 90 days, yet 57 of 68 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.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: an API surface definition (provider/pkg/clients/fake/swagger.json) — a service to probe even with no user interface. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
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.
SC1 Supply-chain hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X21 Side-effecting pattern 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations: 7 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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
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 Dockerfile (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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 25 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with kubeProvider.Configure (cyclomatic 81). — Refactoring it lifts Cyclomatic Complexity from 5.2 to about 5.7/10.
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.
+ 45 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with gen.PulumiSchema (cognitive 203), kubeProvider.Configure (cognitive 103), kubeProvider.Diff (cognitive 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 2.0 to about 4.1/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.1 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 FileTooLong finding(s) in God Classes — start with REDACTED, overlays.go, helm_release.go. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 MethodTooLong finding(s) in God Classes — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 FunctionTooLong finding(s) in God Classes — start with REDACTED, await.go, deprecated.go. — One of this dimension's main actionable groups (4 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.
58 duplicated block group(s) detected. 8.3 % of the production lines (1,965 of 23,762) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3REDACTED:216
Edited copy of a member (21 corresponding lines) · ×3provider/pkg/await/checker/pod/check.go:60
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), awaiters.go, memcache.go. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with REDACTED, ingress.go, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with helm_release.go (2), REDACTED, ingress.go. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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 discovery.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.
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.
24 outdated, 1 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). 46 of 46 direct requirement(s) were graded against proxy.golang.org (0 not served there, 3 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.
Deprecated module: github.com/golang/protobuf
Outdated: github.com/fluxcd/pkg/ssa · ×24
What to do
Resolve the 1 Deprecated module 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 102 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 1 direct `PackageReference`(s), and 101 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: REDACTED (3×56=168); REDACTED (2×24=48)
Hotspot: REDACTED · ×2REDACTED:129
What to do
Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is provider/pkg/provider/provider_parameterize.go. Counted over 68 of the 99 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
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
4 deducted debt markers + 0 dead symbols across 268577 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .go (99% of production source) was not read, and carries at least 36 uncounted task marker(s) in 23 file(s).
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with Program.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 CommentedOutCode finding(s) in Explicit Debt — start with Program.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 56 declarations measured against a convention their peers follow.
`extensionsv1b1ApiVersion` spells `Api` where 22 names in the project spell it `API`REDACTED:106
`frontendIp` spells `Ip` where 32 names in the project spell it `IP`tests/sdk/nodejs/istio/step1/index.ts:54
What to do
Resolve the 1 `extensionsv1b1ApiVersion` spells `Api` where 22 names in the project… finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `frontendIp` spells `Ip` where 32 names in the project spell it `IP` finding(s) in Naming Consistency — start with index.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency4.7 / 10Weak✓ Tool-verified
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
3 API inconsistencies among 57 exposed members measured against a convention their peers follow.
`condition.NewAll` takes no context.Context; its 4 sibling operations take oneprovider/pkg/await/condition/all.go:15
`logging.WithPrefix` signals absence with a nil `*T` where its 3 sibling single-key reads use a bare `T` (the zero value when absent)provider/pkg/logging/log_writer.go:49
`yaml.ParseYamlObjects` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`)sdk/go/kubernetes/yaml/yaml.go:235
What to do
Resolve the 1 `condition.NewAll` takes no context.Context; its 4 sibling operations… finding(s) in Internal API Consistency — start with all.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 `logging.WithPrefix` signals absence with a nil `*T` where its 3 sibling… finding(s) in Internal API Consistency — start with log_writer.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 `yaml.ParseYamlObjects` returns a map (`map[K]V`) where its 3 siblings… finding(s) in Internal API Consistency — start with yaml.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
Resolve the 12 redundant comment finding(s) in Comment Value — start with index.ts (12). — One of this dimension's main actionable groups (12 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 16 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionsdk/dotnet/Pulumi.Kubernetes.csproj:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Pulumi.Kubernetes.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.3 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
32 % of calls cross a namespace and 7 % go through an interface, but 86 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
48 finding(s): 0 critical, 22 high, 25 medium, 1 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `provider/pkg/provider/helm/v4/testdata/reference/templates/pre-install-hook.yaml`, `provider/pkg/provider/helm/v4/testdata/reference/templates/service.yaml`, `provider/pkg/provider/helm/v4/testdata/reference/templates/serviceaccount.yaml`, `provider/pkg/provider/helm/v4/testdata/reference/templates/versioncheck.yaml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 8 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
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 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 222 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (40), REDACTED (40), REDACTED (22). — One of this dimension's main actionable groups (222 warning-level).
Resolve the 65 Low IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED (12), REDACTED (6). — One of this dimension's main actionable groups (65 recommendation-level).
Resolve the 11 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (11 issue-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 the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d36_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.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 27 platform declaration(s) and 16 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.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Pulumi.Kubernetes.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`__Value` is not registered, but `Config` creates it and keeps it in the static `_alwaysRender`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_value, _set; e.g. `_value` at line 28). — sdk/dotnet/Config/Config.cs:11
`kubeProvider` serves requests (gRPC service methods run on a goroutine per request, and every one shares the single `kubeProvider` value the router holds) but writes its fields outside any lock (opts, enableSecrets, defaultNamespace, deleteUnreachable, skipUpdateUnreachable, serverSideApplyMode; e.g. `opts` in `Configure` at line 590). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process. — REDACTED:131
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Go: guard the state handlers share with a sync.Mutex held for the whole update (`mu.Lock(); defer mu.Unlock()`), make counters sync/atomic types (atomic.Int64) and caches a sync.Map, or keep per-request data in locals and the request context. `go test -race` over a handler test confirms the race and then its fix.
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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. 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.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
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.
sdk/python/README.md links to `CONTRIBUTING.md`, but `sdk/python/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — sdk/python/README.md:220
sdk/python/README.md links to `CODE-OF-CONDUCT.md`, but `sdk/python/CODE-OF-CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — sdk/python/README.md:224
What to do
Reconcile the README with reality: sdk/python/README.md links to `CONTRIBUTING.md`, but `sdk/python/CONTRIBUTING.md` does not exist; sdk/python/README.md links to `CODE-OF-CONDUCT.md`, but `sdk/python/CODE-OF-CONDUCT.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
`sdk/dotnet/Pulumi.Kubernetes.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — sdk/dotnet/Pulumi.Kubernetes.csproj:34
What to do
Enable Dependabot/Renovate or a dependency-review gate.
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.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This method contradicts itself about `options`: line 1212 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 1216 then dereferences `options` as `options.Aliases` AFTER the block has closed, where the guard no longer applies. A null `options` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `options` truly cannot be null by then, the guard above is misleading and should go. — sdk/dotnet/Yaml/Yaml.cs:1216
~4.5 `!` suppressions per 1k syntax nodes — 3885 suppression(s) across the 872930 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Where a method null-tests a symbol and then uses it after the guarded block closes, move the trailing work inside the block — the guard skips its body on null, it does not stop the method.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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.
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.
SC1 Supply-chain hygiene — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 70 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 — no DI registrations detected
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — ~43506 lines of test source are present (.go, .ts, .py) 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.
D11 Test Reliability — Test reliability not measured — no test run produced results
D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .go, .java — the .NET project files present are an immaterial minority — so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 CQRS handler(s); 1 event-sourced shape(s) (event folds / event-recording aggregates)
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — sql-migrate is declared, but this repository defines no table or model of its own, so there is no database schema here 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 by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
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.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — go (23,526 lines), java (236 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 0% of this repository's production lines — go (23,526 lines), java (236 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — no async method does work a token could cancel
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — X21 reached only 0% of this repository's production lines — go (23,526 lines), java (236 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 0% of this repository's production lines — go (23,526 lines), java (236 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 0% of this repository's production lines — go (23,526 lines), java (236 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×38
JavaScript dependencies are not locked sdk/nodejs/package.json:16— sdk/nodejs/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/ci-cluster/package.json:3— tests/ci-cluster/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/aliases/step1/package.json:4— tests/sdk/nodejs/aliases/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/autonaming/step1/package.json:4— tests/sdk/nodejs/autonaming/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/crds/step1/package.json:4— tests/sdk/nodejs/crds/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/delete-before-replace/step1/package.json:4— tests/sdk/nodejs/delete-before-replace/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/deployment-rollout/step1/package.json:4— tests/sdk/nodejs/deployment-rollout/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/drift-correct/configmap-csa/package.json:4— tests/sdk/nodejs/drift-correct/configmap-csa/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/drift-correct/configmap-ssa/package.json:4— tests/sdk/nodejs/drift-correct/configmap-ssa/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/empty-array/step1/package.json:4— tests/sdk/nodejs/empty-array/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/apache/package.json:4— tests/sdk/nodejs/examples/apache/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/guestbook/package.json:4— tests/sdk/nodejs/examples/guestbook/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-api-versions/step1/package.json:4— tests/sdk/nodejs/examples/helm-api-versions/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-kube-version/step1/package.json:4— tests/sdk/nodejs/examples/helm-kube-version/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-local-panic/step1/package.json:3— tests/sdk/nodejs/examples/helm-local-panic/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-local/step1/package.json:4— tests/sdk/nodejs/examples/helm-local/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-no-default-provider/package.json:3— tests/sdk/nodejs/examples/helm-no-default-provider/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-release-crd/step1/package.json:3— tests/sdk/nodejs/examples/helm-release-crd/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-release-namespace/step1/package.json:3— tests/sdk/nodejs/examples/helm-release-namespace/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-release-redis/step1/package.json:3— tests/sdk/nodejs/examples/helm-release-redis/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-release/step1/package.json:3— tests/sdk/nodejs/examples/helm-release/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm-skip-crd-rendering/step1/package.json:4— tests/sdk/nodejs/examples/helm-skip-crd-rendering/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/helm/step1/package.json:4— tests/sdk/nodejs/examples/helm/step1/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/ingress/package.json:4— tests/sdk/nodejs/examples/ingress/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tests/sdk/nodejs/examples/mariadb/package.json:4— tests/sdk/nodejs/examples/mariadb/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
FileTooLong: REDACTED REDACTED— FileTooLong — 2053 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: kubeProvider (34 blocks, 131-2954). The bar is 500 significant lines; this is 1553 over it, 4.11× 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: gen/overlays.go provider/pkg/gen/overlays.go— FileTooLong — 1219 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 719 over it, 2.44× 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: provider/helm_release.go provider/pkg/provider/helm_release.go— FileTooLong — 1145 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 645 over it, 2.29× 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: await/await.go provider/pkg/await/await.go— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 102 over it, 1.20× 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: REDACTED REDACTED— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: deploymentInitAwaiter (19 blocks, 109-940). The bar is 500 significant lines; this is 22 over it, 1.04× 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: pulumi-gen-kubernetes/main.go provider/cmd/pulumi-gen-kubernetes/main.go— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 12 over it, 1.02× 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: REDACTED REDACTED— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: PulumiSchema (129-785). The bar is 500 significant lines; this is 12 over it, 1.02× 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.
MethodTooLong: kubeProvider.Configure REDACTED:572— MethodTooLong — Configure runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.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.
MethodTooLong: kubeProvider.Read REDACTED:1899— MethodTooLong — Read runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× 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: kubeProvider.Diff REDACTED:1431— MethodTooLong — Diff runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: kubeProvider.Create REDACTED:1682— MethodTooLong — Create runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: kubeProvider.Update REDACTED:2306— MethodTooLong — Update runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: kubeProvider.Check REDACTED:1158— MethodTooLong — Check runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: ChartProvider.Construct REDACTED:159— MethodTooLong — Construct runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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 (10 lines × 2) provider/pkg/await/awaiters.go:414— provider/pkg/await/awaiters.go:414-423 | provider/pkg/await/awaiters.go:501-511 — 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 `provider/pkg/await/awaiters.go:414` 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) provider/pkg/clients/memcache.go:122— provider/pkg/clients/memcache.go:122-131 | provider/pkg/clients/memcache.go:293-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) REDACTED:178— REDACTED:178-187 | REDACTED:116-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) REDACTED:2006— REDACTED:2006-2015 | REDACTED:2122-2131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:2133` calls `NewPropertyMapFromMap`, `annotateSecrets` and `REDACTED:2017` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) REDACTED:164— REDACTED:164-173 | REDACTED:174-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also 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 (10 lines × 2) REDACTED:181— REDACTED:181-190 | REDACTED:191-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (10 lines × 2) provider/pkg/await/ingress.go:123— provider/pkg/await/ingress.go:123-132 | provider/pkg/await/ingress.go:133-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. 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.
FunctionTooLong: gen.PulumiSchema REDACTED:129— FunctionTooLong — PulumiSchema runs 406 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 306 over it, 4.06× 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: await.Creation provider/pkg/await/await.go:153— FunctionTooLong — Creation runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: kinds.init provider/pkg/kinds/deprecated.go:51— FunctionTooLong — init runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: gen.createKinds REDACTED:604— FunctionTooLong — createKinds runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (8 lines × 2) REDACTED:860— REDACTED:860-867 | REDACTED:873-880 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:860` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) provider/pkg/await/ingress.go:199— provider/pkg/await/ingress.go:199-206 | provider/pkg/await/service.go:204-211 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/await/ingress.go:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) REDACTED:469— REDACTED:469-476 | REDACTED:510-517 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:469` 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 (8 lines × 2) provider/pkg/gen/overlays.go:1654— provider/pkg/gen/overlays.go:1654-1661 | provider/pkg/gen/overlays.go:1738-1745 — 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 `provider/pkg/gen/overlays.go:1654` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) provider/pkg/provider/helm_release.go:1040— provider/pkg/provider/helm_release.go:1040-1044 | REDACTED:2533-2540 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) REDACTED:460— REDACTED:460-465 | REDACTED:1459-1463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:460` 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. 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.
Duplicated block (5 lines × 2) provider/pkg/provider/helm_release.go:857— provider/pkg/provider/helm_release.go:857-861 | provider/pkg/provider/helm_release.go:862-866 — 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 (5 lines × 2) provider/pkg/await/ingress.go:528— provider/pkg/await/ingress.go:528-532 | provider/pkg/await/service.go:435-439 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/await/ingress.go:528` 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.
ClassTooLong: kubeProvider REDACTED:131— ClassTooLong — 1545 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods, 34 blocks, lines 131-2954. The bar is 400 significant lines; this is 1145 over it, 3.86× 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: helmReleaseProvider provider/pkg/provider/helm_release.go:184— ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods, 16 blocks, lines 184-1415. The bar is 400 significant lines; this is 227 over it, 1.57× 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: deploymentInitAwaiter REDACTED:109— ClassTooLong — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods, 19 blocks, lines 109-940. The bar is 400 significant lines; this is 86 over it, 1.22× 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:216— REDACTED:216-261 | provider/pkg/await/ingress.go:156-184 | provider/pkg/await/service.go:162-195 | provider/pkg/await/statefulset.go:221-252 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) provider/pkg/provider/helm_release.go:972— provider/pkg/provider/helm_release.go:972-1035 | provider/pkg/provider/helm_release.go:1139-1212 | REDACTED:1684-1894 | REDACTED:2308-2526 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:1684— REDACTED:1684-1894 | REDACTED:1899-2151 | REDACTED:2308-2526 | REDACTED:2530-2646 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) provider/pkg/await/checker/pod/check.go:60— provider/pkg/await/checker/pod/check.go:60-80 | provider/pkg/await/checker/pod/check.go:82-102 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) REDACTED:811— REDACTED:811-836 | provider/pkg/await/statefulset.go:480-500 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) provider/pkg/await/service.go:200— provider/pkg/await/service.go:200-226 | provider/pkg/await/statefulset.go:257-277 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) provider/pkg/gen/overlays.go:444— provider/pkg/gen/overlays.go:444-458 | provider/pkg/gen/overlays.go:502-516 — 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 `provider/pkg/gen/overlays.go:444` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) provider/pkg/provider/helm_release.go:1105— provider/pkg/provider/helm_release.go:1105-1119 | REDACTED:2008-2022 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/provider/helm_release.go:1105` 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 (15 lines × 2) provider/pkg/await/daemonset.go:248— provider/pkg/await/daemonset.go:248-262 | provider/pkg/await/statefulset.go:529-543 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/await/daemonset.go:248` 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 (13 lines × 3) REDACTED:1780— REDACTED:1780-1792 | REDACTED:2432-2444 | REDACTED:2586-2598 — 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:1780` 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 (13 lines × 3) provider/pkg/gen/overlays.go:151— provider/pkg/gen/overlays.go:151-163 | provider/pkg/gen/overlays.go:1329-1341 | provider/pkg/gen/overlays.go:1432-1465 — 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 `provider/pkg/gen/overlays.go:151` 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.
Duplicated block (13 lines × 3) provider/pkg/await/ingress.go:297— provider/pkg/await/ingress.go:297-309 | provider/pkg/await/service.go:275-287 | provider/pkg/await/service.go:319-335 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. 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:307— REDACTED:307-318 | REDACTED:158-169 — 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 `REDACTED:307` 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 (12 lines × 2) REDACTED:1063— REDACTED:1063-1074 | REDACTED:1122-1133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) provider/pkg/await/condition/observer.go:179— provider/pkg/await/condition/observer.go:179-190 | provider/pkg/await/util.go:84-95 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `provider/pkg/await/condition/observer.go:176` calls `Observe` and `provider/pkg/await/util.go:73` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) provider/pkg/provider/helm_release.go:976— provider/pkg/provider/helm_release.go:976-984 | REDACTED:1711-1719 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) provider/pkg/await/job.go:164— provider/pkg/await/job.go:164-172 | provider/pkg/await/pod.go:189-197 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/await/job.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) provider/pkg/clients/unstructured.go:195— provider/pkg/clients/unstructured.go:195-203 | provider/pkg/clients/unstructured.go:213-221 — 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 `provider/pkg/clients/unstructured.go:195` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) REDACTED:1702— REDACTED:1702-1708 | REDACTED:2335-2341 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) provider/pkg/await/checker/job/check.go:80— provider/pkg/await/checker/job/check.go:80-86 | provider/pkg/await/checker/pod/check.go:204-210 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) REDACTED:459— REDACTED:459-465 | provider/pkg/provider/helm_release.go:1417-1423 — 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.
Hotspot: REDACTED REDACTED:129— REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in gen.PulumiSchema at line 129. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:46:36 +00:00' --until='2026-11-16 23:46:36 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:159— REDACTED changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ChartProvider.Construct at line 159. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 23:46:36 +00:00' --until='2026-11-16 23:46:36 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TodoComment tests/sdk/dotnet/basic/Program.cs:100— // TODO: Re-enable these tests once CI GKE account has the appropriate permissions to create the RoleBinding below. — 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 tests/sdk/dotnet/server-side-apply/Program.cs:154— // TODO: Get isn't currently supported for CustomResources. — 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.
TooManyFields: kubeProvider REDACTED:131— TooManyFields — 41 stored fields beside 39 methods. The bar is 30 stored fields; this is 11 over it, 1.37× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Release provider/pkg/provider/helm_release.go:70— TooManyFields — 34 stored fields. The bar is 30 stored fields; this is 4 over it, 1.13× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) provider/pkg/await/service.go:122— provider/pkg/await/service.go:122-160 | provider/pkg/await/statefulset.go:190-219 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) REDACTED:313— REDACTED:313-352 | provider/pkg/await/statefulset.go:283-312 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) provider/pkg/gomega/matchers.go:95— provider/pkg/gomega/matchers.go:95-111 | provider/pkg/gomega/matchers.go:113-129 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) provider/pkg/clients/unstructured.go:190— provider/pkg/clients/unstructured.go:190-206 | provider/pkg/clients/unstructured.go:208-224 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (22 lines × 2) provider/pkg/provider/helm_release.go:1000— provider/pkg/provider/helm_release.go:1000-1021 | provider/pkg/provider/helm_release.go:1179-1200 — 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 `provider/pkg/provider/helm_release.go:1000` 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 (22 lines × 2) REDACTED:1744— REDACTED:1744-1765 | REDACTED:2398-2419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1744` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) REDACTED:524— REDACTED:524-537 | REDACTED:545-558 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:524` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) provider/pkg/gomega/matchers.go:98— provider/pkg/gomega/matchers.go:98-111 | provider/pkg/gomega/matchers.go:116-129 — 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 `provider/pkg/gomega/matchers.go:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) REDACTED:821— REDACTED:821-831 | provider/pkg/await/statefulset.go:485-495 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:821` 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) provider/pkg/provider/yaml/v2/configfile.go:74— provider/pkg/provider/yaml/v2/configfile.go:74-84 | provider/pkg/provider/yaml/v2/configgroup.go:78-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 3) provider/cmd/pulumi-gen-kubernetes/main.go:288— provider/cmd/pulumi-gen-kubernetes/main.go:288-296 | provider/cmd/pulumi-gen-kubernetes/main.go:336-344 | provider/cmd/pulumi-gen-kubernetes/main.go:430-438 — 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 `provider/cmd/pulumi-gen-kubernetes/main.go:288` 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 (9 lines × 3) REDACTED:2007— REDACTED:2007-2015 | REDACTED:2123-2131 | REDACTED:2630-2638 — 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:2007` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:2133` calls `NewPropertyMapFromMap`, `annotateSecrets` and `REDACTED:2017` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×2
NuGet dependencies are not locked sdk/dotnet/Pulumi.Kubernetes.csproj:34— sdk/dotnet/Pulumi.Kubernetes.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked tests/sdk/dotnet/options/options-test.csproj:10— tests/sdk/dotnet/options/options-test.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Stateful shared instance: __Value sdk/dotnet/Config/Config.cs:11— `__Value` is not registered, but `Config` creates it and keeps it in the static `_alwaysRender`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_value, _set; e.g. `_value` at line 28).
Stateful handler: kubeProvider REDACTED:131— `kubeProvider` serves requests (gRPC service methods run on a goroutine per request, and every one shares the single `kubeProvider` value the router holds) but writes its fields outside any lock (opts, enableSecrets, defaultNamespace, deleteUnreachable, skipUpdateUnreachable, serverSideApplyMode; e.g. `opts` in `Configure` at line 590). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process.
kubeProvider.Configure (cyclomatic 81) REDACTED:572— kubeProvider.Configure has cyclomatic complexity 81 (threshold 15). Of this number, 50 points are the body's own statements and 31 belong to 15 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
gen.PulumiSchema (cyclomatic 56) REDACTED:129— gen.PulumiSchema has cyclomatic complexity 56 (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.
kubeProvider.Check (cyclomatic 47) REDACTED:1158— kubeProvider.Check has cyclomatic complexity 47 (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 file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
kubeProvider.Diff (cyclomatic 43) REDACTED:1431— kubeProvider.Diff has cyclomatic complexity 43 (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 file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
kubeProvider.Read (cyclomatic 33) REDACTED:1899— kubeProvider.Read has cyclomatic complexity 33 (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 file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
kubeProvider.CheckConfig (cyclomatic 32) REDACTED:332— kubeProvider.CheckConfig has cyclomatic complexity 32 (threshold 15). Of this number, 27 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. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
kubeProvider.Create (cyclomatic 32) REDACTED:1682— kubeProvider.Create has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
await.Creation (cyclomatic 30) provider/pkg/await/await.go:153— await.Creation has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 168). 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.
gen.createKinds (cyclomatic 30) REDACTED:604— gen.createKinds has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
kubeProvider.List (cyclomatic 30) REDACTED:2154— kubeProvider.List 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. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
kubeProvider.Update (cyclomatic 29) REDACTED:2306— kubeProvider.Update 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. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
deploymentInitAwaiter.processDeploymentEvent (cyclomatic 27) REDACTED:444— deploymentInitAwaiter.processDeploymentEvent has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
deploymentInitAwaiter.checkReplicaSetStatus (cyclomatic 27) REDACTED:593— deploymentInitAwaiter.checkReplicaSetStatus has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
patchConverter.addPatchValueToDiff (cyclomatic 27) REDACTED:3288— patchConverter.addPatchValueToDiff has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
main.findPulumiTokenFromTerraformToken (cyclomatic 24) provider/cmd/pulumi-gen-kubernetes/main.go:620— main.findPulumiTokenFromTerraformToken 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.
statefulsetInitAwaiter.processStatefulSetEvent (cyclomatic 24) provider/pkg/await/statefulset.go:347— statefulsetInitAwaiter.processStatefulSetEvent has cyclomatic complexity 24 (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.
ChartProvider.Construct (cyclomatic 24) REDACTED:159— ChartProvider.Construct has cyclomatic complexity 24 (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.
gen.makeSchemaTypeSpec (cyclomatic 23) REDACTED:353— gen.makeSchemaTypeSpec has cyclomatic complexity 23 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ingressInitAwaiter.checkIfEndpointsReady (cyclomatic 22) provider/pkg/await/ingress.go:353— ingressInitAwaiter.checkIfEndpointsReady has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
kubeProvider.Invoke (cyclomatic 21) REDACTED:1035— kubeProvider.Invoke 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. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
provider.locateChart (cyclomatic 20) provider/pkg/provider/helm_release.go:1586— provider.locateChart 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.
TemplateOrInstallCommand.runInstall (cyclomatic 19) REDACTED:246— TemplateOrInstallCommand.runInstall has cyclomatic complexity 19 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
helmReleaseProvider.helmUpdate (cyclomatic 19) provider/pkg/provider/helm_release.go:691— helmReleaseProvider.helmUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
kubeProvider.DiffConfig (cyclomatic 19) REDACTED:454— kubeProvider.DiffConfig has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
helmReleaseProvider.helmCreate (cyclomatic 18) provider/pkg/provider/helm_release.go:564— helmReleaseProvider.helmCreate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
chart.template (cyclomatic 18) provider/pkg/provider/invoke_helm_template.go:227— chart.template has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
gen.genPropertySpec (cyclomatic 17) REDACTED:787— gen.genPropertySpec has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
provider.flattenOpenAPI (cyclomatic 17) provider/pkg/provider/provider_parameterize.go:209— provider.flattenOpenAPI has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
helmReleaseProvider.Diff (cyclomatic 17) provider/pkg/provider/helm_release.go:800— helmReleaseProvider.Diff has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
provider.parseListQuery (cyclomatic 16) REDACTED:2771— provider.parseListQuery has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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 file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 12 of the 30 functions over the threshold — including the worst — and 230 of the 392 points over it (59%), 5.3× the next-largest file (REDACTED at 43). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Deprecated module: github.com/golang/protobuf — `github.com/golang/protobuf` is required at v1.5.4 in REDACTED, and its author has DEPRECATED the module: "Use the "google.golang.org/protobuf" module instead." A deprecation is declared by the author in the module's own REDACTED and applies to the whole module, not to one release, so moving to a newer version of it does not clear this. Follow the replacement the notice names.
gen.PulumiSchema (cognitive 203) REDACTED:129— gen.PulumiSchema has cognitive complexity 203 (threshold 15). Drivers by points: if/else 32 (123 pts), loops 21 (78 pts), boolean chains 2 (nesting depth added 148). 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.
kubeProvider.Configure (cognitive 103) REDACTED:572— kubeProvider.Configure has cognitive complexity 103 (threshold 15). Drivers by points: if/else 77 (97 pts), boolean chains 6 (nesting depth added 20). Of this number, 72 points are the body's own statements and 31 belong to 15 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
kubeProvider.Diff (cognitive 80) REDACTED:1431— kubeProvider.Diff has cognitive complexity 80 (threshold 15). Drivers by points: if/else 29 (56 pts), loops 5 (15 pts), match/switch 2 (6 pts), boolean chains 3 (nesting depth added 41). 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.
kubeProvider.Check (cognitive 73) REDACTED:1158— kubeProvider.Check has cognitive complexity 73 (threshold 15). Drivers by points: if/else 41 (66 pts), boolean chains 7 (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.
ingressInitAwaiter.checkIfEndpointsReady (cognitive 57) provider/pkg/await/ingress.go:353— ingressInitAwaiter.checkIfEndpointsReady has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (42 pts), loops 4 (10 pts), boolean chains 4, match/switch 1 (nesting depth added 35). 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.
kubeProvider.Read (cognitive 53) REDACTED:1899— kubeProvider.Read has cognitive complexity 53 (threshold 15). Drivers by points: if/else 31 (50 pts), loops 1 (2 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.
deploymentInitAwaiter.processDeploymentEvent (cognitive 49) REDACTED:444— deploymentInitAwaiter.processDeploymentEvent has cognitive complexity 49 (threshold 15). Drivers by points: if/else 20 (42 pts), boolean chains 6, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gen.createKinds (cognitive 49) REDACTED:604— gen.createKinds has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 5 (12 pts), match/switch 2 (6 pts), boolean chains 3 (nesting depth added 29). 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.findPulumiTokenFromTerraformToken (cognitive 45) provider/cmd/pulumi-gen-kubernetes/main.go:620— main.findPulumiTokenFromTerraformToken has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 6 (9 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider.flattenOpenAPI (cognitive 44) provider/pkg/provider/provider_parameterize.go:209— provider.flattenOpenAPI has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (38 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 28). 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.
kubeProvider.Create (cognitive 44) REDACTED:1682— kubeProvider.Create has cognitive complexity 44 (threshold 15). Drivers by points: if/else 23 (39 pts), boolean chains 5 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kubeProvider.CheckConfig (cognitive 43) REDACTED:332— kubeProvider.CheckConfig has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (30 pts), boolean chains 11, match/switch 1 (2 pts) (nesting depth added 13). Of this number, 38 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.
await.Creation (cognitive 40) provider/pkg/await/await.go:153— await.Creation has cognitive complexity 40 (threshold 15). Drivers by points: if/else 23 (34 pts), boolean chains 6 (nesting depth added 11). Most of this is not in the body itself: 13 of the 40 points are its own statements and the rest belongs to one function literal inside it that branches (line 168). 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.
kubeProvider.Update (cognitive 38) REDACTED:2306— kubeProvider.Update has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 5 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
patchConverter.addPatchValueToDiff (cognitive 38) REDACTED:3288— patchConverter.addPatchValueToDiff has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (27 pts), match/switch 3 (6 pts), boolean chains 4, loops 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.
TemplateOrInstallCommand.runInstall (cognitive 36) REDACTED:246— TemplateOrInstallCommand.runInstall has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 2 (nesting depth added 17). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
kubeProvider.List (cognitive 35) REDACTED:2154— kubeProvider.List has cognitive complexity 35 (threshold 15). Drivers by points: if/else 27 (32 pts), boolean chains 2, 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, 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.
kubeProvider.Invoke (cognitive 33) REDACTED:1035— kubeProvider.Invoke has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 4, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChartProvider.Construct (cognitive 29) REDACTED:159— ChartProvider.Construct has cognitive complexity 29 (threshold 15). Drivers by points: if/else 24 (29 pts) (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, 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.
deploymentInitAwaiter.checkReplicaSetStatus (cognitive 28) REDACTED:593— deploymentInitAwaiter.checkReplicaSetStatus has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 7 (nesting depth added 6). Of this number, 24 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider.locateChart (cognitive 28) provider/pkg/provider/helm_release.go:1586— provider.locateChart has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 4 (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.
statefulsetInitAwaiter.processStatefulSetEvent (cognitive 27) provider/pkg/await/statefulset.go:347— statefulsetInitAwaiter.processStatefulSetEvent has cognitive complexity 27 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
memCacheClient.refreshLocked (cognitive 24) provider/pkg/clients/memcache.go:248— memCacheClient.refreshLocked has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (9 pts), boolean chains 2 (nesting depth added 11). Of this number, 16 points are the body's own statements and 8 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.
provider.decodeYaml (cognitive 24) provider/pkg/provider/invoke_decode_yaml.go:29— provider.decodeYaml has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.buildPulumiFieldsFromTerraform (cognitive 23) provider/cmd/pulumi-gen-kubernetes/main.go:731— main.buildPulumiFieldsFromTerraform has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 2 (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.
provider.convertYAMLManifestToJSON (cognitive 23) provider/pkg/provider/manifest_json.go:27— provider.convertYAMLManifestToJSON has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (5 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
kubeProvider.DiffConfig (cognitive 23) REDACTED:454— kubeProvider.DiffConfig has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 6). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body 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.
provider.parseListQuery (cognitive 22) REDACTED:2771— provider.parseListQuery has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (22 pts) (nesting depth added 7). Of this number, 20 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.
helmReleaseProvider.helmCreate (cognitive 22) provider/pkg/provider/helm_release.go:564— helmReleaseProvider.helmCreate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 3 (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.
helmReleaseProvider.helmUpdate (cognitive 22) provider/pkg/provider/helm_release.go:691— helmReleaseProvider.helmUpdate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 3 (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.
helmReleaseProvider.Diff (cognitive 22) provider/pkg/provider/helm_release.go:800— helmReleaseProvider.Diff has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), loops 3 (5 pts), match/switch 1 (3 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
kubeProvider.Delete (cognitive 22) REDACTED:2530— kubeProvider.Delete has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
await.handleSSAIgnoreFields (cognitive 21) provider/pkg/await/await.go:716— await.handleSSAIgnoreFields has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 2, match/switch 1 (2 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.
gen.genPropertySpec (cognitive 21) REDACTED:787— gen.genPropertySpec has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 5). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider.decodeRelease (cognitive 21) provider/pkg/provider/helm_release.go:292— provider.decodeRelease has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 2 (6 pts), loops 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chart.template (cognitive 21) provider/pkg/provider/invoke_helm_template.go:227— chart.template has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 2 (nesting depth added 4). Of this number, 13 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
kinds.init (cognitive 19) provider/pkg/kinds/deprecated.go:51— kinds.init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (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.
metadata.ReadyCondition (cognitive 19) provider/pkg/metadata/overrides.go:100— metadata.ReadyCondition has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider.pruneSlice (cognitive 19) REDACTED:271— provider.pruneSlice has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, match/switch 1 (2 pts), loops 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.
helm.NewRegistryClient (cognitive 18) REDACTED:372— helm.NewRegistryClient has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (nesting depth added 5). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
await.Read (cognitive 17) provider/pkg/await/await.go:376— await.Read has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
condition.checkCondition (cognitive 17) REDACTED:30— condition.checkCondition has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
gen.makeSchemaTypeSpec (cognitive 17) REDACTED:353— gen.makeSchemaTypeSpec has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
patchConverter.addPatchArrayToDiff (cognitive 17) REDACTED:3425— patchConverter.addPatchArrayToDiff has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body 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.
observer.Range (cognitive 16) provider/pkg/await/condition/observer.go:146— observer.Range has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
deploymentInitAwaiter.waitUntilDeploymentControllerReconciles (cognitive 16) REDACTED:354— deploymentInitAwaiter.waitUntilDeploymentControllerReconciles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ingressInitAwaiter.await (cognitive 16) provider/pkg/await/ingress.go:222— ingressInitAwaiter.await has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
jsonpath.splitOnValue (cognitive 16) provider/pkg/jsonpath/jsonpath.go:117— jsonpath.splitOnValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 4, match/switch 1 (2 pts), loops 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.
provider.annotateSecrets (cognitive 16) REDACTED:3474— provider.annotateSecrets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
helmReleaseProvider.Read (cognitive 16) provider/pkg/provider/helm_release.go:1037— helmReleaseProvider.Read has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D22 · Internal API Consistency· `condition.NewAll` takes no context.Context; its 4 sibling operations take one · ×1
`condition.NewAll` takes no context.Context; its 4 sibling operations take one provider/pkg/await/condition/all.go:15— 4 of 5 fallible operations of `package condition` take a `ctx context.Context` (4 of 5). Siblings: condition.NewCustom (provider/pkg/await/condition/custom.go:30); condition.NewDeleted (provider/pkg/await/condition/deleted.go:47); condition.NewJSONPath (provider/pkg/await/condition/jsonpath.go:26); condition.NewDeletionSource (provider/pkg/await/condition/source.go:120). Take `ctx context.Context` as the first parameter, like its siblings, and pass it on. [rule A1]
D22 · Internal API Consistency· `logging.WithPrefix` signals absence with a nil `*T` where its 3 sibling single-key reads use a bare `T` (the zero value when absent) · ×1
`logging.WithPrefix` signals absence with a nil `*T` where its 3 sibling single-key reads use a bare `T` (the zero value when absent) provider/pkg/logging/log_writer.go:49— 3 of 4 single-key reads of `package logging` return a bare `T` (the zero value when absent) (3 of 4). Siblings: logging.StatusMessage (provider/pkg/logging/message.go:37); logging.WarningMessage (provider/pkg/logging/message.go:42); logging.ErrorMessage (provider/pkg/logging/message.go:47). Return a bare `T` (the zero value when absent) like its siblings. [rule A5]
D22 · Internal API Consistency· `yaml.ParseYamlObjects` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) · ×1
`yaml.ParseYamlObjects` returns a map (`map[K]V`) where its 3 siblings return a slice (`[]T`) sdk/go/kubernetes/yaml/yaml.go:235— 3 of 4 collection-returning members of `package yaml` return a slice (`[]T`) (3 of 4). Siblings: yaml.GetChildOptions (sdk/go/kubernetes/yaml/yaml.go:101); yaml.GetInvokeOptions (sdk/go/kubernetes/yaml/yaml.go:116); yaml.AddSkipAwaitTransformation (sdk/go/kubernetes/yaml/yaml.go:207). Return a slice (`[]T`). [rule A4]
TooManyMethods: kubeProvider REDACTED:131— TooManyMethods — 39 methods, declared across 4 files: REDACTED (33), provider/provider_parameterize.go (3), provider/provider_construct.go (2), provider/diff.go (1). The bar is 30 methods; this is 9 over it, 1.30× 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) provider/pkg/provider/helm_release.go:802— provider/pkg/provider/helm_release.go:802-942 | provider/pkg/provider/helm_release.go:1139-1212 | REDACTED:457-569 | REDACTED:1431-1677 | REDACTED:2308-2526 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) provider/pkg/provider/yaml/v2/configfile.go:59— provider/pkg/provider/yaml/v2/configfile.go:59-132 | provider/pkg/provider/yaml/v2/configgroup.go:63-144 — These two members are one piece of code written twice and then edited apart: 74 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 (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) REDACTED:143— REDACTED:143-214 | provider/pkg/await/ingress.go:102-154 — These two members are one piece of code written twice and then edited apart: 53 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) REDACTED:265— REDACTED:265-303 | provider/pkg/await/ingress.go:188-219 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) provider/pkg/await/ingress.go:296— provider/pkg/await/ingress.go:296-339 | provider/pkg/await/service.go:274-316 — 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 (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) provider/pkg/host/fake/engine.go:35— provider/pkg/host/fake/engine.go:35-60 | provider/pkg/host/fake/monitor.go:54-79 — 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 copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) provider/pkg/await/daemonset.go:245— provider/pkg/await/daemonset.go:245-262 | provider/pkg/await/service.go:429-446 | provider/pkg/await/statefulset.go:526-543 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) REDACTED:763— REDACTED:763-790 | REDACTED:800-827 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) REDACTED:383— REDACTED:383-413 | provider/pkg/provider/invoke_helm_template.go:340-373 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) REDACTED:751— REDACTED:751-773 | provider/pkg/await/statefulset.go:457-478 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (31 lines × 2) provider/pkg/await/await.go:340— provider/pkg/await/await.go:340-370 | provider/pkg/await/await.go:524-554 — 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 `provider/pkg/await/await.go:340` 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 (24–25 lines × 2) provider/pkg/await/await.go:295— provider/pkg/await/await.go:295-318 | provider/pkg/await/await.go:479-503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also 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 (15–24 lines × 4) REDACTED:219— REDACTED:219-240 | provider/pkg/await/ingress.go:158-172 | provider/pkg/await/service.go:163-186 | provider/pkg/await/statefulset.go:223-245 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 2) provider/pkg/provider/yaml/v2/configfile.go:112— provider/pkg/provider/yaml/v2/configfile.go:112-132 | provider/pkg/provider/yaml/v2/configgroup.go:123-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/provider/yaml/v2/configfile.go:112` 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 (18–21 lines × 2) provider/pkg/await/await.go:693— provider/pkg/await/await.go:693-710 | provider/pkg/await/await.go:786-806 — 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 `provider/pkg/await/await.go:693` 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 (21 lines × 2) REDACTED:483— REDACTED:483-503 | REDACTED:522-542 — 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 (20 lines × 2) provider/pkg/provider/helm_release.go:342— provider/pkg/provider/helm_release.go:342-361 | REDACTED:1202-1221 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18–19 lines × 2) provider/pkg/await/await.go:321— provider/pkg/await/await.go:321-338 | provider/pkg/await/await.go:503-521 — 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 `provider/pkg/await/await.go:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–18 lines × 2) REDACTED:585— REDACTED:585-598 | REDACTED:623-640 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:623` 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–17 lines × 2) provider/cmd/pulumi-gen-kubernetes/main.go:282— provider/cmd/pulumi-gen-kubernetes/main.go:282-298 | provider/cmd/pulumi-gen-kubernetes/main.go:330-345 — 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 `provider/cmd/pulumi-gen-kubernetes/main.go:282` 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 (17 lines × 2) REDACTED:1857— REDACTED:1857-1873 | REDACTED:2486-2502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1857` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15–16 lines × 4) provider/pkg/provider/helm_release.go:809— provider/pkg/provider/helm_release.go:809-823 | provider/pkg/provider/helm_release.go:1142-1157 | REDACTED:1463-1477 | REDACTED:2344-2358 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/provider/helm_release.go:809` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:2339` calls `GetPreview`, `Errorf` and `REDACTED:1459` 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 (13–15 lines × 4) provider/pkg/provider/helm_release.go:1010— provider/pkg/provider/helm_release.go:1010-1022 | provider/pkg/provider/helm_release.go:1189-1201 | REDACTED:1857-1871 | REDACTED:2486-2500 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/provider/helm_release.go:1010` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 4) REDACTED:1752— REDACTED:1752-1762 | REDACTED:1856-1866 | REDACTED:2406-2416 | REDACTED:2485-2495 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:1852` calls `GetPreview`, `RemoveNestedField` and `REDACTED:2482` 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 (10 lines × 4) REDACTED:1778— REDACTED:1778-1787 | REDACTED:2033-2042 | REDACTED:2430-2439 | REDACTED:2584-2593 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1778` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) REDACTED:1067— REDACTED:1067-1076 | REDACTED:1102-1111 | REDACTED:1126-1135 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) REDACTED:242— REDACTED:242-247 | REDACTED:249-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:242` 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 × 4) provider/pkg/gen/overlays.go:151— provider/pkg/gen/overlays.go:151-163 | provider/pkg/gen/overlays.go:1329-1341 | provider/pkg/gen/overlays.go:1432-1464 | provider/pkg/gen/overlays.go:1566-1578 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `provider/pkg/gen/overlays.go:151` 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.
Duplicated block (16 lines × 2) REDACTED:288— REDACTED:288-303 | provider/pkg/await/statefulset.go:262-277 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:288` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) REDACTED:904— REDACTED:904-911 | REDACTED:913-920 | REDACTED:922-929 — 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:904` 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.
End-of-life runtime: .NET net6.0 sdk/dotnet/Pulumi.Kubernetes.csproj:14— sdk/dotnet/Pulumi.Kubernetes.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Low cohesion: StubResettableRESTMapper (LCOM4 7) provider/pkg/clients/fake/discovery.go:131— StubResettableRESTMapper's methods fall into 7 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 7 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.
X5 · Nullable reference types· Null guard scopes only part of the work it protects · ×1
Null guard scopes only part of the work it protects sdk/dotnet/Yaml/Yaml.cs:1216— This method contradicts itself about `options`: line 1212 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 1216 then dereferences `options` as `options.Aliases` AFTER the block has closed, where the guard no longer applies. A null `options` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `options` truly cannot be null by then, the guard above is misleading and should go.
redundant comment tests/sdk/nodejs/crds/step1/index.ts:19— "Create a CustomResourceDefinition and a CustomResource." repeats the code it sits on: 4 of its 4 words (create, custom, resource, definition) are already in `const crd = new k8s.apiextensions.v1.CustomResourceDefinition("foobar", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/crds/step2/index.ts:20— "Create a CustomResourceDefinition and a CustomResource." repeats the code it sits on: 4 of its 4 words (create, custom, resource, definition) are already in `const crd = new k8s.apiextensions.v1.CustomResourceDefinition("foobar", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/crds/step2/index.ts:78— "Get the CustomResource." repeats the code it sits on: 3 of its 3 words (get, custom, resource) are already in `export const objRef = k8s.apiextensions.CustomResource.get("my-new-foobar-object-ref", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/get/step1/index.ts:19— "`get`s the Kubernetes API service." repeats the code it sits on: 4 of its 4 words (get, kubernetes, api, service) are already in `export const svc = k8s.core.v1.Service.get("kube-api", "default/kubernetes");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/get/step1/index.ts:52— "Create a CustomResourceDefinition, a CustomResource, and then `.get` it." repeats the code it sits on: 4 of its 5 words (create, custom, resource, definition) are already in `export const ct = new k8s.apiextensions.v1.CustomResourceDefinition("crontab", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/get/step2/index.ts:20— "`get`s the Kubernetes API service." repeats the code it sits on: 4 of its 4 words (get, kubernetes, api, service) are already in `export const svc = k8s.core.v1.Service.get("kube-api", "default/kubernetes");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/get/step2/index.ts:65— "Create a CustomResourceDefinition, a CustomResource, and then `.get` it." repeats the code it sits on: 4 of its 5 words (create, custom, resource, definition) are already in `export const ct = new k8s.apiextensions.v1.CustomResourceDefinition("crontab", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/server-side-apply/step1/index.ts:100— "Patch the CronTab CustomResource to add a label." repeats the code it sits on: 6 of its 7 words (patch, cron, tab, custom, resource, label) are already in `export const crPatched = new k8s.apiextensions.CustomResourcePatch("label-cr",`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/server-side-apply/step2/index.ts:100— "Patch the CronTab CustomResource to add a label." repeats the code it sits on: 6 of its 7 words (patch, cron, tab, custom, resource, label) are already in `export const crPatched = new k8s.apiextensions.CustomResourcePatch("label-cr",`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/server-side-apply/step3/index.ts:100— "Patch the CronTab CustomResource to add a label." repeats the code it sits on: 6 of its 7 words (patch, cron, tab, custom, resource, label) are already in `export const crPatched = new k8s.apiextensions.CustomResourcePatch("label-cr",`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/skip-update-unreachable/step1/index.ts:30— "Create a namespace and a configmap in the provided cluster." repeats the code it sits on: 4 of its 5 words (create, namespace, configmap, cluster) are already in `function createCM(clusterNumber: number, provider: k8s.Provider): [k8s.core.v1.Namespace, k8s.core.v1.ConfigMap]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/sdk/nodejs/skip-update-unreachable/step2/index.ts:30— "Create a namespace and a configmap in the provided cluster." repeats the code it sits on: 4 of its 5 words (create, namespace, configmap, cluster) are already in `function createCM(clusterNumber: number, provider: k8s.Provider): [k8s.core.v1.Namespace, k8s.core.v1.ConfigMap]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
README/code drift sdk/python/README.md:220— sdk/python/README.md links to `CONTRIBUTING.md`, but `sdk/python/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift sdk/python/README.md:224— sdk/python/README.md links to `CODE-OF-CONDUCT.md`, but `sdk/python/CODE-OF-CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: provider/pkg/provider/provider_parameterize.go, provider/pkg/gen/dotnet.go. Pair on, review, or document these before any departure.
D21 · Naming Consistency· `extensionsv1b1ApiVersion` spells `Api` where 22 names in the project spell it `API` · ×1
`extensionsv1b1ApiVersion` spells `Api` where 22 names in the project spell it `API` REDACTED:106— 22 of 23 names in project github.com/pulumi/pulumi-kubernetes/provider/v4 spell the token `API` (22 of 23; unit: names in project github.com/pulumi/pulumi-kubernetes/provider/v4 containing `API`). Peers: ProviderConfig.InitialAPIVersion (provider/pkg/await/await.go:79); awaitConfig.initialAPIVersion (provider/pkg/await/awaiters.go:50); fake.LoadOpenAPISchema (provider/pkg/clients/fake/discovery.go:50); SimpleDiscovery.OpenAPISchema (provider/pkg/clients/fake/discovery.go:96); memCacheClient.OpenAPISchema (provider/pkg/clients/memcache.go:206). Rename to `extensionsv1b1APIVersion`. [rule N6]
D21 · Naming Consistency· `frontendIp` spells `Ip` where 32 names in the project spell it `IP` · ×1
`frontendIp` spells `Ip` where 32 names in the project spell it `IP` tests/sdk/nodejs/istio/step1/index.ts:54— 32 of 33 names in project repository spell the token `IP` (32 of 33; unit: names in project repository containing `IP`). Peers: sdk.nodejs.types.input.ClientIPConfig (sdk/nodejs/types/input.ts:14944); sdk.nodejs.types.input.ClientIPConfigPatch (sdk/nodejs/types/input.ts:14954); ContainerPort.hostIP (sdk/nodejs/types/input.ts:15522); ContainerPortPatch.hostIP (sdk/nodejs/types/input.ts:15548); sdk.nodejs.types.input.HostIP (sdk/nodejs/types/input.ts:17314). Rename to `frontendIP`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion sdk/dotnet/Pulumi.Kubernetes.csproj:1— `Pulumi.Kubernetes` overshoots its size bounds (268577 LoC, 5331 public types across 220 namespaces). 1 of 16 project(s) overshoot their size bounds, lowering Project Cohesion to 8.8/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No dependency-update automation sdk/dotnet/Pulumi.Kubernetes.csproj:34— `sdk/dotnet/Pulumi.Kubernetes.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Duplicated predicate REDACTED:3500— `outValue.IsObject() && inValue.IsObject()` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~4.5 `!` suppressions per 1k syntax nodes — 3885 suppression(s) across the 872930 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated: github.com/fluxcd/pkg/ssa — `github.com/fluxcd/pkg/ssa` is required at v0.71.1-0.20260424094917-4f94dc680419 in REDACTED, but v0.84.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/fluxcd/pkg/ssa@v0.84.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-openapi/jsonreference — `github.com/go-openapi/jsonreference` is required at v1.0.1 in REDACTED, but v1.0.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/go-openapi/jsonreference@v1.0.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/hashicorp/hcl/v2 — `github.com/hashicorp/hcl/v2` is required at v2.24.0 in REDACTED, but v2.25.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/hashicorp/hcl/v2@v2.25.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/imdario/mergo — `github.com/imdario/mergo` is required at v0.3.16 in REDACTED, but v1.0.2 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/imdario/mergo@v1.0.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/onsi/ginkgo/v2 — `github.com/onsi/ginkgo/v2` is required at v2.32.0 in REDACTED, but v2.34.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/onsi/ginkgo/v2@v2.34.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/onsi/gomega — `github.com/onsi/gomega` is required at v1.40.0 in REDACTED, but v1.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/onsi/gomega@v1.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/pgavlin/fx/v2 — `github.com/pgavlin/fx/v2` is required at v2.0.12 in REDACTED, but v2.0.13 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/pgavlin/fx/v2@v2.0.13 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/pulumi/pulumi-dotnet/pulumi-language-dotnet/v3 — `github.com/pulumi/pulumi-dotnet/pulumi-language-dotnet/v3` is required at v3.113.1 in REDACTED, but v3.119.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/pulumi/pulumi-dotnet/pulumi-language-dotnet/v3@v3.119.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/pulumi/pulumi/pkg/v3 — `github.com/pulumi/pulumi/pkg/v3` is required at v3.268.0 in REDACTED, but v3.276.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/pulumi/pulumi/pkg/v3@v3.276.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/pulumi/pulumi/sdk/v3 — `github.com/pulumi/pulumi/sdk/v3` is required at v3.268.0 in REDACTED, but v3.276.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/pulumi/pulumi/sdk/v3@v3.276.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/pulumi/pulumi/sdk/v3 — `github.com/pulumi/pulumi/sdk/v3` is required at v3.268.0 in REDACTED, but v3.276.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/pulumi/pulumi/sdk/v3@v3.276.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/theory/jsonpath — `github.com/theory/jsonpath` is required at v0.9.0 in REDACTED, but v0.12.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/theory/jsonpath@v0.12.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: google.golang.org/grpc — `google.golang.org/grpc` is required at v1.84.0 in REDACTED, but v1.85.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get google.golang.org/grpc@v1.85.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: helm.sh/helm/v3 — `helm.sh/helm/v3` is required at v3.20.2 in REDACTED, but v3.22.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get helm.sh/helm/v3@v3.22.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/api — `k8s.io/api` is required at v0.37.1 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/api@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/apiextensions-apiserver — `k8s.io/apiextensions-apiserver` is required at v0.37.0 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/apiextensions-apiserver@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/apimachinery — `k8s.io/apimachinery` is required at v0.37.1 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/apimachinery@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/apiserver — `k8s.io/apiserver` is required at v0.37.1 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/apiserver@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/cli-runtime — `k8s.io/cli-runtime` is required at v0.37.1 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/cli-runtime@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/client-go — `k8s.io/client-go` is required at v0.37.1 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/client-go@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: k8s.io/kubectl — `k8s.io/kubectl` is required at v0.37.1 in REDACTED, but v0.37.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get k8s.io/kubectl@v0.37.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: oras.land/oras-go/v2 — `oras.land/oras-go/v2` is required at v2.6.2 in REDACTED, but v2.7.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get oras.land/oras-go/v2@v2.7.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: sigs.k8s.io/kustomize/api — `sigs.k8s.io/kustomize/api` is required at v0.21.1 in REDACTED, but v0.21.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/kustomize/api@v0.21.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: sigs.k8s.io/kustomize/kyaml — `sigs.k8s.io/kustomize/kyaml` is required at v0.21.1 in REDACTED, but v0.21.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/kustomize/kyaml@v0.21.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.
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.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e704-5a09-7bc9-afaa-8d64e13fc660 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 40 · Warnings: 501 · Recommendations: 93 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 00:59 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.