blockly — Watchdog Audit

Executive summary

The platform currently operates at a weak health standing of 44%, presenting a workable system that carries significant compliance and operational risk. While the codebase is mature and logically sound, its weakest areas expose the business to avoidable liability, particularly regarding accessibility and production readiness. This assessment is based on a comprehensive analysis of the entire codebase, though specific domain modeling and event-driven patterns were not measured, meaning the picture is partial.

The asset is substantial, comprising over 130,000 lines of production code and nearly 120,000 lines of frontend code. Rebuilding this logic from scratch would require approximately 1.3 person-years and cost around €190,000, highlighting the high value tied up in the current implementation. The code is largely custom logic with minimal boilerplate, indicating a tailored solution that is expensive to replace but valuable to maintain. The primary risk is not structural collapse, but rather regulatory exposure and user exclusion due to poor accessibility standards.

The most critical theme is accessibility compliance, which scored only 40%. For a system of this size, failing to meet basic web standards is not just a technical debt issue but a direct business risk involving potential legal liability and loss of market reach. The second theme is production readiness, which also scored low at 40%. This suggests that while the code works, it lacks the observability and error-handling depth required for safe, independent operation by new teams or during outages. Errors are often silently discarded, making reproduction difficult and increasing mean-time-to-resolution.

Genuinely good news is that the core code health, architecture, and maturity scores are all above 60%, indicating a stable, maintainable foundation. The team has built a solid, logical structure that is not prone to immediate collapse. The focus should be on remediating accessibility first, as this offers the highest leverage. Declaring language attributes, proper landmarks, and fixing heading structures are low-effort changes that immediately reduce legal risk. Following this, implementing basic error logging will improve operational reliability without requiring a major refactor.

Code Health 65% Adequate Architecture 63% Adequate · gated by R9 Maturity 68% Adequate · gated by M2 Readiness 40% Weak · gated by R8, P2, P3 Security 41% Weak · gated by D29, D30, D36, D43 Accessibility 40% Weak · gated by AC3 Performance 60% Adequate

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Accessibility 40% · 46% weightReadiness 40% · 25% weightSecurity 41% · 14% weightPerformance 60% · 8% weightArchitecture 63% · 4% weightCode Health 65% · 2% weightMaturity 68% · 1% weight

No single dominant problem — the weakest areas are close, so progress on any of them moves the score.

Code composition — where the lines go

Tests 100%

New since the last scan (27+)

27 finding(s) are new versus the previous scan (2026-09-16) — surfaced by this scheduled scan itself, no pull request required.

D1 · plugin.createPlugin (cyclomatic 21) packages/plugins/dev-create/bin/plugin.js
D2 · plugin.createPlugin (cognitive 19) packages/plugins/dev-create/bin/plugin.js
D4 · Duplicated block (7 lines × 2) packages/blockly/scripts/i18n/js_to_json.py
D5 · Off the main sequence: blockly
D6 · Low cohesion: WorkspaceComment (LCOM4 6) packages/blockly/core/comments/workspace_comment.ts
D6 · Low cohesion: Block (LCOM4 5) packages/blockly/core/block.ts
D6 · Low cohesion: ConstantProvider (LCOM4 5) packages/blockly/core/renderers/zelos/constants.ts
D6 · Low cohesion: CommentEditor (LCOM4 4) packages/blockly/core/comments/comment_editor.ts
D6 · Low cohesion: BlockSuggestor (LCOM4 4) packages/plugins/suggested-blocks/src/index.js
D6 · Low cohesion: TypedVariableModal (LCOM4 4) packages/plugins/typed-variable-modal/src/TypedVariableModal.js
D15 · Repeated repair: packages/blockly/core/trashcan.ts packages/blockly/core/trashcan.ts
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D34 · Orphaned knowledge packages/blockly/core/renderers/common/info.ts
P2 · No structured logging
PF3 · Sync-over-async blocking packages/blockly/scripts/langfiles.mjs
PF3 · Sync-over-async blocking packages/blockly/tests/generators/test_generators.mjs
PF3 · Sync-over-async blocking packages/blockly/tests/generators/webdriver.js
PF3 · Sync-over-async blocking packages/plugins/migration/bin/rename.js

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €64,000–€320,000

Cost to rebuild	€64,000–€320,000 (0.6–2.0 person-years (1,062–3,368 h), ~1–3 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.7× (at 44% quality) — the last 20% of quality is most of the work
Size & shape	Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~1.3 person-years of build effort (about ~€190,000 to rebuild). Its weakest lens is Accessibility at 40% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED.

+2.3 pts · Low effort · Malicious Dependencies

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

+3.7 pts · Medium effort · Page structure

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.

+3.7 pts · Medium effort · A11y enforcement

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk

This is a Large asset (~1.3 person-years to rebuild), and its weakest lens is Accessibility at 40%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Large, ~1.3 person-years rebuild (132,605 LoC) · weakest lens: Accessibility 40%

→ Direct remediation budget at Accessibility first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

523 modules, 1065 dependencies. 3 dependency cycles across 57 modules, marked above the diagonal.

Showing the 40 most-connected modules; 483 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	2 theme	3 utils.coordinate	4 utils.size	5 utils.toolbox	6 comments.comment_view	7 comments.workspace_comment	8 connection	9 events.events_abstract	10 interfaces.i_draggable	11 interfaces.i_focusable_tree	12 metrics_manager	13 serialization.procedures	14 utils.rect	15 inputs.input	16 interfaces.i_focusable_node	18 trashcan	19 comments.rendered_workspace_comment	20 field	21 rendered_connection	22 block_svg	23 renderers.common.constants	24 renderers.measurables.base	25 renderers.measurables.row	26 renderers.common.info	27 renderers.common.renderer	28 workspace_svg	29 blockly_options	31 interfaces.i_flyout	32 interfaces.i_toolbox	33 gesture	34 options	36 workspace	37 interfaces.i_variable_model	38 block
1 interfaces.i_navigation_policy
2 theme
3 utils.coordinate
4 utils.size
5 utils.toolbox
6 comments.comment_view		1	1																							1
7 comments.workspace_comment		1	1																													1
8 connection																																		1
9 events.events_abstract																																1
10 interfaces.i_draggable		2
11 interfaces.i_focusable_tree															1
12 metrics_manager			1	1																						1
13 serialization.procedures																																3
14 utils.rect		1
15 inputs.input							1											1																1
16 interfaces.i_focusable_node										1
17 interfaces.i_procedure_model												1
18 trashcan				1				1	1		1	1														1
19 comments.rendered_workspace_comment		1	1		1	1			1	1			1		1											1
20 field		1	1							1			1	1	1																			1
21 rendered_connection		1					1			1					1					1
22 block_svg	1	1					1		3	1			1	1	1				1							1								1
23 renderers.common.constants	2																		1
24 renderers.measurables.base																					1
25 renderers.measurables.row																					1
26 renderers.common.info														1					1	1	1	1	1		1
27 renderers.common.renderer	2																		1	1	1			1
28 workspace_svg	1	1	1			1				1			1		1	1	1			1					1						1	1		1
29 blockly_options																										1
30 bubbles.bubble		1	1							1	1		1		1											1
31 interfaces.i_flyout																										1
32 interfaces.i_toolbox				1																						1
33 gesture		1							1								1	1		1						1		1
34 options	1			1																							4
35 toolbox.toolbox				3					1	1					1											1		1	1
36 workspace				1		1		1																							1		2	1
37 interfaces.i_variable_model																																2
38 block		1	1				1							1				1														1	2
39 packages.blockly.core		2	3	1		2	2	1			2		3	1	2	1	1	3	1	6						19	1		1	1	3	6	2	8
40 icons.icon		1	1							1																								1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 65% · Adequate ·

The Good

D3 · TypeScript God Classes 8.3 D4 · TypeScript Code Duplication 10.0 D17 · TypeScript Explicit Debt 9.8 R10 · React / TS Code Duplication 9.0 R2 · React / TS Cyclomatic Complexity 8.0 X25 · Repo Inert configuration knob 10.0 X29 · Repo Per-element action decided by a fixed element 10.0

The Bad

D1 · TypeScript Cyclomatic Complexity 6.4 D2 · TypeScript Cognitive Complexity 6.0 R1 · React / TS Type Safety 7.0 R7 · React / TS Dead Code 6.0

The Ugly

R3 · React / TS Large Files 4.4

At a glance — Architecture · 63% · Adequate · gated by R9 ·

The Good

D5 · TypeScript Coupling 9.8 D6 · TypeScript Cohesion (LCOM4) 9.5 D26 · TypeScript Project Cohesion 9.6 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0

The Ugly

R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 68% · Adequate · gated by M2 ·

The Good

D15 · TypeScript Churn × Complexity Hotspots 10.0 D16 · TypeScript Bus Factor 9.3 D19 · TypeScript Documentation Quality 9.2 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 7.2 M1 · Repo Documentation (README) 8.6 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Ugly

D20 · TypeScript ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 40% · Weak · gated by R8, P2, P3 ·

The Good

D9 · TypeScript Test Distribution 10.0 D13 · TypeScript REDACTED Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 7.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 8.2 R5 · React / TS Dependency Freshness 7.9 R6 · React / TS Tooling 10.0

The Ugly

P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 1.0

At a glance — Security · 41% · Weak · gated by D29, D30, D36, D43 ·

The Good

D28 · TypeScript Secrets (history) 9.0 D44 · TypeScript Platform End-of-Life 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Ugly

D29 · TypeScript Static Analysis (SAST) 2.8 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 2.5 D43 · TypeScript Malicious Dependencies 0.0

At a glance — Accessibility · 40% · Weak · gated by AC3 ·

The Bad

AC6 · Repo Visual & motion safety 6.3

The Ugly

AC3 · Repo Page structure 2.7 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2021 — Injection	35	High / Critical
A06:2021 — Vulnerable & Outdated Components	22	High / Critical
A02:2021 — Cryptographic Failures	2	High / Critical

Roadmap

First, correct the page structure by adding essential semantic landmarks and metadata to ensure proper document hierarchy. Second, enforce accessibility standards by integrating linting and automated testing into the development workflow and CI pipeline. Third, implement detailed diagnostic logging to capture error traces, enabling users to report issues effectively and developers to reproduce them. Fourth, add static analysis to the CI process to prevent security regressions from being merged. Finally, clean up dependencies by removing unused packages and explicitly declaring all imports to maintain a lean and transparent codebase.

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

Do this	Helps	Effort	Dimension
Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED.	+2.3 pts	Low	Malicious Dependencies
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.	+3.7 pts	Medium	Page structure
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.	+3.7 pts	Medium	A11y enforcement
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.	+3.5 pts	Medium	Observability
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.	+3.5 pts	Medium	Security & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+3.5 pts	Medium	Dependency Hygiene
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.	+3.4 pts	Medium	Visual & motion safety
Bump outdated dependencies to current versions to limit upgrade debt.	+2.8 pts	Medium	Dependency Freshness

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.5	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.5	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): High: REDACTED
packages/blockly/core/dragging/block_drag_strategy.ts	5.5	Mixed	Cyclomatic Complexity: BlockDragStrategy.updateConnectionPreview (cyclomatic 17)
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
packages/blockly/core/xml.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/generators/dart/lists.ts	6.0	Mixed	Explicit Debt: XxxComment
packages/blockly/core/utils/parsing.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/core/workspace_svg.ts	6.0	Mixed	Explicit Debt: TodoComment repeated across 12 files
packages/blockly/core/block.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/core/field.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/generators/javascript/javascript_generator.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/generators/php/php_generator.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/core/block_svg.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/blockly/core/gesture.ts	6.0	Mixed	Explicit Debt: TodoComment

How the grades work

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

Critical — 66

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 — 472

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 — 43

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

Could not be resolved — 35

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

Watchdog 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. 50 of 54 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 54 dimensions across the health lenses

D1D2D3D4D5D6D9D13D14D15D16D17D19D20D21D26D28D29D30D34D35D36D43D44AC3AC6AC7AX10AX3AX4M1M2M3M4P1P10P2P3P4P6PF3R1R10R2R3R4R5R6R7R8R9X24X25X29

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, 559 of 581 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0f9ba-8c45-76d8-a7ce-c3848f36401d.

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

Run transparency — what happened this run

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

D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the JavaScript/TypeScript suite (mocha via `npm ci --ignore-scripts` in packages/blockly/; mocha via `npm ci --ignore-scripts` in packages/plugins/migration/ (60 tests)) did not finish re-running within its budget: too large to re-run within its budget.
D12 Dependency Hygiene — not measured this run — Watchdog 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 — 1 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D22 Internal API Consistency — not measured this run — Watchdog 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. A language sidecar this run needed FAILED, so the code model the non-MSBuild public-API collector reads was never built — this is a DEGRADED run, not a settled gap, and the surface may well be collectable on a re-run: The PHP sidecar exited 0 and produced a model, but its own source census reports it opened ZERO PHP files — while the engine's presence probe found PHP source in this tree. The model is therefore empty for a reason on OUR side, not the repository's, and PHP is recorded as unread rather than as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `packages/blockly/core/config.ts` 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.
AX1 Captive dependencies — not measured this run — Watchdog 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/blockly/core/css.ts, whose lifetimes are not modelled 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.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog 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 finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 228 further occurrence(s) are not listed individually; the score already reflects all 268.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 53 further occurrence(s) are not listed individually; the score already reflects all 93.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 48 further occurrence(s) are not listed individually; the score already reflects all 88.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin and Scala source only, and no C# was loaded, no Java, Kotlin or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java and Rust source only, and no C# was loaded and no Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala source only, and no C# was loaded and no Scala was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala source only, and no C# was loaded and no Scala was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 54 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.4 / 10Adequate✓ Tool-verified

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

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

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

