Public report of google/skills, 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:54 UTC · Survey ID cd_677610daa37f4a5fb125013514fd6519
google/skills
Measured 17 November 2026, 01:53 UTC, at code version 56fba3e
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 1.1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 49,854 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 32.4
Findings by how serious they are
5 critical545 serious56 minor
9 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, 01:53 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 ▸
61of 61 dimensions measured by tools.
584of 606 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
61dimensions across 7 lenses, read from 49,854 lines of product code in 11 projects.
google/skills falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 53.0 out of 100 and is rated Adequate, and all five of its critical findings are security problems.
Production Readiness, at 32.4, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 16.9 points. Adding tests for untested code comes next, worth about 14.1 points. Raising Production Readiness to 70 would lift the score to about 68.6.
Three settings leave the servers or containers unsafe. One known security hole in a package the code depends on can be used by attackers, and one password or key is open to anyone who can read the repository. Replacing the exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks.
The product code is 49,854 lines, about €56,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 32.4 to 70, the lowest score rated Strong, the score would rise from 53.0 to about 68.6.
Code composition: what the lines of code are
Product code 87%Tests 13%
New since the last survey: 143 findings
These 143 critical or serious findings weren't in the previous survey, on 5 November 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FileTooLong: scripts/package_ai_pack.py skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py
God Classes · FileTooLong: scripts/benchmark_on_device.py skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py
God Classes · FileTooLong: scripts/compile_model.py skills/platform-devices/litert-google-tensor/scripts/compile_model.py
God Classes · FileTooLong: assets/extraction_stats_template.py skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py
God Classes · FileTooLong: scripts/release_radar.py skills/cloud/google-cloud-release-radar/scripts/release_radar.py
God Classes · FileTooLong: scripts/debug_workload.py skills/cloud/pathways-workload/scripts/debug_workload.py
Code Duplication · Edited copy of a member (95 corresponding lines) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 9 findings
These 9 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one.
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €56,000 · Estimate
Cost to rebuild
€19,000 to €93,000, for 309 to 981 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 53. 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: 49,854 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 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 16.9 points · Low effort · Secret Scanning
2
Resolve the 16 Low coverage finding(s) in Code Coverage — start with analyze_traffic.py (2), check_telemetry.py (2), create_online_monitor.py (2).
Raises the score by about 14.1 points · Medium effort · Code Coverage
3
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
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 €56,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 32.4 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 16.9 points for low effort, because it clears the 1 Secret Scanning 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 4.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 17% on every change. The history of the code shows how much it changes: about 208,132 lines over the last 90 days, which is about 844,091 lines a year. At that pace, the extra work comes to an estimated 161.2 to 967.4 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.
84 modules, with 14 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 44 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.
TensorModelLoader.Path uses TensorModelLoader, so a change to TensorModelLoader can break TensorModelLoader.Path, while a change to TensorModelLoader.Path can't break TensorModelLoader.
Position
Below the diagonal: TensorModelLoader.Path uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in skills.cloud.assuredworkloads-frameworks-navigator.scripts uses a type in skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_output_match_analyzer.
skills.cloud.assuredworkloads-frameworks-navigator.scripts uses skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_output_match_analyzer, so a change to skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_output_match_analyzer can break skills.cloud.assuredworkloads-frameworks-navigator.scripts, while a change to skills.cloud.assuredworkloads-frameworks-navigator.scripts can't break skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_output_match_analyzer.
Position
Below the diagonal: skills.cloud.assuredworkloads-frameworks-navigator.scripts uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in skills.cloud.assuredworkloads-frameworks-navigator.scripts uses a type in skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_resources_loader.
skills.cloud.assuredworkloads-frameworks-navigator.scripts uses skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_resources_loader, so a change to skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_resources_loader can break skills.cloud.assuredworkloads-frameworks-navigator.scripts, while a change to skills.cloud.assuredworkloads-frameworks-navigator.scripts can't break skills.cloud.assuredworkloads-frameworks-navigator.scripts.db_resources_loader.
Position
Below the diagonal: skills.cloud.assuredworkloads-frameworks-navigator.scripts uses a module listed above it, which is the healthy direction.
skills.cloud.cloud-logging-finops.scripts uses skills.cloud.cloud-logging-finops.scripts.actions, so a change to skills.cloud.cloud-logging-finops.scripts.actions can break skills.cloud.cloud-logging-finops.scripts, while a change to skills.cloud.cloud-logging-finops.scripts can't break skills.cloud.cloud-logging-finops.scripts.actions.
Position
Below the diagonal: skills.cloud.cloud-logging-finops.scripts uses a module listed above it, which is the healthy direction.
skills.cloud.cloud-logging-finops.scripts uses skills.cloud.cloud-logging-finops.scripts.billing, so a change to skills.cloud.cloud-logging-finops.scripts.billing can break skills.cloud.cloud-logging-finops.scripts, while a change to skills.cloud.cloud-logging-finops.scripts can't break skills.cloud.cloud-logging-finops.scripts.billing.
Position
Below the diagonal: skills.cloud.cloud-logging-finops.scripts uses a module listed above it, which is the healthy direction.
skills.cloud.cloud-logging-finops.scripts uses skills.cloud.cloud-logging-finops.scripts.monitoring, so a change to skills.cloud.cloud-logging-finops.scripts.monitoring can break skills.cloud.cloud-logging-finops.scripts, while a change to skills.cloud.cloud-logging-finops.scripts can't break skills.cloud.cloud-logging-finops.scripts.monitoring.
Position
Below the diagonal: skills.cloud.cloud-logging-finops.scripts uses a module listed above it, which is the healthy direction.
skills.cloud.cloud-logging-finops.scripts uses skills.cloud.cloud-logging-finops.scripts.pricing, so a change to skills.cloud.cloud-logging-finops.scripts.pricing can break skills.cloud.cloud-logging-finops.scripts, while a change to skills.cloud.cloud-logging-finops.scripts can't break skills.cloud.cloud-logging-finops.scripts.pricing.
Position
Below the diagonal: skills.cloud.cloud-logging-finops.scripts uses a module listed above it, which is the healthy direction.
skills.cloud.cloud-logging-finops.scripts uses skills.cloud.cloud-logging-finops.scripts.provenance, so a change to skills.cloud.cloud-logging-finops.scripts.provenance can break skills.cloud.cloud-logging-finops.scripts, while a change to skills.cloud.cloud-logging-finops.scripts can't break skills.cloud.cloud-logging-finops.scripts.provenance.
Position
Below the diagonal: skills.cloud.cloud-logging-finops.scripts uses a module listed above it, which is the healthy direction.
skills.cloud.cloud-logging-finops.scripts uses skills.cloud.cloud-logging-finops.scripts.verify_claim, so a change to skills.cloud.cloud-logging-finops.scripts.verify_claim can break skills.cloud.cloud-logging-finops.scripts, while a change to skills.cloud.cloud-logging-finops.scripts can't break skills.cloud.cloud-logging-finops.scripts.verify_claim.
Position
Below the diagonal: skills.cloud.cloud-logging-finops.scripts uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in skills.cloud.cloud-monitoring-chart-generation.scripts uses a type in skills.cloud.cloud-monitoring-chart-generation.scripts.textproto_util.
skills.cloud.cloud-monitoring-chart-generation.scripts uses skills.cloud.cloud-monitoring-chart-generation.scripts.textproto_util, so a change to skills.cloud.cloud-monitoring-chart-generation.scripts.textproto_util can break skills.cloud.cloud-monitoring-chart-generation.scripts, while a change to skills.cloud.cloud-monitoring-chart-generation.scripts can't break skills.cloud.cloud-monitoring-chart-generation.scripts.textproto_util.
Position
Below the diagonal: skills.cloud.cloud-monitoring-chart-generation.scripts uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in skills.cloud.cloud-trace-querying.scripts.search_traces.src uses a type in skills.cloud.cloud-trace-querying.scripts.search_traces.src.trace_searcher.
skills.cloud.cloud-trace-querying.scripts.search_traces.src uses skills.cloud.cloud-trace-querying.scripts.search_traces.src.trace_searcher, so a change to skills.cloud.cloud-trace-querying.scripts.search_traces.src.trace_searcher can break skills.cloud.cloud-trace-querying.scripts.search_traces.src, while a change to skills.cloud.cloud-trace-querying.scripts.search_traces.src can't break skills.cloud.cloud-trace-querying.scripts.search_traces.src.trace_searcher.
Position
Below the diagonal: skills.cloud.cloud-trace-querying.scripts.search_traces.src uses a module listed above it, which is the healthy direction.
skills.cloud.pathways-workload.scripts uses skills.cloud.pathways-workload.scripts.debug_workload, so a change to skills.cloud.pathways-workload.scripts.debug_workload can break skills.cloud.pathways-workload.scripts, while a change to skills.cloud.pathways-workload.scripts can't break skills.cloud.pathways-workload.scripts.debug_workload.
Position
Below the diagonal: skills.cloud.pathways-workload.scripts uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in skills.platform-devices.litert-google-tensor.scripts uses a type in skills.platform-devices.litert-google-tensor.scripts.benchmark_on_device.
skills.platform-devices.litert-google-tensor.scripts uses skills.platform-devices.litert-google-tensor.scripts.benchmark_on_device, so a change to skills.platform-devices.litert-google-tensor.scripts.benchmark_on_device can break skills.platform-devices.litert-google-tensor.scripts, while a change to skills.platform-devices.litert-google-tensor.scripts can't break skills.platform-devices.litert-google-tensor.scripts.benchmark_on_device.
Position
Below the diagonal: skills.platform-devices.litert-google-tensor.scripts uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 77.3 · Adequate · gated by D1, 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
71
High / Critical
A05:2025 — Injection
4
Medium
A03:2025 — Software Supply Chain Failures
2
High / Critical
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Resolve the 16 Low coverage finding(s) in Code Coverage — start with analyze_traffic.py (2), check_telemetry.py (2), create_online_monitor.py (2); Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 5
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 — 545
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 — 56
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
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 61 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 — 61 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, 584 of 606 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.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 1 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (8 contributor(s) across 613 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 7 hold 0.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (skills/platform-devices/litert-google-tensor/assets/templates/runtime_strings/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `skills/platform-devices/litert-google-tensor/assets/templates/TensorModelLoader.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Skills/cloud/gke-cluster-autoscaler/assets/capacity-buffer-serving.yaml:27 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, 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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
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.
+ 101 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with infographic_template.html.renderAll (cyclomatic 166), package_ai_pack.plan_update (cyclomatic 141), benchmark_on_device.main (cyclomatic 106). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: 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.
+ 160 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 68 bodies over 30 down to 30 or less in Cognitive Complexity — start with validate_mcp_openapi.validate_mcp_spec (cognitive 224), package_ai_pack.plan_update (cognitive 214), infographic_template.html.renderAll (cognitive 162). — 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 68 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 FileTooLong finding(s) in God Classes — start with package_ai_pack.py, dbt_translator.py, benchmark_on_device.py. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 4 FunctionTooLong finding(s) in God Classes — start with REDACTED (3), infographic_template.html. — 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.
95 duplicated block group(s) detected. 10.6 % of the production lines (5,266 of 49,854) are in a reported copy. A further 25 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:23
+ 87 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with list_log_scope_table_names.py (3), config_utils.py, lint_syntax.py. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with skill_registry_ops.py (2), gather_agent_info.py, main.py. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with extraction_stats_template.py, compile_model.py, package_ai_pack.py. — 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.
2 production modules (npm+source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and — for the source no manifest declares — its top-level source directories, with the imports between them as edges; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 15.5% — 16 file(s) below 50%. Measured from the Python suite (repository root: `coverage run -m pytest`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
Resolve the 16 Low coverage finding(s) in Code Coverage — start with analyze_traffic.py (2), check_telemetry.py (2), create_online_monitor.py (2). — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether 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: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with prepare_dataset.py, dbt_translator.py. — 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.
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.
0 deducted task-comment markers across 49854 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 11 build units (Python, checkout, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
92 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
4 finding(s): 0 critical, 0 high, 4 medium, 0 low. semgrep hit a parse error in 7 file(s) — `REDACTED` (line 118, line 125, line 511, …), `skills/cloud/apigee-agent-gateway-governance/scripts/deploy_proxy.sh`, `skills/cloud/apigee-agent-gateway-governance/scripts/ensure_apigee_environment.sh`, `skills/cloud/apigee-agent-gateway-governance/scripts/ensure_gateway_connectivity.sh` (line 77, line 83, lines 84–149), `skills/cloud/apigee-agent-gateway-governance/scripts/ensure_vector_search.sh`, … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 52 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (24), REDACTED (11), REDACTED (11). — One of this dimension's main actionable groups (52 warning-level).
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 16 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (16 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 115 of the 148 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
2/3 workload(s) run every container under a seccomp profile; 0/3 declare an AppArmor/SELinux profile.
No seccomp profileREDACTED:6
What to do
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.
Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 19 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — REDACTED:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — REDACTED:1010
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.sev-segment` moves (`transition: width 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:299
`.accordion-arrow` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:319
`.payload-box` moves (`transition: max-height 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:357
`details[open] summary .telemetry-toggle-arrow` moves (`transition: transform 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:492
`summary .telemetry-toggle-arrow` moves (`transition: transform 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:496
`.badge` sets color: #94a3b8 on background-color: #334155 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:71
`.copy-btn` sets color: #fff on background-color: #3b82f6 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:363
`.bar-fill` moves (`transition: width 0.5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — skills/developers/migrate-to-rust/references/infographic_template.html:371
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether 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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether 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.
plugins/cloud/google-cloud-developer/.antigravity-plugin/README.md links to `./rules/google-cloud-discovery.md`, but `plugins/cloud/google-cloud-developer/.antigravity-plugin/rules/google-cloud-discovery.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. — plugins/cloud/google-cloud-developer/.antigravity-plugin/README.md:35
plugins/cloud/google-cloud-developer/.codex-plugin/README.md links to `./rules/google-cloud-discovery.md`, but `plugins/cloud/google-cloud-developer/.codex-plugin/rules/google-cloud-discovery.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. — plugins/cloud/google-cloud-developer/.codex-plugin/README.md:77
What to do
Reconcile the README with reality: plugins/cloud/google-cloud-developer/.antigravity-plugin/README.md links to `./rules/google-cloud-discovery.md`, but `plugins/cloud/google-cloud-developer/.antigravity-plugin/rules/google-cloud-discovery.md` does not exist; plugins/cloud/google-cloud-developer/.codex-plugin/README.md links to `./rules/google-cloud-discovery.md`, but `plugins/cloud/google-cloud-developer/.codex-plugin/rules/google-cloud-discovery.md` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates6.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability1.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 5 JVM, Python, JavaScript/TypeScript production file(s) this check read across 3 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
`skills/platform-devices/litert-google-tensor/assets/templates/google_tensor_runtime/build.gradle.kts` 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`. — skills/platform-devices/litert-google-tensor/assets/templates/google_tensor_runtime/build.gradle.kts:32
What to do
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
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.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Do you agree with this assessment?
P5 · DR & Backup10.0 / 10Exemplary✓ 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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:65, skills/cloud/google-cloud-solution-multi-agent-security/scripts/verify_egress_policies.py:26
`requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×6) — skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:88, skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:109, skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:130, …
`requests.delete(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:151
`requests.patch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:212
`urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — skills/cloud/iam-helper-for-troubleshooting/scripts/troubleshooting_error_id.py:149, skills/cloud/managed-airflow-recommendations/scripts/lib/monitoring.py:84
What to do
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
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 the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`validate_mcp_spec` is public, takes a document from its caller (line 170) and hands it to `_type_list_schemas`, which calls itself at line 163 (`_type_list_schemas`) with a piece of `node` (and at line 166) — and nowhere in `_type_list_schemas` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_type_list_schemas` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:163
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:275, skills/cloud/google-cloud-filestore-nfs-browser/scripts/nfs_browser.py:48, skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:64, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1479, skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:175, skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:373, …
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 7 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.
AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXO1 Runtime API surface — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 22 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 53 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.
AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
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
AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, 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 a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~7669 lines of test source are present (.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.
D12 Dependency Hygiene — Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 1 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — Not scored — this repository's 1 declared JVM dependency coordinate(s) were read from its 3 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 0 of them (no diagnostic), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt, .py source were not judged.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (27 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 17 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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
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
X2 Cancellation propagation — no C# was loaded; this repository's Python and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
FileTooLong: scripts/package_ai_pack.py skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py— FileTooLong — 2883 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2383 over it, 5.77× 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: scripts/dbt_translator.py skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py— FileTooLong — 1661 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1161 over it, 3.32× 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: scripts/benchmark_on_device.py skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py— FileTooLong — 1557 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1057 over it, 3.11× 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 — 1501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1001 over it, 3.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scripts/compile_model.py skills/platform-devices/litert-google-tensor/scripts/compile_model.py— FileTooLong — 1442 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 942 over it, 2.88× 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: scripts/provenance.py skills/cloud/cloud-logging-finops/scripts/provenance.py— FileTooLong — 1154 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 654 over it, 2.31× 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: scripts/telemetry.py skills/developers/migrate-to-rust/scripts/telemetry.py— FileTooLong — 1047 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 547 over it, 2.09× 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: scripts/validate_params.py skills/cloud/assured-workloads-basics/scripts/validate_params.py— FileTooLong — 1030 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 530 over it, 2.06× 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: assets/extraction_stats_template.py skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py— FileTooLong — 941 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 441 over it, 1.88× 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: assets/python_embedded_sql_migrator_template.py skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py— FileTooLong — 855 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 355 over it, 1.71× 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: scripts/release_radar.py skills/cloud/google-cloud-release-radar/scripts/release_radar.py— FileTooLong — 816 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 316 over it, 1.63× 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: scripts/debug_workload.py skills/cloud/pathways-workload/scripts/debug_workload.py— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 236 over it, 1.47× 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: scripts/upgrade_policy.py skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py— FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 207 over it, 1.41× 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: scripts/manage_workload_updates.py skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py— FileTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 109 over it, 1.22× 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.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:65— `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:88— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:109— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:130— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:151— `requests.delete(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:212— `requests.patch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:233— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:257— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:279— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/google-cloud-solution-multi-agent-security/scripts/verify_egress_policies.py:26— `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/iam-helper-for-troubleshooting/scripts/troubleshooting_error_id.py:149— `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience skills/cloud/managed-airflow-recommendations/scripts/lib/monitoring.py:84— `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AXH1 · Runtime security headers· Runtime security header not set · ×11
Runtime security header not set: content-security-policy — The live app's responses did not include content-security-policy (restricts the sources a page may load — mitigates XSS/injection). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-embedder-policy — The live app's responses did not include cross-origin-embedder-policy (recommended by the OWASP Secure Headers Project (value: require-corp)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-opener-policy — The live app's responses did not include cross-origin-opener-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-resource-policy — The live app's responses did not include cross-origin-resource-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: permissions-policy — The live app's responses did not include permissions-policy (restricts powerful browser features (camera, geolocation, …)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: referrer-policy — The live app's responses did not include referrer-policy (limits referrer leakage to third parties). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: strict-transport-security — The live app's responses did not include strict-transport-security (forces HTTPS on subsequent requests — mitigates downgrade/MITM). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-content-type-options — The live app's responses did not include x-content-type-options (stops MIME-sniffing (expects 'nosniff')). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-dns-prefetch-control — The live app's responses did not include x-dns-prefetch-control (recommended by the OWASP Secure Headers Project (value: off)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-frame-options — The live app's responses did not include x-frame-options (blocks clickjacking via framing (or use CSP frame-ancestors)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-permitted-cross-domain-policies — The live app's responses did not include x-permitted-cross-domain-policies (recommended by the OWASP Secure Headers Project (value: none)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×6
Animation without a prefers-reduced-motion guard REDACTED:299— `.sev-segment` moves (`transition: width 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:319— `.accordion-arrow` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:357— `.payload-box` moves (`transition: max-height 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:492— `details[open] summary .telemetry-toggle-arrow` moves (`transition: transform 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:496— `summary .telemetry-toggle-arrow` moves (`transition: transform 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard skills/developers/migrate-to-rust/references/infographic_template.html:371— `.bar-fill` moves (`transition: width 0.5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:23— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:23-34 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:23-34 | skills/cloud/cloud-monitoring-alert-configuration/scripts/lint_promql.py:13-24 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:37-48 — 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) skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:23— skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:23-53 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/lint_syntax.py:26-56 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:263-312 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:384-445 — 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) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:45— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:45-66 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:46-64 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:45-66 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:46-64 — 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) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:70— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:70-97 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:68-98 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:70-97 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:68-98 — 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) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:124— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:124-163 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:102-147 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:124-163 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:102-147 — 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) skills/cloud/cloud-trace-querying/scripts/fetch_entire_trace/src/main.py:28— skills/cloud/cloud-trace-querying/scripts/fetch_entire_trace/src/main.py:28-59 | skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/main.py:53-76 | skills/cloud/cloud-trace-querying/scripts/fetch_trace_span/src/main.py:48-85 | skills/cloud/cloud-trace-querying/scripts/search_traces/src/main.py:16-72 — 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.
Swallowed exception (caught, then discarded) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:275— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) skills/cloud/google-cloud-filestore-nfs-browser/scripts/nfs_browser.py:48— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:64— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) skills/cloud/cloud-trace-querying/scripts/get_trace_project/src/project_resolver.py:67— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) skills/cloud/cloud-logging-finops/scripts/billing.py:135— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (empty catch) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1479— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:175— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:373— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:381— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) skills/cloud/cloud-monitoring-chart-generation/scripts/assemble_widget_proto.py:235— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
FunctionTooLong: infographic_template.html.renderAll skills/developers/migrate-to-rust/references/infographic_template.html:883— FunctionTooLong — renderAll runs 375 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 275 over it, 3.75× 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: REDACTED.hydrateDashboard REDACTED:1161— FunctionTooLong — hydrateDashboard runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: REDACTED.renderDailyServiceChart REDACTED:1970— FunctionTooLong — renderDailyServiceChart 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.
FunctionTooLong: REDACTED.renderTrendChart REDACTED:1360— FunctionTooLong — renderTrendChart runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.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.
Duplicated block (12 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:221— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:221-232 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:225-236 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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) skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:41— skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:41-52 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:178-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:104— skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:104-115 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:228-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) skills/cloud/cloud-trace-querying/scripts/fetch_entire_trace/src/main.py:32— skills/cloud/cloud-trace-querying/scripts/fetch_entire_trace/src/main.py:32-43 | skills/cloud/cloud-trace-querying/scripts/fetch_trace_span/src/main.py:51-62 — 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 (8 lines × 2) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:882— skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:882-889 | skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:956-963 — 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 (8 lines × 2) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1374— skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1374-1381 | skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1783-1790 — 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2520— skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2520-2527 | skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:3384-3393 — 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 `skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:3384` 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 (8 lines × 2) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:585— skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:585-592 | skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:601-608 — 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.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×3
Edited copy of a member (22 corresponding lines) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:78— skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:78-99 | skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:103-126 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:57— skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:57-78 | skills/cloud/api-gateway-openapi-spec-authoring/scripts/validate_apigw_openapi.py:196-232 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:95— skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:95-116 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:99-123 — 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 (19 lines × 2) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:268— skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:268-286 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:394-412 — before extracting anything, compare `skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py` and `skills/cloud/gke-alert-configuration/scripts/validate_config.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 255 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:268` 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 (19 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:356— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:356-374 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1005-1025 — 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 `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:356` 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 (19 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:199— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:199-217 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:203-221 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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.
config_utils.extract_alert_policies (cyclomatic 29) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:182— config_utils.extract_alert_policies 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.
config_utils.extract_alert_policies (cyclomatic 29) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:182— config_utils.extract_alert_policies 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.
gather_agent_info.main (cyclomatic 18) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:350— gather_agent_info.main 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.
gather_agent_info.main (cyclomatic 18) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:362— gather_agent_info.main 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.
HCLScanner.extract_alert_policies (cyclomatic 18) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:88— HCLScanner.extract_alert_policies 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.
HCLScanner.extract_alert_policies (cyclomatic 18) skills/cloud/gke-alert-configuration/scripts/validate_config.py:129— HCLScanner.extract_alert_policies 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.
Hotspot: skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py:107— skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in prepare_dataset.convert_to_jsonl at line 107. 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 12:11:22 -08:00' --until='2026-11-16 12:11:22 -08:00' --full-history --no-merges -- skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py`: 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: skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:595— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in dbt_translator.sanitize_json_extractions at line 595. 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 12:11:22 -08:00' --until='2026-11-16 12:11:22 -08:00' --full-history --no-merges -- skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py`: 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.
config_utils.extract_alert_policies (cognitive 75) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:182— config_utils.extract_alert_policies has cognitive complexity 75 (threshold 15). Drivers by points: if/else 13 (44 pts), loops 11 (26 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 48). 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.
config_utils.extract_alert_policies (cognitive 75) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:182— config_utils.extract_alert_policies has cognitive complexity 75 (threshold 15). Drivers by points: if/else 13 (44 pts), loops 11 (26 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 48). 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.
HCLScanner.extract_alert_policies (cognitive 41) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:88— HCLScanner.extract_alert_policies has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (28 pts), loops 5 (10 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HCLScanner.extract_alert_policies (cognitive 41) skills/cloud/gke-alert-configuration/scripts/validate_config.py:129— HCLScanner.extract_alert_policies has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (28 pts), loops 5 (10 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gather_agent_info.main (cognitive 25) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:350— gather_agent_info.main has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (23 pts), ternaries 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gather_agent_info.main (cognitive 25) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:362— gather_agent_info.main has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (23 pts), ternaries 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
analyze_traffic.main (cognitive 22) skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:301— analyze_traffic.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 4 (7 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
analyze_traffic.main (cognitive 22) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:313— analyze_traffic.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 4 (7 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_config.validate_directory_tf_files (cognitive 20) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:192— validate_config.validate_directory_tf_files has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 2 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
validate_config.validate_directory_tf_files (cognitive 20) skills/cloud/gke-alert-configuration/scripts/validate_config.py:316— validate_config.validate_directory_tf_files has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 2 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
config_utils.lint_query (cognitive 18) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:118— config_utils.lint_query has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 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.
config_utils.lint_query (cognitive 18) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:118— config_utils.lint_query has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 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.
list_trace_scope_table_names.main (cognitive 17) skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:101— list_trace_scope_table_names.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 4 (6 pts), error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
list_trace_scope_table_names.main (cognitive 17) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:101— list_trace_scope_table_names.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 4 (6 pts), error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scan_duplicates.validate_directory_tf_files (cognitive 17) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:24— scan_duplicates.validate_directory_tf_files has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (5 pts), loops 4 (5 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scan_duplicates.validate_directory_tf_files (cognitive 17) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:28— scan_duplicates.validate_directory_tf_files has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (5 pts), loops 4 (5 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gather_agent_info.find_agent_via_cais (cognitive 16) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:65— gather_agent_info.find_agent_via_cais has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 3 (6 pts), error handling 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.
gather_agent_info.find_agent_via_cais (cognitive 16) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:69— gather_agent_info.find_agent_via_cais has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 3 (6 pts), error handling 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.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:755— skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:755-778 | skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:386-406 — 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) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1534— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1534-1562 | skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1566-1586 — 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 (46 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:32— skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:32-77 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py:32-77 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `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 (46 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:102— skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:102-147 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:102-147 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (34 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:82— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:82-115 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:82-115 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `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 (34 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:162— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:162-195 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:166-199 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (26 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:23— skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:23-48 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/lint_syntax.py:26-51 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/lint_syntax.py` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/lint_syntax.py:22` calls `insert`, `dirname`, `abspath` and `skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:19` 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 (26 lines × 2) skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:223— skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:223-248 | skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:263-288 — 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 `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 (25 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:175— skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:175-199 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:181-205 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 300 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `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 (25 lines × 2) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:288— skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:288-312 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:421-445 — before extracting anything, compare `skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py` and `skills/cloud/gke-alert-configuration/scripts/validate_config.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 255 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:101— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:101-120 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:101-120 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (20 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:97— skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:97-116 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:104-123 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:45— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:45-62 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:49-66 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:236— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:236-253 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:240-257 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:38— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:38-54 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:38-54 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:119— skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:119-135 | skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:161-177 — 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 (13 lines × 2) skills/developers/migrate-to-rust/scripts/telemetry.py:1107— skills/developers/migrate-to-rust/scripts/telemetry.py:1107-1119 | skills/developers/migrate-to-rust/scripts/telemetry.py:1253-1265 — 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 `skills/developers/migrate-to-rust/scripts/telemetry.py:1107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `skills/developers/migrate-to-rust/scripts/telemetry.py:1251` calls `add_argument` and `skills/developers/migrate-to-rust/scripts/telemetry.py:1106` 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 lines × 2) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1003— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1003-1015 | skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1130-1142 — 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 `skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1003` 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 (12 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:23— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:23-34 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:23-34 | skills/cloud/cloud-monitoring-alert-configuration/scripts/lint_promql.py:13-24 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:37-48 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 × 4) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:128— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:128-139 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:104-115 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:128-139 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:104-115 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:128` 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 × 4) skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:43— skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py:43-53 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/lint_syntax.py:46-56 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:297-307 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:430-440 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/lint_syntax.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/lint_syntax.py` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:31— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:31-41 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:32-42 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:31-41 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:32-42 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:31` 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 (10 lines × 2) skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:99— skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:99-108 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:141-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:769— skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:769-778 | skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:397-406 — 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 `skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:769` 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) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:235— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:235-243 | skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:294-302 — 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) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:980— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:980-988 | skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1107-1115 — 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus REDACTED:1010— This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Low contrast colour pair in CSS (4.0:1) REDACTED:71— `.badge` sets color: #94a3b8 on background-color: #334155 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) REDACTED:363— `.copy-btn` sets color: #fff on background-color: #3b82f6 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AXI1 · Runtime container hardening· Container process runs as root · ×1
Container process runs as root: wd-runtime-app — 'wd-runtime-app' (wd-runtime-app:scan) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a REDACTED reader. Advisory evidence for CRA Annex I (2)(b).
AXO1 · Runtime API surface· API operation answered with no credentials · ×1
API operation answered with no credentials: GET /api/v1/health — http://127.0.0.1:32768/api/v1/health returned HTTP 200 to two GET requests carrying nothing. Observed on the live app. We do not decide whether this operation is meant to be public. Advisory evidence for CRA Annex I (2)(d) and NIS2 IR.4.1.
AXR1 · Runtime accessibility (rendered)· WCAG 2.4.2 reproducibly failed in a rendered surface · ×1
WCAG 2.4.2 reproducibly failed in a rendered surface — axe-core rule(s) document-title failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
AXR1 · Runtime accessibility (rendered)· WCAG 3.1.1 reproducibly failed in a rendered surface · ×1
WCAG 3.1.1 reproducibly failed in a rendered surface — axe-core rule(s) html-has-lang failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
infographic_template.html.renderAll (cyclomatic 166) skills/developers/migrate-to-rust/references/infographic_template.html:883— infographic_template.html.renderAll has cyclomatic complexity 166 (threshold 15). Of this number, 134 points are the body's own statements and 32 belong to 8 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.
package_ai_pack.plan_update (cyclomatic 141) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1686— package_ai_pack.plan_update has cyclomatic complexity 141 (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.
benchmark_on_device.main (cyclomatic 106) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1777— benchmark_on_device.main has cyclomatic complexity 106 (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.
package_ai_pack.check_integration (cyclomatic 103) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2782— package_ai_pack.check_integration has cyclomatic complexity 103 (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.
validate_mcp_openapi.validate_mcp_spec (cyclomatic 100) skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:170— validate_mcp_openapi.validate_mcp_spec has cyclomatic complexity 100 (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.
compile_model.run_colab_compile (cyclomatic 99) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:945— compile_model.run_colab_compile has cyclomatic complexity 99 (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.
extraction_stats_template.analyze_zip_archive (cyclomatic 94) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:604— extraction_stats_template.analyze_zip_archive has cyclomatic complexity 94 (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.
compile_model.main (cyclomatic 77) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1488— compile_model.main has cyclomatic complexity 77 (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.
release_radar.main (cyclomatic 54) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:737— release_radar.main has cyclomatic complexity 54 (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.
dbt_translator.preprocess_metadata (cyclomatic 52) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1551— dbt_translator.preprocess_metadata has cyclomatic complexity 52 (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.
manage_workload_updates.resolve_workload_and_update_names (cyclomatic 51) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:65— manage_workload_updates.resolve_workload_and_update_names has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
python_embedded_sql_migrator_template.safe_reinject_into_python (cyclomatic 50) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:490— python_embedded_sql_migrator_template.safe_reinject_into_python has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
waste.compute_extraneous_spend (cyclomatic 49) skills/cloud/cloud-logging-finops/scripts/waste.py:157— waste.compute_extraneous_spend has cyclomatic complexity 49 (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.
validate_params.validate_create_params (cyclomatic 47) skills/cloud/assured-workloads-basics/scripts/validate_params.py:649— validate_params.validate_create_params 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.
agreement.main (cyclomatic 45) skills/cloud/agent-platform-autorater-customization/scripts/agreement.py:52— agreement.main has cyclomatic complexity 45 (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.
db_output_match_analyzer.analyze_output_matches (cyclomatic 43) skills/cloud/assuredworkloads-frameworks-navigator/scripts/db_output_match_analyzer.py:420— db_output_match_analyzer.analyze_output_matches 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.
telemetry.analyze_directory (cyclomatic 43) skills/developers/migrate-to-rust/scripts/telemetry.py:253— telemetry.analyze_directory 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.
dbt_translator.run_bulk_translation (cyclomatic 42) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1819— dbt_translator.run_bulk_translation has cyclomatic complexity 42 (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.
REDACTED.hydrateDashboard (cyclomatic 40) REDACTED:1161— REDACTED.hydrateDashboard has cyclomatic complexity 40 (threshold 15). Of this number, 38 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.
extraction_stats_template._parse_dumper_telemetry (cyclomatic 39) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:484— extraction_stats_template._parse_dumper_telemetry has cyclomatic complexity 39 (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.
telemetry.compute_derived_metrics (cyclomatic 39) skills/developers/migrate-to-rust/scripts/telemetry.py:650— telemetry.compute_derived_metrics has cyclomatic complexity 39 (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.
upgrade_policy.upgrade_policy (cyclomatic 38) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:796— upgrade_policy.upgrade_policy has cyclomatic complexity 38 (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.
validate_yaral_rule.mask_literals_and_comments (cyclomatic 34) skills/cloud/secops-detection-engineering/scripts/validate_yaral_rule.py:123— validate_yaral_rule.mask_literals_and_comments has cyclomatic complexity 34 (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.
REDACTED.renderDailyServiceChart (cyclomatic 34) REDACTED:1970— REDACTED.renderDailyServiceChart has cyclomatic complexity 34 (threshold 15). Of this number, 16 points are the body's own statements and 18 belong to 7 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.
python_embedded_sql_migrator_template.postprocess (cyclomatic 32) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:913— python_embedded_sql_migrator_template.postprocess 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.
dbt_translator.transform_config_block (cyclomatic 32) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1318— dbt_translator.transform_config_block 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.
REDACTED.renderTrendChart (cyclomatic 31) REDACTED:1360— REDACTED.renderTrendChart has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 belong to 3 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.
REDACTED.renderDailySeverityChart (cyclomatic 31) REDACTED:1750— REDACTED.renderDailySeverityChart has cyclomatic complexity 31 (threshold 15). Of this number, 18 points are the body's own statements and 13 belong to 7 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.
validate_params.validate_apply_update_params (cyclomatic 30) skills/cloud/assured-workloads-basics/scripts/validate_params.py:1285— validate_params.validate_apply_update_params 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.
extraction_stats_template.format_stats_report (cyclomatic 29) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:1166— extraction_stats_template.format_stats_report 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.
REDACTED.renderOptimizationActions (cyclomatic 29) REDACTED:2948— REDACTED.renderOptimizationActions has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2964, 2962). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
trace_searcher.distill_trace (cyclomatic 28) skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:337— trace_searcher.distill_trace has cyclomatic complexity 28 (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.
validate_yaral_rule.validate_single_rule (cyclomatic 28) skills/cloud/secops-detection-engineering/scripts/validate_yaral_rule.py:401— validate_yaral_rule.validate_single_rule has cyclomatic complexity 28 (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.
check_quota_metrics.main (cyclomatic 26) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:294— check_quota_metrics.main has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
manage_workload_updates.execute_manage_workload_updates (cyclomatic 26) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:406— manage_workload_updates.execute_manage_workload_updates has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
textproto_util.dict_to_widget (cyclomatic 26) skills/cloud/cloud-monitoring-chart-generation/scripts/textproto_util.py:136— textproto_util.dict_to_widget has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
package_ai_pack.update_doc_values (cyclomatic 26) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2323— package_ai_pack.update_doc_values has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
REDACTED.renderSampleCard (cyclomatic 26) REDACTED:2491— REDACTED.renderSampleCard has cyclomatic complexity 26 (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.
compile_check.check (cyclomatic 25) skills/cloud/apigee-agent-gateway-governance/scripts/compile_check.py:135— compile_check.check has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
evaluate_control_rules.evaluate_telemetry (cyclomatic 25) skills/cloud/assuredworkloads-environment-assessor/scripts/evaluate_control_rules.py:305— evaluate_control_rules.evaluate_telemetry has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
bq_loader_template.run_loader (cyclomatic 24) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:1074— bq_loader_template.run_loader 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.
release_radar.resolve_catalog_matches (cyclomatic 24) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:368— release_radar.resolve_catalog_matches 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.
release_radar.fetch_feed_entries (cyclomatic 24) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:459— release_radar.fetch_feed_entries has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
benchmark_on_device.analyze_tile_pass (cyclomatic 24) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:923— benchmark_on_device.analyze_tile_pass 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.
install_and_verify.verify (cyclomatic 24) skills/platform-devices/litert-google-tensor/scripts/install_and_verify.py:485— install_and_verify.verify 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.
REDACTED.selectService (cyclomatic 24) REDACTED:2277— REDACTED.selectService has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2313, 2279). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
build_review_page.main (cyclomatic 23) skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:116— build_review_page.main has cyclomatic complexity 23 (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.
collect_logging_data.collect_data (cyclomatic 23) skills/cloud/cloud-logging-finops/scripts/collect_logging_data.py:110— collect_logging_data.collect_data has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
validate_chart.validate_widget (cyclomatic 23) skills/cloud/cloud-monitoring-chart-generation/scripts/validate_chart.py:17— validate_chart.validate_widget has cyclomatic complexity 23 (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.
dbt_translator.discover_dbt_resources (cyclomatic 23) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1442— dbt_translator.discover_dbt_resources has cyclomatic complexity 23 (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.
benchmark_on_device.analyze_power_pass (cyclomatic 23) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1043— benchmark_on_device.analyze_power_pass has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
package_ai_pack.check_inputs (cyclomatic 23) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:545— package_ai_pack.check_inputs has cyclomatic complexity 23 (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.
package_ai_pack.locate_cpu_models (cyclomatic 23) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1594— package_ai_pack.locate_cpu_models has cyclomatic complexity 23 (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.
extraction_stats_template._read_bigquery_tables_jsonl (cyclomatic 22) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:306— extraction_stats_template._read_bigquery_tables_jsonl 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.
benchmark_on_device.markdown_table (cyclomatic 22) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1657— benchmark_on_device.markdown_table has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SQLExtractor.visit_Call (cyclomatic 21) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:217— SQLExtractor.visit_Call 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.
discover_metric_schema.main (cyclomatic 21) skills/cloud/cloud-monitoring-alert-configuration/scripts/discover_metric_schema.py:272— discover_metric_schema.main 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.
REDACTED.renderServicePies (cyclomatic 21) REDACTED:2128— REDACTED.renderServicePies has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 2138, 2160, 2204, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
prepare_dataset.convert_to_jsonl (cyclomatic 20) skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py:107— prepare_dataset.convert_to_jsonl 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.
bq_loader_template._parse_config_yamls (cyclomatic 20) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:301— bq_loader_template._parse_config_yamls 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.
dbt_translator.translate_cast_suffixes (cyclomatic 20) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:106— dbt_translator.translate_cast_suffixes 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.
dbt_translator.sanitize_json_extractions (cyclomatic 20) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:595— dbt_translator.sanitize_json_extractions 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.
diagnose_lib.check_port_allowed (cyclomatic 20) skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/diagnose_lib.py:96— diagnose_lib.check_port_allowed 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.
REDACTED.renderSeverityPies (cyclomatic 20) REDACTED:1877— REDACTED.renderSeverityPies has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 1887, 1906, 1942, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
validate_params.validate_kms_and_resource_settings (cyclomatic 19) skills/cloud/assured-workloads-basics/scripts/validate_params.py:523— validate_params.validate_kms_and_resource_settings has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
validate_workload_payload.load_allowed_frameworks_and_regimes (cyclomatic 19) skills/cloud/assuredworkloads-environment-assessor/scripts/validate_workload_payload.py:35— validate_workload_payload.load_allowed_frameworks_and_regimes has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
upgrade_policy._clean_opt_out_structure (cyclomatic 19) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:521— upgrade_policy._clean_opt_out_structure has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
validate_chart.main (cyclomatic 19) skills/cloud/cloud-monitoring-chart-generation/scripts/validate_chart.py:99— validate_chart.main has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
benchmark_on_device.parse_benchmark_log (cyclomatic 19) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:775— benchmark_on_device.parse_benchmark_log has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
package_ai_pack.verify_package (cyclomatic 19) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:985— package_ai_pack.verify_package has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
package_ai_pack.verify_update (cyclomatic 19) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2276— package_ai_pack.verify_update has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Linter._check_security (cyclomatic 18) skills/cloud/api-gateway-troubleshooting/scripts/lint_openapi_for_gateway.py:458— Linter._check_security 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.
evaluate_control_rules.parse_framework_org_policy_spec (cyclomatic 18) skills/cloud/assuredworkloads-environment-assessor/scripts/evaluate_control_rules.py:136— evaluate_control_rules.parse_framework_org_policy_spec 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.
bq_loader_template._scan_sql_segments (cyclomatic 18) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:695— bq_loader_template._scan_sql_segments 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.
python_embedded_sql_migrator_template.preprocess (cyclomatic 18) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:789— python_embedded_sql_migrator_template.preprocess 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.
discover_metric_schema.validate_promql_against_schema (cyclomatic 18) skills/cloud/cloud-monitoring-alert-configuration/scripts/discover_metric_schema.py:190— discover_metric_schema.validate_promql_against_schema 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.
package_ai_pack.build_update (cyclomatic 18) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2438— package_ai_pack.build_update 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.
REDACTED.renderExtraneousSpend (cyclomatic 18) REDACTED:2732— REDACTED.renderExtraneousSpend has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
render_agent_data.render (cyclomatic 17) skills/cloud/agent-platform-autorater-customization/scripts/render_agent_data.py:31— render_agent_data.render 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.
validate_dataset._validate_agent_data (cyclomatic 17) skills/cloud/agent-platform-eval-flywheel/scripts/validate_dataset.py:161— validate_dataset._validate_agent_data 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.
validate_dataset._validate_eval_case (cyclomatic 17) skills/cloud/agent-platform-eval-flywheel/scripts/validate_dataset.py:223— validate_dataset._validate_eval_case 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.
diagnose_error.diagnose_error (cyclomatic 17) skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:285— diagnose_error.diagnose_error 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.
bq_loader_template._scan_relation_views (cyclomatic 17) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:402— bq_loader_template._scan_relation_views 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.
upgrade_policy.main (cyclomatic 17) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:1167— upgrade_policy.main 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.
aggregations.get_monthly_aggregations (cyclomatic 17) skills/cloud/cloud-logging-finops/scripts/aggregations.py:143— aggregations.get_monthly_aggregations 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.
analytics.fetch_logging_api_samples (cyclomatic 17) skills/cloud/cloud-logging-finops/scripts/analytics.py:400— analytics.fetch_logging_api_samples 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.
dbt_translator.translate_interval_expressions (cyclomatic 17) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:176— dbt_translator.translate_interval_expressions 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.
diagnose_lib.format_single_report (cyclomatic 17) skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/diagnose_lib.py:349— diagnose_lib.format_single_report 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.
main.search_files (cyclomatic 17) skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:128— main.search_files 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.
build_review_page.render_trajectory (cyclomatic 16) skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:63— build_review_page.render_trajectory has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
exclusion_rules.generate_exclusion_candidates (cyclomatic 16) skills/cloud/cloud-logging-finops/scripts/exclusion_rules.py:264— exclusion_rules.generate_exclusion_candidates has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
verify_claim.evaluate_check (cyclomatic 16) skills/cloud/cloud-logging-finops/scripts/verify_claim.py:124— verify_claim.evaluate_check has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
assemble_widget_proto.assemble_widget_textproto (cyclomatic 16) skills/cloud/cloud-monitoring-chart-generation/scripts/assemble_widget_proto.py:73— assemble_widget_proto.assemble_widget_textproto has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compute_labels.compute_widget_title (cyclomatic 16) skills/cloud/cloud-monitoring-chart-generation/scripts/compute_labels.py:78— compute_labels.compute_widget_title has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compute_labels.main (cyclomatic 16) skills/cloud/cloud-monitoring-chart-generation/scripts/compute_labels.py:285— compute_labels.main has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
trace_searcher.search_traces (cyclomatic 16) skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:437— trace_searcher.search_traces has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
release_radar.enrich_sparse_entry (cyclomatic 16) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:545— release_radar.enrich_sparse_entry has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
debug_workload._format_entry (cyclomatic 16) skills/cloud/pathways-workload/scripts/debug_workload.py:1017— debug_workload._format_entry has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
benchmark_on_device.versions_summary (cyclomatic 16) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1282— benchmark_on_device.versions_summary has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
check_compiled.main (cyclomatic 16) skills/platform-devices/litert-google-tensor/scripts/check_compiled.py:112— check_compiled.main has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
package_ai_pack.read_catalog (cyclomatic 16) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1386— package_ai_pack.read_catalog has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
package_ai_pack.compare_io (cyclomatic 16) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2196— package_ai_pack.compare_io has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
package_ai_pack.main (cyclomatic 16) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:3470— package_ai_pack.main has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
validate_mcp_openapi.validate_mcp_spec (cognitive 224) skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:170— validate_mcp_openapi.validate_mcp_spec has cognitive complexity 224 (threshold 15). Drivers by points: if/else 59 (172 pts), boolean chains 29, loops 7 (18 pts), ternaries 2 (5 pts) (nesting depth added 127). 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.
package_ai_pack.plan_update (cognitive 214) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1686— package_ai_pack.plan_update has cognitive complexity 214 (threshold 15). Drivers by points: if/else 85 (135 pts), boolean chains 31, loops 20 (26 pts), ternaries 12 (22 pts) (nesting depth added 66). 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.
infographic_template.html.renderAll (cognitive 162) skills/developers/migrate-to-rust/references/infographic_template.html:883— infographic_template.html.renderAll has cognitive complexity 162 (threshold 15). Drivers by points: boolean chains 71, if/else 45 (51 pts), ternaries 26 (40 pts) (nesting depth added 20). Of this number, 135 points are the body's own statements and 27 belong to 8 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.
package_ai_pack.check_integration (cognitive 152) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2782— package_ai_pack.check_integration has cognitive complexity 152 (threshold 15). Drivers by points: if/else 72 (90 pts), ternaries 20 (35 pts), boolean chains 22, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 35). 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.
benchmark_on_device.main (cognitive 150) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1777— benchmark_on_device.main has cognitive complexity 150 (threshold 15). Drivers by points: if/else 65 (105 pts), boolean chains 24, ternaries 12 (13 pts), error handling 4 (5 pts), loops 2 (3 pts) (nesting depth added 43). 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.
compile_model.run_colab_compile (cognitive 132) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:945— compile_model.run_colab_compile has cognitive complexity 132 (threshold 15). Drivers by points: if/else 44 (63 pts), boolean chains 35, error handling 11 (23 pts), loops 8 (11 pts) (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extraction_stats_template.analyze_zip_archive (cognitive 127) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:604— extraction_stats_template.analyze_zip_archive has cognitive complexity 127 (threshold 15). Drivers by points: if/else 44 (77 pts), boolean chains 35, loops 13 (14 pts), error handling 1 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
telemetry.analyze_directory (cognitive 118) skills/developers/migrate-to-rust/scripts/telemetry.py:253— telemetry.analyze_directory has cognitive complexity 118 (threshold 15). Drivers by points: if/else 26 (94 pts), ternaries 10 (11 pts), loops 3 (6 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 74). 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.
manage_workload_updates.resolve_workload_and_update_names (cognitive 112) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:65— manage_workload_updates.resolve_workload_and_update_names has cognitive complexity 112 (threshold 15). Drivers by points: if/else 38 (96 pts), boolean chains 13, loops 2 (3 pts) (nesting depth added 59). 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.
dbt_translator.preprocess_metadata (cognitive 112) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1551— dbt_translator.preprocess_metadata has cognitive complexity 112 (threshold 15). Drivers by points: if/else 24 (73 pts), loops 9 (21 pts), boolean chains 15, ternaries 1 (3 pts) (nesting depth added 63). 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.
extraction_stats_template._parse_dumper_telemetry (cognitive 104) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:484— extraction_stats_template._parse_dumper_telemetry has cognitive complexity 104 (threshold 15). Drivers by points: if/else 23 (79 pts), loops 5 (12 pts), boolean chains 6, ternaries 1 (4 pts), error handling 1 (3 pts) (nesting depth added 68). 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.
compile_model.main (cognitive 102) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:1488— compile_model.main has cognitive complexity 102 (threshold 15). Drivers by points: if/else 38 (52 pts), ternaries 15 (21 pts), boolean chains 15, loops 4 (8 pts), error handling 6 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
release_radar.main (cognitive 97) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:737— release_radar.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 39 (69 pts), loops 7 (13 pts), ternaries 5 (11 pts), boolean chains 4 (nesting depth added 42). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
python_embedded_sql_migrator_template.postprocess (cognitive 96) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:913— python_embedded_sql_migrator_template.postprocess has cognitive complexity 96 (threshold 15). Drivers by points: if/else 18 (69 pts), loops 7 (19 pts), boolean chains 7, ternaries 1 (nesting depth added 63). 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.
dbt_translator.run_bulk_translation (cognitive 92) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1819— dbt_translator.run_bulk_translation has cognitive complexity 92 (threshold 15). Drivers by points: if/else 28 (69 pts), loops 8 (16 pts), boolean chains 6, ternaries 1 (nesting depth added 49). 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.
python_embedded_sql_migrator_template.safe_reinject_into_python (cognitive 88) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:490— python_embedded_sql_migrator_template.safe_reinject_into_python has cognitive complexity 88 (threshold 15). Drivers by points: if/else 28 (63 pts), ternaries 3 (11 pts), boolean chains 9, loops 2 (5 pts) (nesting depth added 46). 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.
agreement.main (cognitive 86) skills/cloud/agent-platform-autorater-customization/scripts/agreement.py:52— agreement.main has cognitive complexity 86 (threshold 15). Drivers by points: if/else 14 (41 pts), boolean chains 17, loops 8 (15 pts), ternaries 5 (13 pts) (nesting depth added 42). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
upgrade_policy.upgrade_policy (cognitive 83) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:796— upgrade_policy.upgrade_policy has cognitive complexity 83 (threshold 15). Drivers by points: if/else 25 (64 pts), loops 4 (8 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 45). 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.
validate_yaral_rule.mask_literals_and_comments (cognitive 80) skills/cloud/secops-detection-engineering/scripts/validate_yaral_rule.py:123— validate_yaral_rule.mask_literals_and_comments has cognitive complexity 80 (threshold 15). Drivers by points: if/else 16 (53 pts), loops 6 (16 pts), boolean chains 11 (nesting depth added 47). 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.
db_output_match_analyzer.analyze_output_matches (cognitive 74) skills/cloud/assuredworkloads-frameworks-navigator/scripts/db_output_match_analyzer.py:420— db_output_match_analyzer.analyze_output_matches has cognitive complexity 74 (threshold 15). Drivers by points: if/else 17 (37 pts), boolean chains 14, ternaries 3 (12 pts), loops 8 (11 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dbt_translator.discover_dbt_resources (cognitive 72) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1442— dbt_translator.discover_dbt_resources has cognitive complexity 72 (threshold 15). Drivers by points: if/else 10 (45 pts), loops 4 (16 pts), boolean chains 6, error handling 1 (4 pts), ternaries 1 (nesting depth added 50). 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.
telemetry.compute_derived_metrics (cognitive 66) skills/developers/migrate-to-rust/scripts/telemetry.py:650— telemetry.compute_derived_metrics has cognitive complexity 66 (threshold 15). Drivers by points: if/else 26 (29 pts), ternaries 10 (22 pts), boolean chains 14, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
REDACTED.hydrateDashboard (cognitive 65) REDACTED:1161— REDACTED.hydrateDashboard has cognitive complexity 65 (threshold 15). Drivers by points: if/else 31 (50 pts), ternaries 6 (9 pts), boolean chains 6 (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.
waste.compute_extraneous_spend (cognitive 64) skills/cloud/cloud-logging-finops/scripts/waste.py:157— waste.compute_extraneous_spend has cognitive complexity 64 (threshold 15). Drivers by points: if/else 23 (35 pts), boolean chains 15, loops 6 (8 pts), ternaries 5 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extraction_stats_template.format_stats_report (cognitive 62) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:1166— extraction_stats_template.format_stats_report has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 7 (24 pts), if/else 11 (23 pts), boolean chains 8, loops 3 (7 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_params.validate_create_params (cognitive 57) skills/cloud/assured-workloads-basics/scripts/validate_params.py:649— validate_params.validate_create_params has cognitive complexity 57 (threshold 15). Drivers by points: if/else 36 (48 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_params.validate_apply_update_params (cognitive 56) skills/cloud/assured-workloads-basics/scripts/validate_params.py:1285— validate_params.validate_apply_update_params has cognitive complexity 56 (threshold 15). Drivers by points: if/else 21 (41 pts), boolean chains 6, ternaries 3 (6 pts), loops 2 (3 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dbt_translator.transform_config_block (cognitive 56) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1318— dbt_translator.transform_config_block has cognitive complexity 56 (threshold 15). Drivers by points: if/else 24 (41 pts), loops 5 (10 pts), boolean chains 4, error handling 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.
upgrade_policy._clean_opt_out_structure (cognitive 53) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:521— upgrade_policy._clean_opt_out_structure has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (44 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 33). 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.
textproto_util.dict_to_widget (cognitive 50) skills/cloud/cloud-monitoring-chart-generation/scripts/textproto_util.py:136— textproto_util.dict_to_widget has cognitive complexity 50 (threshold 15). Drivers by points: if/else 21 (45 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 24). 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.
compile_check.check (cognitive 49) skills/cloud/apigee-agent-gateway-governance/scripts/compile_check.py:135— compile_check.check has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (30 pts), loops 11 (19 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.search_files (cognitive 48) skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:128— main.search_files has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (34 pts), loops 3 (7 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_yaral_rule.validate_single_rule (cognitive 47) skills/cloud/secops-detection-engineering/scripts/validate_yaral_rule.py:401— validate_yaral_rule.validate_single_rule has cognitive complexity 47 (threshold 15). Drivers by points: if/else 16 (35 pts), boolean chains 6, loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
trace_searcher.distill_trace (cognitive 46) skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:337— trace_searcher.distill_trace has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 10, error handling 2 (6 pts), loops 2 (3 pts) (nesting depth added 19). 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.
discover_metric_schema.validate_promql_against_schema (cognitive 43) skills/cloud/cloud-monitoring-alert-configuration/scripts/discover_metric_schema.py:190— discover_metric_schema.validate_promql_against_schema has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (36 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 26). 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.
dbt_translator.translate_cast_suffixes (cognitive 42) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:106— dbt_translator.translate_cast_suffixes has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (33 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.check_inputs (cognitive 42) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:545— package_ai_pack.check_inputs has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (37 pts), boolean chains 4, loops 1 (nesting depth added 19). 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.
validate_chart.validate_widget (cognitive 41) skills/cloud/cloud-monitoring-chart-generation/scripts/validate_chart.py:17— validate_chart.validate_widget has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (34 pts), boolean chains 3, error handling 1 (2 pts), loops 2 (nesting depth added 19). 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.
release_radar.resolve_catalog_matches (cognitive 41) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:368— release_radar.resolve_catalog_matches has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 5 (10 pts), boolean chains 8 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluate_control_rules.evaluate_telemetry (cognitive 40) skills/cloud/assuredworkloads-environment-assessor/scripts/evaluate_control_rules.py:305— evaluate_control_rules.evaluate_telemetry has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (22 pts), ternaries 5 (8 pts), loops 4 (6 pts), boolean chains 4 (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.
build_review_page.main (cognitive 39) skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:116— build_review_page.main has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 4 (13 pts), if/else 7 (12 pts), boolean chains 7, loops 5 (7 pts) (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.
python_embedded_sql_migrator_template.preprocess (cognitive 39) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:789— python_embedded_sql_migrator_template.preprocess has cognitive complexity 39 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 7 (14 pts), error handling 1 (4 pts), ternaries 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.locate_cpu_models (cognitive 39) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1594— package_ai_pack.locate_cpu_models has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 4 (8 pts), ternaries 4 (7 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.update_doc_values (cognitive 39) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2323— package_ai_pack.update_doc_values has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 7 (15 pts), if/else 10 (13 pts), boolean chains 6, loops 4 (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.
bq_loader_template.list_and_read_sql_files (cognitive 37) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:112— bq_loader_template.list_and_read_sql_files has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 3 (13 pts), loops 3 (10 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bq_loader_template._parse_config_yamls (cognitive 37) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:301— bq_loader_template._parse_config_yamls has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (15 pts), ternaries 4 (12 pts), boolean chains 4, error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Linter._check_security (cognitive 36) skills/cloud/api-gateway-troubleshooting/scripts/lint_openapi_for_gateway.py:458— Linter._check_security has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 4 (8 pts), boolean chains 3, ternaries 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manage_workload_updates.execute_manage_workload_updates (cognitive 36) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:406— manage_workload_updates.execute_manage_workload_updates has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19 (28 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bq_loader_template.run_loader (cognitive 36) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:1074— bq_loader_template.run_loader has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 4 (7 pts), boolean chains 6, error handling 2 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
discover_metric_schema.main (cognitive 36) skills/cloud/cloud-monitoring-alert-configuration/scripts/discover_metric_schema.py:272— discover_metric_schema.main has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 6 (12 pts), ternaries 1 (4 pts), boolean chains 3 (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.
dbt_translator.sanitize_json_extractions (cognitive 35) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:595— dbt_translator.sanitize_json_extractions has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluate_control_rules.parse_framework_org_policy_spec (cognitive 34) skills/cloud/assuredworkloads-environment-assessor/scripts/evaluate_control_rules.py:136— evaluate_control_rules.parse_framework_org_policy_spec has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 5 (11 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 19). 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.
diagnose_lib.check_port_allowed (cognitive 34) skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/diagnose_lib.py:96— diagnose_lib.check_port_allowed has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 8, error handling 2 (6 pts), loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render_agent_data.render (cognitive 33) skills/cloud/agent-platform-autorater-customization/scripts/render_agent_data.py:31— render_agent_data.render has cognitive complexity 33 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 3 (6 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 19). 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.
bq_loader_template._scan_sql_segments (cognitive 33) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:695— bq_loader_template._scan_sql_segments has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 5 (17 pts), loops 3 (7 pts), if/else 4 (6 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extraction_stats_template._read_bigquery_tables_jsonl (cognitive 33) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:306— extraction_stats_template._read_bigquery_tables_jsonl has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 9, loops 2 (3 pts), error handling 1 (2 pts), ternaries 1 (2 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.
check_quota_metrics.extract_limited_metrics (cognitive 32) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:102— check_quota_metrics.extract_limited_metrics has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 2 (8 pts), boolean chains 2 (nesting depth added 20). 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.
validate_workload_payload.load_allowed_frameworks_and_regimes (cognitive 32) skills/cloud/assuredworkloads-environment-assessor/scripts/validate_workload_payload.py:35— validate_workload_payload.load_allowed_frameworks_and_regimes has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 3 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aggregations.get_monthly_aggregations (cognitive 32) skills/cloud/cloud-logging-finops/scripts/aggregations.py:143— aggregations.get_monthly_aggregations has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 5 (9 pts), loops 5 (9 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
assemble_widget_proto.assemble_widget_textproto (cognitive 31) skills/cloud/cloud-monitoring-chart-generation/scripts/assemble_widget_proto.py:73— assemble_widget_proto.assemble_widget_textproto has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 1 (3 pts), boolean chains 2, ternaries 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dbt_translator.translate_interval_expressions (cognitive 31) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:176— dbt_translator.translate_interval_expressions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.compare_io (cognitive 31) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2196— package_ai_pack.compare_io has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 4 (7 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
REDACTED.renderDailyServiceChart (cognitive 31) REDACTED:1970— REDACTED.renderDailyServiceChart has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 10 (16 pts), if/else 8, boolean chains 6, loops 1 (nesting depth added 6). Most of this is not in the body itself: 9 of the 31 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 2065, 2057, 1990, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
REDACTED.renderSampleCard (cognitive 31) REDACTED:2491— REDACTED.renderSampleCard has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 9 (11 pts), boolean chains 9 (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.
bq_loader_template._scan_relation_views (cognitive 30) skills/cloud/bigquery-migration-data-loader/assets/bq_loader_template.py:402— bq_loader_template._scan_relation_views has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, ternaries 2 (4 pts), error handling 1 (3 pts), loops 2 (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.
validate_chart.main (cognitive 30) skills/cloud/cloud-monitoring-chart-generation/scripts/validate_chart.py:99— validate_chart.main has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 5 (9 pts), error handling 3 (5 pts), boolean chains 2 (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.
diagnose_lib.format_single_report (cognitive 30) skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/diagnose_lib.py:349— diagnose_lib.format_single_report has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 5 (9 pts), ternaries 2, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
REDACTED.selectService (cognitive 30) REDACTED:2277— REDACTED.selectService has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (11 pts), ternaries 3 (8 pts) (nesting depth added 8). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2313, 2279). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
run_metrics.collect (cognitive 29) skills/cloud/agent-platform-autorater-customization/scripts/run_metrics.py:72— run_metrics.collect has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 3 (12 pts), loops 4 (10 pts), boolean chains 5, if/else 1 (2 pts) (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.
inspect_results._case_rows (cognitive 29) skills/cloud/agent-platform-eval-flywheel/scripts/inspect_results.py:46— inspect_results._case_rows has cognitive complexity 29 (threshold 15). Drivers by points: if/else 2 (8 pts), ternaries 2 (8 pts), boolean chains 7, loops 3 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
collect_logging_data.collect_data (cognitive 29) skills/cloud/cloud-logging-finops/scripts/collect_logging_data.py:110— collect_logging_data.collect_data has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (16 pts), loops 3 (6 pts), ternaries 4, error handling 1 (2 pts), boolean chains 1 (nesting depth added 5). 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.
textproto_util.tokenize_textproto (cognitive 29) skills/cloud/cloud-monitoring-chart-generation/scripts/textproto_util.py:58— textproto_util.tokenize_textproto has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (9 pts), boolean chains 4 (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.
benchmark_on_device.parse_benchmark_log (cognitive 29) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:775— benchmark_on_device.parse_benchmark_log has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 3, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SQLExtractor.visit_Call (cognitive 28) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:217— SQLExtractor.visit_Call has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verify_claim.evaluate_check (cognitive 28) skills/cloud/cloud-logging-finops/scripts/verify_claim.py:124— verify_claim.evaluate_check has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (12 pts), boolean chains 3, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_params.validate_kms_and_resource_settings (cognitive 27) skills/cloud/assured-workloads-basics/scripts/validate_params.py:523— validate_params.validate_kms_and_resource_settings has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (22 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.
main.list_tree (cognitive 27) skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:82— main.list_tree has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (7 pts), ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
REDACTED.renderDailySeverityChart (cognitive 27) REDACTED:1750— REDACTED.renderDailySeverityChart has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, ternaries 5 (8 pts), loops 1 (nesting depth added 4). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 1837, 1829, 1762, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
check_quota_metrics.main (cognitive 26) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:294— check_quota_metrics.main has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (8 pts), loops 4, ternaries 3, error handling 1 (nesting depth added 1). 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.
upgrade_policy.main (cognitive 26) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:1167— upgrade_policy.main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 1 (4 pts), boolean chains 2, error handling 2, loops 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.
benchmark_on_device.analyze_tile_pass (cognitive 26) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:923— benchmark_on_device.analyze_tile_pass has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8, ternaries 2 (6 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.
benchmark_on_device.analyze_power_pass (cognitive 26) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1043— benchmark_on_device.analyze_power_pass has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 8, ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.verify_update (cognitive 26) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2276— package_ai_pack.verify_update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 5, ternaries 2 (3 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.
REDACTED.renderOptimizationActions (cognitive 26) REDACTED:2948— REDACTED.renderOptimizationActions has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 10, ternaries 9, if/else 7. Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2964, 2962). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
run_metrics.main (cognitive 25) skills/cloud/agent-platform-autorater-customization/scripts/run_metrics.py:109— run_metrics.main has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (8 pts), boolean chains 3, ternaries 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.
package_ai_pack.inspect_project (cognitive 25) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1205— package_ai_pack.inspect_project has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepare_dataset.convert_to_jsonl (cognitive 24) skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py:107— prepare_dataset.convert_to_jsonl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 2, boolean chains 1, loops 1, ternaries 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.
upgrade_policy.transform_preconfigured_waf_config (cognitive 24) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:723— upgrade_policy.transform_preconfigured_waf_config has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 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.
textproto_util.parse_textproto_tokens (cognitive 24) skills/cloud/cloud-monitoring-chart-generation/scripts/textproto_util.py:102— textproto_util.parse_textproto_tokens has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.read_file (cognitive 24) skills/cloud/google-cloud-filestore-nfs-browser/scripts/bridge_server/main.py:187— main.read_file has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 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.
release_radar.fetch_feed_entries (cognitive 24) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:459— release_radar.fetch_feed_entries has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, if/else 4 (8 pts), loops 2 (3 pts), error handling 1 (nesting depth added 5). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
install_and_verify.verify (cognitive 24) skills/platform-devices/litert-google-tensor/scripts/install_and_verify.py:485— install_and_verify.verify has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, boolean chains 7, ternaries 6. 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.
package_ai_pack.scan_model (cognitive 24) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:246— package_ai_pack.scan_model has cognitive complexity 24 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (8 pts), boolean chains 6, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_dataset._validate_eval_case (cognitive 23) skills/cloud/agent-platform-eval-flywheel/scripts/validate_dataset.py:223— validate_dataset._validate_eval_case has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
db_resources_loader.fetch_and_filter_db_resources (cognitive 23) skills/cloud/assuredworkloads-frameworks-navigator/scripts/db_resources_loader.py:227— db_resources_loader.fetch_and_filter_db_resources has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (5 pts), boolean chains 2 (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.
validate_promql.main (cognitive 23) skills/cloud/cloud-monitoring-promql-query/scripts/validate_promql.py:186— validate_promql.main has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (7 pts), error handling 1 (2 pts), ternaries 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.
package_ai_pack.build_update (cognitive 23) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2438— package_ai_pack.build_update has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, loops 2 (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.
build_review_page.render_trajectory (cognitive 22) skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:63— build_review_page.render_trajectory has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 7, loops 3 (6 pts), ternaries 1 (5 pts), if/else 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepare_dataset._validate_example (cognitive 22) skills/cloud/agent-platform-tuning/scripts/prepare_dataset.py:18— prepare_dataset._validate_example has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetch_terraform_template._output_files (cognitive 22) skills/cloud/application-design-center-design-deploy/scripts/fetch_terraform_template.py:236— fetch_terraform_template._output_files has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 1 (4 pts), loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
diagnose_error.diagnose_error (cognitive 22) skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:285— diagnose_error.diagnose_error has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, loops 2, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
db_output_match_analyzer._validate_cc_parameters (cognitive 22) skills/cloud/assuredworkloads-frameworks-navigator/scripts/db_output_match_analyzer.py:350— db_output_match_analyzer._validate_cc_parameters has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (6 pts), boolean chains 3, 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.
analytics.fetch_logging_api_samples (cognitive 22) skills/cloud/cloud-logging-finops/scripts/analytics.py:400— analytics.fetch_logging_api_samples has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, loops 3 (5 pts), error handling 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.
trace_searcher.search_traces (cognitive 22) skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py:437— trace_searcher.search_traces has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 6 (8 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
benchmark_on_device.markdown_table (cognitive 22) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1657— benchmark_on_device.markdown_table has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, if/else 3 (4 pts), ternaries 2, loops 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
package_ai_pack.verify_package (cognitive 22) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:985— package_ai_pack.verify_package has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, ternaries 3, loops 2, error handling 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.
package_ai_pack._mini_toml (cognitive 22) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1442— package_ai_pack._mini_toml has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (8 pts), boolean chains 2 (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.
package_ai_pack.main (cognitive 22) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:3470— package_ai_pack.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (15 pts), error handling 3 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
REDACTED.renderTrendChart (cognitive 22) REDACTED:1360— REDACTED.renderTrendChart has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (7 pts), boolean chains 5, loops 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_dataset._validate_agent_data (cognitive 21) skills/cloud/agent-platform-eval-flywheel/scripts/validate_dataset.py:161— validate_dataset._validate_agent_data has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_quota_metrics.extract_quota_metrics (cognitive 21) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:77— check_quota_metrics.extract_quota_metrics has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manage_workload_updates._apply_single_update_and_poll (cognitive 21) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:326— manage_workload_updates._apply_single_update_and_poll has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
actions.merge_actions (cognitive 21) skills/cloud/cloud-logging-finops/scripts/actions.py:313— actions.merge_actions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
billing.resolve_billing_source (cognitive 21) skills/cloud/cloud-logging-finops/scripts/billing.py:421— billing.resolve_billing_source has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 5, error handling 1 (3 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exclusion_rules.generate_exclusion_candidates (cognitive 21) skills/cloud/cloud-logging-finops/scripts/exclusion_rules.py:264— exclusion_rules.generate_exclusion_candidates has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_compiled.main (cognitive 21) skills/platform-devices/litert-google-tensor/scripts/check_compiled.py:112— check_compiled.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.detect_runtime (cognitive 21) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1506— package_ai_pack.detect_runtime has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 3 (9 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
compute_labels.compute_widget_title (cognitive 20) skills/cloud/cloud-monitoring-chart-generation/scripts/compute_labels.py:78— compute_labels.compute_widget_title has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, ternaries 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.
workload_restarts.main (cognitive 20) skills/cloud/managed-airflow-recommendations/scripts/workload_restarts.py:27— workload_restarts.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (6 pts), error handling 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_yaral_rule.extract_rules (cognitive 20) skills/cloud/secops-detection-engineering/scripts/validate_yaral_rule.py:309— validate_yaral_rule.extract_rules has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.find_packs (cognitive 20) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1252— package_ai_pack.find_packs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.read_catalog (cognitive 20) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1386— package_ai_pack.read_catalog has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, ternaries 1 (3 pts), error handling 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_quota_metrics._fetch_live_config_metrics (cognitive 19) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:188— check_quota_metrics._fetch_live_config_metrics has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 3 (4 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.
aggregations.project_month (cognitive 19) skills/cloud/cloud-logging-finops/scripts/aggregations.py:648— aggregations.project_month has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (6 pts), ternaries 2 (4 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.
validate_config.validate_plan_file (cognitive 19) skills/cloud/gke-alert-configuration/scripts/validate_config.py:233— validate_config.validate_plan_file has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts), boolean chains 2, error handling 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.
REDACTED.renderServicePies (cognitive 19) REDACTED:2128— REDACTED.renderServicePies has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 6, boolean chains 4 (nesting depth added 1). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 2138, 2160, 2204, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
evaluate_control_rules.is_location_allowed (cognitive 18) skills/cloud/assuredworkloads-environment-assessor/scripts/evaluate_control_rules.py:209— evaluate_control_rules.is_location_allowed has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 2, ternaries 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.
db_output_match_analyzer._resolve_parent_builtin_frameworks (cognitive 18) skills/cloud/assuredworkloads-frameworks-navigator/scripts/db_output_match_analyzer.py:295— db_output_match_analyzer._resolve_parent_builtin_frameworks has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aggregations._compute_sample_coverage (cognitive 18) skills/cloud/cloud-logging-finops/scripts/aggregations.py:357— aggregations._compute_sample_coverage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate_config.main (cognitive 18) skills/cloud/gke-alert-configuration/scripts/validate_config.py:383— validate_config.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (8 pts), error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quick_diagnose._apply_remediations (cognitive 18) skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/quick_diagnose.py:162— quick_diagnose._apply_remediations has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 2 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
benchmark_on_device.resolve_dispatch_lib (cognitive 18) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:646— benchmark_on_device.resolve_dispatch_lib has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3 (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.
install_and_verify.find_app_module (cognitive 18) skills/platform-devices/litert-google-tensor/scripts/install_and_verify.py:196— install_and_verify.find_app_module has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
REDACTED.renderSeverityPies (cognitive 18) REDACTED:1877— REDACTED.renderSeverityPies has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 6, ternaries 5. Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 1887, 1906, 1942, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
parse_adk_traces.main (cognitive 17) skills/cloud/agent-platform-eval-flywheel/scripts/parse_adk_traces.py:210— parse_adk_traces.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Linter.lint_file (cognitive 17) skills/cloud/api-gateway-troubleshooting/scripts/lint_openapi_for_gateway.py:354— Linter.lint_file has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
validate_params.validate_update_params (cognitive 17) skills/cloud/assured-workloads-basics/scripts/validate_params.py:1107— validate_params.validate_update_params has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 1 (2 pts), boolean chains 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.
evaluate_control_rules.get_target_asset_types (cognitive 17) skills/cloud/assuredworkloads-environment-assessor/scripts/evaluate_control_rules.py:246— evaluate_control_rules.get_target_asset_types has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (5 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.
extraction_stats_template.discover_zip_sources (cognitive 17) skills/cloud/bigquery-migration-metadata-extractor/assets/extraction_stats_template.py:151— extraction_stats_template.discover_zip_sources has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
upgrade_policy.generate_gcloud_commands (cognitive 17) skills/cloud/cloud-armor-crs-rule-upgrader/scripts/upgrade_policy.py:1059— upgrade_policy.generate_gcloud_commands has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
inventory.fetch_flow_log_configs (cognitive 17) skills/cloud/cloud-logging-finops/scripts/inventory.py:89— inventory.fetch_flow_log_configs has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (9 pts), boolean chains 4, if/else 1 (4 pts) (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
verify_claim.render (cognitive 17) skills/cloud/cloud-logging-finops/scripts/verify_claim.py:266— verify_claim.render has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 3 (6 pts), ternaries 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
release_radar.enrich_sparse_entry (cognitive 17) skills/cloud/google-cloud-release-radar/scripts/release_radar.py:545— release_radar.enrich_sparse_entry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, error handling 2, loops 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
least_privileged_role.find_least_privileged_role (cognitive 17) skills/cloud/iam-helper-for-troubleshooting/scripts/least_privileged_role.py:60— least_privileged_role.find_least_privileged_role has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4 (6 pts), boolean chains 2 (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.
environment_health.main (cognitive 17) skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:26— environment_health.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (6 pts), error handling 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.
install_and_verify.wait_for_result (cognitive 17) skills/platform-devices/litert-google-tensor/scripts/install_and_verify.py:445— install_and_verify.wait_for_result has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 1 (5 pts), loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
package_ai_pack.plugin_version (cognitive 17) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:2718— package_ai_pack.plugin_version has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (4 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.
REDACTED.renderExtraneousSpend (cognitive 17) REDACTED:2732— REDACTED.renderExtraneousSpend has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
validate_workload_payload.validate_v2_workload_payload (cognitive 16) skills/cloud/assuredworkloads-environment-assessor/scripts/validate_workload_payload.py:164— validate_workload_payload.validate_v2_workload_payload has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SQLExtractor._extract_joined_str (cognitive 16) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:314— SQLExtractor._extract_joined_str has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), ternaries 2 (4 pts), boolean chains 2, 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.
aggregations.get_mom_patterns (cognitive 16) skills/cloud/cloud-logging-finops/scripts/aggregations.py:583— aggregations.get_mom_patterns has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pricing.build_price_book (cognitive 16) skills/cloud/cloud-logging-finops/scripts/pricing.py:403— pricing.build_price_book has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (5 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.
FilestoreAuditor.audit_instance (cognitive 16) skills/cloud/google-cloud-filestore-auditing/scripts/filestore_audit.py:304— FilestoreAuditor.audit_instance has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (6 pts), if/else 4 (5 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
benchmark_on_device.versions_summary (cognitive 16) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1282— benchmark_on_device.versions_summary has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
compile_model._resolve_sdk_input (cognitive 16) skills/platform-devices/litert-google-tensor/scripts/compile_model.py:911— compile_model._resolve_sdk_input 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.
package_ai_pack.app_module_for (cognitive 16) skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1359— package_ai_pack.app_module_for has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Near-duplicate member family (4 members, 68 shared lines) · ×1
Near-duplicate member family (4 members, 68 shared lines) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:183— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:183-319 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:183-319 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:89-189 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:130-230 — These 4 members are variants of one another: a block of 68 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 34 shared lines) · ×1
Near-duplicate member family (4 members, 34 shared lines) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:27— skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:27-91 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:31-95 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:193-259 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:317-380 — These 4 members are variants of one another: a block of 34 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:76— skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:76-95 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:99-116 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:120-137 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:141-158 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:223-240 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:244-264 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:268-286 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Edited copy of a member (95 corresponding lines) · ×1
Edited copy of a member (95 corresponding lines) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:924— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:924-1018 | skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:1044-1145 — These two members are one piece of code written twice and then edited apart: 95 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 122+ corresponding lines) · ×1
Edited copies of one member (3 members, 122+ corresponding lines) skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:28— skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:28-152 | skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py:28-152 | skills/cloud/managed-airflow-recommendations/scripts/workload_memory_usage.py:28-152 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 122 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 (92 corresponding lines) · ×1
Edited copy of a member (92 corresponding lines) skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:207— skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:207-298 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:213-310 — These two members are one piece of code written twice and then edited apart: 92 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:119— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:119-179 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:119-179 — These two members are one piece of code written twice and then edited apart: 61 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 (67 corresponding lines) · ×1
Edited copy of a member (67 corresponding lines) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:107— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:107-173 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:177-253 — These two members are one piece of code written twice and then edited apart: 67 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 (115 corresponding lines) · ×1
Edited copy of a member (115 corresponding lines) skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:27— skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:27-141 | skills/cloud/managed-airflow-recommendations/scripts/workload_restarts.py:28-144 — These two members are one piece of code written twice and then edited apart: 115 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 (6 members, 16+ corresponding lines) · ×1
Edited copies of one member (6 members, 16+ corresponding lines) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:259— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:259-281 | skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:312-328 | skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:332-347 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:263-287 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:318-337 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:341-359 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/observability_scopes.py:27— skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/observability_scopes.py:27-43 | skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/observability_scopes.py:49-62 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) skills/cloud/cloud-logging-finops/scripts/monitoring.py:363— skills/cloud/cloud-logging-finops/scripts/monitoring.py:363-377 | skills/cloud/cloud-logging-finops/scripts/monitoring.py:396-406 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) skills/cloud/agent-platform-inference/scripts/gemini_openai_sdk.py:9— skills/cloud/agent-platform-inference/scripts/gemini_openai_sdk.py:9-13 | skills/cloud/agent-platform-inference/scripts/openmaas_openai_sdk.py:9-11 — These two members are one piece of code written twice and then edited apart: 3 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 (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:57— skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:57-60 | skills/cloud/agent-platform-autorater-customization/scripts/render_agent_data.py:25-28 — These two members are one piece of code written twice and then edited apart: 4 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 (115 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:358— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:358-472 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:370-484 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:358` 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 (100 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:302— skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:302-401 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:314-413 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 300 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (96 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:71— skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:71-166 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:77-172 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 300 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (79 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:220— skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:220-298 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:232-310 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 300 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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, `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py:227` calls `CredentialsMissingError` and `skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:218` 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 (76 lines × 3) skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:77— skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:77-152 | skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py:77-152 | skills/cloud/managed-airflow-recommendations/scripts/workload_memory_usage.py:77-152 — before extracting anything, compare `skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py` and `skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:77` 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 (76 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py:72— skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py:72-147 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/create_online_monitor.py:72-147 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/create_online_monitor.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (64 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:256— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:256-319 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:256-319 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:256` 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 (57–59 lines × 2) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:201— skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:201-259 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:324-380 — before extracting anything, compare `skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py` and `skills/cloud/gke-alert-configuration/scripts/validate_config.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 255 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (57 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:35— skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:35-91 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:39-95 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (56 lines × 4) skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:32— skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:32-87 | skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py:32-87 | skills/cloud/managed-airflow-recommendations/scripts/workload_memory_usage.py:32-87 | skills/cloud/managed-airflow-recommendations/scripts/workload_restarts.py:32-87 — before extracting anything, compare `skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py` and `skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:32` 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 (56 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:123— skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:123-178 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py:123-178 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (54 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:68— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:68-121 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:72-125 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (51 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:129— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:129-179 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:129-179 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (45 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:183— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:183-227 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:183-227 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:89-133 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:130-174 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:230` calls `search`, `group` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:136` 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 (40 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:124— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:124-163 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:124-163 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (38–39 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:124— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:124-162 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:193-230 — 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 (37 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:83— skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:83-119 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py:83-119 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (33 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py:151— skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py:151-183 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/create_online_monitor.py:151-183 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/create_online_monitor.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (32 lines × 2) skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:158— skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:158-189 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:199-230 — before extracting anything, compare `skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py` and `skills/cloud/gke-alert-configuration/scripts/validate_config.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 255 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (31 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:68— skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:68-98 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:68-98 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (30 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:127— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:127-156 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:131-160 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (29–30 lines × 2) skills/cloud/application-design-center-design-deploy/scripts/fetch_terraform_template.py:74— skills/cloud/application-design-center-design-deploy/scripts/fetch_terraform_template.py:74-102 | skills/cloud/application-design-center-design-deploy/scripts/fetch_terraform_template.py:145-174 — 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 `skills/cloud/application-design-center-design-deploy/scripts/fetch_terraform_template.py:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. 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 (29 lines × 2) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:90— skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:90-118 | skills/cloud/assured-workloads-basics/scripts/validate_params.py:1308-1336 — 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 (23–28 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:247— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:247-269 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:247-269 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:149-176 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:190-217 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:247` 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 (28 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:70— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:70-97 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:70-97 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (27 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py:37— skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py:37-63 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/create_online_monitor.py:37-63 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/create_online_monitor.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/create_online_monitor.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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 (25–27 lines × 2) skills/cloud/managed-airflow-recommendations/scripts/dag_parsing_stats.py:36— skills/cloud/managed-airflow-recommendations/scripts/dag_parsing_stats.py:36-62 | skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:54-78 — 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 `skills/cloud/managed-airflow-recommendations/scripts/dag_parsing_stats.py:36` 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 (21–23 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:621— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:621-643 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:673-693 — 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 `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:621` 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 (22 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:287— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:287-308 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:293-314 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 322 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also 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) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:58— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:58-78 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:58-78 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `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 (19–20 lines × 3) skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:119— skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:119-138 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py:119-138 | skills/cloud/cloud-monitoring-alert-configuration/scripts/lint_promql.py:28-46 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:61— skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:61-80 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:65-84 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:231-249 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:352-370 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:743— skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:743-766 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:2083-2101 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:2368-2389 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:743` 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–19 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:771— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:771-786 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:797-815 — 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. 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 (18 lines × 5) skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:41— skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:41-58 | skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:51-68 | skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py:51-68 | skills/cloud/managed-airflow-recommendations/scripts/workload_memory_usage.py:51-68 | skills/cloud/managed-airflow-recommendations/scripts/workload_restarts.py:51-68 — before extracting anything, compare `skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py` and `skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:41` 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 (18 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:45— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:45-62 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:46-63 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:45-62 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:46-63 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `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 (18 lines × 3) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1447— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1447-1464 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1856-1873 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:2457-2474 — 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 `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:2457` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:2475` calls `startswith` and `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1873` 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 (17 lines × 5) skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:27— skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:27-43 | skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py:28-44 | skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py:28-44 | skills/cloud/managed-airflow-recommendations/scripts/workload_memory_usage.py:28-44 | skills/cloud/managed-airflow-recommendations/scripts/workload_restarts.py:28-44 — before extracting anything, compare `skills/cloud/managed-airflow-recommendations/scripts/workload_cpu_usage.py` and `skills/cloud/managed-airflow-recommendations/scripts/workload_disk_usage.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/managed-airflow-recommendations/scripts/environment_health.py:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) skills/cloud/google-cloud-filestore-auditing/scripts/filestore_audit.py:30— skills/cloud/google-cloud-filestore-auditing/scripts/filestore_audit.py:30-46 | skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/diagnose_lib.py:22-38 | skills/cloud/google-cloud-filestore-nfs-browser/scripts/jump_host_engine.py:18-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/google-cloud-filestore-auditing/scripts/filestore_audit.py:30` 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 (15–16 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:27— skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:27-42 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py:31-46 | skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py:193-208 | skills/cloud/gke-alert-configuration/scripts/validate_config.py:317-331 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py` and `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14–16 lines × 2) skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:187— skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:187-200 | skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:151-166 — 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 `skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:187` 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–16 lines × 2) skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:318— skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:318-333 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:341-355 — 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 `skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/gather_agent_info.py:318` 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 lines × 2) skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:82— skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:82-96 | skills/cloud/api-gateway-openapi-spec-authoring/scripts/validate_apigw_openapi.py:294-308 — 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 (14 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:489— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:489-502 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:507-520 — 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 (13–14 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1910— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1910-1923 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1969-1981 — 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 `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1910` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:80— skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:80-92 | skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py:82-94 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_log_scope_table_names.py:80-92 | skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/list_trace_scope_table_names.py:82-94 — before extracting anything, compare `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py` and `skills/cloud/agent-platform-alert-configuration/scripts/list_trace_scope_table_names.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/agent-platform-alert-configuration/scripts/list_log_scope_table_names.py:80` 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. 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 (11–12 lines × 4) skills/cloud/cloud-trace-querying/scripts/fetch_entire_trace/src/main.py:46— skills/cloud/cloud-trace-querying/scripts/fetch_entire_trace/src/main.py:46-56 | skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/main.py:62-73 | skills/cloud/cloud-trace-querying/scripts/fetch_trace_span/src/main.py:68-78 | skills/cloud/cloud-trace-querying/scripts/search_traces/src/main.py:58-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/main.py:62` 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–12 lines × 2) skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:83— skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:83-94 | skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:109-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:107` calls `isinstance`, `get` and `skills/cloud/api-gateway-backend-security-and-rate-limiting/scripts/check_quota_metrics.py:82` 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–11 lines × 2) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:314— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:314-324 | skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:334-343 — 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 `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:314` 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 (8–11 lines × 2) skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:149— skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:149-159 | skills/cloud/assured-workloads-basics/scripts/validate_params.py:422-429 — 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 `skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:478— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:478-488 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:494-504 — 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 × 3) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:478— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:478-487 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:494-503 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:512-521 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:488` calls `group`, `upper` and `skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:522` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) skills/platform-devices/litert-google-tensor/scripts/install_and_verify.py:641— skills/platform-devices/litert-google-tensor/scripts/install_and_verify.py:641-649 | skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:3517-3526 — 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 (8–9 lines × 6) skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:88— skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:88-95 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:109-116 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:130-137 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:233-240 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:256-264 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:279-286 — all 6 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 `skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 3) skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:259— skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:259-266 | skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:312-320 | skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:332-340 — 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 `skills/cloud/agent-platform-alert-configuration/scripts/gather_agent_info.py:259` 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 (8–9 lines × 2) skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:974— skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:974-981 | skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:1176-1184 — 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 (8 lines × 3) skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:258— skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:258-265 | skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:189-196 | skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py:154-162 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 2) skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:67— skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:67-72 | skills/cloud/agent-platform-skill-registry/scripts/skill_registry_ops.py:214-219 — 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 × 4) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:227— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:227-231 | skills/platform-devices/litert-google-tensor/scripts/check_compiled.py:69-73 | skills/platform-devices/litert-google-tensor/scripts/compile_model.py:368-372 | skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:306-310 — 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 3) skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:515— skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:515-519 | skills/platform-devices/litert-google-tensor/scripts/compile_model.py:376-380 | skills/platform-devices/litert-google-tensor/scripts/package_ai_pack.py:1164-1168 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
No structured logging — No logging call was found in the 5 JVM, Python, JavaScript/TypeScript production file(s) this check read across 3 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap skills/cloud/api-gateway-mcp-server/scripts/validate_mcp_openapi.py:163— `validate_mcp_spec` is public, takes a document from its caller (line 170) and hands it to `_type_list_schemas`, which calls itself at line 163 (`_type_list_schemas`) with a piece of `node` (and at line 166) — and nowhere in `_type_list_schemas` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_type_list_schemas` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Duplicated predicate skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:199— `DISPATCH_OP_MARKER in data and BUILD_STAMP_KEY in data` appears character-identically in 2 files — skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py, skills/platform-devices/litert-google-tensor/scripts/compile_model.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:379— `args.metrics_file == "-" or not args.metrics_file` appears character-identically in 2 files — skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/google-cloud-filestore-auditing/scripts/filestore_audit.py:31— `attr_path or os.path.join( os.path.dirname(os.path.abspath(__file__)), "..", "references", "attribution.md", )` appears character-identically in 3 files — skills/cloud/google-cloud-filestore-auditing/scripts/filestore_audit.py, skills/cloud/google-cloud-filestore-log-troubleshooting/scripts/diagnose_lib.py, skills/cloud/google-cloud-filestore-nfs-browser/scripts/jump_host_engine.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:139— `autocorr_1w > 0.75 and variance_ratio <= 2.0` appears character-identically in 2 files — skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py:59— `has_telemetry_toggle and has_capture_toggle` appears character-identically in 2 files — skills/cloud/agent-platform-alert-configuration/scripts/check_telemetry.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/check_telemetry.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/assured-workloads-basics/scripts/diagnose_error.py:244— `hasattr(service, "_http") and hasattr( googleapiclient.http, "set_user_agent" )` appears character-identically in 2 files — skills/cloud/assured-workloads-basics/scripts/diagnose_error.py, skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:118— `inferred_org and inferred_loc and inferred_wid` appears character-identically in 2 files — skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py, skills/cloud/assured-workloads-basics/scripts/validate_params.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py:58— `isinstance(d, dict) and d.get(n) is not None` appears character-identically in 2 files — skills/cloud/agent-platform-autorater-customization/scripts/build_review_page.py, skills/cloud/agent-platform-autorater-customization/scripts/render_agent_data.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py:338— `isinstance(node, ast.Constant) and isinstance(node.value, str)` appears character-identically in 2 files — skills/cloud/bigquery-migration-sql-translator/assets/python_embedded_sql_migrator_template.py, skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py:201— `len(data) >= 8 and data[4:8] == TFLITE_FILE_IDENTIFIER` appears character-identically in 3 files — skills/platform-devices/litert-google-tensor/scripts/benchmark_on_device.py, skills/platform-devices/litert-google-tensor/scripts/check_compiled.py, skills/platform-devices/litert-google-tensor/scripts/compile_model.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py:61— `len(matches) > 1 and signal_type != "unknown"` appears character-identically in 4 files — skills/cloud/agent-platform-alert-configuration/scripts/scan_duplicates.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/scan_duplicates.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py, skills/cloud/gke-alert-configuration/scripts/validate_config.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:221— `len(raw_tokens) == 1 and raw_tokens[0].upper() == "ALL"` appears character-identically in 2 files — skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py, skills/cloud/assured-workloads-basics/scripts/validate_params.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/log_fetcher.py:118— `min_start is None or start_dt < min_start` appears character-identically in 2 files — skills/cloud/cloud-trace-querying/scripts/fetch_related_logs/src/log_fetcher.py, skills/cloud/cloud-trace-querying/scripts/search_traces/src/trace_searcher.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:370— `not args.metrics_file and sys.stdin.isatty()` appears character-identically in 2 files — skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:349— `not args.project_id or not args.reasoning_engine_id` appears character-identically in 2 files — skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py:179— `not organization or not organization.strip()` appears character-identically in 3 files — skills/cloud/assured-workloads-basics/scripts/manage_workload_updates.py, skills/cloud/assured-workloads-basics/scripts/restrict_allowed_resources.py, skills/cloud/assured-workloads-basics/scripts/validate_params.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/cloud-logging-finops/scripts/analytics.py:462— `now or datetime.datetime.now(datetime.timezone.utc)` appears character-identically in 3 files — skills/cloud/cloud-logging-finops/scripts/analytics.py, skills/cloud/cloud-logging-finops/scripts/billing.py, skills/cloud/pathways-workload/scripts/debug_workload.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py:267— `res_pat in res_lower or disp_pat in disp_lower` appears character-identically in 4 files — skills/cloud/agent-platform-alert-configuration/scripts/config_utils.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/config_utils.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/kubernetes/validate_config.py, skills/cloud/gke-alert-configuration/scripts/validate_config.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-eval-flywheel/scripts/compare_results.py:28— `s in result.get("summary_metrics") or []` appears character-identically in 2 files — skills/cloud/agent-platform-eval-flywheel/scripts/compare_results.py, skills/cloud/agent-platform-eval-flywheel/scripts/inspect_results.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-eval-flywheel/scripts/compare_results.py:32— `s.get("mean_score") or s.get("meanScore")` appears character-identically in 2 files — skills/cloud/agent-platform-eval-flywheel/scripts/compare_results.py, skills/cloud/agent-platform-eval-flywheel/scripts/inspect_results.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-eval-flywheel/scripts/compare_results.py:29— `s.get("metric_name") or s.get("metricName")` appears character-identically in 2 files — skills/cloud/agent-platform-eval-flywheel/scripts/compare_results.py, skills/cloud/agent-platform-eval-flywheel/scripts/inspect_results.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py:109— `stddev_last > 0.0001 and stddev_prev > 0.0001` appears character-identically in 2 files — skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic.py, skills/cloud/cloud-monitoring-alert-configuration/scripts/agent_platform/analyze_traffic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Hand-rolled JSON/XML parsing via regex skills/cloud/google-cloud-release-radar/scripts/release_radar.py:185— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/cloud/google-cloud-release-radar/scripts/release_radar.py:193— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/cloud/google-cloud-release-radar/scripts/release_radar.py:205— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/cloud/google-cloud-release-radar/scripts/release_radar.py:207— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/cloud/google-cloud-release-radar/scripts/release_radar.py:581— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex skills/cloud/dbt-sf-to-bq-translator/scripts/dbt_translator.py:865— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
README/code drift plugins/cloud/google-cloud-developer/.antigravity-plugin/README.md:35— plugins/cloud/google-cloud-developer/.antigravity-plugin/README.md links to `./rules/google-cloud-discovery.md`, but `plugins/cloud/google-cloud-developer/.antigravity-plugin/rules/google-cloud-discovery.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 plugins/cloud/google-cloud-developer/.codex-plugin/README.md:77— plugins/cloud/google-cloud-developer/.codex-plugin/README.md links to `./rules/google-cloud-discovery.md`, but `plugins/cloud/google-cloud-developer/.codex-plugin/rules/google-cloud-discovery.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.
Silent fallback default on parse failure skills/cloud/api-gateway-troubleshooting/scripts/lint_openapi_for_gateway.py:259— `_host` returns `''` when `ValueError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure skills/cloud/iam-helper-for-troubleshooting/scripts/troubleshooting_error_id.py:31— `extract_project_id` returns `''` when `(binascii.Error, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — `(repository root)` (35058 LoC, 102 module-visible types across 35 directories) overshoots its size bounds. 1 of 11 build unit(s) (Python, checkout, npm) overshoot their size bounds, lowering Project Cohesion to 8.2/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
No seccomp profile REDACTED:6— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P1 · CI/CD gates· CI build step not evidenced · ×1
CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
No SAST — No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation skills/platform-devices/litert-google-tensor/assets/templates/google_tensor_runtime/build.gradle.kts:32— `skills/platform-devices/litert-google-tensor/assets/templates/google_tensor_runtime/build.gradle.kts` 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`.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `skills/platform-devices/litert-google-tensor/assets/templates/TensorModelLoader.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
Run 01a1e735-f9b7-754b-a474-a2a1cd6040db · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 5 · Warnings: 545 · Recommendations: 56 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 01:53 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.