Public report of helsingborg-stad/Municipio, published 16 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 19:13 UTC · Survey ID cd_571643bd87544a53b0aaf6b07ce032c3

helsingborg-stad/Municipio

Measured 16 November 2026, 19:08 UTC, at code version 861257f

First survey, so nothing to compare with yet Code coverage: not measuredTest reliability: not measured

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureRepoBuildError).

Test reliability is not measured: The JS/TS suite's lockfile was refused.

CAI score 43.6out of 100 Weak
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 140,585 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Production Readiness, 26.4

Findings by how serious they are

82 critical 570 serious 128 minor

15 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 19:08 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

68of 68 dimensions measured by tools.
754of 780 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
68dimensions across 7 lenses, read from 140,585 lines of product code in 2 projects.
Chapters

Executive summary

helsingborg-stad/Municipio falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 43.6 out of 100 and is rated Weak, and 62 of its 82 critical findings are security problems.

Production Readiness, at 26.4, is the weakest lens and counts most in the score. The best first step is replacing the three packages under a banned licence, worth about 12.7 points. Adding automated security scanning would lift Production Readiness itself, worth about 4.4 points. Raising Production Readiness to 70 would lift the score to about 57.4.

Twenty-eight known security holes in the packages the code depends on can be used by attackers. Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and seven secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the four passwords or keys in the code's history need replacing, with the old ones switched off. The four parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.

The product code is 140,585 lines, about €160,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 26.4 · counts for 46%Accessibility 52.1 · counts for 25%Code Health 55.6 · counts for 14%Security and Compliance 57.6 · counts for 8%Maturity 71.7 · counts for 4%Architecture 91.8 · counts for 2%Performance 100.0 · counts for 1%

If Production Readiness rose from 26.4 to 70, the lowest score rated Strong, the score would rise from 43.6 to about 57.4.

Code composition: what the lines of code are
Product code 79%Tests 21%
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€52,000 to €260,000, for 863 to 2,738 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 140,585 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 3 Banned license finding(s) in License Compliance.
Raises the score by about 12.7 points · Low effort · License Compliance
2
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 4.4 points · Medium effort · Security & performance tooling
3
Add tests that import the unreached modules (directly or through their public entry).
Raises the score by about 2.6 points · Medium effort · Test Coverage

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 26.4 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 12.7 points for low effort, because it clears the 3 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

557 modules, with 522 dependencies between them. 7 loops run through 16 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 517 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Modularity.Module.Posts.Helper.GetPosts2 Municipio.Api3 Municipio.Controller.Navigation4 Municipio.Helper.SiteSwitcher5 Municipio.HooksRegistrar6 Municipio.ImageConvert.Logging7 Municipio.Kulturkortet.MunicipioAuth.navigation8 Municipio.Kulturkortet.MunicipioAuth.user9 Municipio.PostObject10 Municipio.PostsList.Config.AppearanceConfig11 Municipio.PostsList.Config.FilterConfig12 Municipio.PostsList.QueryVars13 Municipio.ProgressReporter14 Municipio.SchemaData.Config.Contracts15 Municipio.SchemaData.ExternalContent.Filter.FilterDefinition.Contracts16 Municipio.SchemaData.ExternalContent.SourceReaders17 Municipio.SearchIndex.Config18 Municipio.Upgrade19 Modularity20 Municipio.Helper.User21 Municipio.ImageConvert.Strategy22 Municipio.Kulturkortet.MunicipioAuth.views23 Municipio.PostsList.Config.GetPostsConfig24 Municipio.PostsList.ViewCallableProviders25 Municipio.SchemaData.ExternalContent.Config26 Municipio.SchemaData.Utils27 Municipio.SearchIndex.Provider28 Modularity.Module.Posts29 Municipio.Controller30 Municipio.Controller.Archive31 Municipio.ImageConvert32 Municipio.PostsList33 Municipio.SchemaData.ExternalContent.SyncHandler34 Municipio.SchemaData.SchemaObjectFromPost35 Municipio.SearchIndex.Admin.Indexing36 Municipio.UserGroup37 Municipio.PostObject.Decorators38 Municipio.PostObject.Factory39 Municipio40 Municipio.SchemaData.SchemaPropertiesForm.StoreFormFieldValues
1 Modularity.Module.Posts.Helper.GetPosts
2 Municipio.Api
3 Municipio.Controller.Navigation
4 Municipio.Helper.SiteSwitcher
5 Municipio.HooksRegistrar
6 Municipio.ImageConvert.Logging
7 Municipio.Kulturkortet.MunicipioAuth.navigation
8 Municipio.Kulturkortet.MunicipioAuth.user
9 Municipio.PostObject
10 Municipio.PostsList.Config.AppearanceConfig
11 Municipio.PostsList.Config.FilterConfig
12 Municipio.PostsList.QueryVars
13 Municipio.ProgressReporter
14 Municipio.SchemaData.Config.Contracts
15 Municipio.SchemaData.ExternalContent.Filter.FilterDefinition.Contracts
16 Municipio.SchemaData.ExternalContent.SourceReaders
17 Municipio.SearchIndex.Config
18 Municipio.Upgrade
19 Modularity1
20 Municipio.Helper.User2
21 Municipio.ImageConvert.Strategy11
22 Municipio.Kulturkortet.MunicipioAuth.views11
23 Municipio.PostsList.Config.GetPostsConfig1
24 Municipio.PostsList.ViewCallableProviders24
25 Municipio.SchemaData.ExternalContent.Config5
26 Municipio.SchemaData.Utils11
27 Municipio.SearchIndex.Provider1
28 Modularity.Module.Posts21
29 Municipio.Controller10515
30 Municipio.Controller.Archive4323
31 Municipio.ImageConvert521
32 Municipio.PostsList1111
33 Municipio.SchemaData.ExternalContent.SyncHandler1111
34 Municipio.SchemaData.SchemaObjectFromPost22
35 Municipio.SearchIndex.Admin.Indexing232
36 Municipio.UserGroup181
37 Municipio.PostObject.Decorators131
38 Municipio.PostObject.Factory21
39 Municipio211121
40 Municipio.SchemaData.SchemaPropertiesForm.StoreFormFieldValues111
Uses a module listed above itPart of a loopThe module itself
1 Modularity.Module.Posts.Helper.GetPosts2 Municipio.Api3 Municipio.Controller.Navigation4 Municipio.Helper.SiteSwitcher5 Municipio.HooksRegistrar6 Municipio.ImageConvert.Logging7 Municipio.Kulturkortet.MunicipioAuth.navigation8 Municipio.Kulturkortet.MunicipioAuth.user9 Municipio.PostObject10 Municipio.PostsList.Config.AppearanceConfig11 Municipio.PostsList.Config.FilterConfig12 Municipio.PostsList.QueryVars13 Municipio.ProgressReporter14 Municipio.SchemaData.Config.Contracts15 Municipio.SchemaData.ExternalContent.Filter.FilterDefinition.Contracts16 Municipio.SchemaData.ExternalContent.SourceReaders17 Municipio.SearchIndex.Config18 Municipio.Upgrade19 Modularity20 Municipio.Helper.User21 Municipio.ImageConvert.Strategy22 Municipio.Kulturkortet.MunicipioAuth.views23 Municipio.PostsList.Config.GetPostsConfig24 Municipio.PostsList.ViewCallableProviders25 Municipio.SchemaData.ExternalContent.Config26 Municipio.SchemaData.Utils27 Municipio.SearchIndex.Provider28 Modularity.Module.Posts29 Municipio.Controller30 Municipio.Controller.Archive31 Municipio.ImageConvert32 Municipio.PostsList33 Municipio.SchemaData.ExternalContent.SyncHandler34 Municipio.SchemaData.SchemaObjectFromPost35 Municipio.SearchIndex.Admin.Indexing36 Municipio.UserGroup37 Municipio.PostObject.Decorators38 Municipio.PostObject.Factory39 Municipio40 Municipio.SchemaData.SchemaPropertiesForm.StoreFormFieldValuesModularity.Module.Posts.Helper.GetPosts1Municipio.Api2Municipio.Controller.Navigation3Municipio.Helper.SiteSwitcher4Municipio.HooksRegistrar5Municipio.ImageConvert.Logging6Municipio.Kulturkortet.MunicipioAuth.navigation7Municipio.Kulturkortet.MunicipioAuth.user8Municipio.PostObject9Municipio.PostsList.Config.AppearanceConfig10Municipio.PostsList.Config.FilterConfig11Municipio.PostsList.QueryVars12Municipio.ProgressReporter13Municipio.SchemaData.Config.Contracts14Municipio.SchemaData.ExternalContent.Filter.FilterDefinition.Contracts15Municipio.SchemaData.ExternalContent.SourceReaders16Municipio.SearchIndex.Config17Municipio.Upgrade18Modularity19Municipio.Helper.User20Municipio.ImageConvert.Strategy21Municipio.Kulturkortet.MunicipioAuth.views22Municipio.PostsList.Config.GetPostsConfig23Municipio.PostsList.ViewCallableProviders24Municipio.SchemaData.ExternalContent.Config25Municipio.SchemaData.Utils26Municipio.SearchIndex.Provider27Modularity.Module.Posts28Municipio.Controller29Municipio.Controller.Archive30Municipio.ImageConvert31Municipio.PostsList32Municipio.SchemaData.ExternalContent.SyncHandler33Municipio.SchemaData.SchemaObjectFromPost34Municipio.SearchIndex.Admin.Indexing35Municipio.UserGroup36Municipio.PostObject.Decorators37Municipio.PostObject.Factory38Municipio39Municipio.SchemaData.SchemaPropertiesForm.StoreFormFieldValues40121111124511121105154323521111111112223218113121211121111+517 more modules (most-connected shown)

At a glance — Code Health · 55.6 · Adequate · gated by X5 ·

At a glance — Architecture · 91.8 · Adequate · gated by D26 ·

At a glance — Maturity · 71.7 · Adequate · gated by M2 ·

At a glance — Readiness · 26.4 · Weak · gated by R4, R8, P3, P7 ·

At a glance — Security · 57.6 · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 52.1 · Adequate ·

At a glance — Performance · 100.0 · Exemplary ·

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 categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures48High / Critical
A05:2025 — Injection43High / Critical
A07:2025 — Authentication Failures5High / Critical

Roadmap

Top priorities: Resolve the 3 Banned license finding(s) in License Compliance; Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry).

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

Do thisHelpsEffortDimension
Resolve the 3 Banned license finding(s) in License Compliance.+12.7 ptsLowLicense Compliance
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+4.4 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+2.6 ptsMediumTest Coverage
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.2 ptsMediumDependency Hygiene
Resolve the 5 redundant comment finding(s) in Comment Value — start with module.js (4), mod-curator-load-more.js.+1.0 ptsLowComment Value
Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.+1.5 ptsMediumOutbound HTTP resilience
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.+1.4 ptsMediumText alternatives
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.+1.2 ptsMediumVisual & motion safety

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED1.1SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
library/Upgrade.php5.5MixedCyclomatic Complexity: Upgrade.v_13 (cyclomatic 21)
library/Helper/Navigation.php5.5MixedCyclomatic Complexity: Navigation.getItems (cyclomatic 18)
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
library/Template.php5.7MixedCyclomatic Complexity: Template.loadController (cyclomatic 26)
Modularity/source/php/BlockManager.php5.7MixedCyclomatic Complexity: BlockManager.renderBlock (cyclomatic 18)
Modularity/source/php/Module/ManualInput/ManualInput.php6.0MixedExplicit Debt: TodoComment
library/Controller/BaseController.php6.0MixedExplicit Debt: TodoComment
Modularity/source/php/Editor.php6.0MixedExplicit Debt: TodoComment
library/Api/Pdf/PdfArchiveEndpoint.php6.3MixedCognitive Complexity: PdfArchiveEndpoint.getPostsFromArchiveQuery (cognitive 20)
library/Api/Pdf/PdfGenerator.php6.3MixedGod Classes: MethodTooLong: PdfGenerator.addAcfToPdfGeneratorOptionsPage

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

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

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

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

Could not be resolved — 15

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 68 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D16D17D19D21D24D26D27D28D29D30D34D35D36D43D44AC1AC2AC3AC5AC6AX10AX3AX4AX6C2M1M2M3M4P1P3P4P5P6P7PF3R1R10R2R3R4R5R6R7R8R9X16X18X19X2X21X25X27X28X3X30X5

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
  1. 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, 754 of 780 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e5c2-a32a-7459-b1f5-f4add309179f.

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.

  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,889 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 27 test source file(s) (.ts, .tsx, .mjs, .js) that it cannot: it reads the test types the .php frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in Modularity/ was NOT MEASURED: the dependency install for Modularity/ could not reach npm.pkg.github.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://npm.pkg.github.com/download/@helsingborg-stad/openstreetmap/0.53.6/d86d2f2a6448bc1a394da30449b4d093f7037b05), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Composer package 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.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The newest 494 of 12161 commits were scanned for secrets, back to commit 1b59963e0046; older commits were not. The history budget was spent before the next range could start. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php`, `Modularity/source/php/Module/Posts/Helper/GetPosts/GetPostsFromMultipleSites.php`, `Modularity/source/php/Module/Posts/Helper/GetPosts/UserGroupResolver/UserGroupResolver.php`, `library/A11yStatement/A11yStatement.php`, `library/AcfFieldContentModifiers/Registrar.php`, … (+224 more) 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.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at resolvePath (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31509:29) / at async Promise.all (index 0) / at async computeEntries (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31514:44) / at async scan (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31448:19) / at async file://<repo>/node_modules/vite/dist/node/chunks/config.js:34191:15 / VITE v7.3.6 ready in 339 ms / ➜ Local: http://localhost:5173/ / ➜ Network: use --host to expose" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at resolvePath (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31509:29) / at async Promise.all (index 0) / at async computeEntries (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31514:44) / at async scan (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31448:19) / at async file://<repo>/node_modules/vite/dist/node/chunks/config.js:34191:15 / VITE v7.3.6 ready in 339 ms / ➜ Local: http://localhost:5173/ / ➜ Network: use --host to expose" No runtime evidence was gathered.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (library/App.php:58), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (library/App.php:58), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (library/App.php:58), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (library/App.php:58), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 111 further occurrence(s) are not listed individually; the score already reflects all 151.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 38 further occurrence(s) are not listed individually; the score already reflects all 78.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • 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.

Dimensions

D1 · Cyclomatic Complexity6.6 / 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.6 / 10 · rule-coverage 100% · ceiling Prevented

44 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WoffConverter.convertToTTF at 57. A further 4 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 ApplyI18n.getTranslationForString at 418 — they are counted neither in the figure above nor in this dimension's score. 4 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: library/Styleguide/Customize/ComponentData/Decorators/ApplyI18n.php (ApplyI18n.getTranslationForString at 418), library/Styleguide/Customize/TokenData/Decorators/ApplyI18n.php (ApplyI18n.getTranslationForString at 238), Modularity/source/php/Module/FilesList/FilesList.php (FilesList.getIconClass at 33), library/Theme/Sidebars.php (Sidebars.moduleSidebarIncompability at 33). 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.

WoffConverter.convertToTTF (cyclomatic 57)library/Helper/FileConverters/WoffConverter.php:122
TransparencyDetector.webpHasTransparency (cyclomatic 39)library/ImageConvert/TransparencyDetector.php:96
Version70.migrateBlocks (cyclomatic 38)library/Upgrade/V70/Version70.php:73
Contacts.prepareContacts (cyclomatic 28)Modularity/source/php/Module/Contacts/Contacts.php:88
ManualInput.data (cyclomatic 27)Modularity/source/php/Module/ManualInput/ManualInput.php:38

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

What to do

  1. Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with WoffConverter.convertToTTF (cyclomatic 57), TransparencyDetector.webpHasTransparency (cyclomatic 39), Version70.migrateBlocks (cyclomatic 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity5.9 / 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 5.9 / 10 · rule-coverage 100% · ceiling Prevented

90 method(s) exceeded the cognitive complexity threshold of 15; the worst was WoffConverter.convertToTTF at 107.

WoffConverter.convertToTTF (cognitive 107)library/Helper/FileConverters/WoffConverter.php:122
Version70.migrateBlocks (cognitive 86)library/Upgrade/V70/Version70.php:73
AcfBlockIndexRepeaterMigrator.migrate (cognitive 58)Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:22
TransparencyDetector.webpHasTransparency (cognitive 53)library/ImageConvert/TransparencyDetector.php:96
PopulateUsedColors.countBlocks (cognitive 53)library/Upgrade/Palette/PopulateUsedColors.php:67

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with WoffConverter.convertToTTF (cognitive 107), Version70.migrateBlocks (cognitive 86). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes9.2 / 10Stronggated by 30 serious findings✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Prevented

30 god class(es) detected.

MethodTooLong: Archive.__construct · ×13library/Customizer/Sections/Archive.php:12
TooManyMethods: Upgrade · ×7library/Upgrade.php:51
ClassTooLong: Upgrade · ×5library/Upgrade.php:51
FunctionTooLong: module.Module.addModule · ×3Modularity/source/js/editor/module.js:165
FileTooLong: library/Upgrade.php · ×2library/Upgrade.php

What to do

  1. Resolve the 13 MethodTooLong finding(s) in God Classes — start with PdfGenerator.php (2), Archive.php, BaseController.php. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 7 TooManyMethods finding(s) in God Classes — start with Upgrade.php, BaseController.php, MenuBuilder.php. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 5 ClassTooLong finding(s) in God Classes — start with Upgrade.php, BaseController.php, REDACTED. — One of this dimension's main actionable groups (5 warning-level).

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

D4 · Code Duplication8.8 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

108 duplicated block group(s) detected. 3.0 % of the production lines (4,280 of 140,585) are in a reported copy. A further 83 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (7 lines × 2) · ×13library/ImageConvert/Cache/ConversionCache.php:243
Duplicated block (9 lines × 2) · ×10library/Controller/E401.php:82
Duplicated block (11 lines × 2) · ×8library/Customizer/CustomField.php:23
Duplicated block (8 lines × 2) · ×8Modularity/source/php/Helper/Wp.php:47
Edited copy of a member (5 corresponding lines) · ×7library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php:26

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

What to do

  1. Resolve the 13 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with PrivateController.php (2), UspsGenerator.php (2), ConversionCache.php. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 10 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with E401.php (2), ResolvePageTreeTranslatedChildren.php (2), PostsListBlockRenderer.php. — One of this dimension's main actionable groups (10 warning-level).
  3. Resolve the 8 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with CustomField.php, MigrateLegacyGoogleFontsToNativeFontLibrary.php, Version64.php. — One of this dimension's main actionable groups (8 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.6 / 10Stronggated by 16 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.6 / 10 · rule-coverage 100% · ceiling Verified

16 of 469 classes have LCOM4 above 3.

Low cohesion: Upgrade (LCOM4 49) · ×16library/Upgrade.php:51

What to do

  1. Resolve the 16 Low cohesion finding(s) in Cohesion (LCOM4) — start with Editor.php (2), Navigation.php (2), Upgrade.php. — One of this dimension's main actionable groups (16 warning-level).

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

D10 · Test Quality9.9 / 10Stronggated by 16 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 16 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1889 tests. Measured on the .php suite only — at least 27 test source file(s) (.ts, .tsx, .mjs, .js) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: testAddHooks · ×16library/CommonFieldGroups/DisableFieldsThatAreCommonlyManagedOnSubsitesTest.php:97

What to do

  1. Resolve the 16 No assertions finding(s) in Test Quality — start with NullProgressReporterServiceTest.php (4), SseProgressReporterServiceTest.php (3), EnsureVisitingSingularOccasionTest.php (2). — One of this dimension's main actionable groups (16 warning-level).

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

D12 · Dependency Hygiene10.0 7.6 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 76% · ceiling Verified

0 outdated, 0 abandoned direct Composer dependencies. 19 of 25 direct production requirements were graded against Packagist (0 not published there, which is what a private Satis repository looks like, 6 with no release resolution). PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.

Detailed fixes: d12_recommendation.md.

D13 · Secret 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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance4.0 / 10Weak✓ Tool-verified

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 4.0 / 10 · rule-coverage 100% · ceiling Verified

3 of 69 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 47 package(s) under `packages-dev` are not installed for a consumer and are excluded. 1 of them declare no licence; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package 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.

Banned license: dompdf/php-svg-lib · ×3

What to do

  1. Resolve the 3 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (3 issue-level).

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

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 18 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: library/Controller/BaseController.php (12×22=264); library/Upgrade/V70/Version70.php (3×38=114); library/Admin/Gutenberg/Blocks/BlockManager.php (3×21=63) Repeated repair below the complexity floor: library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php (5 of 6 changes were fixes); library/Chat/Render/ChatRenderConfig.php (4 of 5 changes were fixes); library/ImageConvert/ImageProcessor.php (3 of 5 changes were fixes)

Repeated repair: library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php · ×10library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php:117
Hotspot: library/Controller/BaseController.php · ×8library/Controller/BaseController.php:68

What to do

  1. Resolve the 10 Repeated repair finding(s) in Churn × Complexity Hotspots — start with WordPressAssetEnqueuer.php, ChatRenderConfig.php, ImageProcessor.php. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with BaseController.php, Version70.php, BlockManager.php. — One of this dimension's main actionable groups (8 warning-level).

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

D16 · Bus Factor8.3 / 10Strong✓ 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 8.3 / 10 · rule-coverage 100% · ceiling Documented

99 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is library/Theme/Icon.php. Counted over 570 of the 1983 production source files in this repository: 1411 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)

What to do

  1. Resolve the 4 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (4 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 10 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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

TodoComment · ×10library/SchemaData/SchemaPropertiesForm/SetPostTitleFromSchemaTitle/SetPostTitleFromSchemaTitleTest.php:53

What to do

  1. Resolve the 10 TodoComment finding(s) in Explicit Debt — start with BaseController.php (4), SetPostTitleFromSchemaTitleTest.php, AllowCronToEditPosts.php. — One of this dimension's main actionable groups (10 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 24 document(s) read across 2 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D21 · Naming Consistency7.0 / 10Adequate✓ Tool-verified

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

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 33 declarations measured against a convention their peers follow.

`getUniqueID` spells `ID` where 32 names in the project spell it `Id`library/ProgressReporter/AdminProgressAction/js/UIComponents/ProgressBarWithLabel.ts:72

What to do

  1. Resolve the 1 `getUniqueID` spells `ID` where 32 names in the project spell it `Id` finding(s) in Naming Consistency — start with ProgressBarWithLabel.ts. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value1.8 1.8 / 10Critical✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 1.8 / 10 · rule-coverage 99% · ceiling Documented

5 of 61 judged comments only repeat the code they sit on (8.2 %). 1 comment(s) in another language or script were not judged.

redundant comment · ×5Modularity/source/js/editor/module.js:188
doc comments repeat the names · ×2Modularity/source/js/helpers/ModuleRefresher.js:20

What to do

  1. Resolve the 5 redundant comment finding(s) in Comment Value — start with module.js (4), mod-curator-load-more.js. — One of this dimension's main actionable groups (5 recommendation-level).

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

D26 · Project Cohesion0.0 / 10Critical✓ 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.

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

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

Projects may be oversized for their cohesion · ×2package.json:1

What to do

  1. Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

20 % of calls cross a namespace and 1 % go through an interface, but 69 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)6.0 / 10Adequate✓ Tool-verified

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

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

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