79 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.Root at 67. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FieldBitmap.onPixelGridKeyDown at 20 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/plugins/field-bitmap/src/field-bitmap.ts (FieldBitmap.onPixelGridKeyDown at 20), packages/plugins/field-grid-dropdown/src/grid.ts (Grid.onKeyDown at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

lists.lists_setIndex (cyclomatic 21) · ×3packages/blockly/generators/dart/lists.ts:280

loops.controls_for (cyclomatic 16) · ×3packages/blockly/generators/dart/loops.ts:79

lists.lists_getIndex (cyclomatic 25) · ×2packages/blockly/generators/javascript/lists.ts:98

math.math_single (cyclomatic 25) · ×2packages/blockly/generators/javascript/math.ts:55

math.math_on_list (cyclomatic 17) · ×2packages/blockly/generators/javascript/math.ts:235

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

What to do

Resolve the 3 lists.lists_setIndex (cyclomatic 21) finding(s) in Cyclomatic Complexity — start with lists.ts (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 loops.controls_for (cyclomatic 16) finding(s) in Cyclomatic Complexity — start with loops.ts (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 lists.lists_getIndex (cyclomatic 25) finding(s) in Cyclomatic Complexity — start with lists.ts (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity6.0 / 10Adequate✓ Tool-verified

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

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

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

101 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.Root at 99.

lists.lists_setIndex (cognitive 21) · ×3packages/blockly/generators/dart/lists.ts:280

loops.controls_for (cognitive 18) · ×3packages/blockly/generators/dart/loops.ts:79

RenderInfo.addElemSpacing_ (cognitive 16) · ×2packages/blockly/core/renderers/geras/info.ts:103

index.Root (cognitive 99)packages/docs/src/theme/Root/index.js:14

parsing.tokenizeInterpolationInternal (cognitive 77)packages/blockly/core/utils/parsing.ts:24

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

What to do

Resolve the 3 lists.lists_setIndex (cognitive 21) finding(s) in Cognitive Complexity — start with lists.ts (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 loops.controls_for (cognitive 18) finding(s) in Cognitive Complexity — start with loops.ts (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 RenderInfo.addElemSpacing_ (cognitive 16) finding(s) in Cognitive Complexity — start with info.ts (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.3 / 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.

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

58 god class(es) detected.

TooManyMethods: WorkspaceSvg · ×22packages/blockly/core/workspace_svg.ts:98

FileTooLong: core/workspace_svg.ts · ×18packages/blockly/core/workspace_svg.ts

ClassTooLong: WorkspaceSvg · ×10packages/blockly/core/workspace_svg.ts:98

FunctionTooLong: index.Root · ×8packages/docs/src/theme/Root/index.js:14

What to do

Resolve the 22 TooManyMethods finding(s) in God Classes — start with workspace_svg.ts, block.ts, block_svg.ts. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 18 FileTooLong finding(s) in God Classes — start with workspace_svg.ts, shortcut_items.ts, block.ts. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 10 ClassTooLong finding(s) in God Classes — start with workspace_svg.ts, block_drag_strategy.ts, field.ts. — One of this dimension's main actionable groups (10 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 duplicated block group(s) detected. Measured on part of this repository only: .ts (99% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (7 lines × 2)packages/blockly/scripts/i18n/js_to_json.py:117

What to do

Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with js_to_json.py. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

52 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 24 of the 52 (the rest declare no modelled class or interface, export only macros, or have no source directory of their own).

Off the main sequence: blockly

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.5 / 10Stronggated by 6 serious findings✓ Tool-verified

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

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

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

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

6 of 152 classes have LCOM4 above 3.

Low cohesion: WorkspaceComment (LCOM4 6) · ×6packages/blockly/core/comments/workspace_comment.ts:17

What to do

Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with workspace_comment.ts, block.ts, constants.ts. — One of this dimension's main actionable groups (6 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 1 test function(s) across 1 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

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

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 25 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 1 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (24 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 1 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

Top hotspots: packages/blockly/core/dragging/block_drag_strategy.ts (11×17=187) Repeated repair below the complexity floor: packages/blockly/core/trashcan.ts (3 of 5 changes were fixes)

Hotspot: packages/blockly/core/dragging/block_drag_strategy.tspackages/blockly/core/dragging/block_drag_strategy.ts:691

Repeated repair: packages/blockly/core/trashcan.tspackages/blockly/core/trashcan.ts:609

What to do

Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with block_drag_strategy.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with trashcan.ts. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D16 · Bus Factor9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/blockly/core/variables.ts. Counted over 341 of the 563 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×2

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D17 · Explicit Debt9.8 / 10Stronggated by 67 serious findings✓ Tool-verified

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

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

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

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

TodoComment · ×64packages/blockly/blocks/procedures.ts:896

TodoComment repeated across 12 filespackages/blockly/core/workspace_svg.ts:319

TodoComment repeated across 13 filespackages/blockly/generators/dart/text.ts:139

XxxCommentpackages/blockly/generators/dart/lists.ts:522

What to do

Resolve the 64 TodoComment finding(s) in Explicit Debt — start with index.ts (16), procedures.ts (3), events_comment_move.ts (3). — One of this dimension's main actionable groups (64 warning-level).
Resolve the 1 TodoComment repeated across 12 files finding(s) in Explicit Debt — start with workspace_svg.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TodoComment repeated across 13 files finding(s) in Explicit Debt — start with text.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README is a clear overview of Blockly (a client-side visual editor for web apps) with links to live demos, developer docs, the create-package tool, and an extensive Getting Started guide. It also documents the packages/docs/ directory as its own README, covering installation, local development, build, test, formatting, API reference generation, and a detailed plugin-reference section (TypeDoc-generated docs). The architecture/design docs are separate markdown files at the top of the list. All visible content is present in the outline; no missing sections. The repository's READMEs are clear and complete for the packages/plugins directories: each one documents its own directory (e.g. @blockly/dev-tools, @blockly/disable-top-blocks) with installation commands, usage examples, a playground section showing how to create and control the tool, API docs, license, and an outline of all the sections present in the document. The READMEs document the packages/plugins directories (field-multilineinput, field-slider, fixed-edges, migration) rather than the repository root, so each is judged only against its own directory's job. The four standard sections are present in every file: overview, installation with Yarn/npm commands, usage example showing how to register a FieldMultilineInput/FieldSlider and define blocks, and license. All files also carry an architecture/design doc (the first line of the body is a link to the repository root's architecture docs). The visible content is clear and complete for its scope.

Documentation: no architecture or design documentation · ×2packages/plugins/field-colour-hsv-sliders/README.md

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

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

1 of 54 build units (npm) flagged as possibly oversized/incoherent.

Split packages/blockly

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)2.8 / 10Weak✓ Tool-verified

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

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

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

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

35 finding(s): 0 critical, 34 high, 1 medium, 0 low. 27 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `packages/blockly/core/config.ts` (line 68), `packages/blockly/demos/blockfactory/index.html` (line 338) — 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

What to do

Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 27 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (27 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

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

21 finding(s): 0 critical, 16 high, 3 medium, 2 low.

REDACTED

What to do

Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness7.2 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

95 of 341 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/blockly/core/scrollbar.ts. Counted over 341 of the 563 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2packages/blockly/core/scrollbar.ts

Further orphaned files (smaller)

What to do

Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with scrollbar.ts, info.ts. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: field_checkbox.ts↔field_textinput.ts 60%; field_label.ts↔field_textinput.ts 55%; block_flyout_inflater.ts↔flyout_base.ts 50%

Change coupling: field_checkbox.ts ↔ field_textinput.ts · ×4packages/blockly/core/field_checkbox.ts

What to do

Resolve the 4 Change coupling finding(s) in Change Coupling — start with field_checkbox.ts, field_label.ts, block_flyout_inflater.ts. — One of this dimension's main actionable groups (4 warning-level).

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

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D43 · Malicious Dependencies0.0 / 10Critical✓ Tool-verified

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. Scored 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. SCORED, not informational.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

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

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

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC3 · Page structure2.7 / 10Weak✓ Tool-verified

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.

The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — packages/plugins/sample-app-ts/src/index.html:2, packages/plugins/sample-app/src/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — packages/plugins/sample-app-ts/src/index.html:2, packages/plugins/sample-app/src/index.html: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.

Do you agree with this assessment?

AC6 · Visual & motion safety6.3 / 10Adequate✓ Tool-verified

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.

`button.primary` sets color: #fff on background-color: #dd4b39 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/blockly/demos/code/style.css:30

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.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 3 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

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

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

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

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M1 · Documentation (README)8.6 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 3 of 53 project(s) that lack one — worth up to 0.1 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language 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 · Observability0.0 / 10Critical✓ Tool-verified

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

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

No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

What to do

Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.

Do you agree with this assessment?

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 23794 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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 the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

`buildLangfileShims` is async and calls mkdirSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/blockly/scripts/langfiles.mjs:63
`generators` is async and calls mkdirSync, spawnSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/blockly/tests/generators/test_generators.mjs:78
`runLangGeneratorInBrowser` is async and calls writeFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/blockly/tests/generators/webdriver.js:26
`rename` is async and calls statSync, readFileSync, writeFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/plugins/migration/bin/rename.js:35

What to do

TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.

Do you agree with this assessment?

R1 · Type Safety7.0 / 10Adequate✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

570 typed · 248 plain JS — the untyped files are packages/blockly/scripts/build_constants.mjs, packages/blockly/scripts/clean.mjs, packages/blockly/scripts/helpers.js, packages/blockly/scripts/langfiles.mjs, packages/blockly/scripts/lib/exec.mjs, packages/blockly/scripts/lib/fs_utils.mjs (+242 more).

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication9.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

56 duplicated blocks under packages/blockly/generators/ have copies in at least two of the sibling directories dart, javascript, lua, php, python — 52 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 56 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 56 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 56 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/blockly/generators/dart/lists.ts:50
21 duplicated blocks under packages/plugins/ have copies in at least two of the sibling directories content-highlight, dev-tools, field-angle, field-bitmap, field-colour, field-colour-hsv-sliders (+11 more sibling(s) not listed) — 12 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/plugins/dev-tools/src/toolboxCategories.js:1
18 duplicated blocks under packages/blockly/core/renderers/ have copies in at least two of the sibling directories common, geras, thrasos, zelos — 17 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/blockly/core/renderers/geras/info.ts:111
15 duplicated blocks under packages/ have copies in at least two of the sibling directories blockly, plugins — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/blockly/core/field_input.ts:303
5 duplicated blocks under packages/blockly/core/ have copies in at least two of the sibling directories bubbles, comments, dragging, renderers, serialization, utils — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/blockly/core/bubbles/textinput_bubble.ts:127
packages/plugins/dev-tools/src/toolboxCategories.js:1 · packages/plugins/strict-connection-checker/src/toolboxCategories.js:1 — these 2 files are line-for-line copies of one another — 381 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/plugins/dev-tools/src/toolboxCategories.js:1
packages/plugins/sample-app-ts/src/toolbox.ts:15 · packages/plugins/sample-app/src/toolbox.js:15 — these 2 files are line-for-line copies of one another — 348 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/plugins/sample-app-ts/src/toolbox.ts:15
packages/blockly/generators/dart/lists.ts:50 · packages/blockly/generators/javascript/lists.ts:60 — the two spans are one implementation copied and then locally edited — 1706 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/dart/lists.ts:50
packages/blockly/generators/javascript/math.ts:51 · packages/blockly/generators/php/math.ts:49 — the two spans are one implementation copied and then locally edited — 1641 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/javascript/math.ts:51
packages/blockly/generators/dart/math.ts:24 · packages/blockly/generators/python/math.ts:25 — the two spans are one implementation copied and then locally edited — 1632 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/dart/math.ts:24
packages/blockly/generators/dart/text.ts:38 · packages/blockly/generators/javascript/text.ts:89 — the two spans are one implementation copied and then locally edited — 1191 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/dart/text.ts:38
packages/blockly/core/flyout_horizontal.ts:72 · packages/blockly/core/flyout_vertical.ts:61 — the two spans are one implementation copied and then locally edited — 930 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/core/flyout_horizontal.ts:72
packages/blockly/generators/dart/math.ts:62 · packages/blockly/generators/javascript/math.ts:48 — the two spans are one implementation copied and then locally edited — 920 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/dart/math.ts:62
packages/blockly/generators/lua/math.ts:24 · packages/blockly/generators/php/math.ts:28 — the two spans are one implementation copied and then locally edited — 994 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/lua/math.ts:24
packages/blockly/core/renderers/geras/info.ts:111 · packages/blockly/core/renderers/thrasos/info.ts:56 — the two spans are one implementation copied and then locally edited — 1020 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/core/renderers/geras/info.ts:111
packages/blockly/generators/php/lists.ts:128 · packages/blockly/generators/python/lists.ts:96 — the two spans are one implementation copied and then locally edited — 872 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/php/lists.ts:128
packages/blockly/generators/javascript/javascript_generator.ts:80 · packages/blockly/generators/php/php_generator.ts:71 — the two spans are one implementation copied and then locally edited — 849 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/javascript/javascript_generator.ts:80
packages/blockly/generators/javascript/math.ts:23 · packages/blockly/generators/lua/math.ts:23 — the two spans are one implementation copied and then locally edited — 820 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/javascript/math.ts:23
packages/plugins/block-dynamic-connection/src/dynamic_list_create.ts:39 · packages/plugins/block-dynamic-connection/src/dynamic_text_join.ts:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/plugins/block-dynamic-connection/src/dynamic_list_create.ts:39
packages/blockly/generators/python/lists.ts:51 · packages/blockly/generators/python/text.ts:98 — the two spans are one implementation copied and then locally edited — 692 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/python/lists.ts:51
packages/blockly/generators/javascript/lists.ts:95 · packages/blockly/generators/python/lists.ts:113 — the two spans are one implementation copied and then locally edited — 670 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/javascript/lists.ts:95
packages/plugins/field-colour/src/blocks/colourBlend.ts:49 · packages/plugins/field-colour/src/blocks/colourRgb.ts:48 — the two spans are one implementation copied and then locally edited — 714 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/plugins/field-colour/src/blocks/colourBlend.ts:49
packages/blockly/generators/javascript/text.ts:21 · packages/blockly/generators/python/text.ts:32 — the two spans are one implementation copied and then locally edited — 748 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/javascript/text.ts:21
packages/blockly/generators/dart/loops.ts:79 · packages/blockly/generators/javascript/loops.ts:85 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/blockly/generators/dart/loops.ts:79
packages/blockly/generators/dart/loops.ts:13 · packages/blockly/generators/php/loops.ts:13 — these 2 files are line-for-line copies of one another — 93 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/blockly/generators/dart/loops.ts:13
packages/blockly/generators/javascript/lists.ts:285 · packages/blockly/generators/javascript/text.ts:44 — the two spans are one implementation copied and then locally edited — 514 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/javascript/lists.ts:285
packages/blockly/generators/dart/logic.ts:13 · packages/blockly/generators/javascript/logic.ts:13 · packages/blockly/generators/php/logic.ts:13 — these 3 files are line-for-line copies of one another — 85 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/blockly/generators/dart/logic.ts:13
packages/blockly/core/bubbles/textinput_bubble.ts:127 · packages/blockly/core/comments/comment_view.ts:251 — the two spans are one implementation copied and then locally edited — 365 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/core/bubbles/textinput_bubble.ts:127
packages/plugins/block-plus-minus/src/list_create.js:37 · packages/plugins/block-plus-minus/src/text_join.js:15 — the two spans are one implementation copied and then locally edited — 445 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/plugins/block-plus-minus/src/list_create.js:37
packages/blockly/blocks/variables.ts:69 · packages/blockly/blocks/variables_dynamic.ts:69 — the two spans are one implementation copied and then locally edited — 419 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/blocks/variables.ts:69
packages/blockly/generators/javascript/procedures.ts:23 · packages/blockly/generators/python/procedures.ts:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/blockly/generators/javascript/procedures.ts:23
packages/blockly/generators/lua/procedures.ts:23 · packages/blockly/generators/python/procedures.ts:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/blockly/generators/lua/procedures.ts:23
packages/blockly/generators/lua/text.ts:18 · packages/blockly/generators/php/text.ts:18 — the two spans are one implementation copied and then locally edited — 551 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/generators/lua/text.ts:18
packages/blockly/generators/php/procedures.ts:20 · packages/blockly/generators/python/procedures.ts:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blockly/generators/php/procedures.ts:20
packages/blockly/core/icons/mutator_icon.ts:127 · packages/blockly/core/icons/warning_icon.ts:100 — the two spans are one implementation copied and then locally edited — 317 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/core/icons/mutator_icon.ts:127
packages/blockly/generators/dart/procedures.ts:13 · packages/blockly/generators/javascript/procedures.ts:13 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/blockly/generators/dart/procedures.ts:13
packages/blockly/core/renderers/geras/info.ts:317 · packages/blockly/core/renderers/thrasos/info.ts:242 — the two spans are one implementation copied and then locally edited — 360 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/core/renderers/geras/info.ts:317
packages/blockly/core/events/events_var_create.ts:28 · packages/blockly/core/events/events_var_delete.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blockly/core/events/events_var_create.ts:28
packages/blockly/blocks/lists.ts:821 · packages/blockly/blocks/text.ts:243 — the two spans are one implementation copied and then locally edited — 431 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/blockly/blocks/lists.ts:821
packages/blockly/generators/lua/lua_generator.ts:117 · packages/blockly/generators/php/php_generator.ts:150 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/blockly/generators/lua/lua_generator.ts:117

What to do

Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.

Do you agree with this assessment?

R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

getInRowSpacing_ has cyclomatic complexity 60 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/renderers/geras/info.ts:146
getInRowSpacing_ has cyclomatic complexity 55 and cognitive complexity 71; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/renderers/thrasos/info.ts:91
blockToDom has cyclomatic complexity 37 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/xml.ts:185
lists_getIndex has cyclomatic complexity 37 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/php/lists.ts:154
lists_getIndex has cyclomatic complexity 36 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/dart/lists.ts:91
tokenizeInterpolationInternal has cyclomatic complexity 35 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/utils/parsing.ts:24
lookUpFocusableNode has cyclomatic complexity 35 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/workspace_svg.ts:2922
resize has cyclomatic complexity 29 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/scrollbar_pair.ts:102
jsonInit has cyclomatic complexity 29 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/block.ts:1756
math_single has cyclomatic complexity 28 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/dart/math.ts:69
filter has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/events/utils.ts:230
lists_setIndex has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/php/lists.ts:285
constructor has cyclomatic complexity 25 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/core/options.ts:83
lists_getIndex has cyclomatic complexity 25 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/python/lists.ts:116
lists_getIndex has cyclomatic complexity 25 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/javascript/lists.ts:98
math_single has cyclomatic complexity 25 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — packages/blockly/generators/javascript/math.ts:55, packages/blockly/generators/php/math.ts:53
lists_getIndex has cyclomatic complexity 24 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/lua/lists.ts:151
text_getSubstring has cyclomatic complexity 24 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/javascript/text.ts:193
math_single has cyclomatic complexity 24 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/blockly/generators/python/math.ts:62

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files4.4 / 10Weak✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

80 file(s) over 400 lines (counted as significant lines — blank lines excluded — over production source only, tests excluded), largest first: packages/blockly/core/workspace_svg.ts (2833), packages/blockly/core/block.ts (2361), packages/blockly/core/shortcut_items.ts (1892), packages/blockly/core/block_svg.ts (1856), packages/blockly/core/field.ts (1515), packages/blockly/blocks/procedures.ts (1307) (+74 more).

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage8.2 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — packages/blockly/blocks/procedures.ts, packages/blockly/blocks/lists.ts, packages/blockly/blocks/text.ts, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R5 · Dependency Freshness7.9 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

Bump outdated dependencies to current versions to limit upgrade debt.

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

Do you agree with this assessment?

R7 · Dead Code6.0 / 10Adequate✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

1 file(s) (~38 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
Unreachable from the 105 application, 17 tooling and 274 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/procedures.ts, packages/blockly/generators/javascript/procedures.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/blocks/procedures.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/lists.ts, packages/blockly/generators/javascript/lists.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/blocks/lists.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/text.ts, packages/blockly/generators/javascript/text.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/blocks/text.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/blocks/blocks.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — packages/blockly/blocks/logic.ts, packages/blockly/blocks/math.ts, packages/blockly/blocks/variables_dynamic.ts, …
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×6) — packages/blockly/generators/php/lists.ts, packages/blockly/generators/php/math.ts, packages/blockly/generators/php/text.ts, …
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/dart.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — packages/blockly/generators/dart/math.ts, packages/blockly/generators/dart/lists.ts, packages/blockly/generators/dart/text.ts, …
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/lua.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — packages/blockly/generators/lua/math.ts, packages/blockly/generators/lua/lists.ts, packages/blockly/generators/lua/text.ts, …
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/javascript.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/javascript/math.ts, packages/blockly/generators/javascript/text.ts, …
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/python.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — packages/blockly/generators/python/math.ts, packages/blockly/generators/python/lists.ts, packages/blockly/generators/python/text.ts, …
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/loops.ts, packages/blockly/generators/javascript/loops.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/blocks/loops.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/python.ts, packages/blockly/generators/python/lists.ts, packages/blockly/generators/python/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/generators/python/python_generator.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/javascript.ts, packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/javascript/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/generators/javascript/javascript_generator.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/dart.ts, packages/blockly/generators/dart/lists.ts, packages/blockly/generators/dart/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/generators/dart/dart_generator.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/php.ts, packages/blockly/generators/php/lists.ts, packages/blockly/generators/php/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/generators/php/php_generator.ts
no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/lua.ts, packages/blockly/generators/lua/lists.ts, packages/blockly/generators/lua/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/blockly/generators/lua/lua_generator.ts

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene1.0 / 10Critical✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×4) — packages/plugins/dev-create/templates/block/template/test/block_test.mocha.js:7, packages/plugins/field-multilineinput/test/field_multilineinput_test.mocha.js:153, packages/plugins/workspace-minimap/test/minimap_tests.mocha.js:440, …
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports0.0 / 10Critical✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

packages/blockly/core/block_svg.ts → packages/blockly/core/dragging/block_drag_strategy.ts → packages/blockly/core/hints.ts → packages/blockly/core/shortcut_items.ts → packages/blockly/core/block_svg.ts (one verified cycle inside a mutually-dependent group of 19 files) — packages/blockly/core/block_svg.ts
packages/blockly/core/bubbles/bubble.ts → packages/blockly/core/utils.ts → packages/blockly/core/extensions.ts → packages/blockly/core/icons/mutator_icon.ts → packages/blockly/core/bubbles/mini_workspace_bubble.ts → packages/blockly/core/bubbles/bubble.ts (one verified cycle inside a mutually-dependent group of 6 files) — packages/blockly/core/bubbles/bubble.ts
packages/blockly/core/comments/rendered_workspace_comment.ts → packages/blockly/core/contextmenu.ts → packages/blockly/core/serialization/blocks.ts → packages/blockly/core/variables.ts → packages/blockly/core/events/events.ts → packages/blockly/core/events/events_block_change.ts → packages/blockly/core/xml.ts → packages/blockly/core/comments/rendered_workspace_comment.ts (one verified cycle inside a mutually-dependent group of 9 files) — packages/blockly/core/comments/rendered_workspace_comment.ts
packages/blockly/core/common.ts → packages/blockly/core/events/utils.ts → packages/blockly/core/common.ts — packages/blockly/core/common.ts
packages/blockly/core/field.ts → packages/blockly/core/widgetdiv.ts → packages/blockly/core/field.ts — packages/blockly/core/field.ts
packages/blockly/core/utils/aria.ts → packages/blockly/core/utils/dom.ts → packages/blockly/core/utils/aria.ts — packages/blockly/core/utils/aria.ts
packages/plugins/block-shareable-procedures/src/events_procedure_create.ts → packages/plugins/block-shareable-procedures/src/observable_procedure_model.ts → packages/plugins/block-shareable-procedures/src/events_procedure_create.ts — packages/plugins/block-shareable-procedures/src/events_procedure_create.ts

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

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.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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. 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?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 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).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

Not statically assessed — these 47 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	65%	Adequate	Strongest area.
Architecture	63%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	68%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	40%	Weak — gated by R8, P2, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	41%	Weak — gated by D29, D30, D36, D43	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	40%	Weak — gated by AC3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Acceptable, with room to improve.

Unscored — 2 check(s) recorded observations but carry no score

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

X10 Duplicated predicate — 25 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 — 4 control(s) we could not find positive evidence for

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

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

Not included — 72 check(s) not relevant to this codebase

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

AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — not 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
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~21293 lines of test source are present (.ts) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Not scored — 1 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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.
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. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — packages/blockly/ runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 1 domain event(s); its 1 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD; its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. 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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — 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
X27 Collection changed while being enumerated — 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
X28 Index access outside its own emptiness guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — not 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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 66 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · High CVE · ×15

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R9 · Circular Imports · Import cycle (2 files) · ×4

Import cycle (2 files) packages/blockly/core/common.ts — packages/blockly/core/common.ts → packages/blockly/core/events/utils.ts → packages/blockly/core/common.ts
Import cycle (2 files) packages/blockly/core/field.ts — packages/blockly/core/field.ts → packages/blockly/core/widgetdiv.ts → packages/blockly/core/field.ts
Import cycle (2 files) packages/blockly/core/utils/aria.ts — packages/blockly/core/utils/aria.ts → packages/blockly/core/utils/dom.ts → packages/blockly/core/utils/aria.ts
Import cycle (2 files) packages/plugins/block-shareable-procedures/src/events_procedure_create.ts — packages/plugins/block-shareable-procedures/src/events_procedure_create.ts → packages/plugins/block-shareable-procedures/src/observable_procedure_model.ts → packages/plugins/block-shareable-procedures/src/events_procedure_create.ts

AC3 · Page structure · <html> without a lang · ×2

<html> without a lang packages/plugins/sample-app-ts/src/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/plugins/sample-app/src/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

D34 · Knowledge Freshness · Orphaned knowledge · ×2

Orphaned knowledge packages/blockly/core/scrollbar.ts — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/blockly/core/renderers/common/info.ts — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.

R8 · Dependency Hygiene · Unlisted import 'jsdom-global' · ×2

Unlisted import 'jsdom-global' packages/plugins/field-multilineinput/test/field_multilineinput_test.mocha.js:153 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'jsdom-global' packages/plugins/workspace-minimap/test/minimap_tests.mocha.js:440 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

D28 · Secrets (history) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

R8 · Dependency Hygiene · Unlisted import 'chai' · ×1

Unlisted import 'chai' packages/plugins/dev-create/templates/block/template/test/block_test.mocha.js:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'sinon' · ×1

Unlisted import 'sinon' packages/plugins/workspace-minimap/test/minimap_tests.mocha.js:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (4 files) · ×1

Import cycle (4 files) packages/blockly/core/block_svg.ts — packages/blockly/core/block_svg.ts → packages/blockly/core/dragging/block_drag_strategy.ts → packages/blockly/core/hints.ts → packages/blockly/core/shortcut_items.ts → packages/blockly/core/block_svg.ts (one verified cycle inside a mutually-dependent group of 19 files)

R9 · Circular Imports · Import cycle (5 files) · ×1

Import cycle (5 files) packages/blockly/core/bubbles/bubble.ts — packages/blockly/core/bubbles/bubble.ts → packages/blockly/core/utils.ts → packages/blockly/core/extensions.ts → packages/blockly/core/icons/mutator_icon.ts → packages/blockly/core/bubbles/mini_workspace_bubble.ts → packages/blockly/core/bubbles/bubble.ts (one verified cycle inside a mutually-dependent group of 6 files)

R9 · Circular Imports · Import cycle (7 files) · ×1

Import cycle (7 files) packages/blockly/core/comments/rendered_workspace_comment.ts — packages/blockly/core/comments/rendered_workspace_comment.ts → packages/blockly/core/contextmenu.ts → packages/blockly/core/serialization/blocks.ts → packages/blockly/core/variables.ts → packages/blockly/core/events/events.ts → packages/blockly/core/events/events_block_change.ts → packages/blockly/core/xml.ts → packages/blockly/core/comments/rendered_workspace_comment.ts (one verified cycle inside a mutually-dependent group of 9 files)

Serious — 472 finding(s)

D17 · Explicit Debt · TodoComment · ×64

TodoComment packages/blockly/blocks/procedures.ts:896 — // TODO(#6920)
TodoComment packages/blockly/blocks/procedures.ts:1015 — // TODO(#6920)
TodoComment packages/blockly/blocks/logic.ts:563 — // TODO(#6920)
TodoComment packages/blockly/blocks/procedures.ts:898 — // TODO(#6920): investigate claimed circular initialisers.
TodoComment packages/blockly/blocks/logic.ts:420 — // TODO(#6920): null valid, undefined not.
TodoComment packages/blockly/blocks/lists.ts:579 — // TODO(#6920): The .unplug only has one parameter.
TodoComment packages/blockly/blocks/lists.ts:1049 — // TODO(#6920): This is probably not needed; see details in bug.
TodoComment packages/blockly/core/xml.ts:662 — // TODO(@picklesrus): #387. Remove when domToBlock avoids resizing.
TodoComment packages/blockly/core/tooltip.ts:204 — // TODO (#6097): Don't stash wrapper info on the DOM.
TodoComment packages/blockly/core/tooltip.ts:233 — // TODO (#6097): Don't stash wrapper info on the DOM.
TodoComment packages/blockly/core/insertion_marker_previewer.ts:99 — // TODO(7898): Instead of special casing, we should change the dragger to — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/gesture.ts:908 — // TODO (fenichel): Move bubbles to the front. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/flyout_vertical.ts:298 — // TODO(#7689): Remove this.
TodoComment packages/blockly/core/flyout_horizontal.ts:321 — // TODO(#7689): Remove this.
TodoComment packages/blockly/core/flyout_base.ts:244 — // TODO: Move GAP_X and GAP_Y to their appropriate files. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/field_number.ts:261 — // TODO: Handle cases like 'ten', '1.203,14', etc. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/field.ts:251 — // TODO (#2884): Possibly add CSS class config option.
TodoComment packages/blockly/core/field.ts:252 — // TODO (#2885): Possibly add cursor config option.
TodoComment packages/blockly/core/block_svg.ts:1092 — // TODO(#6020): This warning is never removed.
TodoComment packages/blockly/core/block.ts:1619 — // TODO: Improve truncation so that text from this block is given — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/bubbles/mini_workspace_bubble.ts:73 — // TODO (#7422): Change this to `internalIsMiniWorkspace` or something. Not
TodoComment packages/blockly/core/bubbles/bubble.ts:365 — // TODO: I believe relativeLeft_ should actually be called relativeStart_ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/comments/comment_view.ts:138 — // TODO: Remove this comment before merging. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/blockly/core/events/events_comment_move.ts:31 — // TODO(#6774): We should remove underscores.
TodoComment packages/blockly/core/events/events_comment_change.ts:27 — // TODO(#6774): We should remove underscores.
+ 39 more in this group — see findings.md.

R4 · Test Coverage · No test reaches this file · ×40

No test reaches this file packages/blockly/blocks/procedures.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/blocks/lists.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/blocks/text.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/blocks/logic.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/blocks/math.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/php/lists.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/dart/math.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/dart/lists.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/lua/math.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/javascript/lists.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/javascript/math.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/lua/lists.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/python/math.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/javascript/text.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/blocks/loops.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/php/math.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/dart/text.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/python/lists.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/lua/text.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/python/python_generator.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/scripts/package.mjs — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/javascript/javascript_generator.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/python/text.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/dart/dart_generator.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/blockly/generators/php/php_generator.ts — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 15 more in this group — see findings.md.

D3 · God Classes · TooManyMethods · ×22

TooManyMethods: WorkspaceSvg packages/blockly/core/workspace_svg.ts:98 — TooManyMethods — 129 methods. The bar is 30 methods; this is 99 over it, 4.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Block packages/blockly/core/block.ts:57 — TooManyMethods — 111 methods. The bar is 30 methods; this is 81 over it, 3.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BlockSvg packages/blockly/core/block_svg.ts:79 — TooManyMethods — 109 methods. The bar is 30 methods; this is 79 over it, 3.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Field packages/blockly/core/field.ts:69 — TooManyMethods — 81 methods. The bar is 30 methods; this is 51 over it, 2.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Toolbox packages/blockly/core/toolbox/toolbox.ts:56 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Backpack packages/plugins/workspace-backpack/src/backpack.ts:27 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Gesture packages/blockly/core/gesture.ts:57 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Workspace packages/blockly/core/workspace.ts:42 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Bubble packages/blockly/core/bubbles/bubble.ts:42 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CommentView packages/blockly/core/comments/comment_view.ts:25 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WorkspaceSearch packages/plugins/workspace-search/src/workspace_search.ts:14 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FieldBitmap packages/plugins/field-bitmap/src/field-bitmap.ts:25 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BlockDragStrategy packages/blockly/core/dragging/block_drag_strategy.ts:67 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RenderedConnection packages/blockly/core/rendered_connection.ts:42 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Flyout packages/blockly/core/flyout_base.ts:45 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ToolboxCategory packages/blockly/core/toolbox/category.ts:38 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RenderedWorkspaceComment packages/blockly/core/comments/rendered_workspace_comment.ts:34 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FieldDropdown packages/blockly/core/field_dropdown.ts:36 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FieldInput packages/blockly/core/field_input.ts:58 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CommentIcon packages/blockly/core/icons/comment_icon.ts:40 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Scrollbar packages/blockly/core/scrollbar.ts:33 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Connection packages/blockly/core/connection.ts:28 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · FileTooLong · ×18

FileTooLong: core/workspace_svg.ts packages/blockly/core/workspace_svg.ts — FileTooLong — 1328 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: WorkspaceSvg (98-3112). The bar is 500 significant lines; this is 828 over it, 2.66× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: core/shortcut_items.ts packages/blockly/core/shortcut_items.ts — FileTooLong — 1277 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 777 over it, 2.55× 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: core/block.ts packages/blockly/core/block.ts — FileTooLong — 1046 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 546 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: core/block_svg.ts packages/blockly/core/block_svg.ts — FileTooLong — 897 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 397 over it, 1.79× 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: dragging/block_drag_strategy.ts packages/blockly/core/dragging/block_drag_strategy.ts — FileTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: BlockDragStrategy (67-1382). The bar is 500 significant lines; this is 258 over it, 1.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: blocks/procedures.ts packages/blockly/blocks/procedures.ts — FileTooLong — 754 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 254 over it, 1.51× 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: src/blocks.ts packages/plugins/block-shareable-procedures/src/blocks.ts — FileTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 212 over it, 1.42× 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: blocks/lists.ts packages/blockly/blocks/lists.ts — FileTooLong — 672 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 172 over it, 1.34× 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: core/xml.ts packages/blockly/core/xml.ts — FileTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 136 over it, 1.27× 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: blocks/text.ts packages/blockly/blocks/text.ts — FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 95 over it, 1.19× 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: core/field.ts packages/blockly/core/field.ts — FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: Field (69-1622). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: common/constants.ts packages/blockly/core/renderers/common/constants.ts — FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: ConstantProvider (124-1230). The bar is 500 significant lines; this is 62 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/backpack.ts packages/plugins/workspace-backpack/src/backpack.ts — FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: Backpack (27-1027). The bar is 500 significant lines; this is 57 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/field-bitmap.ts packages/plugins/field-bitmap/src/field-bitmap.ts — FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: FieldBitmap (25-939). The bar is 500 significant lines; this is 35 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: toolbox/toolbox.ts packages/blockly/core/toolbox/toolbox.ts — FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: Toolbox (56-1084). The bar is 500 significant lines; this is 16 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: core/field_dropdown.ts packages/blockly/core/field_dropdown.ts — FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: FieldDropdown (36-988). The bar is 500 significant lines; this is 15 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/field_colour_hsv_sliders.ts packages/plugins/field-colour-hsv-sliders/src/field_colour_hsv_sliders.ts — FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: FieldColourHsvSliders (190-706). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: core/field_input.ts packages/blockly/core/field_input.ts — FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: FieldInput (58-1002). The bar is 500 significant lines; this is 2 over it, 1.00× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.

D3 · God Classes · ClassTooLong · ×10

ClassTooLong: WorkspaceSvg packages/blockly/core/workspace_svg.ts:98 — ClassTooLong — 1249 significant lines (blank, comment-only and punctuation-only lines excluded), 129 methods. The bar is 400 significant lines; this is 849 over it, 3.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BlockDragStrategy packages/blockly/core/dragging/block_drag_strategy.ts:67 — ClassTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 315 over it, 1.79× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Field packages/blockly/core/field.ts:69 — ClassTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded), 81 methods. The bar is 400 significant lines; this is 151 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ConstantProvider packages/blockly/core/renderers/common/constants.ts:124 — ClassTooLong — 496 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 96 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FieldBitmap packages/plugins/field-bitmap/src/field-bitmap.ts:25 — ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 77 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FieldDropdown packages/blockly/core/field_dropdown.ts:36 — ClassTooLong — 472 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 72 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Backpack packages/plugins/workspace-backpack/src/backpack.ts:27 — ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FieldInput packages/blockly/core/field_input.ts:58 — ClassTooLong — 457 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 57 over it, 1.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Gesture packages/blockly/core/gesture.ts:57 — ClassTooLong — 455 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 55 over it, 1.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Toolbox packages/blockly/core/toolbox/toolbox.ts:56 — ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 52 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · FunctionTooLong · ×8

FunctionTooLong: index.Root packages/docs/src/theme/Root/index.js:14 — FunctionTooLong — Root runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× 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: math.math_on_list packages/blockly/generators/dart/math.ts:269 — FunctionTooLong — math_on_list runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: lists.lists_getIndex packages/blockly/generators/dart/lists.ts:91 — FunctionTooLong — lists_getIndex runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: lists.lists_getIndex packages/blockly/generators/php/lists.ts:154 — FunctionTooLong — lists_getIndex runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: parsing.tokenizeInterpolationInternal packages/blockly/core/utils/parsing.ts:24 — FunctionTooLong — tokenizeInterpolationInternal runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: math.math_on_list packages/blockly/generators/javascript/math.ts:235 — FunctionTooLong — math_on_list 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.
FunctionTooLong: loops.controls_for packages/blockly/generators/python/loops.ts:64 — FunctionTooLong — controls_for 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.
FunctionTooLong: lists.lists_getSublist packages/blockly/generators/php/lists.ts:398 — FunctionTooLong — lists_getSublist runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D6 · Cohesion (LCOM4) · Low cohesion · ×6

Low cohesion: WorkspaceComment (LCOM4 6) packages/blockly/core/comments/workspace_comment.ts:17 — WorkspaceComment's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Block (LCOM4 5) packages/blockly/core/block.ts:57 — Block's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ConstantProvider (LCOM4 5) packages/blockly/core/renderers/zelos/constants.ts:34 — ConstantProvider's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CommentEditor (LCOM4 4) packages/blockly/core/comments/comment_editor.ts:30 — CommentEditor's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BlockSuggestor (LCOM4 4) packages/plugins/suggested-blocks/src/index.js:21 — BlockSuggestor's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TypedVariableModal (LCOM4 4) packages/plugins/typed-variable-modal/src/TypedVariableModal.js:19 — TypedVariableModal's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

D35 · Change Coupling · Change coupling · ×4

Change coupling: field_checkbox.ts ↔ field_textinput.ts packages/blockly/core/field_checkbox.ts — `packages/blockly/core/field_checkbox.ts` and `packages/blockly/core/field_textinput.ts` change together 60% of the time (42 of the 70 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 42 shared commits counted here, the most recent 3 are `c43350e9` chore: Remove unused imports (#10080); `28ac0c44` fix: improve types in FieldRegistry (#8062) (at that commit the files were still `core/field_checkbox.ts` and `core/field_textinput.ts`); `faa95d02` fix(fields): Make SKIP_SETUP a Symbol; remove Sentinel class (#6919) (at that commit the files were still `core/field_checkbox.ts` and `core/field_textinput.ts`) — run `git show` on any of them.
Change coupling: field_label.ts ↔ field_textinput.ts packages/blockly/core/field_label.ts — `packages/blockly/core/field_label.ts` and `packages/blockly/core/field_textinput.ts` change together 55% of the time (34 of the 62 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 34 shared commits counted here, the most recent 3 are `28ac0c44` fix: improve types in FieldRegistry (#8062) (at that commit the files were still `core/field_label.ts` and `core/field_textinput.ts`); `faa95d02` fix(fields): Make SKIP_SETUP a Symbol; remove Sentinel class (#6919) (at that commit the files were still `core/field_label.ts` and `core/field_textinput.ts`); `0fb64a67` fix: replace 'AnyDuringMigration' for `core/field.ts` value functions… (at that commit the files were still `core/field_label.ts` and `core/field_textinput.ts`) — run `git show` on any of them.
Change coupling: block_flyout_inflater.ts ↔ flyout_base.ts packages/blockly/core/block_flyout_inflater.ts — `packages/blockly/core/block_flyout_inflater.ts` and `packages/blockly/core/flyout_base.ts` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `07c83d3b` chore: use none ARIA role consistently instead of presentation (#10067); `993fa903` fix: Treat the flyout as a listbox with options (#10059); `61ad9944` feat: make flyouts and workspace labels properly accessible (#9774) — run `git show` on any of them.
Change coupling: block_drag_strategy.ts ↔ comment_drag_strategy.ts packages/blockly/core/dragging/block_drag_strategy.ts — `packages/blockly/core/dragging/block_drag_strategy.ts` and `packages/blockly/core/dragging/comment_drag_strategy.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `71ca797d` feat: Add a sound effect when dropping top-level items on the workspa…; `da1db45d` feat!: Allow moving blocks, comments and bubbles using the keyboard (…; `b343a13b` fix: Fixes #8764 by moving the event grouping calls up to dragger.ts … (at that commit the files were still `core/dragging/block_drag_strategy.ts` and `core/dragging/comment_drag_strategy.ts`) — run `git show` on any of them.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×4

Sync-over-async blocking packages/blockly/scripts/langfiles.mjs:63 — `buildLangfileShims` is async and calls mkdirSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/blockly/tests/generators/test_generators.mjs:78 — `generators` is async and calls mkdirSync, spawnSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/blockly/tests/generators/webdriver.js:26 — `runLangGeneratorInBrowser` is async and calls writeFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/plugins/migration/bin/rename.js:35 — `rename` is async and calls statSync, readFileSync, writeFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.

D1 · Cyclomatic Complexity · lists.lists_setIndex (cyclomatic 21) · ×3

lists.lists_setIndex (cyclomatic 21) packages/blockly/generators/dart/lists.ts:280 — lists.lists_setIndex 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.
lists.lists_setIndex (cyclomatic 21) packages/blockly/generators/javascript/lists.ts:184 — lists.lists_setIndex 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.
lists.lists_setIndex (cyclomatic 21) packages/blockly/generators/python/lists.ts:203 — lists.lists_setIndex 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.

D1 · Cyclomatic Complexity · loops.controls_for (cyclomatic 16) · ×3

loops.controls_for (cyclomatic 16) packages/blockly/generators/dart/loops.ts:79 — loops.controls_for 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.
loops.controls_for (cyclomatic 16) packages/blockly/generators/javascript/loops.ts:85 — loops.controls_for 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.
loops.controls_for (cyclomatic 16) packages/blockly/generators/php/loops.ts:79 — loops.controls_for 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.

D2 · Cognitive Complexity · lists.lists_setIndex (cognitive 21) · ×3

lists.lists_setIndex (cognitive 21) packages/blockly/generators/dart/lists.ts:280 — lists.lists_setIndex has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lists.lists_setIndex (cognitive 21) packages/blockly/generators/javascript/lists.ts:184 — lists.lists_setIndex has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lists.lists_setIndex (cognitive 21) packages/blockly/generators/python/lists.ts:203 — lists.lists_setIndex has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · loops.controls_for (cognitive 18) · ×3

loops.controls_for (cognitive 18) packages/blockly/generators/dart/loops.ts:79 — loops.controls_for has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6 (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.
loops.controls_for (cognitive 18) packages/blockly/generators/javascript/loops.ts:85 — loops.controls_for has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6 (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.
loops.controls_for (cognitive 18) packages/blockly/generators/php/loops.ts:79 — loops.controls_for has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6 (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.

D30 · Dependency Vulnerabilities · Medium CVE · ×3

REDACTED
REDACTED
REDACTED

AC3 · Page structure · Page without a main landmark · ×2

Page without a main landmark packages/plugins/sample-app-ts/src/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/plugins/sample-app/src/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

D1 · Cyclomatic Complexity · lists.lists_getIndex (cyclomatic 25) · ×2

lists.lists_getIndex (cyclomatic 25) packages/blockly/generators/javascript/lists.ts:98 — lists.lists_getIndex 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.
lists.lists_getIndex (cyclomatic 25) packages/blockly/generators/python/lists.ts:116 — lists.lists_getIndex 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.

D1 · Cyclomatic Complexity · math.math_single (cyclomatic 25) · ×2

math.math_single (cyclomatic 25) packages/blockly/generators/javascript/math.ts:55 — math.math_single has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
math.math_single (cyclomatic 25) packages/blockly/generators/php/math.ts:53 — math.math_single has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · math.math_on_list (cyclomatic 17) · ×2

math.math_on_list (cyclomatic 17) packages/blockly/generators/javascript/math.ts:235 — math.math_on_list has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
math.math_on_list (cyclomatic 17) packages/blockly/generators/php/math.ts:231 — math.math_on_list has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D2 · Cognitive Complexity · RenderInfo.addElemSpacing_ (cognitive 16) · ×2

RenderInfo.addElemSpacing_ (cognitive 16) packages/blockly/core/renderers/geras/info.ts:103 — RenderInfo.addElemSpacing_ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RenderInfo.addElemSpacing_ (cognitive 16) packages/blockly/core/renderers/thrasos/info.ts:45 — RenderInfo.addElemSpacing_ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

R10 · Code Duplication · Duplicated block with local edits (155 matched lines × 2 locations) · ×2

Duplicated block with local edits (155 matched lines × 2 locations) packages/blockly/core/flyout_horizontal.ts:72 — packages/blockly/core/flyout_horizontal.ts:72 · packages/blockly/core/flyout_vertical.ts:61 — the two spans are one implementation copied and then locally edited — 930 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (155 matched lines × 2 locations) packages/blockly/generators/dart/math.ts:62 — packages/blockly/generators/dart/math.ts:62 · packages/blockly/generators/javascript/math.ts:48 — the two spans are one implementation copied and then locally edited — 920 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (102 matched lines × 2 locations) · ×2

Duplicated block with local edits (102 matched lines × 2 locations) packages/blockly/generators/javascript/lists.ts:95 — packages/blockly/generators/javascript/lists.ts:95 · packages/blockly/generators/python/lists.ts:113 — the two spans are one implementation copied and then locally edited — 670 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (102 matched lines × 2 locations) packages/plugins/field-colour/src/blocks/colourBlend.ts:49 — packages/plugins/field-colour/src/blocks/colourBlend.ts:49 · packages/plugins/field-colour/src/blocks/colourRgb.ts:48 — the two spans are one implementation copied and then locally edited — 714 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R2 · Cyclomatic Complexity · Complex function math_single (cyclomatic 25, cognitive 12) · ×2

Complex function math_single (cyclomatic 25, cognitive 12) packages/blockly/generators/javascript/math.ts:55 — math_single has cyclomatic complexity 25 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function math_single (cyclomatic 25, cognitive 12) packages/blockly/generators/php/math.ts:53 — math_single has cyclomatic complexity 25 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R7 · Dead Code · Dead file (~192 LoC) · ×2

Dead file (~192 LoC) packages/blockly/blocks/variables_dynamic.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/blocks/blocks.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~192 LoC) packages/blockly/generators/lua/loops.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/lua.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~158 LoC) · ×2

Dead file (~158 LoC) packages/blockly/generators/php/procedures.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~158 LoC) packages/blockly/generators/python/procedures.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/python.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~157 LoC) · ×2

Dead file (~157 LoC) packages/blockly/generators/dart/logic.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/dart.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~157 LoC) packages/blockly/generators/php/logic.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.1 · ×1

Low contrast colour pair in CSS (4.1:1) packages/blockly/demos/code/style.css:30 — `button.primary` sets color: #fff on background-color: #dd4b39 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 3 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · index.Root (cyclomatic 67) · ×1

index.Root (cyclomatic 67) packages/docs/src/theme/Root/index.js:14 — index.Root has cyclomatic complexity 67 (threshold 15). Most of this is not in the body itself: 1 of the 67 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 113, 175, 95, …). 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.

D1 · Cyclomatic Complexity · RenderInfo.getInRowSpacing_ (cyclomatic 60) · ×1

RenderInfo.getInRowSpacing_ (cyclomatic 60) packages/blockly/core/renderers/geras/info.ts:146 — RenderInfo.getInRowSpacing_ has cyclomatic complexity 60 (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.

D1 · Cyclomatic Complexity · RenderInfo.getInRowSpacing_ (cyclomatic 55) · ×1

RenderInfo.getInRowSpacing_ (cyclomatic 55) packages/blockly/core/renderers/thrasos/info.ts:91 — RenderInfo.getInRowSpacing_ has cyclomatic complexity 55 (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.

D1 · Cyclomatic Complexity · index.createPlayground (cyclomatic 40) · ×1

index.createPlayground (cyclomatic 40) packages/plugins/dev-tools/src/playground/index.js:86 — index.createPlayground has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 17 function literals inside it that branch (lines 118, 237, 481, …). 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.

D1 · Cyclomatic Complexity · xml.blockToDom (cyclomatic 37) · ×1

xml.blockToDom (cyclomatic 37) packages/blockly/core/xml.ts:185 — xml.blockToDom has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · lists.lists_getIndex (cyclomatic 37) · ×1

lists.lists_getIndex (cyclomatic 37) packages/blockly/generators/php/lists.ts:154 — lists.lists_getIndex has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · lists.lists_getIndex (cyclomatic 36) · ×1

lists.lists_getIndex (cyclomatic 36) packages/blockly/generators/dart/lists.ts:91 — lists.lists_getIndex has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · parsing.tokenizeInterpolationInternal (cyclomatic 34) · ×1

parsing.tokenizeInterpolationInternal (cyclomatic 34) packages/blockly/core/utils/parsing.ts:24 — parsing.tokenizeInterpolationInternal 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.

D1 · Cyclomatic Complexity · WorkspaceSvg.lookUpFocusableNode (cyclomatic 34) · ×1

WorkspaceSvg.lookUpFocusableNode (cyclomatic 34) packages/blockly/core/workspace_svg.ts:2922 — WorkspaceSvg.lookUpFocusableNode 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.

D1 · Cyclomatic Complexity · Block.jsonInit (cyclomatic 29) · ×1

Block.jsonInit (cyclomatic 29) packages/blockly/core/block.ts:1756 — Block.jsonInit has cyclomatic complexity 29 (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.

D1 · Cyclomatic Complexity · ScrollbarPair.resize (cyclomatic 29) · ×1

ScrollbarPair.resize (cyclomatic 29) packages/blockly/core/scrollbar_pair.ts:102 — ScrollbarPair.resize has cyclomatic complexity 29 (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.

D1 · Cyclomatic Complexity · math.math_single (cyclomatic 28) · ×1

math.math_single (cyclomatic 28) packages/blockly/generators/dart/math.ts:69 — math.math_single has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · lists.lists_setIndex (cyclomatic 27) · ×1

lists.lists_setIndex (cyclomatic 27) packages/blockly/generators/php/lists.ts:285 — lists.lists_setIndex has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · tracking.extractFunctionName (cyclomatic 27) · ×1

tracking.extractFunctionName (cyclomatic 27) packages/docs/src/utils/tracking.js:70 — tracking.extractFunctionName has cyclomatic complexity 27 (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.

D1 · Cyclomatic Complexity · utils.filter (cyclomatic 24) · ×1

utils.filter (cyclomatic 24) packages/blockly/core/events/utils.ts:230 — utils.filter 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.

D1 · Cyclomatic Complexity · text.text_getSubstring (cyclomatic 24) · ×1

text.text_getSubstring (cyclomatic 24) packages/blockly/generators/javascript/text.ts:193 — text.text_getSubstring 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.

D1 · Cyclomatic Complexity · lists.lists_getIndex (cyclomatic 24) · ×1

lists.lists_getIndex (cyclomatic 24) packages/blockly/generators/lua/lists.ts:151 — lists.lists_getIndex 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.

D1 · Cyclomatic Complexity · math.math_single (cyclomatic 24) · ×1

math.math_single (cyclomatic 24) packages/blockly/generators/python/math.ts:62 — math.math_single has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · RenderInfo.getInRowSpacing_ (cyclomatic 23) · ×1

RenderInfo.getInRowSpacing_ (cyclomatic 23) packages/blockly/core/renderers/common/info.ts:425 — RenderInfo.getInRowSpacing_ 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.

D1 · Cyclomatic Complexity · shortcut_items.registerHeadingNavigation (cyclomatic 23) · ×1

shortcut_items.registerHeadingNavigation (cyclomatic 23) packages/blockly/core/shortcut_items.ts:1094 — shortcut_items.registerHeadingNavigation has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 1134, 1099, 1168, …). 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.

D1 · Cyclomatic Complexity · RenderInfo.getInRowSpacing_ (cyclomatic 22) · ×1

RenderInfo.getInRowSpacing_ (cyclomatic 22) packages/blockly/core/renderers/zelos/info.ts:176 — RenderInfo.getInRowSpacing_ 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.

D1 · Cyclomatic Complexity · math.math_single (cyclomatic 22) · ×1

math.math_single (cyclomatic 22) packages/blockly/generators/lua/math.ts:49 — math.math_single has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ConnectionChecker.doDragChecks (cyclomatic 21) · ×1

ConnectionChecker.doDragChecks (cyclomatic 21) packages/blockly/core/connection_checker.ts:229 — ConnectionChecker.doDragChecks has cyclomatic complexity 21 (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.

D1 · Cyclomatic Complexity · Options.constructor (cyclomatic 21) · ×1

Options.constructor (cyclomatic 21) packages/blockly/core/options.ts:83 — Options.constructor has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · xml.domToBlockHeadless (cyclomatic 21) · ×1

xml.domToBlockHeadless (cyclomatic 21) packages/blockly/core/xml.ts:981 — xml.domToBlockHeadless 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.

D1 · Cyclomatic Complexity · lists.lists_getSublist (cyclomatic 21) · ×1

lists.lists_getSublist (cyclomatic 21) packages/blockly/generators/javascript/lists.ts:301 — lists.lists_getSublist has cyclomatic complexity 21 (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.

D1 · Cyclomatic Complexity · loops.controls_for (cyclomatic 21) · ×1

loops.controls_for (cyclomatic 21) packages/blockly/generators/python/loops.ts:64 — loops.controls_for has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · plugin.createPlugin (cyclomatic 21) · ×1

plugin.createPlugin (cyclomatic 21) packages/plugins/dev-create/bin/plugin.js:25 — plugin.createPlugin has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · options.addGUIControls (cyclomatic 21) · ×1

options.addGUIControls (cyclomatic 21) packages/plugins/dev-tools/src/playground/options.js:53 — options.addGUIControls has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 295, 325, 109, …). 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.

D1 · Cyclomatic Complexity · RenderInfo.adjustXPosition_ (cyclomatic 20) · ×1

RenderInfo.adjustXPosition_ (cyclomatic 20) packages/blockly/core/renderers/zelos/info.ts:352 — RenderInfo.adjustXPosition_ 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.

D1 · Cyclomatic Complexity · RenderInfo.getNegativeSpacing_ (cyclomatic 20) · ×1

RenderInfo.getNegativeSpacing_ (cyclomatic 20) packages/blockly/core/renderers/zelos/info.ts:526 — RenderInfo.getNegativeSpacing_ 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.

D1 · Cyclomatic Complexity · RenderInfo.finalizeVerticalAlignment_ (cyclomatic 20) · ×1

RenderInfo.finalizeVerticalAlignment_ (cyclomatic 20) packages/blockly/core/renderers/zelos/info.ts:610 — RenderInfo.finalizeVerticalAlignment_ 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.

D1 · Cyclomatic Complexity · create_messages.main (cyclomatic 20) · ×1

create_messages.main (cyclomatic 20) packages/blockly/scripts/i18n/create_messages.py:49 — create_messages.main 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.

D1 · Cyclomatic Complexity · Field.setValue (cyclomatic 19) · ×1

Field.setValue (cyclomatic 19) packages/blockly/core/field.ts:1197 — Field.setValue 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.

D1 · Cyclomatic Complexity · lists.lists_getSublist (cyclomatic 19) · ×1

lists.lists_getSublist (cyclomatic 19) packages/blockly/generators/php/lists.ts:398 — lists.lists_getSublist 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.

D1 · Cyclomatic Complexity · FieldMultilineInput.updateSize_ (cyclomatic 19) · ×1

FieldMultilineInput.updateSize_ (cyclomatic 19) packages/plugins/field-multilineinput/src/field_multilineinput.ts:328 — FieldMultilineInput.updateSize_ 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.

D1 · Cyclomatic Complexity · Backpack.position (cyclomatic 19) · ×1

Backpack.position (cyclomatic 19) packages/plugins/workspace-backpack/src/backpack.ts:385 — Backpack.position 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.

D1 · Cyclomatic Complexity · BlockChange.run (cyclomatic 18) · ×1

BlockChange.run (cyclomatic 18) packages/blockly/core/events/events_block_change.ts:164 — BlockChange.run 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.

D1 · Cyclomatic Complexity · BlockMove.run (cyclomatic 18) · ×1

BlockMove.run (cyclomatic 18) packages/blockly/core/events/events_block_move.ts:239 — BlockMove.run 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.

D1 · Cyclomatic Complexity · RenderInfo.getSpacerRowHeight_ (cyclomatic 18) · ×1

RenderInfo.getSpacerRowHeight_ (cyclomatic 18) packages/blockly/core/renderers/zelos/info.ts:217 — RenderInfo.getSpacerRowHeight_ 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.

D1 · Cyclomatic Complexity · shortcut_items.registerPaste (cyclomatic 18) · ×1

shortcut_items.registerPaste (cyclomatic 18) packages/blockly/core/shortcut_items.ts:322 — shortcut_items.registerPaste 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.

D1 · Cyclomatic Complexity · WorkspaceSvg.dispose (cyclomatic 18) · ×1

WorkspaceSvg.dispose (cyclomatic 18) packages/blockly/core/workspace_svg.ts:927 — WorkspaceSvg.dispose 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.

D1 · Cyclomatic Complexity · procedures.procedures_defreturn (cyclomatic 18) · ×1

procedures.procedures_defreturn (cyclomatic 18) packages/blockly/generators/python/procedures.ts:20 — procedures.procedures_defreturn 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.

D1 · Cyclomatic Complexity · BlockDragStrategy.updateConnectionPreview (cyclomatic 17) · ×1

BlockDragStrategy.updateConnectionPreview (cyclomatic 17) packages/blockly/core/dragging/block_drag_strategy.ts:691 — BlockDragStrategy.updateConnectionPreview 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.

D1 · Cyclomatic Complexity · CodeGenerator.valueToCode (cyclomatic 17) · ×1

CodeGenerator.valueToCode (cyclomatic 17) packages/blockly/core/generator.ts:301 — CodeGenerator.valueToCode 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.

D1 · Cyclomatic Complexity · ConstantProvider.shapeFor (cyclomatic 17) · ×1

ConstantProvider.shapeFor (cyclomatic 17) packages/blockly/core/renderers/zelos/constants.ts:500 — ConstantProvider.shapeFor has cyclomatic complexity 17 (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.

D1 · Cyclomatic Complexity · shortcut_items.registerCopy (cyclomatic 17) · ×1

shortcut_items.registerCopy (cyclomatic 17) packages/blockly/core/shortcut_items.ts:207 — shortcut_items.registerCopy has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · xml.domToWorkspace (cyclomatic 17) · ×1

xml.domToWorkspace (cyclomatic 17) packages/blockly/core/xml.ts:447 — xml.domToWorkspace 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.

D1 · Cyclomatic Complexity · procedures.procedures_defreturn (cyclomatic 17) · ×1

procedures.procedures_defreturn (cyclomatic 17) packages/blockly/generators/php/procedures.ts:20 — procedures.procedures_defreturn has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · FieldColourHsvSliders.getAriaValue (cyclomatic 17) · ×1

FieldColourHsvSliders.getAriaValue (cyclomatic 17) packages/plugins/field-colour-hsv-sliders/src/field_colour_hsv_sliders.ts:657 — FieldColourHsvSliders.getAriaValue has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · VersionRenamer.constructor (cyclomatic 17) · ×1

VersionRenamer.constructor (cyclomatic 17) packages/plugins/migration/bin/rename.js:149 — VersionRenamer.constructor 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.

D1 · Cyclomatic Complexity · PositionedMinimap.setPosition (cyclomatic 17) · ×1

PositionedMinimap.setPosition (cyclomatic 17) packages/plugins/workspace-minimap/src/positioned_minimap.ts:107 — PositionedMinimap.setPosition 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.

D1 · Cyclomatic Complexity · FieldInput.onHtmlInputKeyDown_ (cyclomatic 16) · ×1

FieldInput.onHtmlInputKeyDown_ (cyclomatic 16) packages/blockly/core/field_input.ts:702 — FieldInput.onHtmlInputKeyDown_ has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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.

D1 · Cyclomatic Complexity · FocusManager.focusNode (cyclomatic 16) · ×1

FocusManager.focusNode (cyclomatic 16) packages/blockly/core/focus_manager.ts:355 — FocusManager.focusNode 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.

D1 · Cyclomatic Complexity · CodeGenerator.blockToCode (cyclomatic 16) · ×1

CodeGenerator.blockToCode (cyclomatic 16) packages/blockly/core/generator.ts:235 — CodeGenerator.blockToCode 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.

D1 · Cyclomatic Complexity · shortcut_items.registerArrowNavigation (cyclomatic 16) · ×1

shortcut_items.registerArrowNavigation (cyclomatic 16) packages/blockly/core/shortcut_items.ts:666 — shortcut_items.registerArrowNavigation has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 673, 677, 698, …). 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.

D1 · Cyclomatic Complexity · shortcut_items.jumpPage (cyclomatic 16) · ×1

shortcut_items.jumpPage (cyclomatic 16) packages/blockly/core/shortcut_items.ts:1718 — shortcut_items.jumpPage 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.

D1 · Cyclomatic Complexity · JavascriptGenerator.getAdjusted (cyclomatic 16) · ×1

JavascriptGenerator.getAdjusted (cyclomatic 16) packages/blockly/generators/javascript/javascript_generator.ts:297 — JavascriptGenerator.getAdjusted 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.

D1 · Cyclomatic Complexity · PhpGenerator.getAdjusted (cyclomatic 16) · ×1

PhpGenerator.getAdjusted (cyclomatic 16) packages/blockly/generators/php/php_generator.ts:271 — PhpGenerator.getAdjusted 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.

D1 · Cyclomatic Complexity · RecyclableBlockFlyoutInflater.blockIsRecyclable (cyclomatic 16) · ×1

RecyclableBlockFlyoutInflater.blockIsRecyclable (cyclomatic 16) packages/plugins/continuous-toolbox/src/RecyclableBlockFlyoutInflater.ts:108 — RecyclableBlockFlyoutInflater.blockIsRecyclable 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.

D1 · Cyclomatic Complexity · FixedEdgesMetricsManager.getComputedFixedEdges_ (cyclomatic 16) · ×1

FixedEdgesMetricsManager.getComputedFixedEdges_ (cyclomatic 16) packages/plugins/fixed-edges/src/index.js:82 — FixedEdgesMetricsManager.getComputedFixedEdges_ 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.

D1 · Cyclomatic Complexity · shadow_block_converter.reifyEditedShadowBlock (cyclomatic 16) · ×1

shadow_block_converter.reifyEditedShadowBlock (cyclomatic 16) packages/plugins/shadow-block-converter/src/shadow_block_converter.ts:183 — shadow_block_converter.reifyEditedShadowBlock 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.

D1 · Cyclomatic Complexity · ZoomToFitControl.position (cyclomatic 16) · ×1

ZoomToFitControl.position (cyclomatic 16) packages/plugins/zoom-to-fit/src/index.ts:205 — ZoomToFitControl.position 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.

D1 · Cyclomatic Complexity · exports (cyclomatic 16) · ×1

exports (cyclomatic 16) packages/plugins/dev-scripts/config/webpack.config.js:22 — exports has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×1

Hotspot: packages/blockly/core/dragging/block_drag_strategy.ts packages/blockly/core/dragging/block_drag_strategy.ts:691 — packages/blockly/core/dragging/block_drag_strategy.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BlockDragStrategy.updateConnectionPreview at line 691. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-03..2026-10-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-03 13:25:58 -07:00' --until='2026-10-01 13:25:58 -07:00' --full-history --no-merges -- packages/blockly/core/dragging/block_drag_strategy.ts`: 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.

D15 · Churn × Complexity Hotspots · Repeated repair · ×1

Repeated repair: packages/blockly/core/trashcan.ts packages/blockly/core/trashcan.ts:609 — packages/blockly/core/trashcan.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is Trashcan.cleanBlockJson at line 609), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: drop IFocusableNode from trash and zoom (#10272)”; “fix: Fix display of insertion markers and trashcan lid in RTL (#10211)”; “fix: Fix regression in trashcan lid behavior (#10130)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-03..2026-10-01, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-03 13:25:58 -07:00' --until='2026-10-01 13:25:58 -07:00' --full-history --no-merges -- packages/blockly/core/trashcan.ts`: 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.

D17 · Explicit Debt · TodoComment repeated across 12 files · ×1

TodoComment repeated across 12 files packages/blockly/core/workspace_svg.ts:319 — The identical TodoComment appears in 12 files (26 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 26 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO(b/109816955): remove '!', see go/strict-prop-init-fix.". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)

D17 · Explicit Debt · TodoComment repeated across 13 files · ×1

TodoComment repeated across 13 files packages/blockly/generators/dart/text.ts:139 — The identical TodoComment appears in 13 files (30 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 30 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO(#7600): find better approach than casting to any to override". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)

D17 · Explicit Debt · XxxComment · ×1

XxxComment packages/blockly/generators/dart/lists.ts:522 — // XXX What should the operator precedence be for a `new`? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D2 · Cognitive Complexity · index.Root (cognitive 99) · ×1

index.Root (cognitive 99) packages/docs/src/theme/Root/index.js:14 — index.Root has cognitive complexity 99 (threshold 15). Drivers by points: if/else 38 (78 pts), boolean chains 17, ternaries 1 (3 pts), loops 1 (nesting depth added 42). Most of this is not in the body itself: 0 of the 99 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 175, 113, 95, …). 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.

D2 · Cognitive Complexity · parsing.tokenizeInterpolationInternal (cognitive 77) · ×1

parsing.tokenizeInterpolationInternal (cognitive 77) packages/blockly/core/utils/parsing.ts:24 — parsing.tokenizeInterpolationInternal has cognitive complexity 77 (threshold 15). Drivers by points: if/else 31 (64 pts), boolean chains 6, ternaries 1 (5 pts), loops 2 (nesting depth added 37). 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.

D2 · Cognitive Complexity · RenderInfo.getInRowSpacing_ (cognitive 75) · ×1

RenderInfo.getInRowSpacing_ (cognitive 75) packages/blockly/core/renderers/geras/info.ts:146 — RenderInfo.getInRowSpacing_ has cognitive complexity 75 (threshold 15). Drivers by points: if/else 38 (60 pts), boolean chains 15 (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.

D2 · Cognitive Complexity · RenderInfo.getInRowSpacing_ (cognitive 71) · ×1

RenderInfo.getInRowSpacing_ (cognitive 71) packages/blockly/core/renderers/thrasos/info.ts:91 — RenderInfo.getInRowSpacing_ has cognitive complexity 71 (threshold 15). Drivers by points: if/else 35 (56 pts), boolean chains 15 (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.

D2 · Cognitive Complexity · create_messages.main (cognitive 57) · ×1

create_messages.main (cognitive 57) packages/blockly/scripts/i18n/create_messages.py:49 — create_messages.main has cognitive complexity 57 (threshold 15). Drivers by points: if/else 16 (49 pts), loops 4 (8 pts) (nesting depth added 37). 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.

D2 · Cognitive Complexity · WorkspaceSvg.lookUpFocusableNode (cognitive 55) · ×1

WorkspaceSvg.lookUpFocusableNode (cognitive 55) packages/blockly/core/workspace_svg.ts:2922 — WorkspaceSvg.lookUpFocusableNode has cognitive complexity 55 (threshold 15). Drivers by points: if/else 20 (38 pts), loops 5 (10 pts), boolean chains 7 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · xml.blockToDom (cognitive 55) · ×1

xml.blockToDom (cognitive 55) packages/blockly/core/xml.ts:185 — xml.blockToDom has cognitive complexity 55 (threshold 15). Drivers by points: if/else 26 (41 pts), boolean chains 9, ternaries 2 (4 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lists.lists_getIndex (cognitive 50) · ×1

lists.lists_getIndex (cognitive 50) packages/blockly/generators/dart/lists.ts:91 — lists.lists_getIndex has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (39 pts), boolean chains 8, match/switch 1 (2 pts), ternaries 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.

D2 · Cognitive Complexity · createPlayground (cognitive 46) · ×1

createPlayground (cognitive 46) packages/plugins/dev-tools/src/playground/index.js:86 — createPlayground has cognitive complexity 46 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 17, error handling 3 (6 pts), ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 0 of the 46 points are its own statements and the rest belongs to 29 function items inside it that branch ((anonymous)::updateEditor, (anonymous), (anonymous)::addGenerator, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · loops.controls_for (cognitive 40) · ×1

loops.controls_for (cognitive 40) packages/blockly/generators/python/loops.ts:64 — loops.controls_for has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 8 (nesting depth added 15). Of this number, 37 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lists.lists_getIndex (cognitive 39) · ×1

lists.lists_getIndex (cognitive 39) packages/blockly/generators/php/lists.ts:154 — lists.lists_getIndex has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 15, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · js_to_json.main (cognitive 34) · ×1

js_to_json.main (cognitive 34) packages/blockly/scripts/i18n/js_to_json.py:56 — js_to_json.main has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (32 pts), boolean chains 1, loops 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · xml.domToBlockHeadless (cognitive 33) · ×1

xml.domToBlockHeadless (cognitive 33) packages/blockly/core/xml.ts:981 — xml.domToBlockHeadless has cognitive complexity 33 (threshold 15). Drivers by points: if/else 20 (28 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lists.lists_getIndex (cognitive 33) · ×1

lists.lists_getIndex (cognitive 33) packages/blockly/generators/lua/lists.ts:151 — lists.lists_getIndex has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 12, ternaries 2 (5 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.

D2 · Cognitive Complexity · RenderInfo.adjustXPosition_ (cognitive 32) · ×1

RenderInfo.adjustXPosition_ (cognitive 32) packages/blockly/core/renderers/zelos/info.ts:352 — RenderInfo.adjustXPosition_ has cognitive complexity 32 (threshold 15). Drivers by points: if/else 5 (16 pts), boolean chains 8, loops 2 (4 pts), ternaries 2 (4 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.

D2 · Cognitive Complexity · FieldMultilineInput.updateSize_ (cognitive 32) · ×1

FieldMultilineInput.updateSize_ (cognitive 32) packages/plugins/field-multilineinput/src/field_multilineinput.ts:328 — FieldMultilineInput.updateSize_ has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 15). 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.

D2 · Cognitive Complexity · Block.jsonInit (cognitive 31) · ×1

Block.jsonInit (cognitive 31) packages/blockly/core/block.ts:1756 — Block.jsonInit has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 6, loops 3 (4 pts), ternaries 1 (nesting depth added 2). 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.

D2 · Cognitive Complexity · RenderInfo.finalizeVerticalAlignment_ (cognitive 31) · ×1

RenderInfo.finalizeVerticalAlignment_ (cognitive 31) packages/blockly/core/renderers/zelos/info.ts:610 — RenderInfo.finalizeVerticalAlignment_ has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 5, loops 2 (5 pts), ternaries 2 (4 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.

D2 · Cognitive Complexity · BlockDragStrategy.findTraversalCandidate (cognitive 30) · ×1

BlockDragStrategy.findTraversalCandidate (cognitive 30) packages/blockly/core/dragging/block_drag_strategy.ts:1071 — BlockDragStrategy.findTraversalCandidate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 3 (nesting depth added 12). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Connection.createShadowBlock (cognitive 28) · ×1

Connection.createShadowBlock (cognitive 28) packages/blockly/core/connection.ts:648 — Connection.createShadowBlock has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 2 (nesting depth added 15). 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.

D2 · Cognitive Complexity · lists.lists_getIndex (cognitive 28) · ×1

lists.lists_getIndex (cognitive 28) packages/blockly/generators/python/lists.ts:116 — lists.lists_getIndex has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 3, match/switch 1, ternaries 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.

D2 · Cognitive Complexity · RenderInfo.getNegativeSpacing_ (cognitive 27) · ×1

RenderInfo.getNegativeSpacing_ (cognitive 27) packages/blockly/core/renderers/zelos/info.ts:526 — RenderInfo.getNegativeSpacing_ has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, ternaries 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lists.lists_setIndex (cognitive 27) · ×1

lists.lists_setIndex (cognitive 27) packages/blockly/generators/php/lists.ts:285 — lists.lists_setIndex has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 10, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · options.addGUIControls (cognitive 27) · ×1

options.addGUIControls (cognitive 27) packages/plugins/dev-tools/src/playground/options.js:53 — options.addGUIControls has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 10, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 295, 325, 109, …). 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.

D2 · Cognitive Complexity · VersionRenamer.rename (cognitive 27) · ×1

VersionRenamer.rename (cognitive 27) packages/plugins/migration/bin/rename.js:207 — VersionRenamer.rename has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 2 (6 pts), boolean chains 3, 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.

D2 · Cognitive Complexity · BlockSvg.setWarningText (cognitive 26) · ×1

BlockSvg.setWarningText (cognitive 26) packages/blockly/core/block_svg.ts:1059 — BlockSvg.setWarningText has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 2 (4 pts) (nesting depth added 10). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ScrollbarPair.resize (cognitive 26) · ×1

ScrollbarPair.resize (cognitive 26) packages/blockly/core/scrollbar_pair.ts:102 — ScrollbarPair.resize has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 9 (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.

D2 · Cognitive Complexity · lists.lists_getSublist (cognitive 26) · ×1

lists.lists_getSublist (cognitive 26) packages/blockly/generators/php/lists.ts:398 — lists.lists_getSublist has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 7, match/switch 2 (4 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.

D2 · Cognitive Complexity · BlockMove.run (cognitive 25) · ×1

BlockMove.run (cognitive 25) packages/blockly/core/events/events_block_move.ts:239 — BlockMove.run has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 3, ternaries 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.

D2 · Cognitive Complexity · utils.filter (cognitive 25) · ×1

utils.filter (cognitive 25) packages/blockly/core/events/utils.ts:230 — utils.filter has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 7, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · xml.domToWorkspace (cognitive 25) · ×1

xml.domToWorkspace (cognitive 25) packages/blockly/core/xml.ts:447 — xml.domToWorkspace has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 1 (4 pts), boolean chains 3, 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.

D2 · Cognitive Complexity · lists.lists_getIndex (cognitive 25) · ×1

lists.lists_getIndex (cognitive 25) packages/blockly/generators/javascript/lists.ts:98 — lists.lists_getIndex has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 4, match/switch 1, 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.

D2 · Cognitive Complexity · Backpack.position (cognitive 25) · ×1

Backpack.position (cognitive 25) packages/plugins/workspace-backpack/src/backpack.ts:385 — Backpack.position has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 6, 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.

D2 · Cognitive Complexity · utils.disableOrphans (cognitive 24) · ×1

utils.disableOrphans (cognitive 24) packages/blockly/core/events/utils.ts:432 — utils.disableOrphans has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (8 pts), boolean chains 5 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · shortcut_items.jumpPage (cognitive 24) · ×1

shortcut_items.jumpPage (cognitive 24) packages/blockly/core/shortcut_items.ts:1718 — shortcut_items.jumpPage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 4 (6 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.

D2 · Cognitive Complexity · xml.cloneShadow (cognitive 24) · ×1

xml.cloneShadow (cognitive 24) packages/blockly/core/xml.ts:332 — xml.cloneShadow has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 4, loops 2 (4 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.

D2 · Cognitive Complexity · DartGenerator.scrub_ (cognitive 24) · ×1

DartGenerator.scrub_ (cognitive 24) packages/blockly/generators/dart/dart_generator.ts:227 — DartGenerator.scrub_ has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 13). 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.

D2 · Cognitive Complexity · RecyclableBlockFlyoutInflater.blockIsRecyclable (cognitive 24) · ×1

RecyclableBlockFlyoutInflater.blockIsRecyclable (cognitive 24) packages/plugins/continuous-toolbox/src/RecyclableBlockFlyoutInflater.ts:108 — RecyclableBlockFlyoutInflater.blockIsRecyclable has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (3 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.

D2 · Cognitive Complexity · ZoomToFitControl.position (cognitive 24) · ×1

ZoomToFitControl.position (cognitive 24) packages/plugins/zoom-to-fit/src/index.ts:205 — ZoomToFitControl.position has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, 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.

D2 · Cognitive Complexity · Block.toTokens (cognitive 23) · ×1

Block.toTokens (cognitive 23) packages/blockly/core/block.ts:1636 — Block.toTokens has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, loops 2 (3 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.

D2 · Cognitive Complexity · ContextMenuRegistry.getContextMenuOptions (cognitive 23) · ×1

ContextMenuRegistry.getContextMenuOptions (cognitive 23) packages/blockly/core/contextmenu_registry.ts:84 — ContextMenuRegistry.getContextMenuOptions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 3, ternaries 1 (3 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.

D2 · Cognitive Complexity · CodeGenerator.valueToCode (cognitive 23) · ×1

CodeGenerator.valueToCode (cognitive 23) packages/blockly/core/generator.ts:301 — CodeGenerator.valueToCode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · VersionRenamer.constructor (cognitive 23) · ×1

VersionRenamer.constructor (cognitive 23) packages/plugins/migration/bin/rename.js:149 — VersionRenamer.constructor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 7, loops 2 (4 pts), ternaries 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.

D2 · Cognitive Complexity · PositionedMinimap.setPosition (cognitive 23) · ×1

PositionedMinimap.setPosition (cognitive 23) packages/plugins/workspace-minimap/src/positioned_minimap.ts:107 — PositionedMinimap.setPosition has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, 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.

D2 · Cognitive Complexity · BlockDragStrategy.updateConnectionPreview (cognitive 22) · ×1

BlockDragStrategy.updateConnectionPreview (cognitive 22) packages/blockly/core/dragging/block_drag_strategy.ts:691 — BlockDragStrategy.updateConnectionPreview has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, match/switch 1 (3 pts), ternaries 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.

D2 · Cognitive Complexity · Field.setValue (cognitive 22) · ×1

Field.setValue (cognitive 22) packages/blockly/core/field.ts:1197 — Field.setValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RenderInfo.getInRowSpacing_ (cognitive 22) · ×1

RenderInfo.getInRowSpacing_ (cognitive 22) packages/blockly/core/renderers/common/info.ts:425 — RenderInfo.getInRowSpacing_ has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7 (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.

D2 · Cognitive Complexity · variables.createVariableButtonHandler (cognitive 22) · ×1

variables.createVariableButtonHandler (cognitive 22) packages/blockly/core/variables.ts:358 — variables.createVariableButtonHandler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3 (nesting depth added 9). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 366, 382). 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.

D2 · Cognitive Complexity · tracking.extractFunctionName (cognitive 22) · ×1

tracking.extractFunctionName (cognitive 22) packages/docs/src/utils/tracking.js:70 — tracking.extractFunctionName has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 9 (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.

D2 · Cognitive Complexity · Block.interpolateArguments (cognitive 21) · ×1

Block.interpolateArguments (cognitive 21) packages/blockly/core/block.ts:2046 — Block.interpolateArguments has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 1, 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.

D2 · Cognitive Complexity · RenderInfo.alignRowElements_ (cognitive 21) · ×1

RenderInfo.alignRowElements_ (cognitive 21) packages/blockly/core/renderers/geras/info.ts:358 — RenderInfo.alignRowElements_ has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2, 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.

D2 · Cognitive Complexity · CodeGenerator.blockToCode (cognitive 20) · ×1

CodeGenerator.blockToCode (cognitive 20) packages/blockly/core/generator.ts:235 — CodeGenerator.blockToCode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 2 (4 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.

D2 · Cognitive Complexity · RenderInfo.getSpacerRowHeight_ (cognitive 20) · ×1

RenderInfo.getSpacerRowHeight_ (cognitive 20) packages/blockly/core/renderers/zelos/info.ts:217 — RenderInfo.getSpacerRowHeight_ has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (9 pts), ternaries 1 (2 pts) (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.

D2 · Cognitive Complexity · shortcut_items.registerHeadingNavigation (cognitive 20) · ×1

shortcut_items.registerHeadingNavigation (cognitive 20) packages/blockly/core/shortcut_items.ts:1094 — shortcut_items.registerHeadingNavigation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 2 (3 pts), loops 2 (nesting depth added 3). Most of this is not in the body itself: 0 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 1134, 1099, 1116, …). 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.

D2 · Cognitive Complexity · JavascriptGenerator.scrub_ (cognitive 20) · ×1

JavascriptGenerator.scrub_ (cognitive 20) packages/blockly/generators/javascript/javascript_generator.ts:255 — JavascriptGenerator.scrub_ has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 11). 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.

D2 · Cognitive Complexity · text.text_getSubstring (cognitive 20) · ×1

text.text_getSubstring (cognitive 20) packages/blockly/generators/javascript/text.ts:193 — text.text_getSubstring has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, ternaries 3 (5 pts), match/switch 2 (4 pts), if/else 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LuaGenerator.scrub_ (cognitive 20) · ×1

LuaGenerator.scrub_ (cognitive 20) packages/blockly/generators/lua/lua_generator.ts:196 — LuaGenerator.scrub_ has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 11). 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.

D2 · Cognitive Complexity · text.text_charAt (cognitive 20) · ×1

text.text_charAt (cognitive 20) packages/blockly/generators/lua/text.ts:118 — text.text_charAt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PhpGenerator.scrub_ (cognitive 20) · ×1

PhpGenerator.scrub_ (cognitive 20) packages/blockly/generators/php/php_generator.ts:229 — PhpGenerator.scrub_ has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 11). 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.

D2 · Cognitive Complexity · PythonGenerator.scrub_ (cognitive 20) · ×1

PythonGenerator.scrub_ (cognitive 20) packages/blockly/generators/python/python_generator.ts:280 — PythonGenerator.scrub_ has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 11). 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.

D2 · Cognitive Complexity · exports (cognitive 20) · ×1

exports (cognitive 20) packages/plugins/dev-scripts/config/webpack.config.js:22 — exports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 6, boolean chains 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CodeGenerator.workspaceToCode (cognitive 19) · ×1

CodeGenerator.workspaceToCode (cognitive 19) packages/blockly/core/generator.ts:148 — CodeGenerator.workspaceToCode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 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.

D2 · Cognitive Complexity · RenderedConnection.startTrackingAll (cognitive 19) · ×1

RenderedConnection.startTrackingAll (cognitive 19) packages/blockly/core/rendered_connection.ts:499 — RenderedConnection.startTrackingAll has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 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.

D2 · Cognitive Complexity · WorkspaceSvg.dispose (cognitive 19) · ×1

WorkspaceSvg.dispose (cognitive 19) packages/blockly/core/workspace_svg.ts:927 — WorkspaceSvg.dispose has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 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.

D2 · Cognitive Complexity · lists.lists_getSublist (cognitive 19) · ×1

lists.lists_getSublist (cognitive 19) packages/blockly/generators/javascript/lists.ts:301 — lists.lists_getSublist has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, match/switch 2 (4 pts), ternaries 2 (4 pts), if/else 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · plugin.createPlugin (cognitive 19) · ×1

plugin.createPlugin (cognitive 19) packages/plugins/dev-create/bin/plugin.js:25 — plugin.createPlugin has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7, ternaries 6, boolean chains 5, error handling 1. Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: 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.

D2 · Cognitive Complexity · FieldColourHsvSliders.getAriaValue (cognitive 19) · ×1

FieldColourHsvSliders.getAriaValue (cognitive 19) packages/plugins/field-colour-hsv-sliders/src/field_colour_hsv_sliders.ts:657 — FieldColourHsvSliders.getAriaValue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (16 pts), ternaries 1 (2 pts), boolean chains 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.

D2 · Cognitive Complexity · FixedEdgesMetricsManager.getComputedFixedEdges_ (cognitive 19) · ×1

FixedEdgesMetricsManager.getComputedFixedEdges_ (cognitive 19) packages/plugins/fixed-edges/src/index.js:82 — FixedEdgesMetricsManager.getComputedFixedEdges_ has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4, boolean chains 3 (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.

D2 · Cognitive Complexity · shadow_block_converter.reifyEditedShadowBlock (cognitive 19) · ×1

shadow_block_converter.reifyEditedShadowBlock (cognitive 19) packages/plugins/shadow-block-converter/src/shadow_block_converter.ts:183 — shadow_block_converter.reifyEditedShadowBlock has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2, ternaries 2 (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, 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.

D2 · Cognitive Complexity · BlockSvg.bumpNeighbours (cognitive 18) · ×1

BlockSvg.bumpNeighbours (cognitive 18) packages/blockly/core/block_svg.ts:1614 — BlockSvg.bumpNeighbours has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 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.

D2 · Cognitive Complexity · block_navigation_policy.getBlockNavigationCandidates (cognitive 18) · ×1

block_navigation_policy.getBlockNavigationCandidates (cognitive 18) packages/blockly/core/keyboard_nav/navigation_policies/block_navigation_policy.ts:121 — block_navigation_policy.getBlockNavigationCandidates has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, 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.

D2 · Cognitive Complexity · RenderInfo.getInRowSpacing_ (cognitive 18) · ×1

RenderInfo.getInRowSpacing_ (cognitive 18) packages/blockly/core/renderers/zelos/info.ts:176 — RenderInfo.getInRowSpacing_ has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7 (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.

D2 · Cognitive Complexity · xml.appendDomToWorkspace (cognitive 18) · ×1

xml.appendDomToWorkspace (cognitive 18) packages/blockly/core/xml.ts:555 — xml.appendDomToWorkspace has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), ternaries 1 (2 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.

D2 · Cognitive Complexity · procedures.procedures_defreturn (cognitive 18) · ×1

procedures.procedures_defreturn (cognitive 18) packages/blockly/generators/python/procedures.ts:20 — procedures.procedures_defreturn has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, loops 3, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · BlockSvg.dispose (cognitive 17) · ×1

BlockSvg.dispose (cognitive 17) packages/blockly/core/block_svg.ts:886 — BlockSvg.dispose has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), error handling 1 (nesting depth added 7). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 931). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ConnectionChecker.doDragChecks (cognitive 17) · ×1

ConnectionChecker.doDragChecks (cognitive 17) packages/blockly/core/connection_checker.ts:229 — ConnectionChecker.doDragChecks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, match/switch 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.

D2 · Cognitive Complexity · BlockDragStrategy.getAllConnections (cognitive 17) · ×1

BlockDragStrategy.getAllConnections (cognitive 17) packages/blockly/core/dragging/block_drag_strategy.ts:1223 — BlockDragStrategy.getAllConnections has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FieldInput.onHtmlInputKeyDown_ (cognitive 17) · ×1

FieldInput.onHtmlInputKeyDown_ (cognitive 17) packages/blockly/core/field_input.ts:702 — FieldInput.onHtmlInputKeyDown_ has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 4). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · HorizontalFlyout.getY (cognitive 17) · ×1

HorizontalFlyout.getY (cognitive 17) packages/blockly/core/flyout_horizontal.ts:80 — HorizontalFlyout.getY has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · VerticalFlyout.getX (cognitive 17) · ×1

VerticalFlyout.getX (cognitive 17) packages/blockly/core/flyout_vertical.ts:69 — VerticalFlyout.getX has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FocusManager.constructor (cognitive 17) · ×1

FocusManager.constructor (cognitive 17) packages/blockly/core/focus_manager.ts:117 — FocusManager.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 0 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 121, 159, 166). 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.

D2 · Cognitive Complexity · FocusManager.focusNode (cognitive 17) · ×1

FocusManager.focusNode (cognitive 17) packages/blockly/core/focus_manager.ts:355 — FocusManager.focusNode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2 (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.

D2 · Cognitive Complexity · Gesture.handleUp (cognitive 17) · ×1

Gesture.handleUp (cognitive 17) packages/blockly/core/gesture.ts:484 — Gesture.handleUp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.

D2 · Cognitive Complexity · inject.init (cognitive 17) · ×1

inject.init (cognitive 17) packages/blockly/core/inject.ts:213 — inject.init has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4 (nesting depth added 3). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.

D2 · Cognitive Complexity · Options.parseMoveOptions (cognitive 17) · ×1

Options.parseMoveOptions (cognitive 17) packages/blockly/core/options.ts:204 — Options.parseMoveOptions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ConstantProvider.shapeFor (cognitive 17) · ×1

ConstantProvider.shapeFor (cognitive 17) packages/blockly/core/renderers/zelos/constants.ts:500 — ConstantProvider.shapeFor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, match/switch 2 (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.

D2 · Cognitive Complexity · procedures.procedures_defreturn (cognitive 17) · ×1

procedures.procedures_defreturn (cognitive 17) packages/blockly/generators/php/procedures.ts:20 — procedures.procedures_defreturn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 3, loops 3, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ToolboxSearchCategory.createDom_ (cognitive 17) · ×1

ToolboxSearchCategory.createDom_ (cognitive 17) packages/plugins/toolbox-search/src/toolbox_search.ts:57 — ToolboxSearchCategory.createDom_ has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 71). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · Options.parseZoomOptions (cognitive 16) · ×1

Options.parseZoomOptions (cognitive 16) packages/blockly/core/options.ts:263 — Options.parseZoomOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2. 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.

D2 · Cognitive Complexity · variables.flyoutCategoryBlocks (cognitive 16) · ×1

variables.flyoutCategoryBlocks (cognitive 16) packages/blockly/core/variables.ts:225 — variables.flyoutCategoryBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (6 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1

Duplicated block (7 lines × 2) packages/blockly/scripts/i18n/js_to_json.py:117 — packages/blockly/scripts/i18n/js_to_json.py:117-123 | packages/blockly/scripts/i18n/js_to_json.py:126-132 — 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.

D43 · Malicious Dependencies · Malicious package · ×1

REDACTED

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: blockly — blockly: abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 38 project(s), so it's rigid to change.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — packages/blockly/ runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

P2 · Observability · No structured logging · ×1

No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

R1 · Type Safety · Type Safety · ×1

Type Safety — 570 typed · 248 plain JS — the untyped files are packages/blockly/scripts/build_constants.mjs, packages/blockly/scripts/clean.mjs, packages/blockly/scripts/helpers.js, packages/blockly/scripts/langfiles.mjs, packages/blockly/scripts/lib/exec.mjs, packages/blockly/scripts/lib/fs_utils.mjs (+242 more).

R10 · Code Duplication · Duplication concentrated across 5 sibling directories (56 clone groups) · ×1

Duplication concentrated across 5 sibling directories (56 clone groups) packages/blockly/generators/dart/lists.ts:50 — 56 duplicated blocks under packages/blockly/generators/ have copies in at least two of the sibling directories dart, javascript, lua, php, python — 52 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 56 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 56 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 56 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 17 sibling directories (21 clone groups) · ×1

Duplication concentrated across 17 sibling directories (21 clone groups) packages/plugins/dev-tools/src/toolboxCategories.js:1 — 21 duplicated blocks under packages/plugins/ have copies in at least two of the sibling directories content-highlight, dev-tools, field-angle, field-bitmap, field-colour, field-colour-hsv-sliders (+11 more sibling(s) not listed) — 12 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 4 sibling directories (18 clone groups) · ×1

Duplication concentrated across 4 sibling directories (18 clone groups) packages/blockly/core/renderers/geras/info.ts:111 — 18 duplicated blocks under packages/blockly/core/renderers/ have copies in at least two of the sibling directories common, geras, thrasos, zelos — 17 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 2 sibling directories (15 clone groups) · ×1

Duplication concentrated across 2 sibling directories (15 clone groups) packages/blockly/core/field_input.ts:303 — 15 duplicated blocks under packages/ have copies in at least two of the sibling directories blockly, plugins — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 6 sibling directories (5 clone groups) · ×1

Duplication concentrated across 6 sibling directories (5 clone groups) packages/blockly/core/bubbles/textinput_bubble.ts:127 — 5 duplicated blocks under packages/blockly/core/ have copies in at least two of the sibling directories bubbles, comments, dragging, renderers, serialization, utils — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Wholesale file copy (381 identical lines × 2 files) · ×1

Wholesale file copy (381 identical lines × 2 files) packages/plugins/dev-tools/src/toolboxCategories.js:1 — packages/plugins/dev-tools/src/toolboxCategories.js:1 · packages/plugins/strict-connection-checker/src/toolboxCategories.js:1 — these 2 files are line-for-line copies of one another — 381 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Wholesale file copy (348 identical lines × 2 files) · ×1

Wholesale file copy (348 identical lines × 2 files) packages/plugins/sample-app-ts/src/toolbox.ts:15 — packages/plugins/sample-app-ts/src/toolbox.ts:15 · packages/plugins/sample-app/src/toolbox.js:15 — these 2 files are line-for-line copies of one another — 348 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Duplicated block with local edits (281 matched lines × 2 locations) · ×1

Duplicated block with local edits (281 matched lines × 2 locations) packages/blockly/generators/dart/lists.ts:50 — packages/blockly/generators/dart/lists.ts:50 · packages/blockly/generators/javascript/lists.ts:60 — the two spans are one implementation copied and then locally edited — 1706 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (280 matched lines × 2 locations) · ×1

Duplicated block with local edits (280 matched lines × 2 locations) packages/blockly/generators/javascript/math.ts:51 — packages/blockly/generators/javascript/math.ts:51 · packages/blockly/generators/php/math.ts:49 — the two spans are one implementation copied and then locally edited — 1641 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (276 matched lines × 2 locations) · ×1

Duplicated block with local edits (276 matched lines × 2 locations) packages/blockly/generators/dart/math.ts:24 — packages/blockly/generators/dart/math.ts:24 · packages/blockly/generators/python/math.ts:25 — the two spans are one implementation copied and then locally edited — 1632 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (198 matched lines × 2 locations) · ×1

Duplicated block with local edits (198 matched lines × 2 locations) packages/blockly/generators/dart/text.ts:38 — packages/blockly/generators/dart/text.ts:38 · packages/blockly/generators/javascript/text.ts:89 — the two spans are one implementation copied and then locally edited — 1191 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (150 matched lines × 2 locations) · ×1

Duplicated block with local edits (150 matched lines × 2 locations) packages/blockly/generators/lua/math.ts:24 — packages/blockly/generators/lua/math.ts:24 · packages/blockly/generators/php/math.ts:28 — the two spans are one implementation copied and then locally edited — 994 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (149 matched lines × 2 locations) · ×1

Duplicated block with local edits (149 matched lines × 2 locations) packages/blockly/core/renderers/geras/info.ts:111 — packages/blockly/core/renderers/geras/info.ts:111 · packages/blockly/core/renderers/thrasos/info.ts:56 — the two spans are one implementation copied and then locally edited — 1020 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (143 matched lines × 2 locations) · ×1

Duplicated block with local edits (143 matched lines × 2 locations) packages/blockly/generators/php/lists.ts:128 — packages/blockly/generators/php/lists.ts:128 · packages/blockly/generators/python/lists.ts:96 — the two spans are one implementation copied and then locally edited — 872 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (130 matched lines × 2 locations) · ×1

Duplicated block with local edits (130 matched lines × 2 locations) packages/blockly/generators/javascript/javascript_generator.ts:80 — packages/blockly/generators/javascript/javascript_generator.ts:80 · packages/blockly/generators/php/php_generator.ts:71 — the two spans are one implementation copied and then locally edited — 849 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (123 matched lines × 2 locations) · ×1

Duplicated block with local edits (123 matched lines × 2 locations) packages/blockly/generators/javascript/math.ts:23 — packages/blockly/generators/javascript/math.ts:23 · packages/blockly/generators/lua/math.ts:23 — the two spans are one implementation copied and then locally edited — 820 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (117 lines × 2 locations) · ×1

Duplicated block (117 lines × 2 locations) packages/plugins/block-dynamic-connection/src/dynamic_list_create.ts:39 — packages/plugins/block-dynamic-connection/src/dynamic_list_create.ts:39 · packages/plugins/block-dynamic-connection/src/dynamic_text_join.ts:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (116 matched lines × 2 locations) · ×1

Duplicated block with local edits (116 matched lines × 2 locations) packages/blockly/generators/python/lists.ts:51 — packages/blockly/generators/python/lists.ts:51 · packages/blockly/generators/python/text.ts:98 — the two spans are one implementation copied and then locally edited — 692 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (99 matched lines × 2 locations) · ×1

Duplicated block with local edits (99 matched lines × 2 locations) packages/blockly/generators/javascript/text.ts:21 — packages/blockly/generators/javascript/text.ts:21 · packages/blockly/generators/python/text.ts:32 — the two spans are one implementation copied and then locally edited — 748 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (94 lines × 2 locations) · ×1

Duplicated block (94 lines × 2 locations) packages/blockly/generators/dart/loops.ts:79 — packages/blockly/generators/dart/loops.ts:79 · packages/blockly/generators/javascript/loops.ts:85 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

R10 · Code Duplication · Wholesale file copy (93 identical lines × 2 files) · ×1

Wholesale file copy (93 identical lines × 2 files) packages/blockly/generators/dart/loops.ts:13 — packages/blockly/generators/dart/loops.ts:13 · packages/blockly/generators/php/loops.ts:13 — these 2 files are line-for-line copies of one another — 93 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Duplicated block with local edits (92 matched lines × 2 locations) · ×1

Duplicated block with local edits (92 matched lines × 2 locations) packages/blockly/generators/javascript/lists.ts:285 — packages/blockly/generators/javascript/lists.ts:285 · packages/blockly/generators/javascript/text.ts:44 — the two spans are one implementation copied and then locally edited — 514 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Wholesale file copy (85 identical lines × 3 files) · ×1

Wholesale file copy (85 identical lines × 3 files) packages/blockly/generators/dart/logic.ts:13 — packages/blockly/generators/dart/logic.ts:13 · packages/blockly/generators/javascript/logic.ts:13 · packages/blockly/generators/php/logic.ts:13 — these 3 files are line-for-line copies of one another — 85 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Duplicated block with local edits (80 matched lines × 2 locations) · ×1

Duplicated block with local edits (80 matched lines × 2 locations) packages/blockly/core/bubbles/textinput_bubble.ts:127 — packages/blockly/core/bubbles/textinput_bubble.ts:127 · packages/blockly/core/comments/comment_view.ts:251 — the two spans are one implementation copied and then locally edited — 365 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (79 matched lines × 2 locations) · ×1

Duplicated block with local edits (79 matched lines × 2 locations) packages/plugins/block-plus-minus/src/list_create.js:37 — packages/plugins/block-plus-minus/src/list_create.js:37 · packages/plugins/block-plus-minus/src/text_join.js:15 — the two spans are one implementation copied and then locally edited — 445 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (76 matched lines × 2 locations) · ×1

Duplicated block with local edits (76 matched lines × 2 locations) packages/blockly/blocks/variables.ts:69 — packages/blockly/blocks/variables.ts:69 · packages/blockly/blocks/variables_dynamic.ts:69 — the two spans are one implementation copied and then locally edited — 419 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (75 lines × 2 locations) · ×1

Duplicated block (75 lines × 2 locations) packages/blockly/generators/javascript/procedures.ts:23 — packages/blockly/generators/javascript/procedures.ts:23 · packages/blockly/generators/python/procedures.ts:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

R10 · Code Duplication · Duplicated block (74 lines × 2 locations) · ×1

Duplicated block (74 lines × 2 locations) packages/blockly/generators/lua/procedures.ts:23 — packages/blockly/generators/lua/procedures.ts:23 · packages/blockly/generators/python/procedures.ts:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

R10 · Code Duplication · Duplicated block with local edits (68 matched lines × 2 locations) · ×1

Duplicated block with local edits (68 matched lines × 2 locations) packages/blockly/generators/lua/text.ts:18 — packages/blockly/generators/lua/text.ts:18 · packages/blockly/generators/php/text.ts:18 — the two spans are one implementation copied and then locally edited — 551 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (68 lines × 2 locations) · ×1

Duplicated block (68 lines × 2 locations) packages/blockly/generators/php/procedures.ts:20 — packages/blockly/generators/php/procedures.ts:20 · packages/blockly/generators/python/procedures.ts:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (64 matched lines × 2 locations) · ×1

Duplicated block with local edits (64 matched lines × 2 locations) packages/blockly/core/icons/mutator_icon.ts:127 — packages/blockly/core/icons/mutator_icon.ts:127 · packages/blockly/core/icons/warning_icon.ts:100 — the two spans are one implementation copied and then locally edited — 317 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Wholesale file copy (63 identical lines × 2 files) · ×1

Wholesale file copy (63 identical lines × 2 files) packages/blockly/generators/dart/procedures.ts:13 — packages/blockly/generators/dart/procedures.ts:13 · packages/blockly/generators/javascript/procedures.ts:13 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Duplicated block with local edits (61 matched lines × 2 locations) · ×1

Duplicated block with local edits (61 matched lines × 2 locations) packages/blockly/core/renderers/geras/info.ts:317 — packages/blockly/core/renderers/geras/info.ts:317 · packages/blockly/core/renderers/thrasos/info.ts:242 — the two spans are one implementation copied and then locally edited — 360 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (60 lines × 2 locations) · ×1

Duplicated block (60 lines × 2 locations) packages/blockly/core/events/events_var_create.ts:28 — packages/blockly/core/events/events_var_create.ts:28 · packages/blockly/core/events/events_var_delete.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (55 matched lines × 2 locations) · ×1

Duplicated block with local edits (55 matched lines × 2 locations) packages/blockly/blocks/lists.ts:821 — packages/blockly/blocks/lists.ts:821 · packages/blockly/blocks/text.ts:243 — the two spans are one implementation copied and then locally edited — 431 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (55 lines × 2 locations) · ×1

Duplicated block (55 lines × 2 locations) packages/blockly/generators/lua/lua_generator.ts:117 — packages/blockly/generators/lua/lua_generator.ts:117 · packages/blockly/generators/php/php_generator.ts:150 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R2 · Cyclomatic Complexity · Complex function getInRowSpacing_ (cyclomatic 60, cognitive 81) · ×1

Complex function getInRowSpacing_ (cyclomatic 60, cognitive 81) packages/blockly/core/renderers/geras/info.ts:146 — getInRowSpacing_ has cyclomatic complexity 60 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function getInRowSpacing_ (cyclomatic 55, cognitive 71) · ×1

Complex function getInRowSpacing_ (cyclomatic 55, cognitive 71) packages/blockly/core/renderers/thrasos/info.ts:91 — getInRowSpacing_ has cyclomatic complexity 55 and cognitive complexity 71; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function blockToDom (cyclomatic 37, cognitive 55) · ×1

Complex function blockToDom (cyclomatic 37, cognitive 55) packages/blockly/core/xml.ts:185 — blockToDom has cyclomatic complexity 37 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lists_getIndex (cyclomatic 37, cognitive 39) · ×1

Complex function lists_getIndex (cyclomatic 37, cognitive 39) packages/blockly/generators/php/lists.ts:154 — lists_getIndex has cyclomatic complexity 37 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lists_getIndex (cyclomatic 36, cognitive 50) · ×1

Complex function lists_getIndex (cyclomatic 36, cognitive 50) packages/blockly/generators/dart/lists.ts:91 — lists_getIndex has cyclomatic complexity 36 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function tokenizeInterpolationInternal (cyclomatic 35, cognitive 77) · ×1

Complex function tokenizeInterpolationInternal (cyclomatic 35, cognitive 77) packages/blockly/core/utils/parsing.ts:24 — tokenizeInterpolationInternal has cyclomatic complexity 35 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lookUpFocusableNode (cyclomatic 35, cognitive 56) · ×1

Complex function lookUpFocusableNode (cyclomatic 35, cognitive 56) packages/blockly/core/workspace_svg.ts:2922 — lookUpFocusableNode has cyclomatic complexity 35 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function resize (cyclomatic 29, cognitive 35) · ×1

Complex function resize (cyclomatic 29, cognitive 35) packages/blockly/core/scrollbar_pair.ts:102 — resize has cyclomatic complexity 29 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function jsonInit (cyclomatic 29, cognitive 31) · ×1

Complex function jsonInit (cyclomatic 29, cognitive 31) packages/blockly/core/block.ts:1756 — jsonInit has cyclomatic complexity 29 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function math_single (cyclomatic 28, cognitive 15) · ×1

Complex function math_single (cyclomatic 28, cognitive 15) packages/blockly/generators/dart/math.ts:69 — math_single has cyclomatic complexity 28 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function filter (cyclomatic 26, cognitive 26) · ×1

Complex function filter (cyclomatic 26, cognitive 26) packages/blockly/core/events/utils.ts:230 — filter has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lists_setIndex (cyclomatic 26, cognitive 26) · ×1

Complex function lists_setIndex (cyclomatic 26, cognitive 26) packages/blockly/generators/php/lists.ts:285 — lists_setIndex has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function constructor (cyclomatic 25, cognitive 35) · ×1

Complex function constructor (cyclomatic 25, cognitive 35) packages/blockly/core/options.ts:83 — constructor has cyclomatic complexity 25 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lists_getIndex (cyclomatic 25, cognitive 28) · ×1

Complex function lists_getIndex (cyclomatic 25, cognitive 28) packages/blockly/generators/python/lists.ts:116 — lists_getIndex has cyclomatic complexity 25 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lists_getIndex (cyclomatic 25, cognitive 25) · ×1

Complex function lists_getIndex (cyclomatic 25, cognitive 25) packages/blockly/generators/javascript/lists.ts:98 — lists_getIndex has cyclomatic complexity 25 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function lists_getIndex (cyclomatic 24, cognitive 44) · ×1

Complex function lists_getIndex (cyclomatic 24, cognitive 44) packages/blockly/generators/lua/lists.ts:151 — lists_getIndex has cyclomatic complexity 24 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function text_getSubstring (cyclomatic 24, cognitive 24) · ×1

Complex function text_getSubstring (cyclomatic 24, cognitive 24) packages/blockly/generators/javascript/text.ts:193 — text_getSubstring has cyclomatic complexity 24 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function math_single (cyclomatic 24, cognitive 10) · ×1

Complex function math_single (cyclomatic 24, cognitive 10) packages/blockly/generators/python/math.ts:62 — math_single has cyclomatic complexity 24 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R3 · Large Files · Large Files · ×1

Large Files — 80 file(s) over 400 lines (counted as significant lines — blank lines excluded — over production source only, tests excluded), largest first: packages/blockly/core/workspace_svg.ts (2833), packages/blockly/core/block.ts (2361), packages/blockly/core/shortcut_items.ts (1892), packages/blockly/core/block_svg.ts (1856), packages/blockly/core/field.ts (1515), packages/blockly/blocks/procedures.ts (1307) (+74 more).

R7 · Dead Code · Dead file (~1356 LoC) · ×1

Dead file (~1356 LoC) packages/blockly/blocks/procedures.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/procedures.ts, packages/blockly/generators/javascript/procedures.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~1104 LoC) · ×1

Dead file (~1104 LoC) packages/blockly/blocks/lists.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/lists.ts, packages/blockly/generators/javascript/lists.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~1056 LoC) · ×1

Dead file (~1056 LoC) packages/blockly/blocks/text.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/text.ts, packages/blockly/generators/javascript/text.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~715 LoC) · ×1

Dead file (~715 LoC) packages/blockly/blocks/logic.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/blocks/blocks.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~638 LoC) · ×1

Dead file (~638 LoC) packages/blockly/blocks/math.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/blocks/blocks.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~585 LoC) · ×1

Dead file (~585 LoC) packages/blockly/generators/php/lists.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~559 LoC) · ×1

Dead file (~559 LoC) packages/blockly/generators/dart/math.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/dart.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~525 LoC) · ×1

Dead file (~525 LoC) packages/blockly/generators/dart/lists.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/dart.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~473 LoC) · ×1

Dead file (~473 LoC) packages/blockly/generators/lua/math.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/lua.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~465 LoC) · ×1

Dead file (~465 LoC) packages/blockly/generators/javascript/lists.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/javascript.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~450 LoC) · ×1

Dead file (~450 LoC) packages/blockly/generators/javascript/math.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/javascript.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~445 LoC) · ×1

Dead file (~445 LoC) packages/blockly/generators/lua/lists.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/lua.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~434 LoC) · ×1

Dead file (~434 LoC) packages/blockly/generators/python/math.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/python.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~418 LoC) · ×1

Dead file (~418 LoC) packages/blockly/generators/javascript/text.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/javascript.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~415 LoC) · ×1

Dead file (~415 LoC) packages/blockly/blocks/loops.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (packages/blockly/blocks/blocks.ts, packages/blockly/generators/dart/loops.ts, packages/blockly/generators/javascript/loops.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~408 LoC) · ×1

Dead file (~408 LoC) packages/blockly/generators/php/math.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~405 LoC) · ×1

Dead file (~405 LoC) packages/blockly/generators/dart/text.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/dart.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~398 LoC) · ×1

Dead file (~398 LoC) packages/blockly/generators/python/lists.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/python.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~380 LoC) · ×1

Dead file (~380 LoC) packages/blockly/generators/lua/text.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/lua.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~355 LoC) · ×1

Dead file (~355 LoC) packages/blockly/generators/python/python_generator.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/python.ts, packages/blockly/generators/python/lists.ts, packages/blockly/generators/python/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~346 LoC) · ×1

Dead file (~346 LoC) packages/blockly/generators/javascript/javascript_generator.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/javascript.ts, packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/javascript/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~338 LoC) · ×1

Dead file (~338 LoC) packages/blockly/generators/python/text.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/python.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~321 LoC) · ×1

Dead file (~321 LoC) packages/blockly/generators/dart/dart_generator.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/dart.ts, packages/blockly/generators/dart/lists.ts, packages/blockly/generators/dart/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~320 LoC) · ×1

Dead file (~320 LoC) packages/blockly/generators/php/php_generator.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/php.ts, packages/blockly/generators/php/lists.ts, packages/blockly/generators/php/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~315 LoC) · ×1

Dead file (~315 LoC) packages/blockly/generators/php/text.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~251 LoC) · ×1

