Public report of jsonrainbow/json-schema, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 17 November 2026, 16:27 UTC · Survey ID cd_3115c494dfa748e1a856db132222445f

jsonrainbow/json-schema

Measured 17 November 2026, 16:26 UTC, at code version c25bb4a

Knowledge freshness is not measured: Freshness signal contradicted by repo activity.

CAI score 58.2out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 0.4 since the last survey

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

A small codebase: 9,927 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Maturity, 53.6

Findings by how serious they are

25 critical 131 serious 39 minor

19 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
17 November 2026, 16:26 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 ▸

43of 43 dimensions measured by tools.
185of 195 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
43dimensions across 5 lenses, read from 9,927 lines of product code in 1 project.
Chapters

Executive summary

jsonrainbow/json-schema falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 58.2 out of 100 and is rated Adequate, and all 25 of its critical findings are security problems in the build pipeline.

Maturity, at 53.6, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5.8 points. Adding a diagnostic log is another step, worth about 3.4 points. Raising Maturity to 70 would lift the score to about 61.7.

Eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and one secret can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting the secret to its own step would close these risks.

The product code is 9,927 lines, about €20,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.
Maturity 53.6 · counts for 47%Production Readiness 54.8 · counts for 26%Code Health 63.8 · counts for 14%Security and Compliance 65.0 · counts for 8%Architecture 99.2 · counts for 4%

If Maturity rose from 53.6 to 70, the lowest score rated Strong, the score would rise from 58.2 to about 61.7.

Code composition: what the lines of code are
Product code 51%Tests 49%
New since the last survey: 14 findings

These 14 critical or serious findings weren't in the previous survey, on 5 November 2026.

  • Cyclomatic Complexity · UriResolver.resolve (cyclomatic 18) src/JsonSchema/Uri/UriResolver.php
  • Cognitive Complexity · UriResolver.resolve (cognitive 18) src/JsonSchema/Uri/UriResolver.php
  • Code Duplication · Edited copy of a member (73 corresponding lines) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php
  • Code Duplication · Edited copies of one member (3 members, 36+ corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php
  • Code Duplication · Edited copy of a member (18 corresponding lines) src/JsonSchema/Uri/UriResolver.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/JsonSchema/Constraints/TypeConstraint.php
  • Code Duplication · Edited copy of a member (12 corresponding lines) src/JsonSchema/Uri/UriResolver.php
  • Code Duplication · Edited copy of a member (13 corresponding lines) src/JsonSchema/Constraints/BaseConstraint.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php
  • Code Duplication · Edited copy of a member (5 corresponding lines) src/JsonSchema/Constraints/Constraint.php
  • Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php
  • Code Duplication · Duplicated block (17 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php
  • Churn × Complexity Hotspots · Hotspot: src/JsonSchema/Uri/UriResolver.php src/JsonSchema/Uri/UriResolver.php

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 4 findings

These 4 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one.

  • Code Duplication · Duplicated block (20 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php
  • Code Duplication · Duplicated block (19 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php
  • Code Duplication · Duplicated block (15 lines × 2) src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php
  • Code Duplication · Duplicated block (12 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php
Rebuild cost: about €20,000 · Estimate
Cost to rebuild€6,700 to €34,000, for 112 to 356 hours of work, about 0.1 person-years for one engineer
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.8 at a score of 58. 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.
SizeSmall: 9,927 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 1 No ADRs found finding(s) in ADR Quality — start with composer.json.
Raises the score by about 5.8 points · Low effort · ADR Quality
2
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.
Raises the score by about 4.8 points · Medium effort · Architecture documentation
3
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 3.4 points · Medium effort · Observability

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 €20,000 to build again, about 0.1 person-years of work. Its weakest lens is Maturity, at 53.6 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5.8 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 18% on every change. The history of the code shows how much it changes: about 4,238 lines over the last 90 days, which is about 17,187 lines a year. At that pace, the extra work comes to an estimated 3.4 to 20.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

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

13 modules, with 14 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

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 Constraints.TypeCheck2 Exception3 Iterator4 Tool5 Tool.Validator6 Uri.Retrievers7 Entity8 Constraints9 JsonSchema10 Constraints.Drafts.Draft0611 Constraints.Drafts.Draft0712 Constraints.Drafts.Draft201913 Uri
1 Constraints.TypeCheck
2 Exception
3 Iterator
4 Tool
5 Tool.Validator
6 Uri.Retrievers
7 Entity22
8 Constraints2134
9 JsonSchema1
10 Constraints.Drafts.Draft063251
11 Constraints.Drafts.Draft073454
12 Constraints.Drafts.Draft20193656
13 Uri12
Uses a module listed above itPart of a loopThe module itself
1 Constraints.TypeCheck2 Exception3 Iterator4 Tool5 Tool.Validator6 Uri.Retrievers7 Entity8 Constraints9 JsonSchema10 Constraints.Drafts.Draft0611 Constraints.Drafts.Draft0712 Constraints.Drafts.Draft201913 UriConstraints.TypeCheck1Exception2Iterator3Tool4Tool.Validator5Uri.Retrievers6Entity7Constraints8JsonSchema9Constraints.Drafts.Draft0610Constraints.Drafts.Draft0711Constraints.Drafts.Draft201912Uri13222134132513454365612

At a glance — Code Health · 63.8 · Adequate · gated by D2, D4 ·

At a glance — Architecture · 99.2 · Exemplary ·

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

At a glance — Readiness · 54.8 · Adequate · gated by P2 ·

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

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
A05:2025 — Injection25High / Critical
A03:2025 — Software Supply Chain Failures5Medium

Roadmap

Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json; 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; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json.+5.8 ptsLowADR Quality
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.+4.8 ptsMediumArchitecture documentation
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.+3.4 ptsMediumObservability
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor.+1.4 ptsLowBus Factor
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.+1.4 ptsLowBus Factor
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6).+0.9 ptsLowStatic Analysis (SAST)
Swallowed exception (caught, then discarded)+1.4 ptsMediumException handling
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with FormatConstraint.php (2), UriResolver.php.+1.1 ptsHighChurn × Complexity Hotspots

File quality

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

FileScoreBandWorst signal
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php7.0MixedCyclomatic Complexity: FormatConstraint.check (cyclomatic 51)
src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php7.0MixedCyclomatic Complexity: FormatConstraint.check (cyclomatic 40)
src/JsonSchema/Constraints/UndefinedConstraint.php7.0MixedCyclomatic Complexity: UndefinedConstraint.applyDefaultValues (cyclomatic 26)
src/JsonSchema/Uri/UriResolver.php7.1MixedCyclomatic Complexity: UriResolver.resolve (cyclomatic 18)
src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php7.1MixedCode Duplication: Edited copy of a member (46 corresponding lines)
src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php7.2MixedCyclomatic Complexity: FormatConstraint.check (cyclomatic 55)
src/JsonSchema/Constraints/TypeConstraint.php7.2MixedCyclomatic Complexity: TypeConstraint.validateType (cyclomatic 18)
src/JsonSchema/Constraints/CollectionConstraint.php7.2MixedCyclomatic Complexity: CollectionConstraint.validateItems (cyclomatic 16)
src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php7.2MixedCode Duplication: Edited copies of one member (3 members, 36+ corresponding lines)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php7.4MixedCyclomatic Complexity: PropertiesNamesConstraint.check (cyclomatic 17)

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

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

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

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

Could not be resolved — 19

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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, 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 — 43 dimensions across the health lenses
D1D2D3D4D6D10D13D15D16D17D19D20D27D28D29D35D36D37D44AX10AX3AX4AX6M1M2M3P1P10P2P3P4P6X14X16X19X21X25X27X28X29X3X30X5

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, 185 of 195 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 01a1ea55-0f13-7590-be67-d879c1c47e82.

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.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • 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 source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (9927 LoC, 159 module-visible types across 13 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 87 commits in the last 90 days, yet 20 of 35 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's , PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's , PHP 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • P7 Outbound HTTP resilience — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. No service entry point was found in the PHP source it does read, and the rest of this repository's production source is , which it does not read yet — the service may well be there — a gap in this analyzer's language reach, not a finding about the code.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 make no call through a named logger, 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.
  • 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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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").
  • 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.
  • 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.
  • 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.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

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

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

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

17 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FormatConstraint.check at 55.

PropertiesNamesConstraint.check (cyclomatic 17) · ×3src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php:25
FormatConstraint.check (cyclomatic 55)src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:31
UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cyclomatic 52)src/JsonSchema/Constraints/Drafts/Draft2019/UnevaluatedPropertiesConstraint.php:68
FormatConstraint.check (cyclomatic 51)src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:31
FormatConstraint.check (cyclomatic 43)src/JsonSchema/Constraints/FormatConstraint.php:32

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

What to do

  1. Bring the 17 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with FormatConstraint.check (cyclomatic 55), UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cyclomatic 52), FormatConstraint.check (cyclomatic 51). — 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 17 together lifts Cyclomatic Complexity from 6.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity2.9 / 10Weak✓ 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 2.9 / 10 · rule-coverage 100% · ceiling Prevented

29 method(s) exceeded the cognitive complexity threshold of 15; the worst was UnevaluatedPropertiesConstraint.collectEvaluatedProperties at 85.

PropertiesNamesConstraint.check (cognitive 27) · ×3src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php:25
AdditionalPropertiesConstraint.check (cognitive 21) · ×3src/JsonSchema/Constraints/Drafts/Draft06/AdditionalPropertiesConstraint.php:26
DependenciesConstraint.check (cognitive 24) · ×2src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:25
UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cognitive 85)src/JsonSchema/Constraints/Drafts/Draft2019/UnevaluatedPropertiesConstraint.php:68
FormatConstraint.check (cognitive 52)src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:31

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cognitive 85). — Refactoring it lifts Cognitive Complexity from 2.9 to about 4.0/10.

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

D3 · God Classes10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication0.1 / 10Critical✓ 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 0.1 / 10 · rule-coverage 100% · ceiling Verified

58 duplicated block group(s) detected. 24.7 % of the production lines (2,449 of 9,927) are in a reported copy. A further 14 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (14 lines × 3) · ×9src/JsonSchema/Constraints/Drafts/Draft06/AllOfConstraint.php:27
Duplicated block (13 lines × 3) · ×5src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:25
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3src/JsonSchema/Constraints/CollectionConstraint.php:32
Duplicated block (17 lines × 3) · ×3src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:27
Duplicated block (7 lines × 3) · ×3src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:103

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

What to do

  1. Resolve the 9 Duplicated block (14 lines × 3) finding(s) in Code Duplication — start with AllOfConstraint.php, MaxItemsConstraint.php, MaxLengthConstraint.php. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 5 Duplicated block (13 lines × 3) finding(s) in Code Duplication — start with EnumConstraint.php, ExclusiveMaximumConstraint.php, ExclusiveMinimumConstraint.php. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 3 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with CollectionConstraint.php, EnumConstraint.php, FormatConstraint.php. — One of this dimension's main actionable groups (3 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 108 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality9.8 / 10Stronggated by 3 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.8 / 10 · rule-coverage 100% · ceiling Prevented

5 skipped (5 with a documented reason), 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 225 tests.

No assertions: testCoerceCasesUsingAssoc · ×3tests/Constraints/CoerciveTest.php:232
Skipped (documented): testInvalidCasesUsingAssoc · ×5tests/Constraints/BaseTestCase.php:57
No assertions (declared): testValidateTypeNameWordingtests/Constraints/TypeTest.php:94

What to do

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

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.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.

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

Top hotspots: src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php (9×55=495); src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php (8×51=408); src/JsonSchema/Uri/UriResolver.php (2×18=36)

Hotspot: src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php · ×3src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:31

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with FormatConstraint.php (2), UriResolver.php. — One of this dimension's main actionable groups (3 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

6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php. Counted over 35 of the 161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

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

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 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 / 10Exemplary○ Nothing flagged

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

0 deducted task-comment markers across 9927 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.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. 3 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundcomposer.json:61

What to do

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

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

D27 · Navigability9.1 / 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.1 / 10 · rule-coverage 100% · ceiling Documented

30 % of calls cross a namespace and 0 % go through an interface, but 43 % 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)10.0 / 10Exemplary○ Nothing flagged

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

25 finding(s): 0 critical, 25 high, 0 medium, 0 low. 17 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. Separately, one or more rules could not re-parse an embedded snippet in 3 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

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — 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 17 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 (17 issue-level, 0 of them charged here).

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.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

What to do

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 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 segregation10.0 / 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.

M1 · Documentation (README)7.3 / 10Strong✓ 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 documentation0.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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

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.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.

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.

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

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

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

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

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

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

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

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

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

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.

X19 · Unrestored process-global state3.5 / 10Weak✓ Tool-verified

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.

  • `retrieve` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the error handler (changed at line 37, reset at line 41) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — src/JsonSchema/Uri/Retrievers/FileGetContents.php:30

What to do

  • Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a `cwd` and `env` passed to Symfony `Process` or `proc_open`, an absolute path, or an explicit `DateTimeZone`/locale/encoding argument is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move (an error handler around a call that warns), a `try`/`finally` is the least that makes the restore unconditional.
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.

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

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

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

X3 · Exception handling4.2 / 10Weak✓ 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. (×4) — src/JsonSchema/Constraints/FormatConstraint.php:159, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:183, src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:174, …

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 types9.6 / 10Exemplary✓ 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.

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 Health63.8Adequate — gated by D2, D4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture99.2ExemplaryStrongest area.
Maturity53.6Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness54.8Adequate — gated by P2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security65.0Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 1 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's 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.
  • AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
  • 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
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — Test reliability not included — no .php test runner
  • D12 Dependency Hygiene — Not scored — 1 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed PHP surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
  • 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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
  • 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
  • D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • 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
  • M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (environment variable 3); M4 checks only links and versions and artefact counts.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not 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
  • 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.
  • PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
  • 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 — 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
  • 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. Not a gap in the analyzer and not a finding about your code.
  • 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
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 25 finding(s)
D29 · Static Analysis (SAST) · 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
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 131 finding(s)
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×9
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/AllOfConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/AllOfConstraint.php:27-40 | src/JsonSchema/Constraints/Drafts/Draft07/AllOfConstraint.php:27-40 | src/JsonSchema/Constraints/Drafts/Draft2019/AllOfConstraint.php:27-40 — `src/JsonSchema/Constraints/Drafts/Draft06/AllOfConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/AllOfConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MaxItemsConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MaxItemsConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft07/MaxItemsConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft2019/MaxItemsConstraint.php:24-37 — `src/JsonSchema/Constraints/Drafts/Draft06/MaxItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MaxItemsConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MaxLengthConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MaxLengthConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft07/MaxLengthConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft2019/MaxLengthConstraint.php:24-37 — `src/JsonSchema/Constraints/Drafts/Draft06/MaxLengthConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MaxLengthConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MaxPropertiesConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MaxPropertiesConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft07/MaxPropertiesConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft2019/MaxPropertiesConstraint.php:24-37 — `src/JsonSchema/Constraints/Drafts/Draft06/MaxPropertiesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MaxPropertiesConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MinItemsConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MinItemsConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft07/MinItemsConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft2019/MinItemsConstraint.php:24-37 — `src/JsonSchema/Constraints/Drafts/Draft06/MinItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MinItemsConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MinLengthConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MinLengthConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft07/MinLengthConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft2019/MinLengthConstraint.php:24-37 — `src/JsonSchema/Constraints/Drafts/Draft06/MinLengthConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MinLengthConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MinPropertiesConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MinPropertiesConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft07/MinPropertiesConstraint.php:24-37 | src/JsonSchema/Constraints/Drafts/Draft2019/MinPropertiesConstraint.php:24-37 — `src/JsonSchema/Constraints/Drafts/Draft06/MinPropertiesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MinPropertiesConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/PatternConstraint.php:28 — src/JsonSchema/Constraints/Drafts/Draft06/PatternConstraint.php:28-41 | src/JsonSchema/Constraints/Drafts/Draft07/PatternConstraint.php:28-41 | src/JsonSchema/Constraints/Drafts/Draft2019/PatternConstraint.php:28-41 — `src/JsonSchema/Constraints/Drafts/Draft06/PatternConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/PatternConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (14 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/ConstConstraint.php:20 — src/JsonSchema/Constraints/Drafts/Draft06/ConstConstraint.php:20-33 | src/JsonSchema/Constraints/Drafts/Draft07/ConstConstraint.php:20-33 | src/JsonSchema/Constraints/Drafts/Draft2019/ConstConstraint.php:20-33 — `src/JsonSchema/Constraints/Drafts/Draft06/ConstConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/ConstConstraint.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 1 separate duplicated blocks between them, totalling at least 14 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/ConstConstraint.php:20` 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×5
  • Duplicated block (13 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:25 — src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:25-37 | src/JsonSchema/Constraints/Drafts/Draft07/EnumConstraint.php:25-37 | src/JsonSchema/Constraints/Drafts/Draft2019/EnumConstraint.php:25-37 — `src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/EnumConstraint.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 2 separate duplicated blocks between them, totalling at least 22 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 (13 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/ExclusiveMaximumConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/ExclusiveMaximumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft07/ExclusiveMaximumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft2019/ExclusiveMaximumConstraint.php:24-36 — `src/JsonSchema/Constraints/Drafts/Draft06/ExclusiveMaximumConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/ExclusiveMaximumConstraint.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 1 separate duplicated blocks between them, totalling at least 13 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 (13 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/ExclusiveMinimumConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/ExclusiveMinimumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft07/ExclusiveMinimumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft2019/ExclusiveMinimumConstraint.php:24-36 — `src/JsonSchema/Constraints/Drafts/Draft06/ExclusiveMinimumConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/ExclusiveMinimumConstraint.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 1 separate duplicated blocks between them, totalling at least 13 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 (13 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MaximumConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MaximumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft07/MaximumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft2019/MaximumConstraint.php:24-36 — `src/JsonSchema/Constraints/Drafts/Draft06/MaximumConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MaximumConstraint.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 1 separate duplicated blocks between them, totalling at least 13 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 (13 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MinimumConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MinimumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft07/MinimumConstraint.php:24-36 | src/JsonSchema/Constraints/Drafts/Draft2019/MinimumConstraint.php:24-36 — `src/JsonSchema/Constraints/Drafts/Draft06/MinimumConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MinimumConstraint.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 1 separate duplicated blocks between them, totalling at least 13 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) src/JsonSchema/Constraints/FormatConstraint.php:159 — `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) src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:183 — `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) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:174 — `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) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:135 — `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.
D1 · Cyclomatic Complexity · PropertiesNamesConstraint.check (cyclomatic 17) · ×3
  • PropertiesNamesConstraint.check (cyclomatic 17) src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php:25 — PropertiesNamesConstraint.check 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.
  • PropertiesNamesConstraint.check (cyclomatic 17) src/JsonSchema/Constraints/Drafts/Draft07/PropertiesNamesConstraint.php:25 — PropertiesNamesConstraint.check 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.
  • PropertiesNamesConstraint.check (cyclomatic 17) src/JsonSchema/Constraints/Drafts/Draft2019/PropertiesNamesConstraint.php:25 — PropertiesNamesConstraint.check 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.
D10 · Test Quality · No assertions · ×3
  • No assertions: testCoerceCasesUsingAssoc tests/Constraints/CoerciveTest.php:232 — 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: testValidCasesUsingAssoc tests/Constraints/DefaultPropertiesTest.php:195 — 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: testValidCasesUsingAssocWithoutTypeCast tests/Constraints/DefaultPropertiesTest.php:206 — 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:31 — src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in FormatConstraint.check at line 31. 6 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-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 17:41:11 +00:00' --until='2026-11-15 17:41:11 +00:00' --full-history --no-merges -- src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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: src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:31 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in FormatConstraint.check at line 31. 5 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-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 17:41:11 +00:00' --until='2026-11-15 17:41:11 +00:00' --full-history --no-merges -- src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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: src/JsonSchema/Uri/UriResolver.php src/JsonSchema/Uri/UriResolver.php:79 — src/JsonSchema/Uri/UriResolver.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in UriResolver.resolve at line 79. 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-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 17:41:11 +00:00' --until='2026-11-15 17:41:11 +00:00' --full-history --no-merges -- src/JsonSchema/Uri/UriResolver.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.
D2 · Cognitive Complexity · PropertiesNamesConstraint.check (cognitive 27) · ×3
  • PropertiesNamesConstraint.check (cognitive 27) src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php:25 — PropertiesNamesConstraint.check has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (10 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.
  • PropertiesNamesConstraint.check (cognitive 27) src/JsonSchema/Constraints/Drafts/Draft07/PropertiesNamesConstraint.php:25 — PropertiesNamesConstraint.check has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (10 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.
  • PropertiesNamesConstraint.check (cognitive 27) src/JsonSchema/Constraints/Drafts/Draft2019/PropertiesNamesConstraint.php:25 — PropertiesNamesConstraint.check has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (10 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 · AdditionalPropertiesConstraint.check (cognitive 21) · ×3
  • AdditionalPropertiesConstraint.check (cognitive 21) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalPropertiesConstraint.php:26 — AdditionalPropertiesConstraint.check has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (8 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.
  • AdditionalPropertiesConstraint.check (cognitive 21) src/JsonSchema/Constraints/Drafts/Draft07/AdditionalPropertiesConstraint.php:26 — AdditionalPropertiesConstraint.check has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (8 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.
  • AdditionalPropertiesConstraint.check (cognitive 21) src/JsonSchema/Constraints/Drafts/Draft2019/AdditionalPropertiesConstraint.php:26 — AdditionalPropertiesConstraint.check has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (8 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/JsonSchema/Constraints/CollectionConstraint.php:32 — src/JsonSchema/Constraints/CollectionConstraint.php:32-54 | src/JsonSchema/Constraints/Drafts/Draft06/UniqueItemsConstraint.php:25-46 | src/JsonSchema/Constraints/Drafts/Draft07/UniqueItemsConstraint.php:25-46 | src/JsonSchema/Constraints/Drafts/Draft2019/UniqueItemsConstraint.php:25-46 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:25 — src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:25-39 | src/JsonSchema/Constraints/Drafts/Draft07/EnumConstraint.php:25-39 | src/JsonSchema/Constraints/Drafts/Draft2019/EnumConstraint.php:25-39 | src/JsonSchema/Constraints/EnumConstraint.php:32-57 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:32 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:32-128 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:33-153 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:33-162 | src/JsonSchema/Constraints/FormatConstraint.php:34-152 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×3
  • Duplicated block (17 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:27-43 | src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.php:27-43 | src/JsonSchema/Constraints/Drafts/Draft2019/AdditionalItemsConstraint.php:27-43 — `src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.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 3 separate duplicated blocks between them, totalling at least 55 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 (17 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:227 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:227-243 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:450-466 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:455-471 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:227` 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 (17 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php:24-40 | src/JsonSchema/Constraints/Drafts/Draft07/MultipleOfConstraint.php:24-40 | src/JsonSchema/Constraints/Drafts/Draft2019/MultipleOfConstraint.php:24-40 — `src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/MultipleOfConstraint.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 1 separate duplicated blocks between them, totalling at least 17 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×3
  • Duplicated block (7 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:103 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:103-110 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:118-125 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:123-129 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 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 (7 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:108 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:108-115 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:123-130 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:133-139 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 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 (7 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:161 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:161-167 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:230-236 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:239-245 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:161` 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.
D2 · Cognitive Complexity · DependenciesConstraint.check (cognitive 24) · ×2
  • DependenciesConstraint.check (cognitive 24) src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:25 — DependenciesConstraint.check has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • DependenciesConstraint.check (cognitive 24) src/JsonSchema/Constraints/Drafts/Draft07/DependenciesConstraint.php:25 — DependenciesConstraint.check has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) src/JsonSchema/Constraints/TypeConstraint.php:273 — src/JsonSchema/Constraints/TypeConstraint.php:273-283 | src/JsonSchema/Constraints/TypeConstraint.php:328-344 — 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) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:133 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:133-143 | src/JsonSchema/Constraints/FormatConstraint.php:157-171 — 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 · Duplicated block (27 lines × 3) · ×2
  • Duplicated block (27 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/ItemsConstraint.php:26 — src/JsonSchema/Constraints/Drafts/Draft06/ItemsConstraint.php:26-52 | src/JsonSchema/Constraints/Drafts/Draft07/ItemsConstraint.php:26-52 | src/JsonSchema/Constraints/Drafts/Draft2019/ItemsConstraint.php:26-52 — `src/JsonSchema/Constraints/Drafts/Draft06/ItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/ItemsConstraint.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 1 separate duplicated blocks between them, totalling at least 27 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 (27 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/PatternPropertiesConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/PatternPropertiesConstraint.php:27-53 | src/JsonSchema/Constraints/Drafts/Draft07/PatternPropertiesConstraint.php:27-53 | src/JsonSchema/Constraints/Drafts/Draft2019/PatternPropertiesConstraint.php:27-53 — `src/JsonSchema/Constraints/Drafts/Draft06/PatternPropertiesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/PatternPropertiesConstraint.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 1 separate duplicated blocks between them, totalling at least 27 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.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×2
  • Duplicated block (22 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/AnyOfConstraint.php:28 — src/JsonSchema/Constraints/Drafts/Draft06/AnyOfConstraint.php:28-49 | src/JsonSchema/Constraints/Drafts/Draft07/AnyOfConstraint.php:28-49 | src/JsonSchema/Constraints/Drafts/Draft2019/AnyOfConstraint.php:28-49 — `src/JsonSchema/Constraints/Drafts/Draft06/AnyOfConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/AnyOfConstraint.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 1 separate duplicated blocks between them, totalling at least 22 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 (22 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/OneOfConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/OneOfConstraint.php:27-48 | src/JsonSchema/Constraints/Drafts/Draft07/OneOfConstraint.php:27-48 | src/JsonSchema/Constraints/Drafts/Draft2019/OneOfConstraint.php:27-48 — `src/JsonSchema/Constraints/Drafts/Draft06/OneOfConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/OneOfConstraint.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 1 separate duplicated blocks between them, totalling at least 22 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.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×2
  • Duplicated block (16 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/RefConstraint.php:26 — src/JsonSchema/Constraints/Drafts/Draft06/RefConstraint.php:26-41 | src/JsonSchema/Constraints/Drafts/Draft07/RefConstraint.php:26-41 | src/JsonSchema/Constraints/Drafts/Draft2019/RefConstraint.php:26-41 — `src/JsonSchema/Constraints/Drafts/Draft06/RefConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/RefConstraint.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 1 separate duplicated blocks between them, totalling at least 16 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 (16 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:193 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:193-208 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:374-389 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:379-394 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:36 — src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:36-45 | src/JsonSchema/Constraints/Drafts/Draft07/DependenciesConstraint.php:36-45 | src/JsonSchema/Constraints/Drafts/Draft2019/DependentSchemasConstraint.php:36-47 — `src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/DependenciesConstraint.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 2 separate duplicated blocks between them, totalling at least 48 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 (10 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:112 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:112-121 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:132-141 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:141-150 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:112` 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.
D1 · Cyclomatic Complexity · FormatConstraint.check (cyclomatic 55) · ×1
  • FormatConstraint.check (cyclomatic 55) src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:31 — FormatConstraint.check has cyclomatic complexity 55 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cyclomatic 52) · ×1
  • UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cyclomatic 52) src/JsonSchema/Constraints/Drafts/Draft2019/UnevaluatedPropertiesConstraint.php:68 — UnevaluatedPropertiesConstraint.collectEvaluatedProperties has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FormatConstraint.check (cyclomatic 51) · ×1
  • FormatConstraint.check (cyclomatic 51) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:31 — FormatConstraint.check has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FormatConstraint.check (cyclomatic 43) · ×1
  • FormatConstraint.check (cyclomatic 43) src/JsonSchema/Constraints/FormatConstraint.php:32 — FormatConstraint.check has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FormatConstraint.check (cyclomatic 40) · ×1
  • FormatConstraint.check (cyclomatic 40) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:30 — FormatConstraint.check has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · UndefinedConstraint.applyDefaultValues (cyclomatic 26) · ×1
  • UndefinedConstraint.applyDefaultValues (cyclomatic 26) src/JsonSchema/Constraints/UndefinedConstraint.php:235 — UndefinedConstraint.applyDefaultValues 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 · UndefinedConstraint.validateCommonProperties (cyclomatic 24) · ×1
  • UndefinedConstraint.validateCommonProperties (cyclomatic 24) src/JsonSchema/Constraints/UndefinedConstraint.php:106 — UndefinedConstraint.validateCommonProperties 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 · FormatConstraint.validateInternationalizedHostname (cyclomatic 19) · ×1
  • FormatConstraint.validateInternationalizedHostname (cyclomatic 19) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:290 — FormatConstraint.validateInternationalizedHostname 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 · NumberConstraint.check (cyclomatic 19) · ×1
  • NumberConstraint.check (cyclomatic 19) src/JsonSchema/Constraints/NumberConstraint.php:28 — NumberConstraint.check 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 · FormatConstraint.validateInternationalizedHostname (cyclomatic 18) · ×1
  • FormatConstraint.validateInternationalizedHostname (cyclomatic 18) src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:299 — FormatConstraint.validateInternationalizedHostname 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 · TypeConstraint.validateType (cyclomatic 18) · ×1
  • TypeConstraint.validateType (cyclomatic 18) src/JsonSchema/Constraints/TypeConstraint.php:176 — TypeConstraint.validateType 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 · UndefinedConstraint.validateOfProperties (cyclomatic 18) · ×1
  • UndefinedConstraint.validateOfProperties (cyclomatic 18) src/JsonSchema/Constraints/UndefinedConstraint.php:313 — UndefinedConstraint.validateOfProperties 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 · UriResolver.resolve (cyclomatic 18) · ×1
  • UriResolver.resolve (cyclomatic 18) src/JsonSchema/Uri/UriResolver.php:79 — UriResolver.resolve 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 · CollectionConstraint.validateItems (cyclomatic 16) · ×1
  • CollectionConstraint.validateItems (cyclomatic 16) src/JsonSchema/Constraints/CollectionConstraint.php:64 — CollectionConstraint.validateItems has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cognitive 85) · ×1
  • UnevaluatedPropertiesConstraint.collectEvaluatedProperties (cognitive 85) src/JsonSchema/Constraints/Drafts/Draft2019/UnevaluatedPropertiesConstraint.php:68 — UnevaluatedPropertiesConstraint.collectEvaluatedProperties has cognitive complexity 85 (threshold 15). Drivers by points: if/else 24 (50 pts), boolean chains 17, loops 7 (16 pts), error handling 1 (2 pts) (nesting depth added 36). To reduce it, split the body into named stages: move each independent 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 · FormatConstraint.check (cognitive 52) · ×1
  • FormatConstraint.check (cognitive 52) src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:31 — FormatConstraint.check has cognitive complexity 52 (threshold 15). Drivers by points: if/else 24 (46 pts), boolean chains 5, match/switch 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FormatConstraint.check (cognitive 48) · ×1
  • FormatConstraint.check (cognitive 48) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:31 — FormatConstraint.check has cognitive complexity 48 (threshold 15). Drivers by points: if/else 22 (42 pts), boolean chains 5, match/switch 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UndefinedConstraint.validateCommonProperties (cognitive 42) · ×1
  • UndefinedConstraint.validateCommonProperties (cognitive 42) src/JsonSchema/Constraints/UndefinedConstraint.php:106 — UndefinedConstraint.validateCommonProperties has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (31 pts), loops 2 (6 pts), boolean chains 5 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UndefinedConstraint.applyDefaultValues (cognitive 42) · ×1
  • UndefinedConstraint.applyDefaultValues (cognitive 42) src/JsonSchema/Constraints/UndefinedConstraint.php:235 — UndefinedConstraint.applyDefaultValues has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 9, loops 2 (4 pts), 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 · FormatConstraint.check (cognitive 40) · ×1
  • FormatConstraint.check (cognitive 40) src/JsonSchema/Constraints/FormatConstraint.php:32 — FormatConstraint.check has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 10, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CollectionConstraint.validateItems (cognitive 39) · ×1
  • CollectionConstraint.validateItems (cognitive 39) src/JsonSchema/Constraints/CollectionConstraint.php:64 — CollectionConstraint.validateItems has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (29 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 19). 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 · FormatConstraint.check (cognitive 37) · ×1
  • FormatConstraint.check (cognitive 37) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:30 — FormatConstraint.check has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (34 pts), boolean chains 2, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UndefinedConstraint.validateOfProperties (cognitive 37) · ×1
  • UndefinedConstraint.validateOfProperties (cognitive 37) src/JsonSchema/Constraints/UndefinedConstraint.php:313 — UndefinedConstraint.validateOfProperties has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (18 pts), error handling 2 (6 pts), loops 3 (6 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FormatConstraint.validateInternationalizedHostname (cognitive 28) · ×1
  • FormatConstraint.validateInternationalizedHostname (cognitive 28) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:290 — FormatConstraint.validateInternationalizedHostname has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FormatConstraint.validateInternationalizedHostname (cognitive 27) · ×1
  • FormatConstraint.validateInternationalizedHostname (cognitive 27) src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:299 — FormatConstraint.validateInternationalizedHostname has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TypeConstraint.validateType (cognitive 23) · ×1
  • TypeConstraint.validateType (cognitive 23) src/JsonSchema/Constraints/TypeConstraint.php:176 — TypeConstraint.validateType has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (21 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 · NumberConstraint.check (cognitive 22) · ×1
  • NumberConstraint.check (cognitive 22) src/JsonSchema/Constraints/NumberConstraint.php:28 — NumberConstraint.check has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6 (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 · ObjectConstraint.validateElement (cognitive 22) · ×1
  • ObjectConstraint.validateElement (cognitive 22) src/JsonSchema/Constraints/ObjectConstraint.php:84 — ObjectConstraint.validateElement has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EcmaPatternConverter.toPcre (cognitive 22) · ×1
  • EcmaPatternConverter.toPcre (cognitive 22) src/JsonSchema/Tool/EcmaPatternConverter.php:39 — EcmaPatternConverter.toPcre has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (4 pts), ternaries 1 (4 pts), boolean chains 3 (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 · UndefinedConstraint.validateDependencies (cognitive 19) · ×1
  • UndefinedConstraint.validateDependencies (cognitive 19) src/JsonSchema/Constraints/UndefinedConstraint.php:396 — UndefinedConstraint.validateDependencies has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (5 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 · SchemaConstraint.check (cognitive 18) · ×1
  • SchemaConstraint.check (cognitive 18) src/JsonSchema/Constraints/SchemaConstraint.php:35 — SchemaConstraint.check has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UriValidator.isValid (cognitive 18) · ×1
  • UriValidator.isValid (cognitive 18) src/JsonSchema/Tool/Validator/UriValidator.php:9 — UriValidator.isValid has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UriResolver.resolve (cognitive 18) · ×1
  • UriResolver.resolve (cognitive 18) src/JsonSchema/Uri/UriResolver.php:79 — UriResolver.resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8 (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 · EnumConstraint.check (cognitive 16) · ×1
  • EnumConstraint.check (cognitive 16) src/JsonSchema/Constraints/EnumConstraint.php:29 — EnumConstraint.check has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (7 pts), loops 1 (nesting depth added 3). 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 · TypeConstraint.check (cognitive 16) · ×1
  • TypeConstraint.check (cognitive 16) src/JsonSchema/Constraints/TypeConstraint.php:45 — TypeConstraint.check has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:26 — src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:26-71 | src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php:26-73 — These two members are one piece of code written twice and then edited apart: 46 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 (73 corresponding lines) · ×1
  • Edited copy of a member (73 corresponding lines) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:292 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:292-368 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:301-373 — These two members are one piece of code written twice and then edited apart: 73 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, 36+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 36+ corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:27-62 | src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.php:27-62 | src/JsonSchema/Constraints/Drafts/Draft2019/AdditionalItemsConstraint.php:27-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 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 (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) src/JsonSchema/Uri/UriResolver.php:33 — src/JsonSchema/Uri/UriResolver.php:33-50 | src/JsonSchema/Uri/UriRetriever.php:256-275 — These two members are one piece of code written twice and then edited apart: 18 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) · ×1
  • Edited copy of a member (12 corresponding lines) src/JsonSchema/Uri/UriResolver.php:62 — src/JsonSchema/Uri/UriResolver.php:62-73 | src/JsonSchema/Uri/UriRetriever.php:287-299 — 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 (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) src/JsonSchema/Constraints/BaseConstraint.php:72 — src/JsonSchema/Constraints/BaseConstraint.php:72-84 | src/JsonSchema/Entity/ErrorBag.php:87-99 — 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 copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:81 — src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:81-84 | src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php:83-86 | src/JsonSchema/Constraints/Drafts/Draft2019/Draft2019Constraint.php:80-83 — 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 (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) src/JsonSchema/Constraints/Constraint.php:35 — src/JsonSchema/Constraints/Constraint.php:35-46 | src/JsonSchema/Entity/JsonPointer.php:142-146 — 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 · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:172 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:172-175 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:241-244 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:250-253 | src/JsonSchema/Constraints/FormatConstraint.php:200-203 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (66 lines × 2) · ×1
  • Duplicated block (66 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:303 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:303-368 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:308-373 — `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 16 separate duplicated blocks between them, totalling at least 357 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.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:158 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:158-212 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:167-221 — `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 16 separate duplicated blocks between them, totalling at least 357 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:158` 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 (49 lines × 3) · ×1
  • Duplicated block (49 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalPropertiesConstraint.php:28 — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalPropertiesConstraint.php:28-76 | src/JsonSchema/Constraints/Drafts/Draft07/AdditionalPropertiesConstraint.php:28-76 | src/JsonSchema/Constraints/Drafts/Draft2019/AdditionalPropertiesConstraint.php:28-76 — `src/JsonSchema/Constraints/Drafts/Draft06/AdditionalPropertiesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/AdditionalPropertiesConstraint.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 1 separate duplicated blocks between them, totalling at least 49 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/IfThenElseConstraint.php:26 — src/JsonSchema/Constraints/Drafts/Draft07/IfThenElseConstraint.php:26-65 | src/JsonSchema/Constraints/Drafts/Draft2019/IfThenElseConstraint.php:26-65 — `src/JsonSchema/Constraints/Drafts/Draft07/IfThenElseConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/IfThenElseConstraint.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 1 separate duplicated blocks between them, totalling at least 40 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.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:27-62 | src/JsonSchema/Constraints/Drafts/Draft07/DependenciesConstraint.php:27-62 — `src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/DependenciesConstraint.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 2 separate duplicated blocks between them, totalling at least 48 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.
D4 · Code Duplication · Duplicated block (52 lines × 3) · ×1
  • Duplicated block (52 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php:27-78 | src/JsonSchema/Constraints/Drafts/Draft07/PropertiesNamesConstraint.php:27-78 | src/JsonSchema/Constraints/Drafts/Draft2019/PropertiesNamesConstraint.php:27-78 — `src/JsonSchema/Constraints/Drafts/Draft06/PropertiesNamesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/PropertiesNamesConstraint.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 1 separate duplicated blocks between them, totalling at least 52 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.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) src/JsonSchema/Constraints/BaseConstraint.php:43 — src/JsonSchema/Constraints/BaseConstraint.php:43-67 | src/JsonSchema/Entity/ErrorBag.php:56-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.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php:24-48 | src/JsonSchema/Constraints/Drafts/Draft07/TypeConstraint.php:24-48 | src/JsonSchema/Constraints/Drafts/Draft2019/TypeConstraint.php:24-48 — `src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/TypeConstraint.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 1 separate duplicated blocks between them, totalling at least 25 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.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:123 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:123-147 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:133-156 — `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 16 separate duplicated blocks between them, totalling at least 357 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:123` 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 (17–24 lines × 4) · ×1
  • Duplicated block (17–24 lines × 4) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:76 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:76-92 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:81-97 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:86-102 | src/JsonSchema/Constraints/FormatConstraint.php:82-105 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/FormatConstraint.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.
D4 · Code Duplication · Duplicated block (24 lines × 3) · ×1
  • Duplicated block (24 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/PropertiesConstraint.php:26 — src/JsonSchema/Constraints/Drafts/Draft06/PropertiesConstraint.php:26-49 | src/JsonSchema/Constraints/Drafts/Draft07/PropertiesConstraint.php:26-49 | src/JsonSchema/Constraints/Drafts/Draft2019/PropertiesConstraint.php:26-49 — `src/JsonSchema/Constraints/Drafts/Draft06/PropertiesConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/PropertiesConstraint.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 1 separate duplicated blocks between them, totalling at least 24 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:103 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:103-125 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:108-129 — `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 16 separate duplicated blocks between them, totalling at least 357 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:103` 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 (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:265 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:265-287 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:274-296 — `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 16 separate duplicated blocks between them, totalling at least 357 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.
D4 · Code Duplication · Duplicated block (4–22 lines × 4) · ×1
  • Duplicated block (4–22 lines × 4) src/JsonSchema/Constraints/CollectionConstraint.php:43 — src/JsonSchema/Constraints/CollectionConstraint.php:43-46 | src/JsonSchema/Constraints/Drafts/Draft06/UniqueItemsConstraint.php:25-46 | src/JsonSchema/Constraints/Drafts/Draft07/UniqueItemsConstraint.php:25-46 | src/JsonSchema/Constraints/Drafts/Draft2019/UniqueItemsConstraint.php:25-46 — `src/JsonSchema/Constraints/Drafts/Draft06/UniqueItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/UniqueItemsConstraint.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 1 separate duplicated blocks between them, totalling at least 22 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/CollectionConstraint.php:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/JsonSchema/Constraints/CollectionConstraint.php:46` calls `isEqual`, `addError`, `UNIQUE_ITEMS` and `src/JsonSchema/Constraints/Drafts/Draft06/UniqueItemsConstraint.php:46` 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:32 — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:32-51 | src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.php:32-51 — `src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.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 3 separate duplicated blocks between them, totalling at least 55 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/JsonSchema/Constraints/Drafts/Draft06/ContainsConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/ContainsConstraint.php:27-45 | src/JsonSchema/Constraints/Drafts/Draft07/ContainsConstraint.php:27-45 — `src/JsonSchema/Constraints/Drafts/Draft06/ContainsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/ContainsConstraint.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 1 separate duplicated blocks between them, totalling at least 19 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.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:410 — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:410-442 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:415-447 — `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 16 separate duplicated blocks between them, totalling at least 357 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:410` 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.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:45 — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:45-62 | src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.php:45-62 | src/JsonSchema/Constraints/Drafts/Draft2019/AdditionalItemsConstraint.php:45-62 — `src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.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 3 separate duplicated blocks between them, totalling at least 55 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:45` 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 (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:26 — src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:26-43 | src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php:26-43 — before extracting anything, compare `src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 (16–18 lines × 2) · ×1
  • Duplicated block (16–18 lines × 2) src/JsonSchema/Uri/UriResolver.php:35 — src/JsonSchema/Uri/UriResolver.php:35-50 | src/JsonSchema/Uri/UriRetriever.php:258-275 — 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 (15–16 lines × 3) · ×1
  • Duplicated block (15–16 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:32 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:32-46 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:33-48 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:33-48 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (4–15 lines × 4) · ×1
  • Duplicated block (4–15 lines × 4) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:48 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:48-61 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:52-66 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:52-66 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:70-73 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:67` calls `validateRegex` and `src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:73` 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.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/RequiredConstraint.php:24 — src/JsonSchema/Constraints/Drafts/Draft06/RequiredConstraint.php:24-38 | src/JsonSchema/Constraints/Drafts/Draft07/RequiredConstraint.php:24-38 | src/JsonSchema/Constraints/Drafts/Draft2019/RequiredConstraint.php:24-38 — `src/JsonSchema/Constraints/Drafts/Draft06/RequiredConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/RequiredConstraint.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 1 separate duplicated blocks between them, totalling at least 15 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/NotConstraint.php:27 — src/JsonSchema/Constraints/Drafts/Draft06/NotConstraint.php:27-38 | src/JsonSchema/Constraints/Drafts/Draft07/NotConstraint.php:27-38 | src/JsonSchema/Constraints/Drafts/Draft2019/NotConstraint.php:27-38 — `src/JsonSchema/Constraints/Drafts/Draft06/NotConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/NotConstraint.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 1 separate duplicated blocks between them, totalling at least 12 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:118 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:118-128 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:143-153 | src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php:152-162 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:118` 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 (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:103 — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:103-113 | src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:118-128 — `src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.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 11 separate duplicated blocks between them, totalling at least 143 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:31 — src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:31-39 | src/JsonSchema/Constraints/Drafts/Draft07/EnumConstraint.php:31-39 | src/JsonSchema/Constraints/Drafts/Draft2019/EnumConstraint.php:31-39 | src/JsonSchema/Constraints/EnumConstraint.php:49-57 — `src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/EnumConstraint.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 2 separate duplicated blocks between them, totalling at least 22 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:31` 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 (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:38 — src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:38-43 | src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php:38-43 | src/JsonSchema/Constraints/Drafts/Draft2019/Draft2019Constraint.php:31-37 — before extracting anything, compare `src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 `src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:38` 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 (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) src/JsonSchema/Constraints/BaseConstraint.php:165 — src/JsonSchema/Constraints/BaseConstraint.php:165-172 | src/JsonSchema/Entity/ErrorBag.php:104-111 — 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 (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:17 — src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php:17-21 | src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php:17-21 | src/JsonSchema/Constraints/Drafts/Draft2019/Draft2019Constraint.php:17-21 — before extracting anything, compare `src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php` and `src/JsonSchema/Constraints/Drafts/Draft07/Draft07Constraint.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
X19 · Unrestored process-global state · Process-global state is restored only on the happy path · ×1
  • Process-global state is restored only on the happy path src/JsonSchema/Uri/Retrievers/FileGetContents.php:30 — `retrieve` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the error handler (changed at line 37, reset at line 41) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
Minor — 33 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×24
  • Duplicated predicate src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:32 — `!property_exists($schema, 'format') || $this` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/ConstConstraint.php:31 — `$element instanceof UndefinedConstraint && (!isset($schema->required) || !$schema->required)` appears character-identically in 2 files — src/JsonSchema/Constraints/ConstConstraint.php, src/JsonSchema/Constraints/EnumConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:190 — `$format === 'H:i:s.up' || $format === 'H:i:s.uP'` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:184 — `$timezoneOffset >= 86400 || $timezoneOffset <= -86400` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php:33 — `$valueIsNumber && fmod($value, 1.0) === 0.0` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/TypeConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/TypeConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php:31 — `$valueType === 'double' || $valueType === 'integer'` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/TypeConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/TypeConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/TypeConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php:28 — `(!is_int($schema->multipleOf) && !is_float($schema->multipleOf)) || $schema` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/MultipleOfConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/MultipleOfConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php:52 — `-$precision < $modulus && $modulus < $precision` appears character-identically in 4 files — src/JsonSchema/Constraints/Drafts/Draft06/MultipleOfConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/MultipleOfConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/MultipleOfConstraint.php, src/JsonSchema/Constraints/NumberConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:159 — `PHP_VERSION_ID < 80000 && substr($datetime, -1) === 'Z'` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php:100 — `UriValidator::isValid($value) || RelativeReferenceValidator::isValid($value)` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:34 — `additionalItems === false && !property_exists($schema, 'items')` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/AdditionalItemsConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php:34 — `is_numeric($value) && is_numeric($enumCase) && DeepComparer::isEqual((float) $value, (float) $enumCase)` appears character-identically in 3 files — src/JsonSchema/Constraints/Drafts/Draft06/EnumConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/EnumConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/EnumConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:438 — `isset($matches['ipLiteral']) && $matches['ipLiteral'] !== ''` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/CollectionConstraint.php:32 — `isset($schema->minItems) && count($value) < $schema` appears character-identically in 2 files — src/JsonSchema/Constraints/CollectionConstraint.php, src/JsonSchema/Constraints/UndefinedConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:318 — `preg_match('/[\x{05F3}\x{05F4}]/u', $label) && !preg_match('/[\x{0590}-\x{05FF}][\x{05F3}\x{05F4}]/u', $label)` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:339 — `preg_match('/[\x{0964}\x{0965}]/u', $label) && !preg_match('/[\x{0900}-\x{097F}]/u', $label)` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:311 — `preg_match('/\x{0375}/u', $label) && !preg_match('/\x{0375}[\x{0370}-\x{03FF}]/u', $label)` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php:44 — `property_exists($schema, 'items') && is_object($schema->items)` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft06/AdditionalItemsConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/AdditionalItemsConstraint.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 src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php:49 — `property_exists($value, $dependant) && !property_exists($value, $dependency)` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft06/DependenciesConstraint.php, src/JsonSchema/Constraints/Drafts/Draft07/DependenciesConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:325 — `str_contains($label, "\u{30FB}") && !preg_match('/[\x{30A0}-\x{30FF}]/u', $label)` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:278 — `strlen($localPart) > 64 || preg_match('/^(?:' . $dotString . '|' . $quotedString . ')\z/u', $localPart) !== 1` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:50 — `validateDateTime($value, 'H:i:s.up') && !$this` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:48 — `validateDateTime($value, 'H:i:sP') && !$this` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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 src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php:49 — `validateDateTime($value, 'H:i:sp') && !$this` appears character-identically in 2 files — src/JsonSchema/Constraints/Drafts/Draft07/FormatConstraint.php, src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.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.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: src/JsonSchema/Constraints/Drafts/Draft2019/FormatConstraint.php, src/JsonSchema/SchemaStorage.php. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (6 single-owned of 35 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; 35 of the 161 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (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: src/JsonSchema/Constraints/Drafts/Draft06/Draft06Constraint.php, src/JsonSchema/Entity/ErrorBag.php, src/JsonSchema/Constraints/Drafts/Draft2019/UnevaluatedPropertiesConstraint.php, bin/validate-json.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found composer.json:61 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `composer.json` makes this repository a deployable product (line 61).
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
Minor — 6 finding(s)
D10 · Test Quality · Skipped (documented) · ×5
  • Skipped (documented): testInvalidCasesUsingAssoc tests/Constraints/BaseTestCase.php:57 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testValidCasesUsingAssoc tests/Constraints/BaseTestCase.php:118 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testErrorInfiniteOrNotANumberMessage tests/Exception/JsonDecodingExceptionTest.php:62 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testErrorRecursionMessage tests/Exception/JsonDecodingExceptionTest.php:72 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testErrorUnsupportedTypeMessage tests/Exception/JsonDecodingExceptionTest.php:82 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
D10 · Test Quality · No assertions (declared) · ×1
  • No assertions (declared): testValidateTypeNameWording tests/Constraints/TypeTest.php:94 — This test performs no assertions and its author said so, with the test framework's own declaration for exactly that (PHPUnit `#[DoesNotPerformAssertions]`, which switches off PHPUnit's "This test did not perform any assertions" warning). It is reported for visibility and is NOT counted against this dimension's score: D10 looks for tests that verify nothing unintentionally. Worth a read anyway — such a test passes as long as the code under it does not throw, so if it was meant to check something, the declaration is now hiding that it does not.

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-383a9d8bedca4b9ea398cdf14e2f369e/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=738" --report-format json --report-path /tmp/watchdog-gitleaks-383a9d8bedca4b9ea398cdf14e2f369e/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.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-383a9d8bedca4b9ea398cdf14e2f369e/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 .25artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).0—
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.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 Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).0—

Run 01a1ea55-0f13-7590-be67-d879c1c47e82 · 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