4 finding(s): 0 critical, 4 high, 0 medium, 0 low. History coverage: The newest 494 of 12161 commits were scanned for secrets, back to commit 1b59963e0046; older commits were not. The history budget was spent before the next range could start. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  2. 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.

D29 · Static Analysis (SAST)1.3 / 10Critical✓ 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 1.3 / 10 · rule-coverage 100% · ceiling Documented

43 finding(s): 0 critical, 30 high, 13 medium, 0 low. 22 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 261 file(s) — `Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php` (line 27), `Modularity/source/php/Module/Posts/Helper/GetPosts/GetPostsFromMultipleSites.php` (line 28), `Modularity/source/php/Module/Posts/Helper/GetPosts/UserGroupResolver/UserGroupResolver.php` (line 19), `library/A11yStatement/A11yStatement.php` (line 30), `library/AcfFieldContentModifiers/Registrar.php` (line 20), … (+256 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 22 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 (22 issue-level, 0 of them charged here).

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

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

40 finding(s): 0 critical, 28 high, 8 medium, 4 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 28 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27), REDACTED. — One of this dimension's main actionable groups (28 issue-level).
  2. Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 3 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).

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

D34 · Knowledge Freshness9.3 / 10Adequategated by 4 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

39 of 572 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Modularity/source/php/AcfFields/php/mod-contacts.php. Counted over 572 of the 1983 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×4Modularity/source/php/AcfFields/php/mod-contacts.php:1
Orphaned file · ×35Modularity/source/php/AcfFields/php/mod-hero.php:1
Further orphaned files (smaller)

What to do

  1. Resolve the 4 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod-contacts.php, mod-posts-displau.php, mod-video.php. — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 35 Orphaned file finding(s) in Knowledge Freshness — start with mod-hero.php, mod-map.php, mod-index.php. — One of this dimension's main actionable groups (35 recommendation-level).
  3. 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.

D35 · Change Coupling9.9 / 10Adequategated by 3 critical 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: login.blade.php↔user.blade.php 100%; BaseController.php↔Menu.php 83%; single-schema-elementary-school.blade.php↔single-schema-preschool.blade.php 80%

Boundary-crossing change coupling: SingularProject.php ↔ single-schema-project.blade.php · ×3library/Controller/SingularProject.php:1
Change coupling: BaseController.php ↔ Menu.php · ×5library/Controller/BaseController.php:1
Change coupling clique: LoginLogout.php, login.blade.php, user.blade.phplibrary/Customizer/Sections/Header/LoginLogout.php

What to do

  1. Resolve the 3 Boundary-crossing change coupling finding(s) in Change Coupling — start with SingularProject.php, SingularEvent.php, E404.php. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 5 Change coupling finding(s) in Change Coupling — start with BaseController.php, single-schema-elementary-school.blade.php, BackwardsCompatiblePostObject.php. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with LoginLogout.php. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ 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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — library/BrandedEmails/HtmlTemplate/views/default.blade.php:59, views/v3/partials/content/pdf/frontpage.blade.php:6

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels6.6 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — Modularity/templates/editor/modularity-module-description.php:5, Modularity/templates/editor/modularity-sidebar-drop-area.php:11

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.1 / 10Adequate✓ 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) — library/BrandedEmails/HtmlTemplate/views/default.blade.php:1, views/v3/partials/content/pdf/layout.blade.php:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — library/BrandedEmails/HtmlTemplate/views/default.blade.php:1, views/v3/partials/content/pdf/layout.blade.php:2, views/v3/templates/grid.blade.php:6

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.
AC5 · ARIA correctness6.8 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The radio role requires aria-checked to convey its state. Add it. — assets/source/js/admin/acf/paletteColorChoices.ts:70

What to do

  • Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety5.0 / 10Weak✓ 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.

  • `::-webkit-progress-value` moves (`transition: width 1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ProgressReporter/AdminProgressAction/js/UIComponents/ProgressBarWithLabel.ts:35
  • `. . __menu-card` moves (`transition: opacity 0.2s ease, transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/Kulturkortet/QRCodeViewer/css/actions.scss:18
  • `. . __inner-card::before` moves (`animation: snake-rotate 5s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/Kulturkortet/QRCodeViewer/css/ticket.scss:47
  • `.municipio-sortable-item__handle[data-tooltip]::before` moves (`transition: opacity 120ms ease, transform 120ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/Customizer/Controls/Sortable/SortableControl.css:150
  • `.municipio-sortable-item__handle[data-tooltip]::after` moves (`transition: opacity 120ms ease, transform 120ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/Customizer/Controls/Sortable/SortableControl.css:170
  • `.backdrop-banner__navigation-item-content` moves (`transition: opacity 0.2s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/BackdropBanner/js/Front/backdrop-banner.scss:175
  • `.event-accordion__trigger[aria-pressed="true"] .c-icon` moves (`transition: ease .3s transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/source/sass/event.scss:78
  • `.c-header.c-header--flexible.c-header--logotype-scroll-shrink .c-header__lower-left .c-header__item--logotype .c-header__logotype` moves (`transition: transform 0.3s ease, height 0.3s ease, margin-bottom 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/source/sass/navigation/_header-flexible.scss:159
  • `.user::after` moves (`transition: width .3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/source/sass/navigation/_user.scss:27
  • `.modularity-preview-hidden::after` moves (`transition: 500ms opacity, 300ms transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Modularity/source/sass/partials/_block-content.scss:67
  • `body.modularity-loader-takeover::after` moves (`animation: 1000ms loading-ball ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Modularity/source/sass/partials/_loader-takeover.scss:28
  • `.modularity-module-icon svg` moves (`transition: transform 200ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Modularity/source/sass/partials/_modules.scss:73
  • `.modularity-modal-spinner:after` moves (`animation: modularity-spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Modularity/source/sass/partials/_spinner.scss:31
  • `.interactive-map__highlighted-marker` moves (`animation: highlight-marker 0.1s ease-in-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Modularity/source/php/Module/InteractiveMap/assets/interactive-map.scss:27
  • `.interactive-map__filter-icon` moves (`transition: transform .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Modularity/source/php/Module/InteractiveMap/assets/interactive-map.scss:209

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.
AX10 · Code composition9.6 / 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.

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.

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.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `MenuBuilderInterface` declares 34 methods: `setConfig`, `getMenu`, `appendMenuItems`, `mapMenuItemsFromObjectToArray`, `mapMenuItemsAcfFieldValues`, `mapMenuItemsIsAncestor`, `applyMenuItemFilter`, `convertStaticMenuItemsToPageTreeItems`, `appendHomeIconMenuItem`, `appendArchiveMenuItem`, `appendPageTreeAncestorsMenuItems`, `applyBreadcrumbItemsFilter`, `appendPrintMenuItem`, `applyAccessibilityItemsFilter`, `applyAccessibilityItemsDeprecatedFilter`, `pageTreeGetAncestors`, `appendDataFromAncestorIds`, `tryGetPageTreeMenuItemsFromCache`, `pageTreeMenuItemsFormatter`, `pageTreeAppendMenuItemsHref`, `pageTreeAppendMenuItemsCustomTitle`, `pageTreeAppendMenuItemsAncestors`, `pageTreeAppendMenuItemIsCurrentPage`, `pageTreeAppendChildren`, `pageTreeSetMenuItemsCache`, `pageTreeAppendMenuItemsFetchUrl`, `appendAcfFields`, `applyMenuItemsFilter`, `removeSubLevels`, `removeTopLevel`, `structureMenuItems`, `applyNestedMenuItemsFilter`, `standardMenuWithPageTreeSubitemsAppendHasChildren`, `standardMenuWithPageTreeSubitemsAppendAncestors`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — library/Controller/Navigation/MenuBuilderInterface.php:8
  • `ImageConvertConfigInterface` declares 17 methods: `isEnabled`, `imageDownsizePriority`, `mimeTypes`, `internalFilterPriority`, `fileNameSuffixes`, `maxImageDimension`, `intermidiateImageFormat`, `intermidiateImageQuality`, `maxSourceFileSize`, `failedCacheExpiry`, `successCacheExpiry`, `lockExpiry`, `defaultCacheExpiry`, `pageCacheExpiry`, `getImageConversionStrategy`, `getDefaultImageConversionLogWriter`, `maxImageAspectRatioMultiplier`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — library/ImageConvert/Config/ImageConvertConfigInterface.php:5
  • `PostObjectInterface` declares 19 methods: `getId`, `getTitle`, `getContent`, `getExcerpt`, `getContentHeadings`, `getPermalink`, `getCommentCount`, `getPostType`, `getIcon`, `getBlogId`, `getPublishedTime`, `getModifiedTime`, `getArchiveDateTimestamp`, `getArchiveDateFormat`, `getSchemaProperty`, `getSchema`, `getTerms`, `getImage`, `__get`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — library/PostObject/PostObjectInterface.php:9

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C2 · Access Controls8.0 / 10Strong✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • Public opt-outs and open tables (8) outweigh guarded routes and protected tables (7) — review whether the open surface is intended.

What to do

  • Review the open surface — keep public routes deliberate and documented so the open surface stays intentional.
M1 · Documentation (README)10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

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 your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

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.

P3 · Security & performance tooling0.0 / 10Critical✓ 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 phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 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. — REDACTED:6
  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:44

What to do

  • Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ 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.

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `curl_exec(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — library/Chat/Api/ChatEndpoint.php:228

What to do

  • Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 · Type Safety8.3 / 10Strong✓ 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.

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

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 8 duplicated blocks under library/Customizer/Controls/ have copies in at least two of the sibling directories Background, ColorChoice, MultiCheck, MultiColor, MultiSelect, Repeater (+2 more sibling(s) not listed) — 5 of them are reported below, and 3 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — library/Customizer/Controls/MultiColor/MultiColorControl.ts:15
  • Modularity/source/php/Module/Posts/assets/xhr.ts:20 · Modularity/source/php/Module/Posts/assets/xhr.ts:70 — 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. — Modularity/source/php/Module/Posts/assets/xhr.ts:20
  • library/PostsList/Block/js/SettingsPanel/AppearanceSettingsPanel/DateSourceControl/DateSourceControl.tsx:16 · library/PostsList/Block/js/SettingsPanel/PostsSettingsPanel/OrderByControl/OrderByControl.tsx:17 — 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. — library/PostsList/Block/js/SettingsPanel/AppearanceSettingsPanel/DateSourceControl/DateSourceControl.tsx:16
  • Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:113 · Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:143 — 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. — Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:113
  • Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:9 · Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:84 — the two spans are one implementation copied and then locally edited — 111 tokens are still identical, in the same order in both spans, 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. — Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:9
  • Modularity/source/js/editor/dragAndDrop.js:40 · Modularity/source/js/editor/dragAndDrop.js:95 — all 2 copies are in the same file, 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. — Modularity/source/js/editor/dragAndDrop.js:40
  • Modularity/source/js/modularity-editor-modal.js:54 · Modularity/source/js/modularity-editor-modal.js:99 — all 2 copies are in the same file, 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. — Modularity/source/js/modularity-editor-modal.js:54
  • assets/source/js/headingHierarchyIndicator.ts:8 · assets/source/js/vagueControlTextIndicator.ts:39 — the two spans are one implementation copied and then locally edited — 95 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. — assets/source/js/headingHierarchyIndicator.ts:8
  • Modularity/source/php/Module/InteractiveMap/assets/map/filtering/LayerGroupWithoutFilter.ts:30 · Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithSelectFilter.ts:77 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/LayerGroupWithoutFilter.ts:30
  • Modularity/source/js/editor/autosave.js:30 · Modularity/source/js/helpers/serializeObject.js:1 — 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. — Modularity/source/js/editor/autosave.js:30
  • Modularity/source/js/editor/dragAndDrop.js:2 · Modularity/source/js/editor/module.js:1 — the two spans are one implementation copied and then locally edited — 50 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. — Modularity/source/js/editor/dragAndDrop.js:2
  • assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:40 · assets/source/js/headerLogoScrollShrink.ts:16 — 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. — assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:40
  • assets/source/js/missingH1Indicator.ts:6 · assets/source/js/vagueControlTextIndicator.ts:39 — the two spans are one implementation copied and then locally edited — 87 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. — assets/source/js/missingH1Indicator.ts:6
  • assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:147 · assets/source/js/headerLogoScrollShrink.ts:45 — 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. — assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:147
  • Modularity/source/js/modularity-editor-modal.js:36 · Modularity/source/js/modularity-editor-modal.js:85 — all 2 copies are in the same file, 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. — Modularity/source/js/modularity-editor-modal.js:36
  • Modularity/source/php/Module/InteractiveMap/assets/map/filtering/filterButton.ts:52 · Modularity/source/php/Module/InteractiveMap/assets/map/markerClick/markerClick.ts:91 — 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. — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/filterButton.ts:52
  • library/Customizer/Controls/Background/BackgroundControl.ts:29 · library/Customizer/Controls/MultiColor/MultiColorControl.ts:72 — 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. — library/Customizer/Controls/Background/BackgroundControl.ts:29
  • library/Customizer/Controls/ColorChoice/ColorChoiceControl.ts:4 · library/Customizer/Controls/MultiColor/MultiColorControl.ts:15 — 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. — library/Customizer/Controls/ColorChoice/ColorChoiceControl.ts:4
  • library/Chat/js/chat/feedback.ts:22 · library/Chat/js/chat/feedback.ts:36 — all 2 copies are in the same file, 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. — library/Chat/js/chat/feedback.ts:22
  • library/Customizer/Controls/Background/BackgroundControl.ts:14 · library/Customizer/Controls/Sortable/SortableControl.ts:212 — the two spans are one implementation copied and then locally edited — 53 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. — library/Customizer/Controls/Background/BackgroundControl.ts:14
  • library/Customizer/Controls/Repeater/RepeaterControl.ts:26 · library/Customizer/Controls/TabBox/TabBoxControl.ts:10 — the two spans are one implementation copied and then locally edited — 57 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. — library/Customizer/Controls/Repeater/RepeaterControl.ts:26
  • Modularity/source/js/editor/module.js:397 · Modularity/source/js/helpers/widget.js:38 — 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. — Modularity/source/js/editor/module.js:397
  • library/Customizer/Controls/MultiSelect/MultiSelectControl.ts:34 · library/Customizer/Controls/Sortable/SortableControl.ts:286 — 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. — library/Customizer/Controls/MultiSelect/MultiSelectControl.ts:34
  • assets/source/js/comments.ts:13 · assets/source/js/comments.ts:83 — all 2 copies are in the same file, 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. — assets/source/js/comments.ts:13
  • library/Chat/js/chat/ChatSession.ts:75 · library/ProgressReporter/AdminProgressAction/js/FetchStreamSource.ts:55 — the two spans are one implementation copied and then locally edited — 54 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. — library/Chat/js/chat/ChatSession.ts:75
  • Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:78 · Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:86 — 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. — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:78
  • assets/source/js/comments.ts:18 · assets/source/js/comments.ts:88 · assets/source/js/sessionManager.ts:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — assets/source/js/comments.ts:18

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.
R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ 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.

  • sanitizeItemOptions has cyclomatic complexity 17 and cognitive complexity 16; 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. — library/Customizer/Controls/Sortable/SortableControl.ts:38
  • importSettings has cyclomatic complexity 15 and cognitive complexity 32; 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. — assets/source/js/admin/designShareUtils.ts:304
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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. — library/SearchIndex/SearchPage/js/index.ts:179
  • callback has cyclomatic complexity 13 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. — assets/source/js/admin/widgetsAreaHider.js:4
  • (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; 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. — library/SearchIndex/SearchPage/js/index.ts:363
R3 · Large Files9.6 / 10Exemplary✓ 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.

  • library/Customizer/Controls/Sortable/SortableControl.ts has 524 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — library/Customizer/Controls/Sortable/SortableControl.ts:1
  • library/SearchIndex/SearchPage/js/index.ts has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — library/SearchIndex/SearchPage/js/index.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage1.5 / 10Critical✓ 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) — Modularity/source/js/editor/module.js:1, assets/source/js/admin/designShareUtils.ts:1, assets/source/js/nav.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness9.3 / 10Exemplary✓ 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.

R6 · Tooling6.7 / 10Adequate✓ 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.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
  • The package in `Modularity` declares the lint script `lint` (`npx biome lint ./source`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `Modularity` (or the workspace's task runner). — Modularity/package.json:52

What to do

  • Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code9.3 / 10Exemplary✓ 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.

  • Unreachable from the 117 application, 21 tooling and 26 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 (117 application, 21 tooling, 26 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — library/Customizer/Controls/Slider/SliderControl.js, jest-raw-loader.js, Modularity/source/js/helpers/serializeObject.js
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×3) — Modularity/source/js/editor/thickbox.js:7, assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:10, assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:37
  • Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×7) — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/LayerGroupWithoutFilter.ts:13, Modularity/source/php/Module/InteractiveMap/assets/map/filtering/filterHelper.ts:8, Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupFilterFactory.ts:17, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene2.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. (×2) — library/BackdropBanner/js/Editor/backdropBannerPanel.tsx:3, library/PostsList/Block/js/SettingsPanel/PostsSettingsPanel/OrderByControl/OrderByControl.test.tsx:2
  • 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. (×8) — package.json:67, package.json:69, package.json:75, …

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ 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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 1/5 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `fetchMarkup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — assets/source/js/nav.ts:12
  • `refreshNonce` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — assets/source/js/restApi/wpApiSettings.ts:47
  • `getRemoteSiteDesignData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — assets/source/js/admin/designShareUtils.ts:201
  • `submitSubscription` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — Modularity/source/php/Module/Subscribe/assets/ungapd.ts:122

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the array or collection it is walking alone — PHP raises nothing, but the loop's view and the collection part: an array walked by value (and a Doctrine or Laravel collection) is walked as the snapshot taken when the loop began, so an element added in the body is never visited and one removed is visited anyway; an array walked by reference (`as &$v`) and an SPL container (`SplObjectStorage`, `ArrayObject`, `SplQueue`) are walked live, so an added element is walked too and a removal skips the next one; and after an `array_splice`, `array_shift` or sort every later key names a different element.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — library/SearchIndex/Search/SearchQuery.php:50, library/SearchIndex/Index/PostIndexer.php:57, library/SearchIndex/Index/PostIndexer.php:74
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — library/SearchIndex/Index/PostIndexer.php:170, library/Chat/js/chat/ChatSession.ts:174
  • `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — library/SchemaData/ExternalContent/JsonToSchemaObjects/SchemaSanitizer/Mappers/SetEventDatesFromEventSchedule.php:49, library/PostsList/ViewCallableProviders/Schema/ExhibitionEvent/GetOccasionText.php:75, library/Kulturkortet/MunicipioAuth/controller/secure/JWTStrategy.php:49, …
  • `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — library/Customizer/CustomizerPanel.php:26

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.

What to do

  • Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.

WCAG coverage — what static analysis assessed

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 42 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 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.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.

LensScoreRatingImpact
Code Health55.6Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture91.8Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity71.7Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness26.4Weak — gated by R4, R8, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security57.6Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility52.1AdequateAcceptable, with room to improve.
Performance100.0ExemplaryStrongest area.
Unscored — 4 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.

  • P12 CI test-gate honesty — 1 observation(s) recorded · 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'.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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: this repository stores data through '$wpdb' (library/App.php:58) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through '$wpdb' (library/App.php:58) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through '$wpdb' (library/App.php:58) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 53 check(s) not relevant to this codebase

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

  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. 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
  • 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 (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at resolvePath (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31509:29) / at async Promise.all (index 0) / at async computeEntries (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31514:44) / at async scan (file://<repo>/node_modules/vite/dist/node/chunks/config.js:31448:19) / at async file://<repo>/node_modules/vite/dist/node/chunks/config.js:34191:15 / VITE v7.3.6 ready in 339 ms / ➜ Local: http://localhost:5173/ / ➜ Network: use --host to expose" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: this repository stores data through '$wpdb' (library/App.php:58) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
  • D11 Test Reliability — JavaScript/TypeScript suite in Modularity/ was not re-run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • 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) — 229 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.
  • 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 — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (50 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P2 Observability — This repository's JavaScript/TypeScript, PHP source (3 module(s), 2014 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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 — X1 reached only 8% of this repository's production lines — php (122,692 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 8% of this repository's production lines — php (122,692 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — X24 reached only 8% of this repository's production lines — php (122,692 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X29 Per-element action decided by a fixed element — X29 reached only 8% of this repository's production lines — php (122,692 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • 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 — 82 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×28
  • 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
  • + 3 more in this group — see findings.md.
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
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×4
  • Orphaned knowledge Modularity/source/php/AcfFields/php/mod-contacts.php:1 — 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 Modularity/source/php/AcfFields/php/mod-posts-displau.php:1 — 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 Modularity/source/php/AcfFields/php/mod-video.php:1 — 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 Modularity/source/php/AcfFields/php/mod-wpwidget.php:1 — 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.
D14 · License Compliance · Banned license · ×3
  • Banned license: dompdf/php-svg-lib — `dompdf/php-svg-lib` 1.0.2 is in the production `packages` list of this repository's REDACTED — what a `composer install --no-dev` puts in vendor/ — and every licence it declares is one this policy bans (`LGPL-3.0-or-later`). Where a package declares several licences it is charged only when all of them are banned. Replace the package, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: enshrined/svg-sanitize — `enshrined/svg-sanitize` dev-master is in the production `packages` list of this repository's REDACTED — what a `composer install --no-dev` puts in vendor/ — and every licence it declares is one this policy bans (`GPL-2.0-or-later`). Where a package declares several licences it is charged only when all of them are banned. Replace the package, or record an accepted exception.
  • Banned license: jeradin/acf-dynamic-table-field — `jeradin/acf-dynamic-table-field` dev-master is in the production `packages` list of this repository's REDACTED — what a `composer install --no-dev` puts in vendor/ — and every licence it declares is one this policy bans (`GPL-2.0`). Where a package declares several licences it is charged only when all of them are banned. Replace the package, or record an accepted exception.
D35 · Change Coupling · Boundary-crossing change coupling · ×3
  • Boundary-crossing change coupling: SingularProject.php ↔ single-schema-project.blade.php library/Controller/SingularProject.php:1 — `library/Controller/SingularProject.php` (context library) and `views/v3/single-schema-project.blade.php` (context views) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `de3e8e11` refactor: use PostObject data for Project progress (#1394); `99477f2f` feat: print email on project template (#1281); `c99444b4` chore: changing project category names — run `git show` on any of them.
  • Boundary-crossing change coupling: SingularEvent.php ↔ single-schema-event.blade.php library/Controller/SingularEvent.php:1 — `library/Controller/SingularEvent.php` (context library) and `views/v3/single-schema-event.blade.php` (context views) sit in DIFFERENT parts of the tree yet change together 56% of the time (10 of the 18 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `1dbd78bb` refactor(Event): simplify related events rendering (#2307); `0ebad2c4` feat: schema event view links; `829c82cd` fix: related events should use PostsList (#1702) — run `git show` on any of them.
  • Boundary-crossing change coupling: E404.php ↔ default.blade.php library/Controller/E404.php:1 — `library/Controller/E404.php` (context library) and `views/v3/partials/404/default.blade.php` (context views) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `ba7d2dea` feat: customisation for error pages (#1420); `4bf59a92` feat: 401 (#1295); `e8bc5d6a` Styles for 404 — run `git show` on any of them.
AC1 · Text alternatives · <img> without a text alternative · ×2
  • <img> without a text alternative library/BrandedEmails/HtmlTemplate/views/default.blade.php:59 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative views/v3/partials/content/pdf/frontpage.blade.php:6 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang library/BrandedEmails/HtmlTemplate/views/default.blade.php:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang views/v3/partials/content/pdf/layout.blade.php:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label Modularity/templates/editor/modularity-module-description.php:5 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <select> without a programmatic label · ×1
  • <select> without a programmatic label Modularity/templates/editor/modularity-sidebar-drop-area.php:11 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC5 · ARIA correctness · role="radio" missing required aria-checked · ×1
  • role="radio" missing required aria-checked assets/source/js/admin/acf/paletteColorChoices.ts:70 — The radio role requires aria-checked to convey its state. Add it.
D11 · Test Reliability · Test suite cannot be installed from its own lockfile · ×1
  • Test suite cannot be installed from its own lockfile: the repository root — The jest suite in the repository root was never exercised because its dependency install refused the committed lockfile — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@wordpress/components' · ×1
  • Unlisted import '@wordpress/components' library/BackdropBanner/js/Editor/backdropBannerPanel.tsx:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react-dom' · ×1
  • Unlisted import 'react-dom' library/PostsList/Block/js/SettingsPanel/PostsSettingsPanel/OrderByControl/OrderByControl.test.tsx:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 570 finding(s)
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file Modularity/source/js/editor/module.js:1 — 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 assets/source/js/admin/designShareUtils.ts:1 — 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 assets/source/js/nav.ts:1 — 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 assets/source/js/postsList/PostsListAsync.ts:1 — 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 Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:1 — 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 Modularity/source/js/private/userEditableList.ts:1 — 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 Modularity/source/js/editor/dragAndDrop.js:1 — 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 Modularity/source/php/Module/Subscribe/assets/ungapd.ts:1 — 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 assets/source/js/comments.ts:1 — 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 Modularity/source/php/Module/InteractiveMap/assets/map/markers.ts:1 — 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 Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:1 — 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 Modularity/source/js/modularity-editor-modal.js:1 — 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 Modularity/source/php/Module/InteractiveMap/assets/map/markerClick/markerClick.ts:1 — 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 Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:1 — 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 library/Customizer/Controls/MultiSelect/MultiSelectControl.ts:1 — 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 assets/source/js/admin/designShare.ts:1 — 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 Modularity/source/php/Module/Posts/assets/xhr.ts:1 — 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 assets/source/mce-js/mce-buttons.js:1 — 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 library/Customizer/Controls/TabBox/TabBoxControl.ts:1 — 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 library/Chat/js/chat/feedback.ts:1 — 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 library/Chat/js/chat/chat.ts:1 — 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 Modularity/source/js/modularity-editor.js:1 — 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 assets/source/js/restApi/newEndpoint.ts:1 — 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 assets/source/js/hashHighlightManager.ts:1 — 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 assets/source/js/json/language.js:1 — 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.
D10 · Test Quality · No assertions · ×16
  • No assertions: testAddHooks library/CommonFieldGroups/DisableFieldsThatAreCommonlyManagedOnSubsitesTest.php:97 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testAddHooks library/CommonFieldGroups/PopulateCommonFieldGroupSelectTest.php:103 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testRedirectsToFirstFutureOccasion library/Controller/SingularEvent/EnsureVisitingSingularOccasion/EnsureVisitingSingularOccasionTest.php:14 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testRedirectsToLastPastOccasion library/Controller/SingularEvent/EnsureVisitingSingularOccasion/EnsureVisitingSingularOccasionTest.php:33 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testTicketTemplateNameContainsImportKulturkort library/Kulturkortet/Vitec/VitecTicketTest.php:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCurrentDateWithinValidRange library/Kulturkortet/Vitec/VitecTicketTest.php:48 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testStartMethodDoesNothing library/ProgressReporter/NullProgressReporterServiceTest.php:17 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSetMessageMethodDoesNothing library/ProgressReporter/NullProgressReporterServiceTest.php:25 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSetPercentageMethodDoesNothing library/ProgressReporter/NullProgressReporterServiceTest.php:33 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFinishMethodDoesNothing library/ProgressReporter/NullProgressReporterServiceTest.php:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFlushWithContent library/ProgressReporter/OutputBuffer/OutputBufferTest.php:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFlushWithoutContent library/ProgressReporter/OutputBuffer/OutputBufferTest.php:33 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testStartMethodSetsHeaders library/ProgressReporter/SseProgressReporterServiceTest.php:20 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testStartMethodSendsStartEvent library/ProgressReporter/SseProgressReporterServiceTest.php:32 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSetMessageMethodSendsMessageEvent library/ProgressReporter/SseProgressReporterServiceTest.php:42 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testAppliesFilterToMarkupProcessor library/Styleguide/AddLayerOrderDefinitionToHead/AddLayerOrderDefinitionToHeadTest.php:24 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D6 · Cohesion (LCOM4) · Low cohesion · ×16
  • Low cohesion: Upgrade (LCOM4 49) library/Upgrade.php:51 — Upgrade's methods fall into 49 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 49 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: BaseController (LCOM4 27) library/Controller/BaseController.php:29 — BaseController's methods fall into 27 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 27 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: BlockManager (LCOM4 10) Modularity/source/php/BlockManager.php:12 — BlockManager's methods fall into 10 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 10 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: ModuleManager (LCOM4 7) Modularity/source/php/ModuleManager.php:10 — ModuleManager's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: App (LCOM4 6) REDACTED:12 — App'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: Display (LCOM4 5) Modularity/source/php/Display.php:13 — Display'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: Module (LCOM4 5) Modularity/source/php/Module.php:12 — Module'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: Template (LCOM4 5) library/Template.php:25 — Template'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: PostsAjax (LCOM4 4) REDACTED:7 — PostsAjax'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: A11yStatement (LCOM4 4) library/A11yStatement/A11yStatement.php:17 — A11yStatement'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: PaletteColorChoices (LCOM4 4) library/Admin/Acf/PaletteColorChoices.php:22 — PaletteColorChoices'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: Editor (LCOM4 4) library/Admin/Roles/Editor.php:10 — Editor'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: Editor (LCOM4 4) library/Admin/UI/Editor.php:8 — Editor'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: PdfGenerator (LCOM4 4) library/Api/Pdf/PdfGenerator.php:11 — PdfGenerator'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: Navigation (LCOM4 4) library/Helper/Navigation.php:16 — Navigation'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: Navigation (LCOM4 4) library/Theme/Navigation.php:12 — Navigation'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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×15
  • Animation without a prefers-reduced-motion guard library/ProgressReporter/AdminProgressAction/js/UIComponents/ProgressBarWithLabel.ts:35 — `::-webkit-progress-value` moves (`transition: width 1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/Kulturkortet/QRCodeViewer/css/actions.scss:18 — `. . __menu-card` moves (`transition: opacity 0.2s ease, transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/Kulturkortet/QRCodeViewer/css/ticket.scss:47 — `. . __inner-card::before` moves (`animation: snake-rotate 5s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/Customizer/Controls/Sortable/SortableControl.css:150 — `.municipio-sortable-item__handle[data-tooltip]::before` moves (`transition: opacity 120ms ease, transform 120ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/Customizer/Controls/Sortable/SortableControl.css:170 — `.municipio-sortable-item__handle[data-tooltip]::after` moves (`transition: opacity 120ms ease, transform 120ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/BackdropBanner/js/Front/backdrop-banner.scss:175 — `.backdrop-banner__navigation-item-content` moves (`transition: opacity 0.2s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard assets/source/sass/event.scss:78 — `.event-accordion__trigger[aria-pressed="true"] .c-icon` moves (`transition: ease .3s transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard assets/source/sass/navigation/_header-flexible.scss:159 — `.c-header.c-header--flexible.c-header--logotype-scroll-shrink .c-header__lower-left .c-header__item--logotype .c-header__logotype` moves (`transition: transform 0.3s ease, height 0.3s ease, margin-bottom 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard assets/source/sass/navigation/_user.scss:27 — `.user::after` moves (`transition: width .3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Modularity/source/sass/partials/_block-content.scss:67 — `.modularity-preview-hidden::after` moves (`transition: 500ms opacity, 300ms transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Modularity/source/sass/partials/_loader-takeover.scss:28 — `body.modularity-loader-takeover::after` moves (`animation: 1000ms loading-ball ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Modularity/source/sass/partials/_modules.scss:73 — `.modularity-module-icon svg` moves (`transition: transform 200ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Modularity/source/sass/partials/_spinner.scss:31 — `.modularity-modal-spinner:after` moves (`animation: modularity-spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Modularity/source/php/Module/InteractiveMap/assets/interactive-map.scss:27 — `.interactive-map__highlighted-marker` moves (`animation: highlight-marker 0.1s ease-in-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Modularity/source/php/Module/InteractiveMap/assets/interactive-map.scss:209 — `.interactive-map__filter-icon` moves (`transition: transform .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D3 · God Classes · MethodTooLong · ×13
  • MethodTooLong: Archive.__construct library/Customizer/Sections/Archive.php:12 — MethodTooLong — __construct runs 298 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 198 over it, 2.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: BaseController.__construct library/Controller/BaseController.php:68 — MethodTooLong — __construct runs 282 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 182 over it, 2.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: App.__construct library/App.php:52 — MethodTooLong — __construct runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MegaMenu.__construct library/Customizer/Sections/Menu/MegaMenu.php:15 — MethodTooLong — __construct runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PdfGenerator.addAcfToPdfGeneratorOptionsPage library/Api/Pdf/PdfGenerator.php:126 — MethodTooLong — addAcfToPdfGeneratorOptionsPage runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WoffConverter.convertToTTF library/Helper/FileConverters/WoffConverter.php:122 — MethodTooLong — convertToTTF runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Hero.__construct library/Customizer/Sections/Component/Hero.php:10 — MethodTooLong — __construct runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Editor.getAvailableStyleFormats library/Admin/UI/Editor.php:156 — MethodTooLong — getAvailableStyleFormats runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Sidebars.register library/Theme/Sidebars.php:75 — MethodTooLong — register runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PdfGenerator.getFieldsForEachPostType library/Api/Pdf/PdfGenerator.php:368 — MethodTooLong — getFieldsForEachPostType runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Contacts.prepareContacts Modularity/source/php/Module/Contacts/Contacts.php:88 — MethodTooLong — prepareContacts runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Drawer.__construct library/Customizer/Sections/Menu/Drawer.php:12 — MethodTooLong — __construct runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Siteselector.__construct library/Customizer/Sections/Menu/Siteselector.php:10 — MethodTooLong — __construct 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×13
  • Duplicated block (7 lines × 2) library/ImageConvert/Cache/ConversionCache.php:243 — library/ImageConvert/Cache/ConversionCache.php:243-249 | library/ImageConvert/Cache/ConversionCache.php:280-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) REDACTED:189 — REDACTED:189-195 | library/Helper/Url.php:14-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) Modularity/source/php/Module/ManualInput/ManualInput.php:386 — Modularity/source/php/Module/ManualInput/ManualInput.php:386-392 | Modularity/source/php/Module/Map/Map.php:310-316 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) Modularity/source/php/Module/ManualInput/Private/PrivateController.php:190 — Modularity/source/php/Module/ManualInput/Private/PrivateController.php:190-196 | Modularity/source/php/Module/Posts/Private/PrivateController.php:165-171 — before extracting anything, compare `Modularity/source/php/Module/ManualInput/Private/PrivateController.php` and `Modularity/source/php/Module/Posts/Private/PrivateController.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) library/Content/CustomPostType.php:171 — library/Content/CustomPostType.php:171-177 | library/Content/CustomTaxonomy.php:72-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) library/Controller/A11y.php:296 — library/Controller/A11y.php:296-302 | library/Controller/PrivacyPolicy.php:108-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) library/Controller/SingularEvent/Mappers/MapDescription.php:53 — library/Controller/SingularEvent/Mappers/MapDescription.php:53-59 | library/Controller/SingularEvent/Mappers/MapScheduleDescription.php:114-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) library/PostObject/Date/CachedTimestampResolver.php:33 — library/PostObject/Date/CachedTimestampResolver.php:33-39 | library/PostObject/Icon/Resolvers/CachedIconResolver.php:33-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php:61 — library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php:61-67 | library/PostsList/ViewCallableProviders/Schema/Event/GetPermalink.php:56-62 — before extracting anything, compare `library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php` and `library/PostsList/ViewCallableProviders/Schema/Event/GetPermalink.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:150 — library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:150-156 | library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php:87-93 — before extracting anything, compare `library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php` and `library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) Modularity/source/php/Module/ManualInput/Private/PrivateController.php:77 — Modularity/source/php/Module/ManualInput/Private/PrivateController.php:77-83 | Modularity/source/php/Module/Posts/Private/PrivateController.php:59-65 — before extracting anything, compare `Modularity/source/php/Module/ManualInput/Private/PrivateController.php` and `Modularity/source/php/Module/Posts/Private/PrivateController.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) library/Controller/School/ElementarySchool/UspsGenerator.php:22 — library/Controller/School/ElementarySchool/UspsGenerator.php:22-28 | library/Controller/School/Preschool/UspsGenerator.php:23-29 — `library/Controller/School/ElementarySchool/UspsGenerator.php` and `library/Controller/School/Preschool/UspsGenerator.php` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) library/Controller/School/ElementarySchool/UspsGenerator.php:72 — library/Controller/School/ElementarySchool/UspsGenerator.php:72-78 | library/Controller/School/Preschool/UspsGenerator.php:84-90 — `library/Controller/School/ElementarySchool/UspsGenerator.php` and `library/Controller/School/Preschool/UspsGenerator.php` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D15 · Churn × Complexity Hotspots · Repeated repair · ×10
  • Repeated repair: library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php:117 — library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is WordPressAssetEnqueuer.restoreFragment at line 117), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: enqueue assets for oembeds”; “fix: enqueue assets fond by markup indicators of components (#2302)”; “fix: enqueue fab css when a FAB button menu is used.”; “fix: restore assets from Modularity fragment cache (#2256)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php`: 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.
  • Repeated repair: library/Chat/Render/ChatRenderConfig.php library/Chat/Render/ChatRenderConfig.php:126 — library/Chat/Render/ChatRenderConfig.php changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is ChatRenderConfig.getAssistantFromString at line 126), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “🐛 Bug(chat): fix fatal error when chat avatar image is no longer available (#2322)”; “fix: correcting chat block functionality and appearance (#2242)”; “🐛 Bug(chat): preserve chat session id between page loads (#2196)”; “fix: making greetingsphrase a text area for chat”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Chat/Render/ChatRenderConfig.php`: 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.
  • Repeated repair: library/ImageConvert/ImageProcessor.php library/ImageConvert/ImageProcessor.php:81 — library/ImageConvert/ImageProcessor.php 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 ImageProcessor.convertImage at line 81), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: convert palette images to true colour before webp conversion (#2372)”; “fix: compare memory size in image contract feature (#2219)”; “fix: reject invalid intermediate images (#2150)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/ImageConvert/ImageProcessor.php`: 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.
  • Repeated repair: library/Chat/Config/ChatConfig.php library/Chat/Config/ChatConfig.php:44 — library/Chat/Config/ChatConfig.php changed 4 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 7 (its worst body is ChatConfig.getAssistantForActiveQuery at line 44), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: correcting key for chat global options”; “fix: do not use acf to get on/off options (#2222)”; “🐛 Bug(chat): correctly hide bubble even if default assistant is not null”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Chat/Config/ChatConfig.php`: 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.
  • Repeated repair: library/Controller/SingularElementarySchool.php library/Controller/SingularElementarySchool.php:22 — library/Controller/SingularElementarySchool.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is SingularElementarySchool.init at line 22), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: show single school image without slider (#2385)”; “fix(Schools): replace events section with events block (#2305)”; “fix: support alerts for elementary- and pre-schools (#2143)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Controller/SingularElementarySchool.php`: 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.
  • Repeated repair: library/Controller/SingularPreschool.php library/Controller/SingularPreschool.php:21 — library/Controller/SingularPreschool.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is SingularPreschool.init at line 21), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: show single school image without slider (#2385)”; “fix(Schools): replace events section with events block (#2305)”; “fix: support alerts for elementary- and pre-schools (#2143)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Controller/SingularPreschool.php`: 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.
  • Repeated repair: library/Controller/SingularJobPosting.php library/Controller/SingularJobPosting.php:150 — library/Controller/SingularJobPosting.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is SingularJobPosting.populateInformationList at line 150), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(JobPosting): Ensure ethicsPolicy is properly formatted and not empty (#2363)”; “fix(JobPosting): add paragraphs to ethicsPolicy”; “fix(JobPosting): put ethicsPolicy in paper component (#2319)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Controller/SingularJobPosting.php`: 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.
  • Repeated repair: library/SchemaData/ExternalContent/WpPostArgsFromSchemaObject/JobPostingDecorator.php library/SchemaData/ExternalContent/WpPostArgsFromSchemaObject/JobPostingDecorator.php:45 — library/SchemaData/ExternalContent/WpPostArgsFromSchemaObject/JobPostingDecorator.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is JobPostingDecorator.applyPropertiesFromJobPosting at line 45), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(JobPosting): put ethicsPolicy in paper component (#2319)”; “fix(JobPosting): append ethicsPolicy to content (#2318)”; “fix(JobPosting): align views with updated JobPosting json shape (#2279)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/SchemaData/ExternalContent/WpPostArgsFromSchemaObject/JobPostingDecorator.php`: 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.
  • Repeated repair: library/Chat/js/popover/popover.ts library/Chat/js/popover/popover.ts:21 — library/Chat/js/popover/popover.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is Popover.handleBreakpointChange at line 21), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: correcting message height for popover cover mode”; “fix: remove unnecessary coverRanOnce”; “fix: correcting chat cover state (#2240)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Chat/js/popover/popover.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.
  • Repeated repair: library/SearchIndex/Admin/SearchIndexSettings.php library/SearchIndex/Admin/SearchIndexSettings.php:106 — library/SearchIndex/Admin/SearchIndexSettings.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is SearchIndexSettings.addAttachmentMimeTypeChoices at line 106), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(search-index): restrict settings updates to admins (#2189)”; “fix(search-index): honor constant-backed admin values (#2185)”; “fix(search-index): appearance adjustments (#2178)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/SearchIndex/Admin/SearchIndexSettings.php`: 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 · ×10
  • TodoComment library/SchemaData/SchemaPropertiesForm/SetPostTitleFromSchemaTitle/SetPostTitleFromSchemaTitleTest.php:53 — // TODO: how to mock correctly since we are using a static helper? — 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 library/SchemaData/ExternalContent/Cron/AllowCronToEditPosts.php:52 — // TODO: Replace with removeFilter() when it's available in WpService. — 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 library/MarkupProcessor/Processors/TidyProcessor.php:37 — // TODO: Add filter to be able to modify this from withing another feature, e.g. Styleguide — 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 library/Controller/BaseController.php:257 — // TODO: Find out what it does — 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 library/Controller/BaseController.php:268 — // TODO: Find out what it does — 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 library/Controller/BaseController.php:371 — //TODO: MOVE TO USER HELPER CLASS — 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 library/Controller/BaseController.php:383 — //TODO: MOVE TO USER HELPER CLASS — 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 Modularity/source/php/Editor.php:502 — // Todo: This will duplicate for every sidebar, move it to top level of array(?) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:21 — //TODO: Is wp_ajax_get_sortable_meta_keys_v2 ever used? — 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 Modularity/source/php/Module/ManualInput/ManualInput.php:100 — // TODO: change name and migrate — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×10
  • Duplicated block (9 lines × 2) library/Controller/E401.php:82 — library/Controller/E401.php:82-90 | library/Controller/E403.php:80-88 — before extracting anything, compare `library/Controller/E401.php` and `library/Controller/E403.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/E401.php:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) library/Controller/E401.php:151 — library/Controller/E401.php:151-159 | library/Controller/E403.php:146-154 — before extracting anything, compare `library/Controller/E401.php` and `library/Controller/E403.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/E401.php:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) library/PostsList/Block/PostsListBlockRenderer/PostsListBlockRenderer.php:51 — library/PostsList/Block/PostsListBlockRenderer/PostsListBlockRenderer.php:51-59 | library/PostsList/Block/PostsListBlockRenderer/PostsListBlockRenderer.php:70-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) library/Styleguide/Customize/ComponentData/ComponentData.php:21 — library/Styleguide/Customize/ComponentData/ComponentData.php:21-29 | library/Styleguide/Customize/TokenData/TokenData.php:22-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `library/Styleguide/Customize/TokenData/TokenData.php:31` calls `AddOverrideFontFamilies`, `addHooks`, `FontFamilies` and `library/Styleguide/Customize/ComponentData/ComponentData.php:31` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:117 — library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:117-125 | library/Upgrade/V59/MigrateMalformedFlexibleHeaderLowerArea.php:71-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/DateHandler.php:26 — library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/DateHandler.php:26-34 | library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/DateTimeHandler.php:26-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/DateHandler.php:26` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) library/Integrations/Polylang/ResolveHomeUrl.php:61 — library/Integrations/Polylang/ResolveHomeUrl.php:61-69 | library/Integrations/Polylang/ResolvePdfNotFoundUrl.php:61-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:208 — library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:208-216 | library/Integrations/Polylang/ResolveTranslatedPageLink.php:262-270 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:226 — library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:226-234 | library/Integrations/Polylang/ResolveTranslatedPageLink.php:298-306 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) library/Integrations/Polylang/ResolveTranslatedPostTypeArchiveLink.php:96 — library/Integrations/Polylang/ResolveTranslatedPostTypeArchiveLink.php:96-104 | library/Integrations/Polylang/ResolveTranslatedPostTypeLink.php:120-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×10
  • Swallowed exception (caught, then discarded) library/SearchIndex/Search/SearchQuery.php:50 — `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/SearchIndex/Index/PostIndexer.php:57 — `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/SearchIndex/Index/PostIndexer.php:74 — `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/SchemaData/ExternalContent/JsonToSchemaObjects/SchemaSanitizer/Mappers/SetEventDatesFromEventSchedule.php:49 — `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/PostsList/ViewCallableProviders/Schema/ExhibitionEvent/GetOccasionText.php:75 — `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/Kulturkortet/MunicipioAuth/controller/secure/JWTStrategy.php:49 — `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/Kulturkortet/MunicipioAuth/Visma/VismaAuthController.php:54 — `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/Customizer/CustomizerPanel.php:26 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/Controller/Sponsor/SponsorPresentation.php:332 — `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Modularity/source/php/Helper/Cache.php:225 — `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D15 · Churn × Complexity Hotspots · Hotspot · ×8
  • Hotspot: library/Controller/BaseController.php library/Controller/BaseController.php:68 — library/Controller/BaseController.php changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in BaseController.__construct at line 68. 4 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Controller/BaseController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: library/Upgrade/V70/Version70.php library/Upgrade/V70/Version70.php:73 — library/Upgrade/V70/Version70.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in Version70.migrateBlocks at line 73. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Upgrade/V70/Version70.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: library/Admin/Gutenberg/Blocks/BlockManager.php library/Admin/Gutenberg/Blocks/BlockManager.php:149 — library/Admin/Gutenberg/Blocks/BlockManager.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in BlockManager.renderContainerCallback at line 149. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Admin/Gutenberg/Blocks/BlockManager.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: library/Helper/Post.php library/Helper/Post.php:176 — library/Helper/Post.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Post.complementObject at line 176. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Helper/Post.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modularity/source/php/Module/ManualInput/ManualInput.php Modularity/source/php/Module/ManualInput/ManualInput.php:38 — Modularity/source/php/Module/ManualInput/ManualInput.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in ManualInput.data at line 38. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- Modularity/source/php/Module/ManualInput/ManualInput.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: library/Helper/Navigation.php library/Helper/Navigation.php:809 — library/Helper/Navigation.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Navigation.getBreadcrumbItems at line 809. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Helper/Navigation.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modularity/source/php/Module/Posts/Posts.php Modularity/source/php/Module/Posts/Posts.php:145 — Modularity/source/php/Module/Posts/Posts.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Posts.data at line 145. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- Modularity/source/php/Module/Posts/Posts.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: library/Customizer/Applicators/Types/Modifier.php library/Customizer/Applicators/Types/Modifier.php:38 — library/Customizer/Applicators/Types/Modifier.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Modifier.applyDataFilterFunction at line 38. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 13:50:32 +00:00' --until='2026-11-16 13:50:32 +00:00' --full-history --no-merges -- library/Customizer/Applicators/Types/Modifier.php`: 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×8
  • Duplicated block (11 lines × 2) library/Customizer/CustomField.php:23 — library/Customizer/CustomField.php:23-33 | library/Customizer/NativeField.php:21-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:659 — library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:659-669 | library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:670-680 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) library/Upgrade/V64/Version64.php:189 — library/Upgrade/V64/Version64.php:189-199 | library/Upgrade/V65/Version65.php:118-128 — before extracting anything, compare `library/Upgrade/V64/Version64.php` and `library/Upgrade/V65/Version65.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) library/Controller/SingularSponsorDemandEvent.php:11 — library/Controller/SingularSponsorDemandEvent.php:11-21 | library/Controller/SingularSponsorOffer.php:11-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) Modularity/source/php/Module/Iframe/Iframe.php:58 — Modularity/source/php/Module/Iframe/Iframe.php:58-68 | Modularity/source/php/Module/Map/Map.php:268-278 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) library/Controller/A11y.php:88 — library/Controller/A11y.php:88-98 | library/Controller/PrivacyPolicy.php:34-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) library/Controller/SingularEvent/GetEventPlaceName.php:25 — library/Controller/SingularEvent/GetEventPlaceName.php:25-35 | library/PostsList/ViewCallableProviders/Schema/Event/GetPlaceName.php:36-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) library/SchemaData/SchemaPropertiesForm/FormBuilder/Fields/MultiSelectField.php:54 — library/SchemaData/SchemaPropertiesForm/FormBuilder/Fields/MultiSelectField.php:54-64 | library/SchemaData/SchemaPropertiesForm/FormBuilder/Fields/SelectField.php:46-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×8
  • Duplicated block (8 lines × 2) Modularity/source/php/Helper/Wp.php:47 — Modularity/source/php/Helper/Wp.php:47-54 | Modularity/source/php/Helper/Wp.php:93-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Modularity/source/php/Helper/Wp.php:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Modularity/source/php/Module/Script/Script.php:69 — Modularity/source/php/Module/Script/Script.php:69-77 | Modularity/source/php/Module/Script/Script.php:81-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Modularity/source/php/Module/Script/Script.php:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) library/Controller/School/ElementarySchool/UspsGenerator.php:83 — library/Controller/School/ElementarySchool/UspsGenerator.php:83-90 | library/Controller/School/Preschool/UspsGenerator.php:95-102 — `library/Controller/School/ElementarySchool/UspsGenerator.php` and `library/Controller/School/Preschool/UspsGenerator.php` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:642 — library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:642-649 | library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:586-593 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:77 — library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:77-84 | library/SchemaData/SchemaPropertyValueSanitizer/PlaceFromAcfGoogleMapsFieldSanitizer.php:74-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 2) Modularity/source/php/Module/Script/Script.php:158 — Modularity/source/php/Module/Script/Script.php:158-165 | Modularity/source/php/Module/Table/Table.php:32-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:106 — Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:106-113 | Modularity/source/php/Upgrade/Migrators/Module/Custom/AcfModuleIndexRepeaterMigrator.php:73-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) library/Customizer/CustomField.php:46 — library/Customizer/CustomField.php:46-53 | library/Customizer/NativeField.php:44-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · TooManyMethods · ×7
  • TooManyMethods: Upgrade library/Upgrade.php:51 — TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× 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: BaseController library/Controller/BaseController.php:29 — 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: MenuBuilder library/Controller/Navigation/MenuBuilder.php:44 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. Most of these members implement Navigation.MenuBuilderInterface (34 of 36 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: Display Modularity/source/php/Display.php:13 — 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: PanelsRegistry library/Customizer/PanelsRegistry.php:5 — 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.
  • TooManyMethods: Navigation library/Helper/Navigation.php:16 — 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.
  • TooManyMethods: MigrateLegacyGoogleFontsToNativeFontLibrary library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:14 — 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.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×7
  • Edited copy of a member (5 corresponding lines) library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php:26 — library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php:26-30 | library/Controller/School/Preschool/AccordionListItemsGenerator.php:26-30 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) library/Customizer/NativeField.php:179 — library/Customizer/NativeField.php:179-187 | library/Customizer/CustomField.php:155-159 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) library/ImageConvert/Cache/ConversionCache.php:54 — library/ImageConvert/Cache/ConversionCache.php:54-58 | library/ImageConvert/Cache/PageLoadCache.php:68-72 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) library/SchemaData/SchemaPropertyValueSanitizer/DateTimeSanitizer.php:28 — library/SchemaData/SchemaPropertyValueSanitizer/DateTimeSanitizer.php:28-36 | library/SchemaData/SchemaPropertyValueSanitizer/ArrayOfImagesSanitizer.php:28-32 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Modularity/source/php/Helper/FormatObject.php:74 — Modularity/source/php/Helper/FormatObject.php:74-78 | library/Helper/FormatObject.php:70-76 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) REDACTED:407 — REDACTED:407-411 | Modularity/source/php/Module/Posts/Posts.php:349-355 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) library/SchemaData/SchemaPropertiesForm/FormBuilder/Fields/DateField.php:30 — library/SchemaData/SchemaPropertiesForm/FormBuilder/Fields/DateField.php:30-34 | library/SchemaData/SchemaPropertiesForm/FormBuilder/Fields/DateTimeField.php:34-38 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×7
  • Duplicated block (14 lines × 2) library/Controller/BaseController.php:1390 — library/Controller/BaseController.php:1390-1403 | library/Customizer/Sections/Header/Layout.php:337-350 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/BaseController.php:1390` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) library/Controller/E401.php:61 — library/Controller/E401.php:61-74 | library/Controller/E403.php:62-75 — before extracting anything, compare `library/Controller/E401.php` and `library/Controller/E403.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `library/Controller/E401.php:77` calls `escUrl`, `homeUrl`, `addQueryArg` and `library/Controller/E403.php:78` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 2) library/Customizer/Controls/AlphaColor/AlphaColorControl.php:99 — library/Customizer/Controls/AlphaColor/AlphaColorControl.php:99-112 | library/Customizer/Controls/MultiColor/MultiColorControl.php:68-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (14 lines × 2) library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php:78 — library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php:78-91 | library/PostsList/ViewCallableProviders/Schema/Event/GetPermalink.php:73-86 — before extracting anything, compare `library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php` and `library/PostsList/ViewCallableProviders/Schema/Event/GetPermalink.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php:96 — library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php:96-109 | library/PostsList/ViewCallableProviders/Schema/Event/GetPermalink.php:91-104 — before extracting anything, compare `library/PostsList/ViewCallableProviders/Schema/Event/GetDateBadgeDate.php` and `library/PostsList/ViewCallableProviders/Schema/Event/GetPermalink.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:38 — library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:38-51 | library/SchemaData/SchemaPropertyValueSanitizer/PlaceFromAcfGoogleMapsFieldSanitizer.php:35-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (14 lines × 2) library/Theme/Sidebars.php:314 — library/Theme/Sidebars.php:314-327 | library/Theme/Sidebars.php:366-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `library/Theme/Sidebars.php:328` calls `array` and `library/Theme/Sidebars.php:380` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×6
  • Duplicated block (12 lines × 2) Modularity/source/php/Integrations/Component/ImageFocusResolver.php:27 — Modularity/source/php/Integrations/Component/ImageFocusResolver.php:27-38 | library/Integrations/Component/ImageFocusResolver.php:26-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Modularity/source/php/Integrations/Component/ImageFocusResolver.php:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Modularity/source/php/Module/Video/Video.php:232 — Modularity/source/php/Module/Video/Video.php:232-243 | library/Helper/VideoService.php:302-313 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) library/StickyPost/AddStickyCheckboxForPost.php:61 — library/StickyPost/AddStickyCheckboxForPost.php:61-72 | library/UserGroup/AddSelectUserGroupForPrivatePost.php:71-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) library/Theme/Support.php:193 — library/Theme/Support.php:193-204 | library/Theme/Support.php:206-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) Modularity/source/php/BlockManager.php:631 — Modularity/source/php/BlockManager.php:631-642 | Modularity/source/php/Display.php:685-696 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) library/Controller/E401.php:30 — library/Controller/E401.php:30-41 | library/Controller/E403.php:34-45 — before extracting anything, compare `library/Controller/E401.php` and `library/Controller/E403.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemIsCurrentPage.php:28 — library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemIsCurrentPage.php:28-37 | library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemsHref.php:28-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemIsCurrentPage.php:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) library/Controller/Sponsor/SponsorPresentation.php:279 — library/Controller/Sponsor/SponsorPresentation.php:279-288 | library/Controller/Sponsor/SponsorPresentation.php:294-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) library/Upgrade/V70/Version70.php:50 — library/Upgrade/V70/Version70.php:50-59 | library/Upgrade/V71/Version71.php:37-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Upgrade/V70/Version70.php:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `library/Upgrade/V71/Version71.php:36` calls `Version70` and `library/Upgrade/V70/Version70.php:49` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) library/Api/Customizer/DesignLibraryFontActivation.php:177 — library/Api/Customizer/DesignLibraryFontActivation.php:177-186 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:349-358 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) library/Controller/Archive/Mappers/FilterConfigMappers/MapDateFilterEnabled.php:20 — library/Controller/Archive/Mappers/FilterConfigMappers/MapDateFilterEnabled.php:20-29 | library/Controller/Archive/Mappers/FilterConfigMappers/MapTextSearchEnabled.php:20-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) library/ImageConvert/NormalizeImageSize.php:22 — library/ImageConvert/NormalizeImageSize.php:22-31 | library/ImageConvert/Resolvers/MissingSize/ResolveMissingImageSize.php:23-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · ClassTooLong · ×5
  • ClassTooLong: Upgrade library/Upgrade.php:51 — ClassTooLong — 753 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 353 over it, 1.88× 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: BaseController library/Controller/BaseController.php:29 — ClassTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 244 over it, 1.61× 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: App library/App.php:47 — ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 38 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.
  • ClassTooLong: Editor Modularity/source/php/Editor.php:9 — ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 30 over it, 1.08× 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: Navigation library/Helper/Navigation.php:16 — ClassTooLong — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 1 over it, 1.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.
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: BaseController.php ↔ Menu.php library/Controller/BaseController.php:1 — `library/Controller/BaseController.php` and `library/Controller/Navigation/Menu.php` change together 83% of the time (10 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `90d1746e` fix. additional menus; `7864b248` feat: accessibility menu; `dcc4b185` feat: breadcrumb menu — run `git show` on any of them.
  • Change coupling: single-schema-elementary-school.blade.php ↔ single-schema-preschool.blade.php views/v3/single-schema-elementary-school.blade.php:1 — `views/v3/single-schema-elementary-school.blade.php` and `views/v3/single-schema-preschool.blade.php` change together 80% of the time (8 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `f108aefd` fix: show single school image without slider (#2385); `eca89e3f` fix: add missing partials.navigation.helper to school/pre-school (#2111); `47b18f39` fix: description and working title for school actions (#1786) — run `git show` on any of them.
  • Change coupling: BackwardsCompatiblePostObject.php ↔ PostObjectFromWpPost.php library/PostObject/Decorators/BackwardsCompatiblePostObject.php:1 — `library/PostObject/Decorators/BackwardsCompatiblePostObject.php` and `library/PostObject/Decorators/PostObjectFromWpPost.php` change together 60% of the time (6 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, 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 `b32b4651` feat: timestamp getters for PostObjectInterface (#1283); `235539e4` feat: allow PostObject getIcon() to get icons from other blog if orig…; `48b8348c` feat: implement AbstractPostObjectDecorator and update decorators for… — run `git show` on any of them.
  • Change coupling: PdfArchiveEndpoint.php ↔ PdfIdEndpoint.php library/Api/Pdf/PdfArchiveEndpoint.php:1 — `library/Api/Pdf/PdfArchiveEndpoint.php` and `library/Api/Pdf/PdfIdEndpoint.php` change together 58% of the time (7 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `e436fe24` feat: add Polylang compatibility patches for translated page mappings…; `ea122b13` feat: pdf sorted and categorized posts (#886); `5ee2c707` fix: rest route notices — run `git show` on any of them.
  • Change coupling: MenuBuilder.php ↔ MenuDirector.php library/Controller/Navigation/MenuBuilder.php:1 — `library/Controller/Navigation/MenuBuilder.php` and `library/Controller/Navigation/MenuDirector.php` change together 54% of the time (7 of the 13 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `20b16868` feat: page for post type support; `0be18183` fix: standard menu with page tree subitems only append childre to bot…; `888feb5b` fix: standard menu with page tree subitems only append childre to bottom — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) library/PostObject/Icon/Resolvers/PostIconResolver.php:53 — library/PostObject/Icon/Resolvers/PostIconResolver.php:53-65 | library/PostObject/Icon/Resolvers/PostIconResolver.php:76-88 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) library/Api/PlaceSearch/Providers/Openstreetmap.php:94 — library/Api/PlaceSearch/Providers/Openstreetmap.php:94-106 | library/Api/PlaceSearch/Providers/Openstreetmap.php:118-133 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) library/Helper/ElementAttribute.php:22 — library/Helper/ElementAttribute.php:22-36 | library/Helper/ElementAttribute.php:47-59 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/RepeaterWithSchemaObjectsHandler.php:73 — library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/RepeaterWithSchemaObjectsHandler.php:73-86 | library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/GroupWithSchemaObjectHandler.php:66-78 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) library/Upgrade.php:1335 — library/Upgrade.php:1335-1353 | library/Admin/Options/Timestamp.php:15-27 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×5
  • Edited copy of a member (7 corresponding lines) library/Styleguide/ComponentAssets/StylesheetManifest.php:19 — library/Styleguide/ComponentAssets/StylesheetManifest.php:19-25 | library/Styleguide/Customize/ApplyStyles/EditorColorTokens.php:50-56 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) library/Controller/A11y.php:311 — library/Controller/A11y.php:311-319 | library/Controller/PrivacyPolicy.php:122-128 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Modularity/source/php/Upgrade/Migrators/Block/AcfBlockMigrationHandler.php:98 — Modularity/source/php/Upgrade/Migrators/Block/AcfBlockMigrationHandler.php:98-104 | Modularity/source/php/Upgrade/Migrators/Module/AcfModuleMigrationHandler.php:81-87 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) REDACTED:302 — REDACTED:302-308 | Modularity/source/php/Module/Markdown/Markdown.php:277-283 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) library/Integrations/Polylang/ResolveHomeUrl.php:45 — library/Integrations/Polylang/ResolveHomeUrl.php:45-51 | library/Integrations/Polylang/ResolvePdfNotFoundUrl.php:45-51 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) library/Customizer/Applicators/Types/Component.php:125 — library/Customizer/Applicators/Types/Component.php:125-167 | library/Customizer/Applicators/Types/Modifier.php:89-126 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) library/Upgrade/V46/MigrateLegacyFooterCustomizerToComponentTokens.php:103 — library/Upgrade/V46/MigrateLegacyFooterCustomizerToComponentTokens.php:103-123 | library/Upgrade/V48/MigrateLegacyDatebadgeCustomizerToDesignTokens.php:57-77 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) library/Controller/Navigation/Decorators/Menu/StructureMenuItems.php:47 — library/Controller/Navigation/Decorators/Menu/StructureMenuItems.php:47-73 | library/Helper/Navigation/MenuConstructor.php:81-101 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) library/Helper/BladeCache.php:72 — library/Helper/BladeCache.php:72-92 | library/Helper/BladeCache.php:122-146 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×4
  • Edited copy of a member (24 corresponding lines) library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:87 — library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:87-111 | library/Kulturkortet/QRCodeViewer/KulturkortetQRCodeViewerAuthViewFactory.php:135-158 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Modularity/source/php/BlockManager.php:534 — Modularity/source/php/BlockManager.php:534-557 | library/Admin/Gutenberg/Blocks/BlockManager.php:419-449 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) library/Helper/Post.php:46 — library/Helper/Post.php:46-79 | library/Helper/Post.php:104-127 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) library/Controller/Navigation/Helper/GetAncestorIds.php:66 — library/Controller/Navigation/Helper/GetAncestorIds.php:66-89 | library/Helper/Navigation/MenuConstructor.php:163-188 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×4
  • Edited copy of a member (10 corresponding lines) library/Content/Images/Images.php:261 — library/Content/Images/Images.php:261-274 | library/Content/Images/ImagesDeprecated.php:160-169 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) library/Helper/ElementAttribute.php:151 — library/Helper/ElementAttribute.php:151-160 | library/Helper/ElementAttribute.php:171-182 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:75 — library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:75-84 | library/SchemaData/SchemaPropertyValueSanitizer/PlaceFromAcfGoogleMapsFieldSanitizer.php:72-81 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) library/Upgrade/V50/MigrateLegacyDrawerVisibility.php:71 — library/Upgrade/V50/MigrateLegacyDrawerVisibility.php:71-80 | library/Customizer/Sections/Header/Layout.php:398-407 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×4
  • Edited copy of a member (14 corresponding lines) library/Admin/Login/AddLoginAndLogoutNotices.php:84 — library/Admin/Login/AddLoginAndLogoutNotices.php:84-98 | library/Admin/Login/AddLoginAndLogoutNotices.php:106-119 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorFeature.php:82 — library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorFeature.php:82-99 | library/Kulturkortet/QRCodeViewer/KulturkortetQRCodeViewerFeature.php:87-100 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Modularity/source/php/Module/Posts/Helper/EventStartTimestampResolver.php:73 — Modularity/source/php/Module/Posts/Helper/EventStartTimestampResolver.php:73-87 | library/PostsList/ViewCallableProviders/Schema/Event/GetDate.php:100-113 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) library/Controller/A11y.php:263 — library/Controller/A11y.php:263-276 | library/Controller/A11y.php:390-403 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×4
  • Edited copy of a member (11 corresponding lines) Modularity/source/php/Helper/Cache.php:215 — Modularity/source/php/Helper/Cache.php:215-227 | library/Helper/Cache.php:219-229 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:117 — library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:117-131 | library/Upgrade/V59/MigrateMalformedFlexibleHeaderLowerArea.php:71-81 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) library/Helper/Navigation/GetMenuData.php:25 — library/Helper/Navigation/GetMenuData.php:25-38 | library/Helper/Navigation/GetMenuData.php:82-92 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Modularity/source/php/Helper/Cache.php:94 — Modularity/source/php/Helper/Cache.php:94-105 | library/Helper/Cache.php:116-126 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×4
  • Edited copy of a member (8 corresponding lines) library/PostsList/ViewCallableProviders/GetTagsComponentArguments.php:41 — library/PostsList/ViewCallableProviders/GetTagsComponentArguments.php:41-52 | library/PostsList/ViewCallableProviders/GetTermsAsString.php:39-46 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) library/SchemaData/Taxonomy/TaxonomiesFromSchemaType/TaxonomyFilteredBySubProperty.php:134 — library/SchemaData/Taxonomy/TaxonomiesFromSchemaType/TaxonomyFilteredBySubProperty.php:134-143 | library/Upgrade/V41/MapThemeModsToDesignTokens.php:87-94 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Modularity/source/php/Upgrade/Version/V2.php:46 — Modularity/source/php/Upgrade/Version/V2.php:46-53 | Modularity/source/php/Upgrade/Version/V5.php:46-54 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Modularity/source/php/Upgrade/Version/V2.php:34 — Modularity/source/php/Upgrade/Version/V2.php:34-41 | Modularity/source/php/Upgrade/Version/V5.php:34-41 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) library/SchemaData/ExternalContent/ExternalContentFeature.php:59 — library/SchemaData/ExternalContent/ExternalContentFeature.php:59-67 | library/SchemaData/ExternalContent/ExternalContentFeature.php:75-87 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) library/Upgrade/V51/MigrateBusinessFlexibleLowerPadding.php:67 — library/Upgrade/V51/MigrateBusinessFlexibleLowerPadding.php:67-76 | library/Upgrade/V50/MigrateLegacyBusinessHeaderToFlexible.php:129-137 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) library/Controller/Navigation/Cache/NavigationWpCache.php:48 — library/Controller/Navigation/Cache/NavigationWpCache.php:48-56 | library/Helper/Navigation.php:85-93 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/GroupWithSchemaObjectHandler.php:28 — library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/GroupWithSchemaObjectHandler.php:28-36 | library/SchemaData/SchemaPropertiesForm/StoreFormFieldValues/SchemaPropertyHandler/RepeaterWithSchemaObjectsHandler.php:29-37 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×4
  • Duplicated block (6 lines × 2) library/Helper/ElementAttribute.php:151 — library/Helper/ElementAttribute.php:151-156 | library/Helper/ElementAttribute.php:171-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) library/Controller/School/ElementarySchool/UspsGenerator.php:139 — library/Controller/School/ElementarySchool/UspsGenerator.php:139-144 | library/Controller/School/Preschool/UspsGenerator.php:107-112 — `library/Controller/School/ElementarySchool/UspsGenerator.php` and `library/Controller/School/Preschool/UspsGenerator.php` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:152 — library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:152-157 | library/Kulturkortet/QRCodeViewer/KulturkortetQRCodeViewerAuthViewFactory.php:119-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) library/Upgrade/V42/InteractsWithNativeFontLibrary.php:157 — library/Upgrade/V42/InteractsWithNativeFontLibrary.php:157-162 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:783-788 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
X2 · Cancellation propagation · Async function without AbortSignal · ×4
  • Async function without AbortSignal: fetchMarkup assets/source/js/nav.ts:12 — `fetchMarkup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: refreshNonce assets/source/js/restApi/wpApiSettings.ts:47 — `refreshNonce` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: getRemoteSiteDesignData assets/source/js/admin/designShareUtils.ts:201 — `getRemoteSiteDesignData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: submitSubscription Modularity/source/php/Module/Subscribe/assets/ungapd.ts:122 — `submitSubscription` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
AC3 · Page structure · Page without a main landmark · ×3
  • Page without a main landmark library/BrandedEmails/HtmlTemplate/views/default.blade.php:1 — 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 views/v3/partials/content/pdf/layout.blade.php: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 views/v3/templates/grid.blade.php:6 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D3 · God Classes · FunctionTooLong · ×3
  • FunctionTooLong: module.Module.addModule Modularity/source/js/editor/module.js:165 — FunctionTooLong — Module.addModule runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: PostsListAsync.postsListAsync assets/source/js/postsList/PostsListAsync.ts:4 — FunctionTooLong — postsListAsync runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× 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: index.startSearchPage library/SearchIndex/SearchPage/js/index.ts:311 — FunctionTooLong — startSearchPage runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×3
  • Edited copy of a member (3 corresponding lines) library/Controller/BaseController.php:557 — library/Controller/BaseController.php:557-559 | library/Integrations/BrokenLinks/RedirectToLoginWhenInternalContext.php:65-67 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) library/Customizer/Applicators/Types/Component.php:26 — library/Customizer/Applicators/Types/Component.php:26-28 | library/Customizer/Applicators/Types/Modifier.php:25-27 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) library/PostsList/ViewCallableProviders/Filter/GetFilterResetButtonArguments.php:50 — library/PostsList/ViewCallableProviders/Filter/GetFilterResetButtonArguments.php:50-52 | library/PostsList/ViewCallableProviders/Filter/GetFilterSubmitButtonArguments.php:48-50 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×3
  • Duplicated block (14 lines × 3) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:179 — library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:179-192 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:485-499 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:742-755 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:121 — library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:121-134 | library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php:69-82 | library/Upgrade/V58/MigrateWideLogotypeHeightDefault.php:123-136 — before extracting anything, compare `library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php` and `library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 3) library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:167 — library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:167-180 | library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:203-216 | library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php:104-117 — before extracting anything, compare `library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php` and `library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×3
  • Duplicated block (12 lines × 3) library/Controller/BaseController.php:1395 — library/Controller/BaseController.php:1395-1406 | library/Customizer/Controls/MultiColor/MultiColorControl.php:115-126 | library/Customizer/Sections/Header/Layout.php:342-353 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (12 lines × 3) library/Upgrade/V66/Version66.php:88 — library/Upgrade/V66/Version66.php:88-99 | library/Upgrade/V67/Version67.php:75-86 | library/Upgrade/V68/Version68.php:78-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 3) library/Upgrade/V50/MigrateLegacyHeaderModifierCss.php:53 — library/Upgrade/V50/MigrateLegacyHeaderModifierCss.php:53-65 | library/Upgrade/V55/MigrateFlexibleHeaderContainerSelectors.php:53-65 | library/Upgrade/V57/MigrateFooterBeforeBackgroundToSiteWrapperAfter.php:44-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) library/Helper/ColorSwatches.php:542 — library/Helper/ColorSwatches.php:542-550 | library/Upgrade/V46/MigrateLegacyFooterCustomizerToComponentTokens.php:115-123 | library/Upgrade/V48/MigrateLegacyDatebadgeCustomizerToDesignTokens.php:69-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 3) library/Integrations/Polylang/ResolveAcfPostsManualSelectionLanguage.php:163 — library/Integrations/Polylang/ResolveAcfPostsManualSelectionLanguage.php:163-171 | library/Integrations/Polylang/ResolveFontAttachmentQueries.php:108-116 | library/Integrations/Polylang/ResolvePostsModuleManualSelectionLanguage.php:85-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (9 lines × 3) library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:164 — library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:164-172 | library/Integrations/Polylang/ResolveTranslatedPageLink.php:244-252 | library/Integrations/Polylang/ResolveTranslatedPostTypeLink.php:133-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:61 — library/SchemaData/SchemaPropertyValueSanitizer/GeoCoordinatesFromAcfGoogleMapsFieldSanitizer.php:61-65 | library/SchemaData/SchemaPropertyValueSanitizer/PlaceFromAcfGoogleMapsFieldSanitizer.php:58-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) library/Controller/School/AlertGenerator.php:26 — library/Controller/School/AlertGenerator.php:26-30 | library/Controller/School/PreambleGenerator.php:23-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) library/Integrations/ActiveDirectoryApiWpIntegration/SetUserGroupFromCompany.php:42 — library/Integrations/ActiveDirectoryApiWpIntegration/SetUserGroupFromCompany.php:42-46 | library/Integrations/MiniOrange/SetUserGroupFromSsoLoginGroup.php:42-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: library/Upgrade.php library/Upgrade.php — FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Upgrade (51-1615). The bar is 500 significant lines; this is 295 over it, 1.59× 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: Controller/BaseController.php library/Controller/BaseController.php — FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: BaseController (29-1465). The bar is 500 significant lines; this is 166 over it, 1.33× 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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×2
  • Edited copy of a member (37 corresponding lines) library/Customizer/Applicators/Types/Component.php:63 — library/Customizer/Applicators/Types/Component.php:63-99 | library/Customizer/Applicators/Types/Modifier.php:40-79 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) library/Controller/SingularElementarySchool.php:24 — library/Controller/SingularElementarySchool.php:24-68 | library/Controller/SingularPreschool.php:23-59 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×2
  • Edited copy of a member (25 corresponding lines) library/Controller/School/ElementarySchool/UspsGenerator.php:33 — library/Controller/School/ElementarySchool/UspsGenerator.php:33-58 | library/Controller/School/Preschool/UspsGenerator.php:34-58 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) library/StickyPost/AddStickyCheckboxForPost.php:61 — library/StickyPost/AddStickyCheckboxForPost.php:61-85 | library/UserGroup/AddSelectUserGroupForPrivatePost.php:71-101 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×2
  • Edited copy of a member (12 corresponding lines) Modularity/source/php/Upgrade/Migrators/Block/AcfBlockMigrationHandler.php:61 — Modularity/source/php/Upgrade/Migrators/Block/AcfBlockMigrationHandler.php:61-77 | Modularity/source/php/Upgrade/Migrators/Module/AcfModuleMigrationHandler.php:49-60 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) library/Helper/Post.php:479 — library/Helper/Post.php:479-490 | library/PostObject/Decorators/PostObjectWithFilteredContent.php:122-133 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×2
  • Edited copy of a member (16 corresponding lines) Modularity/source/php/Integrations/Component/ImageFocusResolver.php:27 — Modularity/source/php/Integrations/Component/ImageFocusResolver.php:27-42 | library/Integrations/Component/ImageFocusResolver.php:26-48 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) library/Helper/ElementAttribute.php:193 — library/Helper/ElementAttribute.php:193-208 | library/Helper/Html.php:76-91 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) library/Controller/BaseController.php:1388 — library/Controller/BaseController.php:1388-1406 | library/Customizer/Sections/Header/Layout.php:337-353 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) library/Styleguide/Customize/ApplyStyles/ColorSchemeOverrides.php:53 — library/Styleguide/Customize/ApplyStyles/ColorSchemeOverrides.php:53-74 | library/Styleguide/Customize/ApplyStyles/ColorSchemeOverrides.php:86-102 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) library/Api/Customizer/DesignLibraryFontActivation.php:191 — library/Api/Customizer/DesignLibraryFontActivation.php:191-198 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:363-370 | library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:472-483 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) library/Upgrade.php:1201 — library/Upgrade.php:1201-1209 | library/Upgrade.php:1293-1300 | library/Upgrade.php:1306-1313 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) library/StickyPost/AddStickyCheckboxForPost.php:47 — library/StickyPost/AddStickyCheckboxForPost.php:47-50 | library/UserGroup/AddSelectUserGroupForPrivatePost.php:52-55 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Modularity/source/php/Module/Video/Video.php:464 — Modularity/source/php/Module/Video/Video.php:464-467 | library/Template.php:605-608 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) library/Controller/School/ElementarySchool/UspsGenerator.php:36 — library/Controller/School/ElementarySchool/UspsGenerator.php:36-58 | library/Controller/School/Preschool/UspsGenerator.php:36-58 — `library/Controller/School/ElementarySchool/UspsGenerator.php` and `library/Controller/School/Preschool/UspsGenerator.php` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `library/Controller/School/ElementarySchool/UspsGenerator.php:34` calls `getProperty` and `library/Controller/School/Preschool/UspsGenerator.php:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) library/Upgrade/V67/Version67.php:45 — library/Upgrade/V67/Version67.php:45-67 | library/Upgrade/V68/Version68.php:48-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) library/Controller/Navigation/Helper/GetPostsByParent.php:43 — library/Controller/Navigation/Helper/GetPostsByParent.php:43-60 | library/Helper/Navigation.php:360-377 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/Navigation/Helper/GetPostsByParent.php:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) library/Upgrade/V64/Version64.php:129 — library/Upgrade/V64/Version64.php:129-146 | library/Upgrade/V65/Version65.php:68-85 — before extracting anything, compare `library/Upgrade/V64/Version64.php` and `library/Upgrade/V65/Version65.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) library/PostsList/ViewCallableProviders/GetTagsComponentArguments.php:63 — library/PostsList/ViewCallableProviders/GetTagsComponentArguments.php:63-79 | library/PostsList/ViewCallableProviders/GetTermsAsString.php:57-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (17 lines × 2) library/Upgrade/V46/MigrateLegacyFooterCustomizerToComponentTokens.php:103 — library/Upgrade/V46/MigrateLegacyFooterCustomizerToComponentTokens.php:103-119 | library/Upgrade/V48/MigrateLegacyDatebadgeCustomizerToDesignTokens.php:57-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Upgrade/V46/MigrateLegacyFooterCustomizerToComponentTokens.php:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) library/Controller/Navigation/Helper/GetPostsByParent.php:63 — library/Controller/Navigation/Helper/GetPostsByParent.php:63-77 | library/Helper/Navigation.php:380-394 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/Navigation/Helper/GetPostsByParent.php:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php:35 — library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php:35-49 | library/Controller/School/Preschool/AccordionListItemsGenerator.php:35-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) library/Controller/E401.php:150 — library/Controller/E401.php:150-157 | library/Controller/E403.php:145-152 | library/Controller/E404.php:96-103 — before extracting anything, compare `library/Controller/E401.php` and `library/Controller/E403.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `library/Controller/E404.php:106` calls `is_array`, `array_shift` and `library/Controller/E401.php:159` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) library/Customizer/Controls/Background/BackgroundControl.php:151 — library/Customizer/Controls/Background/BackgroundControl.php:151-158 | library/Customizer/Controls/MultiColor/MultiColorControl.php:96-103 | library/Customizer/Controls/Repeater/RepeaterControl.php:98-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×2
  • Duplicated block (13 lines × 3) Modularity/source/php/Upgrade.php:142 — Modularity/source/php/Upgrade.php:142-154 | library/Controller/BaseController.php:1451-1463 | library/Upgrade.php:1601-1613 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 3) library/Integrations/Component/BlogSwitchedImageFocusResolver.php:41 — library/Integrations/Component/BlogSwitchedImageFocusResolver.php:41-53 | library/Integrations/Component/BlogSwitchedImageResolver.php:61-73 | library/MirroredPost/PostObject/MirroredPostObject.php:107-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×2
  • Duplicated block (15 lines × 2 locations) Modularity/source/js/editor/autosave.js:30 — Modularity/source/js/editor/autosave.js:30 · Modularity/source/js/helpers/serializeObject.js:1 — 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.
  • Duplicated block (15 lines × 2 locations) assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:40 — assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:40 · assets/source/js/headerLogoScrollShrink.ts:16 — 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 (15 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (15 matched lines × 2 locations) Modularity/source/js/editor/dragAndDrop.js:2 — Modularity/source/js/editor/dragAndDrop.js:2 · Modularity/source/js/editor/module.js:1 — the two spans are one implementation copied and then locally edited — 50 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 (15 matched lines × 2 locations) assets/source/js/missingH1Indicator.ts:6 — assets/source/js/missingH1Indicator.ts:6 · assets/source/js/vagueControlTextIndicator.ts:39 — the two spans are one implementation copied and then locally edited — 87 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 (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) Modularity/source/js/modularity-editor-modal.js:36 — Modularity/source/js/modularity-editor-modal.js:36 · Modularity/source/js/modularity-editor-modal.js:85 — all 2 copies are in the same file, 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.
  • Duplicated block (12 lines × 2 locations) Modularity/source/php/Module/InteractiveMap/assets/map/filtering/filterButton.ts:52 — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/filterButton.ts:52 · Modularity/source/php/Module/InteractiveMap/assets/map/markerClick/markerClick.ts:91 — 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 (11 lines × 2 locations) · ×2
  • Duplicated block (11 lines × 2 locations) library/Customizer/Controls/Background/BackgroundControl.ts:29 — library/Customizer/Controls/Background/BackgroundControl.ts:29 · library/Customizer/Controls/MultiColor/MultiColorControl.ts:72 — 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.
  • Duplicated block (11 lines × 2 locations) library/Customizer/Controls/ColorChoice/ColorChoiceControl.ts:4 — library/Customizer/Controls/ColorChoice/ColorChoiceControl.ts:4 · library/Customizer/Controls/MultiColor/MultiColorControl.ts:15 — 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 (10 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (10 matched lines × 2 locations) library/Customizer/Controls/Background/BackgroundControl.ts:14 — library/Customizer/Controls/Background/BackgroundControl.ts:14 · library/Customizer/Controls/Sortable/SortableControl.ts:212 — the two spans are one implementation copied and then locally edited — 53 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 (10 matched lines × 2 locations) library/Customizer/Controls/Repeater/RepeaterControl.ts:26 — library/Customizer/Controls/Repeater/RepeaterControl.ts:26 · library/Customizer/Controls/TabBox/TabBoxControl.ts:10 — the two spans are one implementation copied and then locally edited — 57 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 (9 lines × 2 locations) · ×2
  • Duplicated block (9 lines × 2 locations) Modularity/source/js/editor/module.js:397 — Modularity/source/js/editor/module.js:397 · Modularity/source/js/helpers/widget.js:38 — 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.
  • Duplicated block (9 lines × 2 locations) library/Customizer/Controls/MultiSelect/MultiSelectControl.ts:34 — library/Customizer/Controls/MultiSelect/MultiSelectControl.ts:34 · library/Customizer/Controls/Sortable/SortableControl.ts:286 — 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×2
  • Swallowed exception (empty catch) library/SearchIndex/Index/PostIndexer.php:170 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) library/Chat/js/chat/ChatSession.ts:174 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D1 · Cyclomatic Complexity · WoffConverter.convertToTTF (cyclomatic 57) · ×1
  • WoffConverter.convertToTTF (cyclomatic 57) library/Helper/FileConverters/WoffConverter.php:122 — WoffConverter.convertToTTF has cyclomatic complexity 57 (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 · TransparencyDetector.webpHasTransparency (cyclomatic 39) · ×1
  • TransparencyDetector.webpHasTransparency (cyclomatic 39) library/ImageConvert/TransparencyDetector.php:96 — TransparencyDetector.webpHasTransparency has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Version70.migrateBlocks (cyclomatic 38) · ×1
  • Version70.migrateBlocks (cyclomatic 38) library/Upgrade/V70/Version70.php:73 — Version70.migrateBlocks has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Contacts.prepareContacts (cyclomatic 28) · ×1
  • Contacts.prepareContacts (cyclomatic 28) Modularity/source/php/Module/Contacts/Contacts.php:88 — Contacts.prepareContacts has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ManualInput.data (cyclomatic 27) · ×1
  • ManualInput.data (cyclomatic 27) Modularity/source/php/Module/ManualInput/ManualInput.php:38 — ManualInput.data 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 · Template.loadController (cyclomatic 26) · ×1
  • Template.loadController (cyclomatic 26) library/Template.php:192 — Template.loadController has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PostsListAsync.postsListAsync (cyclomatic 25) · ×1
  • PostsListAsync.postsListAsync (cyclomatic 25) assets/source/js/postsList/PostsListAsync.ts:4 — PostsListAsync.postsListAsync has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 157, a function literal at line 81, a function literal at line 110, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · AcfBlockIndexRepeaterMigrator.migrate (cyclomatic 24) · ×1
  • AcfBlockIndexRepeaterMigrator.migrate (cyclomatic 24) Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:22 — AcfBlockIndexRepeaterMigrator.migrate 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 · index.startSearchPage (cyclomatic 24) · ×1
  • index.startSearchPage (cyclomatic 24) library/SearchIndex/SearchPage/js/index.ts:311 — index.startSearchPage has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AcfModuleRepeaterFieldsMigrator.valuesMatch (cyclomatic 23) · ×1
  • AcfModuleRepeaterFieldsMigrator.valuesMatch (cyclomatic 23) Modularity/source/php/Upgrade/Migrators/Module/AcfModuleRepeaterFieldsMigrator.php:126 — AcfModuleRepeaterFieldsMigrator.valuesMatch has cyclomatic complexity 23 (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 · BaseController.__construct (cyclomatic 22) · ×1
  • BaseController.__construct (cyclomatic 22) library/Controller/BaseController.php:68 — BaseController.__construct has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GetPosts.getPostArgs (cyclomatic 21) · ×1
  • GetPosts.getPostArgs (cyclomatic 21) Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php:113 — GetPosts.getPostArgs 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 · BlockManager.renderContainerCallback (cyclomatic 21) · ×1
  • BlockManager.renderContainerCallback (cyclomatic 21) library/Admin/Gutenberg/Blocks/BlockManager.php:149 — BlockManager.renderContainerCallback 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 · Upgrade.v_13 (cyclomatic 21) · ×1
  • Upgrade.v_13 (cyclomatic 21) library/Upgrade.php:250 — Upgrade.v_13 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 · MigrateLegacyUploadedFontsToNativeFontLibrary.installFileInFontDirectory (cyclomatic 21) · ×1
  • MigrateLegacyUploadedFontsToNativeFontLibrary.installFileInFontDirectory (cyclomatic 21) library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:389 — MigrateLegacyUploadedFontsToNativeFontLibrary.installFileInFontDirectory 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 · Template.addTemplateFilters (cyclomatic 20) · ×1
  • Template.addTemplateFilters (cyclomatic 20) library/Template.php:517 — Template.addTemplateFilters 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 · DecorateDesignTokens.decorate (cyclomatic 20) · ×1
  • DecorateDesignTokens.decorate (cyclomatic 20) library/Upgrade/V41/DecorateDesignTokens.php:7 — DecorateDesignTokens.decorate has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Editor.getPostModules (cyclomatic 19) · ×1
  • Editor.getPostModules (cyclomatic 19) Modularity/source/php/Editor.php:425 — Editor.getPostModules 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 · Index.prepareItems (cyclomatic 19) · ×1
  • Index.prepareItems (cyclomatic 19) Modularity/source/php/Module/Index/Index.php:55 — Index.prepareItems 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 · GetPostsByParent.getPostsByParent (cyclomatic 19) · ×1
  • GetPostsByParent.getPostsByParent (cyclomatic 19) library/Controller/Navigation/Helper/GetPostsByParent.php:29 — GetPostsByParent.getPostsByParent 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 · Post.complementObject (cyclomatic 19) · ×1
  • Post.complementObject (cyclomatic 19) library/Helper/Post.php:176 — Post.complementObject 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 · ResolvePageTreeTranslatedChildren.resolveTranslatedChildren (cyclomatic 19) · ×1
  • ResolvePageTreeTranslatedChildren.resolveTranslatedChildren (cyclomatic 19) library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:65 — ResolvePageTreeTranslatedChildren.resolveTranslatedChildren has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BlockManager.renderBlock (cyclomatic 18) · ×1
  • BlockManager.renderBlock (cyclomatic 18) Modularity/source/php/BlockManager.php:414 — BlockManager.renderBlock 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 · GetPosts.sortPosts (cyclomatic 18) · ×1
  • GetPosts.sortPosts (cyclomatic 18) Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php:316 — GetPosts.sortPosts 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 · Navigation.getItems (cyclomatic 18) · ×1
  • Navigation.getItems (cyclomatic 18) library/Helper/Navigation.php:348 — Navigation.getItems 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 · OembedFilters.buildEmbedUrl (cyclomatic 18) · ×1
  • OembedFilters.buildEmbedUrl (cyclomatic 18) library/Oembed/OembedFilters.php:87 — OembedFilters.buildEmbedUrl 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 · MigrateHeaderSortableDataIntegrity.normalizeCustomizerChangesetDrafts (cyclomatic 18) · ×1
  • MigrateHeaderSortableDataIntegrity.normalizeCustomizerChangesetDrafts (cyclomatic 18) library/Upgrade/V52/MigrateHeaderSortableDataIntegrity.php:270 — MigrateHeaderSortableDataIntegrity.normalizeCustomizerChangesetDrafts 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 · Version71.upgradeToVersion (cyclomatic 18) · ×1
  • Version71.upgradeToVersion (cyclomatic 18) library/Upgrade/V71/Version71.php:25 — Version71.upgradeToVersion 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 · SidebarMenu.walk (cyclomatic 18) · ×1
  • SidebarMenu.walk (cyclomatic 18) library/Walker/SidebarMenu.php:7 — SidebarMenu.walk 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 · Posts.data (cyclomatic 17) · ×1
  • Posts.data (cyclomatic 17) Modularity/source/php/Module/Posts/Posts.php:145 — Posts.data 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 · Navigation.getBreadcrumbItems (cyclomatic 17) · ×1
  • Navigation.getBreadcrumbItems (cyclomatic 17) library/Helper/Navigation.php:809 — Navigation.getBreadcrumbItems 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 · FaceDetectingFocusPointResolver.resolve (cyclomatic 17) · ×1
  • FaceDetectingFocusPointResolver.resolve (cyclomatic 17) library/ImageFocus/Resolvers/FaceDetectingFocusPointResolver.php:37 — FaceDetectingFocusPointResolver.resolve 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 · PopulateUsedColors.countBlocks (cyclomatic 17) · ×1
  • PopulateUsedColors.countBlocks (cyclomatic 17) library/Upgrade/Palette/PopulateUsedColors.php:67 — PopulateUsedColors.countBlocks 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 · MigrateLegacyUploadedFontsToNativeFontLibrary.migrate (cyclomatic 17) · ×1
  • MigrateLegacyUploadedFontsToNativeFontLibrary.migrate (cyclomatic 17) library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:71 — MigrateLegacyUploadedFontsToNativeFontLibrary.migrate 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 · MigrateLegacyUploadedFontsToNativeFontLibrary.persistActivatedFontFamily (cyclomatic 17) · ×1
  • MigrateLegacyUploadedFontsToNativeFontLibrary.persistActivatedFontFamily (cyclomatic 17) library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:571 — MigrateLegacyUploadedFontsToNativeFontLibrary.persistActivatedFontFamily 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 · MigrateWideLogotypeHeightDefault.migrate (cyclomatic 17) · ×1
  • MigrateWideLogotypeHeightDefault.migrate (cyclomatic 17) library/Upgrade/V58/MigrateWideLogotypeHeightDefault.php:57 — MigrateWideLogotypeHeightDefault.migrate 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 · Wp.getArchiveSlug (cyclomatic 16) · ×1
  • Wp.getArchiveSlug (cyclomatic 16) Modularity/source/php/Helper/Wp.php:236 — Wp.getArchiveSlug 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 · Script.data (cyclomatic 16) · ×1
  • Script.data (cyclomatic 16) Modularity/source/php/Module/Script/Script.php:36 — Script.data 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 · AcfModuleIndexRepeaterMigrator.migrate (cyclomatic 16) · ×1
  • AcfModuleIndexRepeaterMigrator.migrate (cyclomatic 16) Modularity/source/php/Upgrade/Migrators/Module/Custom/AcfModuleIndexRepeaterMigrator.php:22 — AcfModuleIndexRepeaterMigrator.migrate 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 · BaseController.showSearchForm (cyclomatic 16) · ×1
  • BaseController.showSearchForm (cyclomatic 16) library/Controller/BaseController.php:894 — BaseController.showSearchForm 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 · Modifier.applyDataFilterFunction (cyclomatic 16) · ×1
  • Modifier.applyDataFilterFunction (cyclomatic 16) library/Customizer/Applicators/Types/Modifier.php:38 — Modifier.applyDataFilterFunction 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 · SearchQuery.applySearchResults (cyclomatic 16) · ×1
  • SearchQuery.applySearchResults (cyclomatic 16) library/SearchIndex/Search/SearchQuery.php:32 — SearchQuery.applySearchResults 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 · MainMenuSecondary.walk (cyclomatic 16) · ×1
  • MainMenuSecondary.walk (cyclomatic 16) library/Walker/MainMenuSecondary.php:7 — MainMenuSecondary.walk 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 · paletteColorChoices.enhanceField (cyclomatic 16) · ×1
  • paletteColorChoices.enhanceField (cyclomatic 16) assets/source/js/admin/acf/paletteColorChoices.ts:19 — paletteColorChoices.enhanceField has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 96, 42, 69). 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.
D11 · Test Reliability · Test reliability not measured · ×1
  • Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.
D2 · Cognitive Complexity · WoffConverter.convertToTTF (cognitive 107) · ×1
  • WoffConverter.convertToTTF (cognitive 107) library/Helper/FileConverters/WoffConverter.php:122 — WoffConverter.convertToTTF has cognitive complexity 107 (threshold 15). Drivers by points: if/else 39 (98 pts), loops 5 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 61). To reduce it, split the body into named stages: move each independent 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 · Version70.migrateBlocks (cognitive 86) · ×1
  • Version70.migrateBlocks (cognitive 86) library/Upgrade/V70/Version70.php:73 — Version70.migrateBlocks has cognitive complexity 86 (threshold 15). Drivers by points: if/else 13 (47 pts), loops 8 (25 pts), boolean chains 14 (nesting depth added 51). To reduce it, split the body into named stages: move each independent 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 · AcfBlockIndexRepeaterMigrator.migrate (cognitive 58) · ×1
  • AcfBlockIndexRepeaterMigrator.migrate (cognitive 58) Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:22 — AcfBlockIndexRepeaterMigrator.migrate has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 8 (32 pts), if/else 5 (13 pts), boolean chains 8, loops 2 (5 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TransparencyDetector.webpHasTransparency (cognitive 53) · ×1
  • TransparencyDetector.webpHasTransparency (cognitive 53) library/ImageConvert/TransparencyDetector.php:96 — TransparencyDetector.webpHasTransparency has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 17, match/switch 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PopulateUsedColors.countBlocks (cognitive 53) · ×1
  • PopulateUsedColors.countBlocks (cognitive 53) library/Upgrade/Palette/PopulateUsedColors.php:67 — PopulateUsedColors.countBlocks has cognitive complexity 53 (threshold 15). Drivers by points: if/else 10 (35 pts), loops 4 (16 pts), boolean chains 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 · Component.getData (cognitive 42) · ×1
  • Component.getData (cognitive 42) library/Customizer/Applicators/Types/Component.php:123 — Component.getData has cognitive complexity 42 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 3 (11 pts), ternaries 1 (5 pts), boolean chains 4 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Template.addTemplateFilters (cognitive 41) · ×1
  • Template.addTemplateFilters (cognitive 41) library/Template.php:517 — Template.addTemplateFilters has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (31 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ManualInput.data (cognitive 40) · ×1
  • ManualInput.data (cognitive 40) Modularity/source/php/Module/ManualInput/ManualInput.php:38 — ManualInput.data has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 11 (19 pts), if/else 7 (12 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AcfModuleIndexRepeaterMigrator.migrate (cognitive 40) · ×1
  • AcfModuleIndexRepeaterMigrator.migrate (cognitive 40) Modularity/source/php/Upgrade/Migrators/Module/Custom/AcfModuleIndexRepeaterMigrator.php:22 — AcfModuleIndexRepeaterMigrator.migrate has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 5 (17 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 25). 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 · BlockManager.renderContainerCallback (cognitive 40) · ×1
  • BlockManager.renderContainerCallback (cognitive 40) library/Admin/Gutenberg/Blocks/BlockManager.php:149 — BlockManager.renderContainerCallback has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Editor.getPostModules (cognitive 39) · ×1
  • Editor.getPostModules (cognitive 39) Modularity/source/php/Editor.php:425 — Editor.getPostModules has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 5 (12 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Contacts.prepareContacts (cognitive 39) · ×1
  • Contacts.prepareContacts (cognitive 39) Modularity/source/php/Module/Contacts/Contacts.php:88 — Contacts.prepareContacts has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 5 (10 pts), boolean chains 7, match/switch 2 (5 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Modifier.getData (cognitive 37) · ×1
  • Modifier.getData (cognitive 37) library/Customizer/Applicators/Types/Modifier.php:87 — Modifier.getData has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 3 (11 pts), boolean chains 4 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Template.loadController (cognitive 37) · ×1
  • Template.loadController (cognitive 37) library/Template.php:192 — Template.loadController has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 15, loops 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 · BlockManager.renderBlock (cognitive 33) · ×1
  • BlockManager.renderBlock (cognitive 33) Modularity/source/php/BlockManager.php:414 — BlockManager.renderBlock has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 2 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateHeaderSortableDataIntegrity.normalizeCustomizerChangesetDrafts (cognitive 32) · ×1
  • MigrateHeaderSortableDataIntegrity.normalizeCustomizerChangesetDrafts (cognitive 32) library/Upgrade/V52/MigrateHeaderSortableDataIntegrity.php:270 — MigrateHeaderSortableDataIntegrity.normalizeCustomizerChangesetDrafts has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 3 (7 pts), boolean chains 4, loops 2 (3 pts), error handling 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 · ExpandableListTemplate.prepareExpandableList (cognitive 31) · ×1
  • ExpandableListTemplate.prepareExpandableList (cognitive 31) Modularity/source/php/Module/Posts/TemplateController/ExpandableListTemplate.php:158 — ExpandableListTemplate.prepareExpandableList has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 2 (12 pts), if/else 5 (11 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Index.prepareItems (cognitive 30) · ×1
  • Index.prepareItems (cognitive 30) Modularity/source/php/Module/Index/Index.php:55 — Index.prepareItems has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 10, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Navigation.getBreadcrumbItems (cognitive 30) · ×1
  • Navigation.getBreadcrumbItems (cognitive 30) library/Helper/Navigation.php:809 — Navigation.getBreadcrumbItems has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 2 (6 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 14). 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 · GetPostsByParent.getPostsByParent (cognitive 28) · ×1
  • GetPostsByParent.getPostsByParent (cognitive 28) library/Controller/Navigation/Helper/GetPostsByParent.php:29 — GetPostsByParent.getPostsByParent has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 4, loops 2 (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 · Version71.upgradeToVersion (cognitive 28) · ×1
  • Version71.upgradeToVersion (cognitive 28) library/Upgrade/V71/Version71.php:25 — Version71.upgradeToVersion has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · designShareUtils.importSettings (cognitive 28) · ×1
  • designShareUtils.importSettings (cognitive 28) assets/source/js/admin/designShareUtils.ts:304 — designShareUtils.importSettings has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · widgetsAreaHider.document.addEventListener("DOMContentLoaded") · ×1
  • widgetsAreaHider.document.addEventListener("DOMContentLoaded")::callback (cognitive 28) assets/source/js/admin/widgetsAreaHider.js:4 — widgetsAreaHider.document.addEventListener("DOMContentLoaded")::callback has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) · ×1
  • (anonymous)::callback (cognitive 28) assets/source/js/admin/widgetsAreaHider.js:4 — (anonymous)::callback has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BaseController.__construct (cognitive 27) · ×1
  • BaseController.__construct (cognitive 27) library/Controller/BaseController.php:68 — BaseController.__construct has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 12 (15 pts), if/else 6 (9 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Navigation.getItems (cognitive 27) · ×1
  • Navigation.getItems (cognitive 27) library/Helper/Navigation.php:348 — Navigation.getItems has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaObjectsFilterFromFilterDefinition.filter (cognitive 27) · ×1
  • SchemaObjectsFilterFromFilterDefinition.filter (cognitive 27) library/SchemaData/ExternalContent/Filter/SchemaObjectsFilter/SchemaObjectsFilterFromFilterDefinition.php:26 — SchemaObjectsFilterFromFilterDefinition.filter has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (9 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostsListAsync.postsListAsync (cognitive 27) · ×1
  • PostsListAsync.postsListAsync (cognitive 27) assets/source/js/postsList/PostsListAsync.ts:4 — PostsListAsync.postsListAsync has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15, boolean chains 6, ternaries 4 (5 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 15 function items inside it that branch (a function literal at line 135, a function literal at line 157, a function literal at line 174, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AlphaColorControl.render_content (cognitive 26) · ×1
  • AlphaColorControl.render_content (cognitive 26) library/Customizer/Controls/AlphaColor/AlphaColorControl.php:41 — AlphaColorControl.render_content has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 6 (9 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Version71.repairValues (cognitive 26) · ×1
  • Version71.repairValues (cognitive 26) library/Upgrade/V71/Version71.php:113 — Version71.repairValues has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (5 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateLegacyUploadedFontsToNativeFontLibrary.migrate (cognitive 25) · ×1
  • MigrateLegacyUploadedFontsToNativeFontLibrary.migrate (cognitive 25) library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:71 — MigrateLegacyUploadedFontsToNativeFontLibrary.migrate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Modifier.applyDataFilterFunction (cognitive 24) · ×1
  • Modifier.applyDataFilterFunction (cognitive 24) library/Customizer/Applicators/Types/Modifier.php:38 — Modifier.applyDataFilterFunction has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 5, loops 2 (3 pts), ternaries 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ColorSchemeOverrides.filterComponents (cognitive 24) · ×1
  • ColorSchemeOverrides.filterComponents (cognitive 24) library/Styleguide/Customize/ApplyStyles/ColorSchemeOverrides.php:16 — ColorSchemeOverrides.filterComponents has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Curator.parseSocialMediaPosts (cognitive 23) · ×1
  • Curator.parseSocialMediaPosts (cognitive 23) REDACTED:162 — Curator.parseSocialMediaPosts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InlayList.buildListItems (cognitive 23) · ×1
  • InlayList.buildListItems (cognitive 23) Modularity/source/php/Module/InlayList/InlayList.php:64 — InlayList.buildListItems has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 3 (9 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AcfModuleRepeaterFieldsMigrator.valuesMatch (cognitive 23) · ×1
  • AcfModuleRepeaterFieldsMigrator.valuesMatch (cognitive 23) Modularity/source/php/Upgrade/Migrators/Module/AcfModuleRepeaterFieldsMigrator.php:126 — AcfModuleRepeaterFieldsMigrator.valuesMatch has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, if/else 8 (9 pts), loops 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · Singular.getPostAgeNotice (cognitive 23) · ×1
  • Singular.getPostAgeNotice (cognitive 23) library/Controller/Singular.php:298 — Singular.getPostAgeNotice has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 3, loops 1 (3 pts) (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 · Post.complementObject (cognitive 23) · ×1
  • Post.complementObject (cognitive 23) library/Helper/Post.php:176 — Post.complementObject has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3 (6 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 · Version70.upgradeToVersion (cognitive 23) · ×1
  • Version70.upgradeToVersion (cognitive 23) library/Upgrade/V70/Version70.php:24 — Version70.upgradeToVersion has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MainMenuSecondary.walk (cognitive 23) · ×1
  • MainMenuSecondary.walk (cognitive 23) library/Walker/MainMenuSecondary.php:7 — MainMenuSecondary.walk has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 4 (5 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 · SidebarMenu.walk (cognitive 23) · ×1
  • SidebarMenu.walk (cognitive 23) library/Walker/SidebarMenu.php:7 — SidebarMenu.walk has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 5 (8 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateLegacyGoogleFontsToNativeFontLibrary.getInstallableFontsFromWordPressCollections (cognitive 22) · ×1
  • MigrateLegacyGoogleFontsToNativeFontLibrary.getInstallableFontsFromWordPressCollections (cognitive 22) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:675 — MigrateLegacyGoogleFontsToNativeFontLibrary.getInstallableFontsFromWordPressCollections has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (6 pts), boolean chains 4 (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 · MigrateLegacyUploadedFontsToNativeFontLibrary.installFileInFontDirectory (cognitive 22) · ×1
  • MigrateLegacyUploadedFontsToNativeFontLibrary.installFileInFontDirectory (cognitive 22) library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:389 — MigrateLegacyUploadedFontsToNativeFontLibrary.installFileInFontDirectory has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8, ternaries 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 · GetPosts.getPostArgs (cognitive 21) · ×1
  • GetPosts.getPostArgs (cognitive 21) Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php:113 — GetPosts.getPostArgs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, loops 1 (2 pts), ternaries 2, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Script.data (cognitive 21) · ×1
  • Script.data (cognitive 21) Modularity/source/php/Module/Script/Script.php:36 — Script.data has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 3, loops 2, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ModuleManager.register (cognitive 21) · ×1
  • ModuleManager.register (cognitive 21) Modularity/source/php/ModuleManager.php:178 — ModuleManager.register has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (3 pts), boolean chains 2, ternaries 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 · Upgrade.v_20 (cognitive 21) · ×1
  • Upgrade.v_20 (cognitive 21) library/Upgrade.php:442 — Upgrade.v_20 has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 2 (6 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Upgrade.upgrade (cognitive 20) · ×1
  • Upgrade.upgrade (cognitive 20) Modularity/source/php/Upgrade.php:69 — Upgrade.upgrade has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (6 pts), boolean chains 1, 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 · PdfArchiveEndpoint.getPostsFromArchiveQuery (cognitive 20) · ×1
  • PdfArchiveEndpoint.getPostsFromArchiveQuery (cognitive 20) library/Api/Pdf/PdfArchiveEndpoint.php:146 — PdfArchiveEndpoint.getPostsFromArchiveQuery has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 3, boolean chains 2, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CustomPostType.registerCustomPostTypes (cognitive 20) · ×1
  • CustomPostType.registerCustomPostTypes (cognitive 20) library/Content/CustomPostType.php:54 — CustomPostType.registerCustomPostTypes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (6 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 · Component.getMatchingFilters (cognitive 20) · ×1
  • Component.getMatchingFilters (cognitive 20) library/Customizer/Applicators/Types/Component.php:61 — Component.getMatchingFilters has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResolvePageTreeTranslatedChildren.resolveTranslatedChildren (cognitive 20) · ×1
  • ResolvePageTreeTranslatedChildren.resolveTranslatedChildren (cognitive 20) library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:65 — ResolvePageTreeTranslatedChildren.resolveTranslatedChildren has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8, ternaries 2, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · WordPressAssetEnqueuer.restoreFragment (cognitive 20) · ×1
  • WordPressAssetEnqueuer.restoreFragment (cognitive 20) library/Styleguide/ComponentAssets/WordPressAssetEnqueuer.php:117 — WordPressAssetEnqueuer.restoreFragment has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, loops 4, 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 · MigrateHeaderSortableDataIntegrity.migrate (cognitive 20) · ×1
  • MigrateHeaderSortableDataIntegrity.migrate (cognitive 20) library/Upgrade/V52/MigrateHeaderSortableDataIntegrity.php:66 — MigrateHeaderSortableDataIntegrity.migrate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PdfHelper.getFonts (cognitive 19) · ×1
  • PdfHelper.getFonts (cognitive 19) library/Api/Pdf/PdfHelper.php:23 — PdfHelper.getFonts has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GetAncestors.getAncestors (cognitive 19) · ×1
  • GetAncestors.getAncestors (cognitive 19) library/Controller/Navigation/Helper/GetAncestors.php:22 — GetAncestors.getAncestors has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2, boolean chains 1, 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 · Post.getPostTerms (cognitive 19) · ×1
  • Post.getPostTerms (cognitive 19) library/Helper/Post.php:432 — Post.getPostTerms has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Upgrade.initUpgrade (cognitive 19) · ×1
  • Upgrade.initUpgrade (cognitive 19) library/Upgrade.php:1543 — Upgrade.initUpgrade has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (2 pts), boolean chains 1, 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 · PopulateUsedColors.populate (cognitive 19) · ×1
  • PopulateUsedColors.populate (cognitive 19) library/Upgrade/Palette/PopulateUsedColors.php:131 — PopulateUsedColors.populate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 4 (5 pts), ternaries 3 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DecorateDesignTokens.decorate (cognitive 19) · ×1
  • DecorateDesignTokens.decorate (cognitive 19) library/Upgrade/V41/DecorateDesignTokens.php:7 — DecorateDesignTokens.decorate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Wp.findCoreTemplates (cognitive 18) · ×1
  • Wp.findCoreTemplates (cognitive 18) Modularity/source/php/Helper/Wp.php:75 — Wp.findCoreTemplates has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3 (7 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Posts.data (cognitive 18) · ×1
  • Posts.data (cognitive 18) Modularity/source/php/Module/Posts/Posts.php:145 — Posts.data has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 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 · ListTemplate.prepareList (cognitive 18) · ×1
  • ListTemplate.prepareList (cognitive 18) Modularity/source/php/Module/Posts/TemplateController/ListTemplate.php:47 — ListTemplate.prepareList has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AppendArchiveMenuItem.getMenu (cognitive 18) · ×1
  • AppendArchiveMenuItem.getMenu (cognitive 18) library/Controller/Navigation/Decorators/Breadcrumb/AppendArchiveMenuItem.php:35 — AppendArchiveMenuItem.getMenu has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 4 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Navigation.getAncestors (cognitive 18) · ×1
  • Navigation.getAncestors (cognitive 18) library/Helper/Navigation.php:276 — Navigation.getAncestors has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 1, ternaries 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 · FaceDetectingFocusPointResolver.resolve (cognitive 18) · ×1
  • FaceDetectingFocusPointResolver.resolve (cognitive 18) library/ImageFocus/Resolvers/FaceDetectingFocusPointResolver.php:37 — FaceDetectingFocusPointResolver.resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, error handling 1, loops 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ResolveTranslatedPageLink.buildTranslatedPathSegments (cognitive 18) · ×1
  • ResolveTranslatedPageLink.buildTranslatedPathSegments (cognitive 18) library/Integrations/Polylang/ResolveTranslatedPageLink.php:118 — ResolveTranslatedPageLink.buildTranslatedPathSegments has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, 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 · MergeAdjacentLayerStylesProcessor.singleLayer (cognitive 18) · ×1
  • MergeAdjacentLayerStylesProcessor.singleLayer (cognitive 18) library/MarkupProcessor/Processors/MergeAdjacentLayerStylesProcessor.php:83 — MergeAdjacentLayerStylesProcessor.singleLayer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateLegacyGoogleFontsToNativeFontLibrary.installFont (cognitive 18) · ×1
  • MigrateLegacyGoogleFontsToNativeFontLibrary.installFont (cognitive 18) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:144 — MigrateLegacyGoogleFontsToNativeFontLibrary.installFont has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (5 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateLegacyUploadedFontsToNativeFontLibrary.persistActivatedFontFamily (cognitive 18) · ×1
  • MigrateLegacyUploadedFontsToNativeFontLibrary.persistActivatedFontFamily (cognitive 18) library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:571 — MigrateLegacyUploadedFontsToNativeFontLibrary.persistActivatedFontFamily has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (7 pts), boolean chains 5, if/else 4 (5 pts), loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · index.startSearchPage (cognitive 18) · ×1
  • index.startSearchPage (cognitive 18) library/SearchIndex/SearchPage/js/index.ts:311 — index.startSearchPage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, error handling 1, loops 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (execute, a function literal at line 456). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · Table.tableList (cognitive 17) · ×1
  • Table.tableList (cognitive 17) Modularity/source/php/Module/Table/Table.php:260 — Table.tableList has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 6 (8 pts) (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Color.prepareColor (cognitive 17) · ×1
  • Color.prepareColor (cognitive 17) library/Helper/Color.php:21 — Color.prepareColor has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 5, if/else 3 (4 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateLegacyGoogleFontsToNativeFontLibrary.removeRemoteFontFaces (cognitive 17) · ×1
  • MigrateLegacyGoogleFontsToNativeFontLibrary.removeRemoteFontFaces (cognitive 17) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:195 — MigrateLegacyGoogleFontsToNativeFontLibrary.removeRemoteFontFaces has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (7 pts), boolean chains 6, if/else 2 (3 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateWideLogotypeHeightDefault.migrate (cognitive 17) · ×1
  • MigrateWideLogotypeHeightDefault.migrate (cognitive 17) library/Upgrade/V58/MigrateWideLogotypeHeightDefault.php:57 — MigrateWideLogotypeHeightDefault.migrate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, 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 · Version71.repairBlocks (cognitive 17) · ×1
  • Version71.repairBlocks (cognitive 17) library/Upgrade/V71/Version71.php:86 — Version71.repairBlocks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Editor.getModule (cognitive 16) · ×1
  • Editor.getModule (cognitive 16) Modularity/source/php/Editor.php:537 — Editor.getModule has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 3 (5 pts) (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 · Post.getPostTerms (cognitive 16) · ×1
  • Post.getPostTerms (cognitive 16) Modularity/source/php/Helper/Post.php:171 — Post.getPostTerms has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 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 · Wp.getCoreTemplates (cognitive 16) · ×1
  • Wp.getCoreTemplates (cognitive 16) Modularity/source/php/Helper/Wp.php:13 — Wp.getCoreTemplates has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (6 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Module.getWidgetNames (cognitive 16) · ×1
  • Module.getWidgetNames (cognitive 16) Modularity/source/php/Module.php:577 — Module.getWidgetNames has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AbstractController.addPostData (cognitive 16) · ×1
  • AbstractController.addPostData (cognitive 16) Modularity/source/php/Module/Posts/TemplateController/AbstractController.php:135 — AbstractController.addPostData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (5 pts), boolean chains 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NavigationBranchResolver.findChildren (cognitive 16) · ×1
  • NavigationBranchResolver.findChildren (cognitive 16) library/Api/Navigation/NavigationBranchResolver.php:38 — NavigationBranchResolver.findChildren has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PdfArchiveEndpoint.handleArchivePosts (cognitive 16) · ×1
  • PdfArchiveEndpoint.handleArchivePosts (cognitive 16) library/Api/Pdf/PdfArchiveEndpoint.php:99 — PdfArchiveEndpoint.handleArchivePosts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PdfIdEndpoint.getPostsById (cognitive 16) · ×1
  • PdfIdEndpoint.getPostsById (cognitive 16) library/Api/Pdf/PdfIdEndpoint.php:86 — PdfIdEndpoint.getPostsById has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AppendPageTreeAncestorsMenuItems.getMenu (cognitive 16) · ×1
  • AppendPageTreeAncestorsMenuItems.getMenu (cognitive 16) library/Controller/Navigation/Decorators/Breadcrumb/AppendPageTreeAncestorsMenuItems.php:32 — AppendPageTreeAncestorsMenuItems.getMenu has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RemoveInvalidForAttributesProcessor.process (cognitive 16) · ×1
  • RemoveInvalidForAttributesProcessor.process (cognitive 16) library/MarkupProcessor/Processors/RemoveInvalidForAttributesProcessor.php:16 — RemoveInvalidForAttributesProcessor.process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, loops 2, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontDisplay.useSwapForFontLibraryFaces (cognitive 16) · ×1
  • FontDisplay.useSwapForFontLibraryFaces (cognitive 16) library/Performance/FontDisplay/FontDisplay.php:35 — FontDisplay.useSwapForFontLibraryFaces has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 3 (6 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DateClauseBuilder.buildDateMetaQueryClause (cognitive 16) · ×1
  • DateClauseBuilder.buildDateMetaQueryClause (cognitive 16) library/PostsList/GetPosts/PostsListConfigToGetPostsArgs/DateClauseBuilder.php:30 — DateClauseBuilder.buildDateMetaQueryClause has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 3, if/else 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 · ApplyStyles.getColorSchemeStyles (cognitive 16) · ×1
  • ApplyStyles.getColorSchemeStyles (cognitive 16) library/Styleguide/Customize/ApplyStyles/ApplyStyles.php:105 — ApplyStyles.getColorSchemeStyles has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), ternaries 3, boolean chains 2, if/else 1 (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · (anonymous) (cognitive 16) · ×1
  • (anonymous) (cognitive 16) assets/source/mce-js/mce-print-break.js:2 — (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 6 function items inside it that branch (a function literal at line 13, a function literal at line 52, a function literal at line 33, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: LoginLogout.php, login.blade.php, user.blade.php library/Customizer/Sections/Header/LoginLogout.php — 3 files — `library/Customizer/Sections/Header/LoginLogout.php`, `views/v3/partials/header/user/login.blade.php`, `views/v3/partials/header/user/user.blade.php` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) library/Controller/Navigation/Helper/GetPostsByParent.php:32 — library/Controller/Navigation/Helper/GetPostsByParent.php:32-115 | library/Helper/Navigation.php:351-425 — These two members are one piece of code written twice and then edited apart: 75 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 47+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 47+ corresponding lines) library/Controller/E401.php:59 — library/Controller/E401.php:59-113 | library/Controller/E403.php:62-108 | library/Controller/E404.php:17-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) library/Upgrade/V50/MigrateLegacyBusinessHeaderToFlexible.php:59 — library/Upgrade/V50/MigrateLegacyBusinessHeaderToFlexible.php:59-81 | library/Upgrade/V50/MigrateLegacyCasualHeaderToFlexible.php:51-87 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) library/Helper/Post.php:335 — library/Helper/Post.php:335-379 | library/PostObject/Decorators/PostObjectWithFilteredContent.php:64-109 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) library/A11yStatement/A11yStatement.php:151 — library/A11yStatement/A11yStatement.php:151-193 | library/PrivacyPolicy/PrivacyPolicy.php:88-128 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) library/Api/Customizer/DesignLibraryFontActivation.php:135 — library/Api/Customizer/DesignLibraryFontActivation.php:135-172 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:290-335 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) Modularity/source/php/Helper/Wp.php:15 — Modularity/source/php/Helper/Wp.php:15-68 | Modularity/source/php/Helper/Wp.php:77-110 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 22+ corresponding lines) library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:167 — library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:167-192 | library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:203-224 | library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php:104-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) library/Kulturkortet/MunicipioAuth/Visma/VismaApi.php:48 — library/Kulturkortet/MunicipioAuth/Visma/VismaApi.php:48-67 | library/Kulturkortet/MunicipioAuth/Visma/VismaApi.php:72-95 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemIsCurrentPage.php:28 — library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemIsCurrentPage.php:28-48 | library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemsAncestors.php:28-46 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) library/Helper/User/User.php:225 — library/Helper/User/User.php:225-239 | library/Helper/User/User.php:247-267 | library/Helper/User/User.php:354-368 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) library/Customizer/Controls/MultiCheck/MultiCheckControl.php:83 — library/Customizer/Controls/MultiCheck/MultiCheckControl.php:83-94 | library/Customizer/Controls/MultiSelect/MultiSelectControl.php:82-96 | library/Customizer/Controls/Sortable/SortableControl.php:119-130 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 2+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 2+ corresponding lines) library/Controller/E401.php:122 — library/Controller/E401.php:122-125 | library/Controller/E401.php:134-140 | library/Controller/E403.php:117-120 | library/Controller/E403.php:129-135 | library/Controller/E404.php:75-76 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) library/Controller/Navigation/Decorators/Menu/ApplyMenuItemFilter.php:28 — library/Controller/Navigation/Decorators/Menu/ApplyMenuItemFilter.php:28-43 | library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemsHref.php:28-42 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:97 — library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:97-109 | library/Upgrade/V52/MigrateHeaderSortableDataIntegrity.php:164-176 | library/Upgrade/V59/MigrateMalformedFlexibleHeaderLowerArea.php:89-101 | library/Upgrade/V60/MigrateEmptyHeaderContainerWidthToExplicitDefault.php:68-80 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) library/Upgrade/V66/Version66.php:24 — library/Upgrade/V66/Version66.php:24-32 | library/Upgrade/V67/Version67.php:29-37 | library/Upgrade/V68/Version68.php:32-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 3+ corresponding lines) library/BackdropBanner/BackdropBanner.php:29 — library/BackdropBanner/BackdropBanner.php:29-31 | library/PostsList/Block/PostsListBlock.php:22-25 | library/PrivacyPolicy/PrivacyPolicy.php:36-41 | library/Styleguide/AddLayerOrderDefinitionToHead/AddLayerOrderDefinitionToHead.php:31-33 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) Modularity/source/php/Upgrade/Migrators/Block/AcfBlockMigrationHandler.php:87 — Modularity/source/php/Upgrade/Migrators/Block/AcfBlockMigrationHandler.php:87-93 | Modularity/source/php/Upgrade/Migrators/Block/AcfBlockRepeaterFieldsMigrator.php:83-90 | Modularity/source/php/Upgrade/Migrators/Module/AcfModuleMigrationHandler.php:70-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) library/Controller/Navigation/Decorators/Accessibility/ApplyAccessibilityItemsFilter.php:28 — library/Controller/Navigation/Decorators/Accessibility/ApplyAccessibilityItemsFilter.php:28-31 | library/Controller/Navigation/Decorators/Breadcrumb/ApplyBreadcrumbItemsFilter.php:29-33 | library/Controller/Navigation/Decorators/Menu/ApplyMenuItemsFilter.php:28-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:162 — library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:162-163 | library/Kulturkortet/QRCodeViewer/KulturkortetQRCodeViewerAuthViewFactory.php:129-130 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 1+ corresponding lines) library/Customizer/CustomField.php:143 — library/Customizer/CustomField.php:143-143 | library/Customizer/CustomFieldControlFactory.php:96-96 | library/Customizer/NativeField.php:167-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) library/Upgrade/V64/Version64.php:87 — library/Upgrade/V64/Version64.php:87-121 | library/Upgrade/V65/Version65.php:26-60 — before extracting anything, compare `library/Upgrade/V64/Version64.php` and `library/Upgrade/V65/Version65.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/Upgrade/V64/Version64.php:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:303 — library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:303-335 | library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:435-467 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) library/Controller/Navigation/Helper/GetAncestors.php:60 — library/Controller/Navigation/Helper/GetAncestors.php:60-87 | library/Helper/Navigation.php:307-334 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Controller/Navigation/Helper/GetAncestors.php:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) library/Controller/SingularElementarySchool.php:24 — library/Controller/SingularElementarySchool.php:24-49 | library/Controller/SingularPreschool.php:23-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (21–24 lines × 2) · ×1
  • Duplicated block (21–24 lines × 2) library/Helper/Post.php:56 — library/Helper/Post.php:56-79 | library/Helper/Post.php:107-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:90 — library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:90-111 | library/Kulturkortet/QRCodeViewer/KulturkortetQRCodeViewerAuthViewFactory.php:137-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) Modularity/source/php/Module/ManualInput/Private/PrivateController.php:158 — Modularity/source/php/Module/ManualInput/Private/PrivateController.php:158-178 | Modularity/source/php/Module/Posts/Private/PrivateController.php:133-153 — before extracting anything, compare `Modularity/source/php/Module/ManualInput/Private/PrivateController.php` and `Modularity/source/php/Module/Posts/Private/PrivateController.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) library/Customizer/PanelsRegistry.php:500 — library/Customizer/PanelsRegistry.php:500-519 | library/Customizer/PanelsRegistry.php:530-548 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) library/Integrations/Polylang/ResolveNavigationCacheKey.php:61 — library/Integrations/Polylang/ResolveNavigationCacheKey.php:61-77 | library/Integrations/Polylang/ResolveNavigationFetchUrlLanguage.php:99-115 | library/Integrations/Polylang/ResolvePageTreeTranslatedChildren.php:182-198 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (12–17 lines × 3) · ×1
  • Duplicated block (12–17 lines × 3) library/Upgrade/V64/Version64.php:85 — library/Upgrade/V64/Version64.php:85-101 | library/Upgrade/V65/Version65.php:24-40 | library/Upgrade/V70/Version70.php:43-54 — before extracting anything, compare `library/Upgrade/V64/Version64.php` and `library/Upgrade/V65/Version65.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/Upgrade/V64/Version64.php:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) library/Customizer/Applicators/Types/Component.php:129 — library/Customizer/Applicators/Types/Component.php:129-144 | library/Customizer/Applicators/Types/Modifier.php:93-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `library/Customizer/Applicators/Types/Component.php:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) Modularity/source/php/Module/Posts/Helper/EventStartTimestampResolver.php:51 — Modularity/source/php/Module/Posts/Helper/EventStartTimestampResolver.php:51-65 | library/PostsList/ViewCallableProviders/Schema/Event/GetDate.php:76-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×1
  • Duplicated block (12–13 lines × 3) library/Upgrade/V50/MigrateLegacyHeaderModifierCss.php:73 — library/Upgrade/V50/MigrateLegacyHeaderModifierCss.php:73-85 | library/Upgrade/V55/MigrateFlexibleHeaderContainerSelectors.php:73-85 | library/Upgrade/V57/MigrateFooterBeforeBackgroundToSiteWrapperAfter.php:63-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×1
  • Duplicated block (10–12 lines × 3) library/Customizer/Applicators/Types/Component.php:125 — library/Customizer/Applicators/Types/Component.php:125-134 | library/Customizer/Applicators/Types/Controller.php:38-49 | library/Customizer/Applicators/Types/Modifier.php:89-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `library/Customizer/Applicators/Types/Component.php:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) library/Customizer/Controls/MultiColor/MultiColorControl.php:46 — library/Customizer/Controls/MultiColor/MultiColorControl.php:46-54 | library/Customizer/Controls/Repeater/RepeaterControl.php:42-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×1
  • Duplicated block (7–8 lines × 3) library/Customizer/Controls/AlphaColor/AlphaColorControl.php:53 — library/Customizer/Controls/AlphaColor/AlphaColorControl.php:53-59 | library/Customizer/Controls/ColorChoice/ColorChoiceControl.php:44-50 | library/Customizer/Controls/Slider/SliderControl.php:50-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) library/Customizer/Controls/Background/BackgroundControl.php:51 — library/Customizer/Controls/Background/BackgroundControl.php:51-57 | library/Customizer/Controls/MultiCheck/MultiCheckControl.php:43-49 | library/Customizer/Controls/MultiColor/MultiColorControl.php:48-54 | library/Customizer/Controls/MultiSelect/MultiSelectControl.php:43-49 | library/Customizer/Controls/Repeater/RepeaterControl.php:43-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) library/Api/Customizer/DesignLibraryFontActivation.php:192 — library/Api/Customizer/DesignLibraryFontActivation.php:192-198 | library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php:364-370 | library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php:477-483 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `library/Api/Customizer/DesignLibraryFontActivation.php:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) library/Customizer/CustomFieldControlArguments.php:16 — library/Customizer/CustomFieldControlArguments.php:16-44 | library/Customizer/NativeFieldControlArguments.php:16-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (72 lines × 5) · ×1
  • Duplicated block (72 lines × 5) library/Customizer/Sections/Component/FooterMain.php:11 — library/Customizer/Sections/Component/FooterMain.php:11-95 | library/Customizer/Sections/Component/SliderDefault.php:14-150 | library/Customizer/Sections/ErrorPages.php:11-82 | library/Customizer/Sections/Menu/Quicklinks.php:11-104 | library/Customizer/Sections/Menu/Siteselector.php:12-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (42 lines × 3) · ×1
  • Duplicated block (42 lines × 3) library/Customizer/Sections/Header/Layout.php:155 — library/Customizer/Sections/Header/Layout.php:155-235 | library/Customizer/Sections/Menu/Behaviour.php:12-83 | library/Customizer/Sections/PostType.php:14-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) library/Kulturkortet/MunicipioAuth/Visma/VismaAuthConfig.php:22 — library/Kulturkortet/MunicipioAuth/Visma/VismaAuthConfig.php:22-32 | library/Kulturkortet/MunicipioAuth/Visma/VismaAuthConfig.php:37-47 | library/Kulturkortet/MunicipioAuth/Visma/VismaAuthConfig.php:52-62 | library/Kulturkortet/Vitec/VitecConfig.php:17-27 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. 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.
P12 · CI test-gate honesty · Test failure does not fail the CI gate · ×1
  • Test failure does not fail the CI gate REDACTED:46 — `continue-on-error: true` lets the step or job that runs `npm run test:css-validator 2>&1 | tee test-results/w3c-css-validation.log` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience library/Chat/Api/ChatEndpoint.php:228 — `curl_exec(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (8 clone groups) library/Customizer/Controls/MultiColor/MultiColorControl.ts:15 — 8 duplicated blocks under library/Customizer/Controls/ have copies in at least two of the sibling directories Background, ColorChoice, MultiCheck, MultiColor, MultiSelect, Repeater (+2 more sibling(s) not listed) — 5 of them are reported below, and 3 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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 · Duplicated block (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) Modularity/source/php/Module/Posts/assets/xhr.ts:20 — Modularity/source/php/Module/Posts/assets/xhr.ts:20 · Modularity/source/php/Module/Posts/assets/xhr.ts:70 — 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.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) library/PostsList/Block/js/SettingsPanel/AppearanceSettingsPanel/DateSourceControl/DateSourceControl.tsx:16 — library/PostsList/Block/js/SettingsPanel/AppearanceSettingsPanel/DateSourceControl/DateSourceControl.tsx:16 · library/PostsList/Block/js/SettingsPanel/PostsSettingsPanel/OrderByControl/OrderByControl.tsx:17 — 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 (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:113 — Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:113 · Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:143 — 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.
R10 · Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:9 — Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:9 · Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:84 — the two spans are one implementation copied and then locally edited — 111 tokens are still identical, in the same order in both spans, 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 (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) Modularity/source/js/editor/dragAndDrop.js:40 — Modularity/source/js/editor/dragAndDrop.js:40 · Modularity/source/js/editor/dragAndDrop.js:95 — all 2 copies are in the same file, 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 (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) Modularity/source/js/modularity-editor-modal.js:54 — Modularity/source/js/modularity-editor-modal.js:54 · Modularity/source/js/modularity-editor-modal.js:99 — all 2 copies are in the same file, 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 (18 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (18 matched lines × 2 locations) assets/source/js/headingHierarchyIndicator.ts:8 — assets/source/js/headingHierarchyIndicator.ts:8 · assets/source/js/vagueControlTextIndicator.ts:39 — the two spans are one implementation copied and then locally edited — 95 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 (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) Modularity/source/php/Module/InteractiveMap/assets/map/filtering/LayerGroupWithoutFilter.ts:30 — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/LayerGroupWithoutFilter.ts:30 · Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithSelectFilter.ts:77 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:147 — assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:147 · assets/source/js/headerLogoScrollShrink.ts:45 — 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 (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) library/Chat/js/chat/feedback.ts:22 — library/Chat/js/chat/feedback.ts:22 · library/Chat/js/chat/feedback.ts:36 — all 2 copies are in the same file, 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 (8 lines × 2 locations) · ×1
  • Duplicated block (8 lines × 2 locations) assets/source/js/comments.ts:13 — assets/source/js/comments.ts:13 · assets/source/js/comments.ts:83 — all 2 copies are in the same file, 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 (8 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (8 matched lines × 2 locations) library/Chat/js/chat/ChatSession.ts:75 — library/Chat/js/chat/ChatSession.ts:75 · library/ProgressReporter/AdminProgressAction/js/FetchStreamSource.ts:55 — the two spans are one implementation copied and then locally edited — 54 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 (7 lines × 2 locations) · ×1
  • Duplicated block (7 lines × 2 locations) Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:78 — Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:78 · Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupWithButtonFilter.ts:86 — 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.
R10 · Code Duplication · Duplicated block (7 lines × 3 locations) · ×1
  • Duplicated block (7 lines × 3 locations) assets/source/js/comments.ts:18 — assets/source/js/comments.ts:18 · assets/source/js/comments.ts:88 · assets/source/js/sessionManager.ts:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R2 · Cyclomatic Complexity · Complex function sanitizeItemOptions (cyclomatic 17, cognitive 16) · ×1
  • Complex function sanitizeItemOptions (cyclomatic 17, cognitive 16) library/Customizer/Controls/Sortable/SortableControl.ts:38 — sanitizeItemOptions has cyclomatic complexity 17 and cognitive complexity 16; 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 importSettings (cyclomatic 15, cognitive 32) · ×1
  • Complex function importSettings (cyclomatic 15, cognitive 32) assets/source/js/admin/designShareUtils.ts:304 — importSettings has cyclomatic complexity 15 and cognitive complexity 32; 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 (anonymous) (cyclomatic 14, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 13) library/SearchIndex/SearchPage/js/index.ts:179 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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 callback (cyclomatic 13, cognitive 28) · ×1
  • Complex function callback (cyclomatic 13, cognitive 28) assets/source/js/admin/widgetsAreaHider.js:4 — callback has cyclomatic complexity 13 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 (anonymous) (cyclomatic 11, cognitive 14) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 14) library/SearchIndex/SearchPage/js/index.ts:363 — (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; 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.
R3 · Large Files · library/Customizer/Controls/Sortable/SortableControl.ts · ×1
  • library/Customizer/Controls/Sortable/SortableControl.ts: 524 lines of code library/Customizer/Controls/Sortable/SortableControl.ts:1 — library/Customizer/Controls/Sortable/SortableControl.ts has 524 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · library/SearchIndex/SearchPage/js/index.ts · ×1
  • library/SearchIndex/SearchPage/js/index.ts: 450 lines of code library/SearchIndex/SearchPage/js/index.ts:1 — library/SearchIndex/SearchPage/js/index.ts has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R6 · Tooling · This package's lint script runs in no CI job · ×1
  • This package's lint script runs in no CI job Modularity/package.json:52 — The package in `Modularity` declares the lint script `lint` (`npx biome lint ./source`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `Modularity` (or the workspace's task runner).
R7 · Dead Code · Dead file (~39 LoC) · ×1
  • Dead file (~39 LoC) library/Customizer/Controls/Slider/SliderControl.js — no import path from any entry point (117 application, 21 tooling, 26 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~26 LoC) · ×1
  • Dead file (~26 LoC) jest-raw-loader.js — no import path from any entry point (117 application, 21 tooling, 26 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~15 LoC) · ×1
  • Dead file (~15 LoC) Modularity/source/js/helpers/serializeObject.js — no import path from any entry point (117 application, 21 tooling, 26 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency 'body-parser' · ×1
  • Unused dependency 'body-parser' package.json:67 — 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 'dotenv' · ×1
  • Unused dependency 'dotenv' package.json:69 — 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 'lit-html' · ×1
  • Unused dependency 'lit-html' package.json:75 — 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 'mousetrap-global-bind' · ×1
  • Unused dependency 'mousetrap-global-bind' package.json:76 — 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 'object-fit-images' · ×1
  • Unused dependency 'object-fit-images' package.json:77 — 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 'react-textarea-autosize' · ×1
  • Unused dependency 'react-textarea-autosize' package.json:80 — 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 'vite-plugin-babel' · ×1
  • Unused dependency 'vite-plugin-babel' package.json:87 — 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 'wp-types' · ×1
  • Unused dependency 'wp-types' package.json:89 — 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 — 126 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:94 — `!postTypeSelect || !taxonomySelect || !taxonomySelectLabel || !termsSelect || !termsSelectLabel` appears character-identically in 2 files — Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts, Modularity/source/php/Module/Posts/assets/moduleFilteringSetup.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 Modularity/source/js/editor/dragAndDrop.js:11 — `typeof pagenow !== "undefined" && pagenow == "admin_page_modularity-editor"` appears character-identically in 2 files — Modularity/source/js/editor/dragAndDrop.js, Modularity/source/js/editor/module.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 Modularity/source/php/Editor.php:120 — `!$post && isset($_GET['page_for']) && !empty($_GET['page_for'])` appears character-identically in 2 files — Modularity/source/php/Editor.php, Modularity/source/php/Helper/Wp.php. 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 views/v3/one-page.blade.php:46 — `!empty($callToActionItems['floating']['icon']) && !empty($callToActionItems['floating']['wrapper'])` appears character-identically in 3 files — views/v3/one-page.blade.php, views/v3/partials/article.blade.php, views/v3/partials/post/post-collection.blade.php. 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 Modularity/source/php/Integrations/Component/ImageFocusResolver.php:38 — `!empty($data['id']) && $focusPoint['left'] === 50 && $focusPoint['top'] === 50` appears character-identically in 2 files — Modularity/source/php/Integrations/Component/ImageFocusResolver.php, library/Integrations/Component/ImageFocusResolver.php. 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 Modularity/source/php/Module/Menu/views/menus/listing/components/menuItem.blade.php:18 — `!empty($menuItem['children']) && count($menuItem['children']) > 3` appears character-identically in 2 files — Modularity/source/php/Module/Menu/views/menus/listing/components/menuItem.blade.php, Modularity/source/php/Module/Menu/views/menus/listing/partials/expand.blade.php. 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 views/v3/partials/schema/place/related-posts.blade.php:33 — `!empty($post->callToActionItems['floating']['icon']) && !empty($post->callToActionItems['floating']['wrapper'])` appears character-identically in 2 files — views/v3/partials/schema/place/related-posts.blade.php, views/v3/partials/schema/place/title-area.blade.php. 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 library/Api/Pdf/PdfArchiveEndpoint.php:116 — `!empty($post->id) && empty(get_field('post_single_show_featured_image', $post->id))` appears character-identically in 2 files — library/Api/Pdf/PdfArchiveEndpoint.php, library/Api/Pdf/PdfIdEndpoint.php. 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 Modularity/source/php/Module/Posts/TemplateController/ExpandableListTemplate.php:165 — `!empty($this->data['posts']) && is_array($this->data['posts'])` appears character-identically in 2 files — Modularity/source/php/Module/Posts/TemplateController/ExpandableListTemplate.php, Modularity/source/php/Module/Posts/TemplateController/ListTemplate.php. 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 Modularity/source/php/Module/Posts/TemplateController/AbstractController.php:269 — `!empty($this->fields['posts_open_links_in_new_tab']) && !$this` appears character-identically in 2 files — Modularity/source/php/Module/Posts/TemplateController/AbstractController.php, Modularity/source/php/Module/Posts/TemplateController/ListTemplate.php. 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 library/Controller/School/ElementarySchool/UspsGenerator.php:74 — `!is_array($areaServed) || empty($areaServed)` appears character-identically in 2 files — library/Controller/School/ElementarySchool/UspsGenerator.php, library/Controller/School/Preschool/UspsGenerator.php. 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 library/Helper/ElementAttribute.php:193 — `!is_array($attributesArray) || empty($attributesArray)` appears character-identically in 2 files — library/Helper/ElementAttribute.php, library/Helper/Html.php. 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 Modularity/source/php/Helper/Cache.php:160 — `!is_array($cacheArray) || !array_key_exists($this->hash, $cacheArray)` appears character-identically in 2 files — Modularity/source/php/Helper/Cache.php, library/Helper/Cache.php. 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 library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php:35 — `!is_array($description) || count($description) <= 1` appears character-identically in 2 files — library/Controller/School/ElementarySchool/AccordionListItemsGenerator.php, library/Controller/School/Preschool/AccordionListItemsGenerator.php. 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 library/Api/Customizer/DesignLibraryFontActivation.php:161 — `!is_array($sideloadedFile) || empty($sideloadedFile['file']) || empty($sideloadedFile['url'])` appears character-identically in 3 files — library/Api/Customizer/DesignLibraryFontActivation.php, library/Upgrade/V42/MigrateLegacyGoogleFontsToNativeFontLibrary.php, library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php. 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 library/Api/Customizer/DesignLibrary.php:274 — `!is_numeric($globalStylesPostId) || (int) $globalStylesPostId <= 0` appears character-identically in 2 files — library/Api/Customizer/DesignLibrary.php, library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php. 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 library/Integrations/Polylang/ResolveTranslatedPostTypeArchiveLink.php:77 — `!is_numeric($translatedPageId) || (int) $translatedPageId <= 0` appears character-identically in 2 files — library/Integrations/Polylang/ResolveTranslatedPostTypeArchiveLink.php, library/Integrations/Polylang/ResolveTranslatedPostTypeLink.php. 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 Modularity/source/php/Display.php:811 — `!is_object($module) || empty($module->post_type)` appears character-identically in 2 files — Modularity/source/php/Display.php, Modularity/source/php/Module.php. 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 library/Integrations/Polylang/ResolveNavigationCacheKey.php:47 — `!is_string($currentLanguage) || $currentLanguage === ''` appears character-identically in 3 files — library/Integrations/Polylang/ResolveNavigationCacheKey.php, library/Integrations/Polylang/ResolveNavigationFetchUrlLanguage.php, library/Integrations/Polylang/ResolveNavigationItemsLanguage.php. 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 library/Controller/A11y.php:298 — `!is_string($description) || trim($description) === ''` appears character-identically in 3 files — library/Controller/A11y.php, library/Controller/PrivacyPolicy.php, library/SchemaData/ExternalContent/SyncHandler/SchemaObjectProcessor/ImageSideloadSchemaObjectProcessor.php. 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 library/ImageConvert/TransparencyMetadata.php:31 — `!is_string($filePath) || $filePath === ''` appears character-identically in 2 files — library/ImageConvert/TransparencyMetadata.php, library/Upgrade/V43/MigrateLegacyUploadedFontsToNativeFontLibrary.php. 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 library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php:121 — `!is_string($items) || trim($items) === ''` appears character-identically in 3 files — library/Upgrade/V50/MigrateLegacyHeaderLayoutsToFlexible.php, library/Upgrade/V52/MigrateHeaderSortableDataIntegrity.php, library/Upgrade/V59/MigrateMalformedFlexibleHeaderLowerArea.php. 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 library/Integrations/Polylang/ResolveHomeUrl.php:47 — `!is_string($languageHomeUrl) || $languageHomeUrl === ''` appears character-identically in 2 files — library/Integrations/Polylang/ResolveHomeUrl.php, library/Integrations/Polylang/ResolvePdfNotFoundUrl.php. 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 library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php:139 — `!is_string($legacyValue) || trim($legacyValue) === ''` appears character-identically in 2 files — library/Upgrade/V54/MigrateHeaderAppearanceToDesignTokens.php, library/Upgrade/V56/MigrateHeaderWidthToDesignTokens.php. 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 library/Api/Navigation/NavigationChildrenResolver.php:67 — `!is_string($postType) || $postType === ''` appears character-identically in 2 files — library/Api/Navigation/NavigationChildrenResolver.php, library/SchemaData/ExternalContent/Rest/AjaxSync.php. 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.
  • + 15 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×35
  • Orphaned file Modularity/source/php/AcfFields/php/mod-hero.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-map.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-index.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-subscribe.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-inlaylist.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-all.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file library/Helper/VideoService.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-table-block.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-curator.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-table.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-notice.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file library/AcfFields/php/block-button.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-fileslist.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-image.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/Module/Posts/assets/blockFilteringSetup.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-audio.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-search.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/Upgrade/Migrators/Block/Custom/AcfBlockIndexRepeaterMigrator.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-logogrid.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-posts-filtering.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/Module/Subscribe/assets/ungapd.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-markdown.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/AcfFields/php/mod-rss.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Modularity/source/php/Module/InteractiveMap/assets/map/markerClick/markerClick.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file library/AcfFields/php/options-menu-language.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 10 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×5
  • redundant comment Modularity/source/js/editor/module.js:188 — "Get thickbox url" repeats the code it sits on: 3 of its 3 words (get, thickbox, url) are already in `var thickboxUrl = this.getThickBoxUrl("add", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Modularity/source/js/editor/module.js:193 — "Set thickbox action" repeats the code it sits on: 3 of its 3 words (set, thickbox, action) are already in `lModularity.Editor.Thickbox.postAction = "add";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Modularity/source/js/editor/module.js:204 — "Get import url" repeats the code it sits on: 3 of its 3 words (get, import, url) are already in `var importUrl = this.getImportUrl({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Modularity/source/js/editor/module.js:348 — "Post id input" repeats the code it sits on: 3 of its 3 words (post, id, input) are already in `module.find("input.modularity-js-module-id").val(data.post_id).change();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Modularity/source/php/Module/Curator/assets/mod-curator-load-more.js:131 — "Add the event listener to each button in the array" repeats the code it sits on: 4 of its 5 words (add, event, listener, button) are already in `loadMoreButtons.forEach((button) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D16 · Bus Factor · Off-boarding risk · ×4
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 43 significant file(s) lose their only recent owner: library/Theme/Icon.php, library/Customizer/Controls/Sortable/SortableControl.ts, library/Theme/Sidebars.php, library/A11yStatement/A11yStatement.php, library/Controller/A11y.php, library/AcfFields/php/a11y-statement.php, library/Admin/UI/Editor.php, library/Customizer/Sections/Menu/MegaMenu.php (+35 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 29 significant file(s) lose their only recent owner: library/SearchIndex/SearchPage/js/index.ts, Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php, library/SearchIndex/Provider/Typesense/TypesenseProvider.php, library/SchemaData/SchemaDataFeature.php, library/SchemaData/ExternalContent/ExternalContentFeature.php, Modularity/source/php/Module/Index/Index.php, library/SchemaData/ExternalContent/SyncHandler/SyncHandler.php, library/SearchIndex/Provider/Algolia/AlgoliaProvider.php (+21 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 19 significant file(s) lose their only recent owner: Modularity/source/php/AcfFields/php/mod-modal.php, Modularity/source/php/Module/Contacts/Contacts.php, library/Admin/TinyMce/MceButtons/mce-buttons-template.php, library/Kulturkortet/QRCodeViewer/KulturkortetQRCodeViewerAuthViewFactory.php, library/Kulturkortet/ProfileEditor/KulturkortetProfileEditorAuthViewFactory.php, library/Api/PlaceSearch/Providers/Openstreetmap.php, library/Kulturkortet/MunicipioAuth/controller/secure/SecureMunicipioAuthController.php, library/PostObject/Decorators/PostObjectWithFilters.php (+11 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 4 significant file(s) lose their only recent owner: library/Api/Navigation/NavigationChildrenResolver.php, Modularity/source/php/Upgrade/Migrators/Module/AcfModuleRepeaterFieldsMigrator.php, Modularity/source/php/Options/SingleAdminPage.php, library/Controller/Navigation/Decorators/Menu/PageTreeAppendMenuItemsCustomTitle.php. Pair on, review, or document these before any departure.
AX6 · Interface segregation · Fat interface · ×3
  • Fat interface: MenuBuilderInterface (34 methods) library/Controller/Navigation/MenuBuilderInterface.php:8 — `MenuBuilderInterface` declares 34 methods: `setConfig`, `getMenu`, `appendMenuItems`, `mapMenuItemsFromObjectToArray`, `mapMenuItemsAcfFieldValues`, `mapMenuItemsIsAncestor`, `applyMenuItemFilter`, `convertStaticMenuItemsToPageTreeItems`, `appendHomeIconMenuItem`, `appendArchiveMenuItem`, `appendPageTreeAncestorsMenuItems`, `applyBreadcrumbItemsFilter`, `appendPrintMenuItem`, `applyAccessibilityItemsFilter`, `applyAccessibilityItemsDeprecatedFilter`, `pageTreeGetAncestors`, `appendDataFromAncestorIds`, `tryGetPageTreeMenuItemsFromCache`, `pageTreeMenuItemsFormatter`, `pageTreeAppendMenuItemsHref`, `pageTreeAppendMenuItemsCustomTitle`, `pageTreeAppendMenuItemsAncestors`, `pageTreeAppendMenuItemIsCurrentPage`, `pageTreeAppendChildren`, `pageTreeSetMenuItemsCache`, `pageTreeAppendMenuItemsFetchUrl`, `appendAcfFields`, `applyMenuItemsFilter`, `removeSubLevels`, `removeTopLevel`, `structureMenuItems`, `applyNestedMenuItemsFilter`, `standardMenuWithPageTreeSubitemsAppendHasChildren`, `standardMenuWithPageTreeSubitemsAppendAncestors`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ImageConvertConfigInterface (17 methods) library/ImageConvert/Config/ImageConvertConfigInterface.php:5 — `ImageConvertConfigInterface` declares 17 methods: `isEnabled`, `imageDownsizePriority`, `mimeTypes`, `internalFilterPriority`, `fileNameSuffixes`, `maxImageDimension`, `intermidiateImageFormat`, `intermidiateImageQuality`, `maxSourceFileSize`, `failedCacheExpiry`, `successCacheExpiry`, `lockExpiry`, `defaultCacheExpiry`, `pageCacheExpiry`, `getImageConversionStrategy`, `getDefaultImageConversionLogWriter`, `maxImageAspectRatioMultiplier`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: PostObjectInterface (19 methods) library/PostObject/PostObjectInterface.php:9 — `PostObjectInterface` declares 19 methods: `getId`, `getTitle`, `getContent`, `getExcerpt`, `getContentHeadings`, `getPermalink`, `getCommentCount`, `getPostType`, `getIcon`, `getBlogId`, `getPublishedTime`, `getModifiedTime`, `getArchiveDateTimestamp`, `getArchiveDateFormat`, `getSchemaProperty`, `getSchema`, `getTerms`, `getImage`, `__get`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×3
  • Hand-rolled JSON/XML parsing via regex library/MarkupProcessor/Processors/MergeAdjacentLayerStylesProcessor.php:85 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This PHP code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex library/Helper/GoogleTranslate.php:122 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This PHP code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex library/Helper/GoogleTranslate.php:128 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This PHP code already uses a real parser in the same package; use it here too.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch library/Controller/Sponsor/SponsorPresentation.php:332 — `date` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the docblock, and the row stops firing.
  • Silent fallback default in catch library/Customizer/Controls/controlTypes.ts:85 — `readJsonObject` swallows every exception into `return {}` — 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.
  • Silent fallback default in catch library/Customizer/Controls/TabBox/TabBoxControl.ts:112 — `readControls` swallows every exception into `return []` — 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.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×2
  • Projects may be oversized for their cohesion package.json:1 — `(repository root)` (102322 LoC, 1354 module-visible types across 399 directories) overshoots its size bounds. 2 of 2 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion Modularity/package.json:1 — `Modularity` (30742 LoC, 217 module-visible types across 80 directories) overshoots its size bounds. 2 of 2 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
R7 · Dead Code · Unused private field 'container' · ×2
  • Unused private field 'container' Modularity/source/php/Module/InteractiveMap/assets/map/filtering/LayerGroupWithoutFilter.ts:13 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
  • Unused private field 'container' Modularity/source/php/Module/InteractiveMap/assets/map/layerGroups.ts:8 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
C2 · Access Controls · Anonymous-heavy surface · ×1
  • Anonymous-heavy surface — Public opt-outs and open tables (8) outweigh guarded routes and protected tables (7) — review whether the open surface is intended.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 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 (99 single-owned of 570 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 570 of the 1983 production source files in this repository met that bar). They are anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: library/AcfFields/php/options-theme-custom-post-type.php, Modularity/source/php/Module/InlayList/InlayList.php, library/Controller/Navigation/Decorators/Breadcrumb/AppendPageTreeAncestorsMenuItems.php.
D21 · Naming Consistency · `getUniqueID` spells `ID` where 32 names in the project spell it `Id` · ×1
  • `getUniqueID` spells `ID` where 32 names in the project spell it `Id` library/ProgressReporter/AdminProgressAction/js/UIComponents/ProgressBarWithLabel.ts:72 — 32 of 33 names in project @helsingborg-stad/municipio spell the token `Id` (32 of 33; unit: names in project @helsingborg-stad/municipio containing `Id`). Peers: UserEditableList.constructor(userId) (Modularity/source/js/private/userEditableList.ts:7); UserEditableList.constructor(moduleId) (Modularity/source/js/private/userEditableList.ts:7); UserEditableList.userId (Modularity/source/js/private/userEditableList.ts:13); UserEditableList.moduleId (Modularity/source/js/private/userEditableList.ts:14); InteractiveMap.constructor(mapId) (Modularity/source/php/Module/InteractiveMap/assets/interactiveMap.ts:20). Rename to `getUniqueId`. [rule N6]
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 35 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: Modularity/source/php/AcfFields/php/mod-hero.php, Modularity/source/php/AcfFields/php/mod-map.php, Modularity/source/php/AcfFields/php/mod-index.php, Modularity/source/php/AcfFields/php/mod-subscribe.php, Modularity/source/php/AcfFields/php/mod-inlaylist.php, Modularity/source/php/AcfFields/php/mod-all.php, library/Helper/VideoService.php, Modularity/source/php/AcfFields/php/mod-table-block.php (and 27 more) (39 orphaned of 572 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 572 of the 1983 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
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 REDACTED:6 — No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:44 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused module-local declaration 'postAction' · ×1
  • Unused module-local declaration 'postAction' Modularity/source/js/editor/thickbox.js:7 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused private field 'mapInstance' · ×1
  • Unused private field 'mapInstance' Modularity/source/php/Module/InteractiveMap/assets/map/filtering/filterHelper.ts:8 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code · Unused private field 'storageInstance' · ×1
  • Unused private field 'storageInstance' Modularity/source/php/Module/InteractiveMap/assets/map/filtering/layerGroupFilterFactory.ts:17 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code · Unused module-local declaration 'CustomizeSetting' · ×1
  • Unused module-local declaration 'CustomizeSetting' assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:10 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'aspectRatioSettingId' · ×1
  • Unused module-local declaration 'aspectRatioSettingId' assets/source/js/admin/customizerHeaderLogoScrollAspectRatioPreview.ts:37 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused private field 'lastManualHashChange' · ×1
  • Unused private field 'lastManualHashChange' assets/source/js/hashHighlightManager.ts:5 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code · Unused private field 'async' · ×1
  • Unused private field 'async' library/Chat/js/chat/ChatSession.ts:70 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code · Unused private field 'target' · ×1
  • Unused private field 'target' library/ProgressReporter/AdminProgressAction/js/ProgressStreamController.ts:9 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 1/5 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · PHP static analysis does not check null everywhere · ×1
  • PHP static analysis does not check null everywhere — This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
Minor — 2 finding(s)
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names Modularity/source/js/helpers/ModuleRefresher.js:20 — 1 of 1 documented parameters and 0 of 4 summaries in `@helsingborg-stad/modularity` only repeat the member or parameter name (e.g. "restAPI" for `ModulesRestAPI`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names assets/source/js/comments.ts:96 — 0 of 8 documented parameters and 4 of 37 summaries in `@helsingborg-stad/municipio` only repeat the member or parameter name (e.g. "Handle like button click." for `handleLikeButtonClick`). Delete the restating tags, or add what the name does not say.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=130" --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=330 --max-count=77" --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=407 --max-count=37" --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=444 --max-count=25" --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/history-4.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-4.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=469 --max-count=25" --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/history-5.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-5.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4c8027a836bf4cbb9e0e536f32217e85/tree.json --exit-code 0 --source .0artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .43artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .40artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—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 229 file(s) — `Modularity/source/php/Module/Posts/Helper/GetPosts/GetPosts.php`, `Modularity/source/php/Module/Posts/Helper/GetPosts/GetPostsFromMultipleSites.php`, `Modularity/source/php/Module/Posts/Helper/GetPosts/UserGroupResolver/UserGroupResolver.php`, `library/A11yStatement/A11yStatement.php`, `library/AcfFieldContentModifiers/Registrar.php`, … (+224 more) — 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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e5c2-a32a-7459-b1f5-f4add309179f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md