Dead file (~251 LoC) packages/blockly/generators/python/loops.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/python.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~245 LoC) · ×1

Dead file (~245 LoC) packages/blockly/generators/javascript/loops.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/javascript.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~225 LoC) · ×1

Dead file (~225 LoC) packages/blockly/generators/lua/lua_generator.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (packages/blockly/generators/lua.ts, packages/blockly/generators/lua/lists.ts, packages/blockly/generators/lua/logic.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~218 LoC) · ×1

Dead file (~218 LoC) packages/blockly/generators/php/loops.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/php.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~217 LoC) · ×1

Dead file (~217 LoC) packages/blockly/generators/dart/loops.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/dart.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~182 LoC) · ×1

Dead file (~182 LoC) packages/blockly/blocks/variables.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/blocks/blocks.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~155 LoC) · ×1

Dead file (~155 LoC) packages/blockly/generators/javascript/logic.ts — no import path from any entry point (105 application, 17 tooling, 274 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/blockly/generators/javascript.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R8 · Dependency Hygiene · Unused dependency '@nx/js' · ×1

Unused dependency '@nx/js' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency 'conventional-changelog-conventionalcommits' · ×1

Unused dependency 'conventional-changelog-conventionalcommits' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

Minor — 43 finding(s)

X10 · Duplicated predicate · Duplicated predicate · ×25

Duplicated predicate packages/blockly/blocks/lists.ts:274 — `!this.itemCount_ && !this.getInput('EMPTY')` appears character-identically in 2 files — packages/blockly/blocks/lists.ts, packages/blockly/blocks/text.ts. 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 packages/blockly/generators/dart/lists.ts:98 — `block.getFieldValue('WHERE') || 'FROM_START'` appears character-identically in 10 files — packages/blockly/generators/dart/lists.ts, packages/blockly/generators/dart/text.ts, packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/javascript/text.ts. 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 packages/blockly/generators/dart/logic.ts:48 — `block.getInput('ELSE') || generator.STATEMENT_SUFFIX` appears character-identically in 5 files — packages/blockly/generators/dart/logic.ts, packages/blockly/generators/javascript/logic.ts, packages/blockly/generators/lua/logic.ts, packages/blockly/generators/php/logic.ts. 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 packages/blockly/generators/dart/logic.ts:83 — `generator.valueToCode(block, 'A', order) || '0'` appears character-identically in 9 files — packages/blockly/generators/dart/logic.ts, packages/blockly/generators/dart/math.ts, packages/blockly/generators/javascript/logic.ts, packages/blockly/generators/javascript/math.ts. 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 packages/blockly/generators/dart/text.ts:45 — `generator.valueToCode(block, 'ADD' + i, Order.NONE) || "''"` appears character-identically in 4 files — packages/blockly/generators/dart/text.ts, packages/blockly/generators/lua/text.ts, packages/blockly/generators/php/text.ts, packages/blockly/generators/python/text.ts. 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 packages/blockly/generators/dart/lists.ts:37 — `generator.valueToCode(block, 'ADD' + i, Order.NONE) || 'null'` appears character-identically in 4 files — packages/blockly/generators/dart/lists.ts, packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/php/lists.ts, packages/docs/docs/codelabs/custom-mutator/complete-code/src/generators/javascript.js. 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 packages/blockly/generators/lua/text.ts:33 — `generator.valueToCode(block, 'ADD0', Order.NONE) || "''"` appears character-identically in 3 files — packages/blockly/generators/lua/text.ts, packages/blockly/generators/php/text.ts, packages/blockly/generators/python/text.ts. 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 packages/blockly/generators/dart/procedures.ts:97 — `generator.valueToCode(block, 'ARG' + i, Order.NONE) || 'null'` appears character-identically in 3 files — packages/blockly/generators/dart/procedures.ts, packages/blockly/generators/javascript/procedures.ts, packages/blockly/generators/php/procedures.ts. 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 packages/blockly/generators/lua/lists.ts:171 — `generator.valueToCode(block, 'AT', atOrder) || '1'` appears character-identically in 2 files — packages/blockly/generators/lua/lists.ts, packages/blockly/generators/lua/text.ts. 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 packages/blockly/generators/dart/logic.ts:84 — `generator.valueToCode(block, 'B', order) || '0'` appears character-identically in 9 files — packages/blockly/generators/dart/logic.ts, packages/blockly/generators/dart/math.ts, packages/blockly/generators/javascript/logic.ts, packages/blockly/generators/javascript/math.ts. 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 packages/blockly/generators/dart/logic.ts:122 — `generator.valueToCode(block, 'BOOL', order) || 'true'` appears character-identically in 3 files — packages/blockly/generators/dart/logic.ts, packages/blockly/generators/javascript/logic.ts, packages/blockly/generators/php/logic.ts. 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 packages/blockly/generators/dart/loops.ts:85 — `generator.valueToCode(block, 'BY', Order.ASSIGNMENT) || '1'` appears character-identically in 3 files — packages/blockly/generators/dart/loops.ts, packages/blockly/generators/javascript/loops.ts, packages/blockly/generators/php/loops.ts. 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 packages/blockly/generators/lua/loops.ts:101 — `generator.valueToCode(block, 'BY', Order.NONE) || '1'` appears character-identically in 2 files — packages/blockly/generators/lua/loops.ts, packages/blockly/generators/python/loops.ts. 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 packages/blockly/generators/dart/procedures.ts:120 — `generator.valueToCode(block, 'CONDITION', Order.NONE) || 'false'` appears character-identically in 4 files — packages/blockly/generators/dart/procedures.ts, packages/blockly/generators/javascript/procedures.ts, packages/blockly/generators/lua/procedures.ts, packages/blockly/generators/php/procedures.ts. 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 packages/blockly/generators/dart/lists.ts:496 — `generator.valueToCode(block, 'DELIM', Order.NONE) || "''"` appears character-identically in 4 files — packages/blockly/generators/dart/lists.ts, packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/lua/lists.ts, packages/blockly/generators/php/lists.ts. 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 packages/blockly/generators/javascript/math.ts:216 — `generator.valueToCode(block, 'DELTA', Order.ADDITION) || '0'` appears character-identically in 2 files — packages/blockly/generators/javascript/math.ts, packages/blockly/generators/php/math.ts. 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 packages/blockly/generators/dart/math.ts:250 — `generator.valueToCode(block, 'DELTA', Order.ADDITIVE) || '0'` appears character-identically in 3 files — packages/blockly/generators/dart/math.ts, packages/blockly/generators/lua/math.ts, packages/blockly/generators/python/math.ts. 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 packages/blockly/generators/javascript/math.ts:379 — `generator.valueToCode(block, 'DIVIDEND', Order.MODULUS) || '0'` appears character-identically in 2 files — packages/blockly/generators/javascript/math.ts, packages/blockly/generators/php/math.ts. 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 packages/blockly/generators/dart/math.ts:472 — `generator.valueToCode(block, 'DIVIDEND', Order.MULTIPLICATIVE) || '0'` appears character-identically in 3 files — packages/blockly/generators/dart/math.ts, packages/blockly/generators/lua/math.ts, packages/blockly/generators/python/math.ts. 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 packages/blockly/generators/javascript/math.ts:205 — `generator.valueToCode(block, 'DIVISOR', Order.MODULUS) || '0'` appears character-identically in 2 files — packages/blockly/generators/javascript/math.ts, packages/blockly/generators/php/math.ts. 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 packages/blockly/generators/dart/math.ts:236 — `generator.valueToCode(block, 'DIVISOR', Order.MULTIPLICATIVE) || '0'` appears character-identically in 3 files — packages/blockly/generators/dart/math.ts, packages/blockly/generators/lua/math.ts, packages/blockly/generators/python/math.ts. 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 packages/blockly/generators/dart/logic.ts:154 — `generator.valueToCode(block, 'ELSE', Order.CONDITIONAL) || 'null'` appears character-identically in 3 files — packages/blockly/generators/dart/logic.ts, packages/blockly/generators/javascript/logic.ts, packages/blockly/generators/php/logic.ts. 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 packages/blockly/generators/dart/lists.ts:81 — `generator.valueToCode(block, 'FIND', Order.NONE) || "''"` appears character-identically in 9 files — packages/blockly/generators/dart/lists.ts, packages/blockly/generators/dart/text.ts, packages/blockly/generators/javascript/lists.ts, packages/blockly/generators/javascript/text.ts. 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 packages/blockly/generators/dart/loops.ts:83 — `generator.valueToCode(block, 'FROM', Order.ASSIGNMENT) || '0'` appears character-identically in 3 files — packages/blockly/generators/dart/loops.ts, packages/blockly/generators/javascript/loops.ts, packages/blockly/generators/php/loops.ts. 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 packages/blockly/generators/dart/text.ts:388 — `generator.valueToCode(block, 'FROM', Order.NONE) || "''"` appears character-identically in 5 files — packages/blockly/generators/dart/text.ts, packages/blockly/generators/javascript/text.ts, packages/blockly/generators/lua/text.ts, packages/blockly/generators/php/text.ts. 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.

D16 · Bus Factor · Off-boarding risk · ×2

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 17 significant file(s) lose their only recent owner: packages/blockly/core/variables.ts, packages/plugins/field-bitmap/src/field-bitmap.ts, packages/blockly/core/keyboard_nav/keyboard_mover.ts, packages/blockly/core/connection_db.ts, packages/blockly/core/utils/style.ts, packages/blockly/core/insertion_marker.ts, packages/blockly/core/keyboard_nav/navigators/toolbox_navigator.ts, packages/blockly/core/keyboard_nav/navigators/flyout_navigator.ts (+9 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/plugins/workspace-minimap/src/minimap.ts, packages/plugins/workspace-minimap/src/focus_region.ts, packages/plugins/block-dynamic-connection/src/connection_previewer.ts. Pair on, review, or document these before any departure.

D19 · Documentation Quality · Documentation · ×2

Documentation: no architecture or design documentation packages/plugins/field-colour-hsv-sliders/README.md — The field-colour-hsv-sliders README is a plugin usage doc but there are no architecture or design docs describing how HSV sliders interact with the Blockly API. Add an architecture document explaining the HSV slider type's registration, its JSON shape, and how it maps to the underlying colour model.
Documentation: no project overview packages/plugins/field-slider/README.md — The overview is a single sentence ('A Blockly slider field') with no description of what it does. Expand to say what parameters and configurations this field supports, or link to the referenced FieldNumber docs.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (25 single-owned of 341 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 341 of the 563 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split packages/blockly · ×1

Split packages/blockly — A huge catch-all name that is itself a single cohesive project whose namespaces are all renderers/serialization and generators for the same core. Suggested:

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D30 · Dependency Vulnerabilities · Low CVE · ×1

REDACTED

D30 · Dependency Vulnerabilities · Low vulnerability · ×1

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 93 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/blockly/generators/dart/math.ts, packages/blockly/generators/php/lists.ts, packages/blockly/generators/dart/lists.ts, packages/blockly/core/renderers/geras/info.ts, packages/blockly/core/metrics_manager.ts, packages/blockly/core/extensions.ts, packages/blockly/generators/python/math.ts, packages/blockly/generators/javascript/lists.ts (and 85 more) (95 orphaned of 341 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 341 of the 563 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 23794 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.

X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1

Silent fallback default on parse failure packages/blockly/scripts/i18n/create_messages.py:34 — `string_is_ascii` returns `False` when `TypeError` 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.

X7 · Silent fallback defaults · Silent fallback default in catch · ×1

Silent fallback default in catch packages/blockly/tests/generators/golden/generated.py:1182 — `try_float` (in `lists_sort`) swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. 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.

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a902661327414fadbd72240515c18d7f/history.json --exit-code 0 --source .	3	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a902661327414fadbd72240515c18d7f/tree.json --exit-code 0 --source .	2	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	35	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	21	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packages/blockly/core/config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	1	artifacts/raw/trivy-fs.json

Run 01a0f9ba-8c45-76d8-a7ce-c3848f36401d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

RaspberryPiFoundation/blockly

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 65% · Adequate ·

At a glance — Architecture · 63% · Adequate · gated by R9 ·

At a glance — Maturity · 68% · Adequate · gated by M2 ·

At a glance — Readiness · 40% · Weak · gated by R8, P2, P3 ·

At a glance — Security · 41% · Weak · gated by D29, D30, D36, D43 ·

At a glance — Accessibility · 40% · Weak · gated by AC3 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts