playframework/playframework

Executive summary

playframework/playframework scores 49 out of 100 and is rated Weak, while five of its seven lenses score higher still: Performance at 80, rated Strong, and Architecture at 75, Production Readiness at 69, Code Health at 57 and Maturity at 50, all rated Adequate.

The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 44 and is rated Weak. Its Web-Security Posture dimension scores 2 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off and to resolve the 1 No ADRs found finding(s) in ADR Quality, and if Security and Compliance rose to 70, the score would rise from 49 to about 54.

41 findings are critical: 27 in Static Analysis (SAST), six in Knowledge Freshness, three in Forms & labels, three in Page structure and two in Web-Security Posture.

Watchdog couldn't measure 14 dimensions in this code, among them Code Coverage, Test Reliability and Dependency Hygiene, so they are left out of the score. The product code is 119,629 lines, which would take an estimated 1.2 person-years, around €180,000, to rebuild.

Code Health 57 Adequate, capped by Nullable reference types Architecture 75 Adequate, capped by Project Cohesion Maturity 50 Adequate, capped by Architecture documentation Production Readiness 69 Adequate Security and Compliance 44 Weak, capped by Static Analysis (SAST), Supply-chain Provenance & Signing and Web-Security Posture Accessibility 49 Weak Performance 80 Strong

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.

Security and Compliance 44 · counts for 46%Accessibility 49 · counts for 25%Maturity 50 · counts for 14%Code Health 57 · counts for 8%Production Readiness 69 · counts for 4%Architecture 75 · counts for 2%Performance 80 · counts for 1%

If Security and Compliance rose from 44 to 70, the lowest score rated Strong, the score would rise from 49 to about 54.

Code composition: what the lines of code are

Product code 61%Tests 39%

New since the last survey: 13 findings

These 13 critical or serious findings weren't in the previous survey, on 9 October 2026.

Cyclomatic Complexity · GuiceableModuleConversions.guice (cyclomatic 16) core/play-guice/src/main/scala/play/api/inject/guice/GuiceInjectorBuilder.scala
Cognitive Complexity · GuiceableModuleConversions.guice (cognitive 17) core/play-guice/src/main/scala/play/api/inject/guice/GuiceInjectorBuilder.scala
Knowledge Freshness · Orphaned knowledge core/play-java/src/main/java/play/libs/Time.java
Knowledge Freshness · Orphaned knowledge core/play/src/main/scala/play/api/data/Forms.scala
Knowledge Freshness · Orphaned knowledge core/play/src/main/java/play/Logger.java
Knowledge Freshness · Orphaned knowledge core/play/src/main/scala/play/api/mvc/Cookie.scala
Knowledge Freshness · Orphaned knowledge web/play-java-forms/src/main/java/play/data/validation/Constraints.java
Knowledge Freshness · Orphaned knowledge core/play/src/main/java/play/mvc/Result.java
Web-Security Posture · TLS certificate validation disabled transport/server/play-server/src/main/scala/play/core/server/ssl/DefaultSSLEngineProvider.scala
Web-Security Posture · Weak hash algorithm core/play/src/main/scala/play/api/libs/Codecs.scala
Stateful singletons · Stateful singleton: InstanceController dev-mode/sbt-plugin/src/sbt-test/play-sbt-plugin/routes-compiler-routes-compilation/app/controllers/InstanceController.scala
Visual & motion safety · Focus outline removed in CSS without a :focus replacement documentation/style/main.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement documentation/style/main.css

Watchdog compares 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: 3 findings

These 3 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.

Churn × Complexity Hotspots · Hotspot: transport/server/play-server/src/main/scala/play/core/server/common/ForwardedHeaderHandler.scala transport/server/play-server/src/main/scala/play/core/server/common/ForwardedHeaderHandler.scala
Churn × Complexity Hotspots · Hotspot: transport/server/play-netty-server/src/main/scala/play/core/server/netty/PlayRequestHandler.scala transport/server/play-netty-server/src/main/scala/play/core/server/netty/PlayRequestHandler.scala
Stateful singletons · Stateful singleton: InstanceController dev-mode/sbt-plugin/src/sbt-test/play-sbt-plugin/routes-compiler-injected-routes-compilation/app/controllers/InstanceController.scala

Rebuild cost: about €180,000 · Estimate

Cost to rebuild	€60,000 to €300,000, for 1,006 to 3,192 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Large: 119,629 lines of product code

How the estimate is made: Watchdog prices 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.

This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:138` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `trustAllManager`)), `transport/server/play-server/src/main/scala/play/core/server/ssl/DefaultSSLEngineProvider.scala:96` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain). Each is a separate decision — fixing only the line this row cites leaves the others in place.

Raises the score by about 5 points · Medium effort · Web-Security Posture

Resolve the 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 2 points · Low effort · ADR Quality

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.

Raises the score by about 2 points · Low effort · Supply-chain Provenance & Signing

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 €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Security and Compliance, at 44 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.

Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts

What to do: Start with the Security and Compliance actions in Top priorities.

If you do one thing first · First action

Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

Architecture: 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.

429 modules, with 853 dependencies between them. 2 loops run through 53 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 play.api.libs.Files	2 play.api.libs.ws	3 play.core.parsers.Multipart.BodyPartParser	4 play.core.server.common.WebSocketFlowHandler	5 controllers.b	6 play.api.inject	7 play.api.libs.typedmap	8 play.api.routing	9 play.api.i18n	10 play.api.libs.streams	11 play.api.mvc.request	12 play.core	13 play.inject	14 play.api.ApplicationLoader	15 play.api.data	16 play.filters.cors	17 play.i18n	18 play.mvc	19 play.filters.csp	20 play.filters.csrf	21 play.filters.components	22 play.routing	23 play.components	24 play	26 play.http	27 play.core.j	28 play.api.http	29 controllers	30 play.api.mvc	31 controllers.a	32 play.core.server	33 play.filters	34 play.api.libs.concurrent	35 play.core.server.common	36 play.core.server.common.ClientCertificateHeaderHandler	37 play.api	38 play.api.inject.guice	40 (global)
1 play.api.libs.Files
2 play.api.libs.ws
3 play.core.parsers.Multipart.BodyPartParser
4 play.core.server.common.WebSocketFlowHandler
5 controllers.b																													1
6 play.api.inject			1																											1						7
7 play.api.libs.typedmap																														4
8 play.api.routing																													3
9 play.api.i18n						2																					2		5							4
10 play.api.libs.streams			1		3																									4
11 play.api.mvc.request							3																				1		8	4
12 play.core						3																					1		8							2
13 play.inject						16																		2
14 play.api.ApplicationLoader						1						3																								3
15 play.api.data					2				2																				4	2						1
16 play.filters.cors						1				1	2															1	3		8	1						4
17 play.i18n									8									3						1
18 play.mvc										2	24		1				6								18	1	16		27
19 play.filters.csp						1				3								3											22	1						2
20 play.filters.csrf						2				1			1					11								1	8		13	3						3
21 play.filters.components																2		2	3	4			19	2
22 play.routing						2		3										6			1		1	7		2		1	6							2
23 play.components												1	1					15				1		2	3	2	2		3							1
24 play												6	4	4			3	1			1	1	12		3	2	1		2							8
25 play.data													2				10	5					1	1
26 play.http								1										20						2			8		2							4
27 play.core.j	1				1		6	1	6		4				1			2							1		15		22	6						3
28 play.api.http					1	1		3				4		2												1			29	2						11
29 controllers						3																					6		29	1						7
30 play.api.mvc	6				9	2	9		16	1	30				1												30	2		20
31 controllers.a																													1
32 play.core.server			1			2						3		3													1		5					1	2	20
33 play.filters																				1									1
34 play.api.libs.concurrent			2			4																								2						4
35 play.core.server.common			1	1							6																2		6	1	2				1	1
36 play.core.server.common.ClientCertificateHeaderHandler											2																							2		4
37 play.api	2				1	7		1	2		3	3		6												1	8		8	1			2		1
38 play.api.inject.guice						3		3						1															1	1						15		1
39 play.core.server.netty				1	1						2																2		4	1						2
40 (global)		1						1						2															4			1				8	2

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 57% · Adequate · gated by X5 ·

The Good

D3 · Scala God Classes 9.1 D4 · Scala Code Duplication 9.8 D17 · Scala Explicit Debt 10.0 IC1 · Repo Incompleteness & stubs 9.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.3 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

D1 · Scala Cyclomatic Complexity 6.3 D2 · Scala Cognitive Complexity 5.1 X18 · Repo Disposal-pattern correctness 5.9

The Ugly

X4 · Repo Structured logging 4.7 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 75% · Adequate · gated by D26 ·

The Good

D5 · Scala Coupling 10.0 D6 · Scala Cohesion (LCOM4) 9.3 D35 · Scala Change Coupling 10.0 AX2 · Repo Stateful singletons 7.2 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.9 AX8 · Repo Test isolation 10.0

The Bad

AX10 · Repo Code composition 5.0

The Ugly

D26 · Scala Project Cohesion 2.0

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

The Good

D15 · Scala Churn × Complexity Hotspots 9.9 D16 · Scala Bus Factor 7.1 D19 · Scala Documentation Quality 7.0 D21 · Scala Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 7.2

The Bad

D34 · Scala Knowledge Freshness 5.3 M1 · Repo Documentation (README) 6.7

The Ugly

D20 · Scala ADR Quality 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 69% · Adequate ·

The Good

D9 · Scala Test Distribution 10.0 D13 · Scala Secret Scanning 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.0 P6 · Repo Release Hygiene 10.0

The Bad

P10 · Repo Library API & versioning 6.0

The Ugly

P3 · Repo Security & performance tooling 4.0

At a glance — Security · 44% · Weak · gated by D29, D36, S1 ·

The Good

D28 · Scala Secrets (history) 10.0 D30 · Scala Dependency Vulnerabilities 10.0 D43 · Scala Malicious Dependencies 10.0 D44 · Scala Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Ugly

D29 · Scala Static Analysis (SAST) 2.7 D36 · Scala Supply-chain Provenance & Signing 2.5 S1 · Repo Web-Security Posture 2.0 X15 · Repo Unvalidated length from an untrusted reader 3.5

At a glance — Accessibility · 49% · Weak ·

The Bad

AC2 · Repo Forms & labels 5.5 AC6 · Repo Visual & motion safety 6.5

The Ugly

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

At a glance — Performance · 80% · Strong ·

The Good

PF1 · Repo Benchmark discipline 9.0 PF3 · Repo Async & latency hygiene 10.0

The Bad

PF2 · Repo Allocation hygiene 6.1

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A05:2025 — Injection	36	High / Critical
A03:2025 — Software Supply Chain Failures	3	Medium

Roadmap

Immediately disable the two TLS trust managers that accept any certificate by replacing them with a proper trust store, ensuring verification is never switched off. Establish a structured ADR process by documenting significant design decisions in a dedicated folder with clear context and consequences. Finally, implement supply-chain controls by generating a Software Bill of Materials and ensuring build provenance is recorded.

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

Do this	Helps	Effort	Dimension
Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:138` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `trustAllManager`)), `transport/server/play-server/src/main/scala/play/core/server/ssl/DefaultSSLEngineProvider.scala:96` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain). Each is a separate decision — fixing only the line this row cites leaves the others in place.	+5.1 pts	Medium	Web-Security Posture
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+2.2 pts	Low	ADR Quality
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.9 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.9 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.9 pts	Low	Supply-chain Provenance & Signing
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3).	+1.5 pts	Low	Static Analysis (SAST)
Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3).	+1.2 pts	Low	Documentation 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.	+2.1 pts	Medium	Architecture documentation

File quality

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

File	Score	Band	Worst signal
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.5	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala	6.0	Mixed	Explicit Debt: TodoComment
core/play/src/main/java/play/mvc/BodyParser.java	6.0	Mixed	Explicit Debt: TodoComment
web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala	6.0	Mixed	Explicit Debt: TodoComment
transport/server/play-pekko-http-server/src/main/scala/play/core/server/PekkoHttpServer.scala	6.7	Mixed	Explicit Debt: TodoComment
core/play-java/src/main/java/play/libs/Time.java	7.0	Mixed	Cyclomatic Complexity: CronExpression.getTimeAfter (cyclomatic 63)
core/play/src/main/scala/play/core/routing/GeneratedRouter.scala	7.0	Mixed	Cyclomatic Complexity: GeneratedRouter.call (cyclomatic 22)
web/play-java-forms/src/main/java/play/data/Form.java	7.0	Mixed	Cyclomatic Complexity: Form.field (cyclomatic 26)
core/play/src/main/java/play/libs/F.java	7.0	Mixed	Cyclomatic Complexity: Tuple5.equals (cyclomatic 19)
web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java	7.0	Mixed	Cyclomatic Complexity: AbstractNestablePropertyAccessor.getPropertyValue (cyclomatic 23)
transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala	7.1	Mixed	Cyclomatic Complexity: WebSocketFlowHandler.webSocketProtocol (cyclomatic 79)
web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java	7.1	Mixed	Cyclomatic Complexity: TypeConverterDelegate.convertIfNecessary (cyclomatic 38)
web/play-java-forms/src/main/java/play/data/DynamicForm.java	7.1	Mixed	Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java	7.1	Mixed	Cognitive Complexity: Segment.restructure (cognitive 36)
web/play-java-forms/src/main/java/play/data/internal/binding/util/ObjectUtils.java	7.2	Mixed	Cyclomatic Complexity: ObjectUtils.arrayEquals (cyclomatic 19)
core/play/src/main/scala/play/api/mvc/BodyParsers.scala	7.2	Mixed	Cyclomatic Complexity: PlayBodyParsers.anyContent (cyclomatic 16)
REDACTED	7.2	Mixed	God Classes: TooManyMethods: AhcWSRequest

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

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

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

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

Could not be resolved — 16

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 67 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 70 dimensions across the health lenses

D1D2D3D4D5D6D9D13D15D16D17D19D20D21D26D28D29D30D34D35D36D43D44AC2AC3AC6AC7AX10AX2AX3AX4AX6AX8IC1M1M2M3M4P1P10P2P3P6PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 551 of 565 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16767-f3ce-7961-bb14-47c64ef22f69.

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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .scala) 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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java, .scala) and this repository declares an sbt build (repository root, 333 test files), but it was not re-run: the analyzer environment could not run it. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 5 dependency(ies) and leaving 3 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (dev-mode/gradle-plugin/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `core/play/src/main/scala/play/api/mvc/Render.scala`, `core/play/src/main/scala/play/api/mvc/Results.scala`, `documentation/manual/working/scalaGuide/advanced/routing/code/ScalaSirdRouter.scala`, `documentation/manual/working/scalaGuide/main/ws/code/ScalaWSSpec.scala`, `persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/ApplicationEvolutions.scala`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice and Play dependency injection, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 22 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 245 further occurrence(s) are not listed individually; the score already reflects all 285.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D13 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

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

36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WebSocketFlowHandler.webSocketProtocol at 79.

DevServerStart.mainDev (cyclomatic 22) · ×2transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:88

WebSocketFlowHandler.webSocketProtocol (cyclomatic 79)transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:58

CronExpression.getTimeAfter (cyclomatic 63)core/play-java/src/main/java/play/libs/Time.java:1083

CronExpression.storeExpressionVals (cyclomatic 62)core/play-java/src/main/java/play/libs/Time.java:515

CronExpression.addToSet (cyclomatic 54)core/play-java/src/main/java/play/libs/Time.java:920

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

What to do

Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with WebSocketFlowHandler.webSocketProtocol (cyclomatic 79), CronExpression.getTimeAfter (cyclomatic 63), CronExpression.storeExpressionVals (cyclomatic 62). — 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 6 together lifts Cyclomatic Complexity from 6.3 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity5.1 / 10Adequate✓ Tool-verified

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

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

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

73 method(s) exceeded the cognitive complexity threshold of 15; the worst was GeneratedRouter.call at 231.

DevServerStart.mainDev (cognitive 23) · ×2transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:88

GeneratedRouter.call (cognitive 231)core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:433

GeneratedRouter.call (cognitive 210)core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:407

GeneratedRouter.call (cognitive 190)core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:382

GeneratedRouter.call (cognitive 171)core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:358

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

What to do

Bring the 8 bodies over 120 down to 120 or less in Cognitive Complexity — start with GeneratedRouter.call (cognitive 231), GeneratedRouter.call (cognitive 210), GeneratedRouter.call (cognitive 190). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 5.1 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.1 / 10Stronggated by 44 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

44 god class(es) detected.

TooManyMethods: Results · ×17core/play/src/main/java/play/mvc/Results.java:28

FileTooLong: mvc/Http.java · ×11core/play/src/main/java/play/mvc/Http.java

ClassTooLong: Form · ×9web/play-java-forms/src/main/java/play/data/Form.java:79

MethodTooLong: WebSocketFlowHandler.webSocketProtocol · ×7transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:29

What to do

Resolve the 17 TooManyMethods finding(s) in God Classes — start with Results.java, StatusHeader.java, REDACTED. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with Http.java, Form.java, Results.java. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 9 ClassTooLong finding(s) in God Classes — start with Form.java, Results.java, Time.java. — One of this dimension's main actionable groups (9 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Stronggated by 46 serious findings✓ Tool-verified

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

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

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

43 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (8 lines × 2) · ×5core/play/src/main/scala/play/api/mvc/Render.scala:35

Duplicated block (5 lines × 2) · ×5transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:180

Duplicated block (8 lines × 3) · ×3web/play-filters-helpers/src/main/scala/play/filters/csp/CSPConfig.scala:88

Duplicated block (6 lines × 2) · ×3core/play/src/main/scala/play/api/i18n/Messages.scala:151

Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2core/play/src/main/java/play/libs/F.java:107

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

What to do

Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Render.scala, Colors.scala, Time.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Rfc9440ClientCertificateParser.scala, Time.java, Result.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with CSPConfig.scala, Time.java, NamedCacheImpl.java. — One of this dimension's main actionable groups (3 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

7 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

5 of 87 classes have LCOM4 above 3.

Low cohesion: CSRFActionHelper (LCOM4 5) · ×5web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala:400

What to do

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

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

Do you agree with this assessment?

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

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

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

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

4216 test methods: 4211 unit, 5 integration, 0 BDD, 0 e2e. The Scala suite contributes 3608 test case(s) across 269 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

Top hotspots: transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala (4×79=316)

Hotspot: transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scalatransport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:58

What to do

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

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

Do you agree with this assessment?

D16 · Bus Factor7.1 / 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 7.1 / 10 · rule-coverage 100% · ceiling Documented

106 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is core/play/src/main/java/play/mvc/Http.java. Counted over 348 of the 745 production source files in this repository: 391 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

What to do

Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Stronggated by 23 serious findings✓ Tool-verified

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

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

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

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

TodoComment · ×17core/play-guice/src/main/scala/play/api/libs/concurrent/ActorModule.scala:27

FixmeComment · ×6cache/play-cache/src/main/scala/play/api/cache/Cached.scala:200

What to do

Resolve the 17 TodoComment finding(s) in Explicit Debt — start with ScalaResultsHandlingSpec.scala (2), RangeResult.scala (2), ActorModule.scala. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 6 FixmeComment finding(s) in Explicit Debt — start with PekkoModelConversion.scala (2), Cached.scala, CachedSpec.scala. — One of this dimension's main actionable groups (6 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

The repository's root README (Play Framework - The High Velocity Web Framework) and the documentation/README.md are both excellent at conveying what the project is and how to use it. The dev-mode/sbt-plugin/src/sbt-test/README.md documents its own directory rather than the main repo, so it does not fall under the repository's overview/contribution guidance scope. All four outlined categories (missing-overview, missing-installation, missing-usage, missing-contributing) are present in the root README and are judged there; none appear in any of the clipped documents.

Documentation: no project overview · ×3README.md

What to do

Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion2.0 / 10Critical✓ Tool-verified

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

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

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

2 of 5 build units (Gradle, sbt) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

36 finding(s): 0 critical, 27 high, 4 medium, 5 low. 21 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 19 file(s) — `core/play/src/main/scala/play/api/mvc/Render.scala`, `core/play/src/main/scala/play/api/mvc/Results.scala`, `core/play/src/main/scala/views/defaultpages/devError.scala.html` (lines 1–5, lines 11–115, line 122, …), `core/play/src/main/scala/views/defaultpages/devNotFound.scala.html` (lines 1–5, lines 11–100, line 111, …), `core/play/src/main/scala/views/helper/script.scala.html` (lines 1–17), … (+14 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

Do you agree with this assessment?

D34 · Knowledge Freshness5.3 / 10Adequate✓ Tool-verified

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

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

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

163 of 354 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/play-java/src/main/java/play/libs/Time.java. Counted over 354 of the 745 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×6core/play-java/src/main/java/play/libs/Time.java:1

Orphaned file · ×157dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/templates/package.scala:1

Further orphaned files (smaller)

What to do

Resolve the 157 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (3), QueryStringParameterMacros.scala (2), csrf.scala. — One of this dimension's main actionable groups (157 recommendation-level).
Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with Time.java, Forms.scala, Logger.java. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change 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.

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels5.5 / 10Adequate✓ Tool-verified

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

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

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

This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — core/play/src/main/scala/views/play20/manual.scala.html:17, documentation/manual/working/javaGuide/main/upload/code/javaguide/fileupload/views/uploadForm.scala.html:5, documentation/manual/working/scalaGuide/main/upload/code/scalaguide/templates/views/uploadForm.scala.html:5

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure4.9 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×10) — core/play/src/main/scala/views/defaultpages/badRequest.scala.html:6, core/play/src/main/scala/views/defaultpages/devError.scala.html:7, core/play/src/main/scala/views/defaultpages/devNotFound.scala.html:7, …
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — core/play/src/main/scala/views/defaultpages/todo.scala.html:7, core/play/src/main/scala/views/play20/manual.scala.html:2, documentation/manual/tutorial/code/javaguide/hello/main.scala.html:4

What to do

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

Do you agree with this assessment?

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

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

`object` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — documentation/style/main.css:5
`:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — documentation/style/main.css:13

What to do

Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

Do you agree with this assessment?

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

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

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

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

No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 37 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.

Do you agree with this assessment?

AX10 · Code composition5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

AX2 · Stateful singletons7.2 / 10Strong✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

`DefaultHttpErrorHandler` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (playEditor; e.g. `playEditor` in `setPlayEditor` at line 185). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — core/play/src/main/scala/play/api/http/HttpErrorHandler.scala:140
`DefaultTemporaryFileReaper` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (playTempFolder; e.g. `playTempFolder` in `updateTempFolder` at line 364). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — core/play/src/main/scala/play/api/libs/Files.scala:348
`InlineCache` is one shared instance (Play controller: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (cache; e.g. `cache` in `fresh` at line 72). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — core/play/src/main/scala/play/utils/InlineCache.scala:41
`ApplicationEvolutions` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (invalidDatabaseRevisions; e.g. `invalidDatabaseRevisions` in `start` at line 71). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/ApplicationEvolutions.scala:27
`InstanceController` is one shared instance (Play controller: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (invoked; e.g. `invoked` in `index` at line 14). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. (×2) — dev-mode/sbt-plugin/src/sbt-test/play-sbt-plugin/routes-compiler-no-package-declaration-in-routes-file/app/router/InstanceController.scala:10, dev-mode/sbt-plugin/src/sbt-test/play-sbt-plugin/routes-compiler-routes-compilation/app/controllers/InstanceController.scala:10

What to do

Scala: keep controllers and singletons stateless — per-request data in locals, shared data in a store — or hold the state in a thread-safe type (TrieMap, AtomicInteger/AtomicReference, a cats-effect Ref) or update it under `synchronized { }`; a flag that is only ever overwritten can be a `@volatile var`.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

`WSRequest` declares 66 abstract methods: `addCookie`, `addCookie`, `addCookies`, `addHeader`, `addQueryParameter`, `delete`, `execute`, `execute`, `get`, `getHeaders`, `getQueryParameters`, `getUrl`, `head`, `options`, `patch`, `patch`, `patch`, `patch`, `patch`, `patch`, `patch`, `post`, `post`, `post`, `post`, `post`, `post`, `post`, `put`, `put`, `put`, `put`, `put`, `put`, `put`, `query`, `query`, `query`, `query`, `query`, and 26 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 66 declarations carry 31 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 31 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — transport/client/play-ws/src/main/java/play/libs/ws/WSRequest.java:26
`WSResponse` declares 18 abstract methods: `asByteArray`, `asJson`, `asXml`, `getAllHeaders`, `getBody`, `getBody`, `getBodyAsBytes`, `getBodyAsSource`, `getBodyAsStream`, `getContentType`, `getCookie`, `getCookies`, `getHeaderValues`, `getHeaders`, `getSingleHeader`, `getStatus`, `getStatusText`, `getUnderlying`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 18 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — transport/client/play-ws/src/main/java/play/libs/ws/WSResponse.java:17
`Cookie` declares 19 abstract methods: `domain`, `isHttpOnly`, `isPartitioned`, `isSecure`, `maxAge`, `name`, `path`, `sameSite`, `setDomain`, `setHttpOnly`, `setMaxAge`, `setPartitioned`, `setPath`, `setSameSite`, `setSecure`, `setValue`, `setWrap`, `value`, `wrap`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/play/src/main/java/play/core/cookie/encoding/Cookie.java:19
`RequestHeader` declares 28 abstract methods: `acceptLanguages`, `acceptedTypes`, `accepts`, `addAttr`, `addAttrs`, `addAttrs`, `addAttrs`, `addAttrs`, `asScala`, `attrs`, `charset`, `contentType`, `cookie`, `cookies`, `getCookie`, `getHeaders`, `getQueryString`, `hasBody`, `headers`, `method`, `path`, `queryString`, `queryString`, `removeAttr`, `uri`, `version`, `withAttrs`, `withBody`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 28 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/play/src/main/java/play/mvc/Http.java:829
`MessagesApi` declares 16 abstract members under just 13 distinct name(s): `messages`, `preferred`, `preferred`, `preferred`, `apply`, `apply`, `translate`, `isDefinedAt`, `setLang`, `withoutLang`, `langCookieName`, `langCookieMaxAge`, `langCookieSecure`, `langCookieHttpOnly`, `langCookieSameSite`, `langCookiePartitioned`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — core/play/src/main/scala/play/api/i18n/Messages.scala:337
`WSRequest` declares 41 abstract members: `withHeaders`, `withHttpHeaders`, `withQueryString`, `withQueryStringParameters`, `addCookies`, `withCookies`, `method`, `body`, `headers`, `queryString`, `calc`, `auth`, `followRedirects`, `requestTimeout`, `virtualHost`, `proxyServer`, `sign`, `withAuth`, `withFollowRedirects`, `withRequestTimeout`, `withRequestFilter`, `withVirtualHost`, `withProxyServer`, `withBody`, `withMethod`, `get`, `post`, `post`, `post`, `patch`, `patch`, `patch`, `put`, `put`, `put`, `query`, `delete`, `head`, `options`, `execute`, and 1 more. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 41 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — transport/client/play-ws/src/main/scala/play/api/libs/ws/WSRequest.scala:19

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

`render` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — documentation/manual/working/javaGuide/main/http/code/javaguide/http/JavaActions.java:121
`recordAbnormalClosure` has an empty body — confirm it's an intentional no-op and not an unfinished method. — documentation/manual/releases/release31/migration31/code/WebSocketCloseMigration.java:19

What to do

Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.

Do you agree with this assessment?

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 2 of 3 project(s) that lack one — worth up to 1.3 pts.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M4 · Documentation accuracy7.2 / 10Strong◐ Sampled · advisory

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

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

documentation/README.md links to `some/relative/path`, but `documentation/some/relative/path` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/README.md:17
documentation/README.md links to `code/javaguide/pekko/JavaPekko.java`, but `documentation/code/javaguide/pekko/JavaPekko.java` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/README.md:27
documentation/manual/hacking/BuildingFromSource.md changes into `playframework/documentation`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/hacking/BuildingFromSource.md:50
documentation/manual/tutorial/ImplementingHelloWorld.md names `app/views/hello.scala.html`, but no file or folder `app/views/hello.scala.html` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/tutorial/ImplementingHelloWorld.md:82
documentation/manual/working/commonGuide/configuration/ApplicationSecret.md documents the environment variable `APPLICATION_SECRET`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/ApplicationSecret.md:33
documentation/manual/working/commonGuide/configuration/SettingsJDBC.md links to `/confs/play-jdbc/reference.conf`, but `confs/play-jdbc/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsJDBC.md:33
documentation/manual/working/commonGuide/configuration/SettingsLogger.md links to `/confs/play-logback/logback-play-dev.xml`, but `confs/play-logback/logback-play-dev.xml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsLogger.md:11
documentation/manual/working/commonGuide/configuration/SettingsLogger.md links to `/confs/play-logback/logback-play-default.xml`, but `confs/play-logback/logback-play-default.xml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsLogger.md:15
documentation/manual/working/commonGuide/configuration/SettingsNetty.md links to `/confs/play-netty-server/reference.conf`, but `confs/play-netty-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsNetty.md:13
documentation/manual/working/commonGuide/configuration/SettingsNetty.md links to `/confs/play-server/reference.conf`, but `confs/play-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsNetty.md:17
documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md links to `/confs/play-pekko-http-server/reference.conf`, but `confs/play-pekko-http-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md:9
documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md links to `/confs/play-server/reference.conf`, but `confs/play-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md:13
documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md links to `/confs/play-pekko-http2-support/reference.conf`, but `confs/play-pekko-http2-support/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md:30
documentation/manual/working/commonGuide/configuration/SettingsSession.md links to `/confs/play/reference.conf`, but `confs/play/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/SettingsSession.md:30
documentation/manual/working/commonGuide/configuration/ThreadPools.md links to `api/java/play/libs/concurrent/ClassLoaderExecutionContext.html`, but `documentation/manual/working/commonGuide/configuration/api/java/play/libs/concurrent/ClassLoaderExecutionContext.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/ThreadPools.md:46
documentation/manual/working/commonGuide/configuration/WsCache.md links to `/confs/play-ahc-ws/reference.conf`, but `confs/play-ahc-ws/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/configuration/WsCache.md:90
documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/java/play/db/Database.html`, but `documentation/manual/working/commonGuide/database/api/java/play/db/Database.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:146
documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/scala/play/api/db/Database.html`, but `documentation/manual/working/commonGuide/database/api/scala/play/api/db/Database.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:146
documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/java/play/libs/concurrent/CustomExecutionContext.html`, but `documentation/manual/working/commonGuide/database/api/java/play/libs/concurrent/CustomExecutionContext.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:178
documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/scala/play/api/libs/concurrent/CustomExecutionContext.html`, but `documentation/manual/working/commonGuide/database/api/scala/play/api/libs/concurrent/CustomExecutionContext.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:178
documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `resources/confs/play-jdbc/reference.conf`, but `documentation/manual/working/commonGuide/database/resources/confs/play-jdbc/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:208
documentation/manual/working/commonGuide/filters/AllowedHostsFilter.md links to `resources/confs/play-filters-helpers/reference.conf`, but `documentation/manual/working/commonGuide/filters/resources/confs/play-filters-helpers/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/AllowedHostsFilter.md:23
documentation/manual/working/commonGuide/filters/CorsFilter.md links to `resources/confs/play-filters-helpers/reference.conf`, but `documentation/manual/working/commonGuide/filters/resources/confs/play-filters-helpers/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CorsFilter.md:19
documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/scala/play/filters/csp/CSPFilter.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/filters/csp/CSPFilter.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CspFilter.md:17
documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/scala/play/filters/csp/CSPComponents.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/filters/csp/CSPComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CspFilter.md:27
documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/java/play/filters/components/CSPComponents.html`, but `documentation/manual/working/commonGuide/filters/api/java/play/filters/components/CSPComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CspFilter.md:29
documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/scala/play/filters/csp/DefaultCSPProcessor.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/filters/csp/DefaultCSPProcessor.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CspFilter.md:145
documentation/manual/working/commonGuide/filters/CspFilter.md links to `/confs/play-filters-helpers/reference.conf`, but `confs/play-filters-helpers/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CspFilter.md:147
documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/scala/play/api/mvc/RequestHeader.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/api/mvc/RequestHeader.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/CspFilter.md:196
documentation/manual/working/commonGuide/filters/Filters.md links to `api/scala/play/api/BuiltInComponents.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/api/BuiltInComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/Filters.md:112
documentation/manual/working/commonGuide/filters/Filters.md links to `api/java/play/BuiltInComponents.html`, but `documentation/manual/working/commonGuide/filters/api/java/play/BuiltInComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/Filters.md:112
documentation/manual/working/commonGuide/filters/Filters.md links to `api/scala/play/filters/HttpFiltersComponents.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/filters/HttpFiltersComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/Filters.md:112
documentation/manual/working/commonGuide/filters/Filters.md links to `api/java/play/filters/components/HttpFiltersComponents.html`, but `documentation/manual/working/commonGuide/filters/api/java/play/filters/components/HttpFiltersComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/Filters.md:112
documentation/manual/working/commonGuide/filters/Filters.md links to `api/scala/play/api/NoHttpFiltersComponents.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/api/NoHttpFiltersComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/Filters.md:130
documentation/manual/working/commonGuide/filters/Filters.md links to `api/java/play/filters/components/NoHttpFiltersComponents.html`, but `documentation/manual/working/commonGuide/filters/api/java/play/filters/components/NoHttpFiltersComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/Filters.md:130
documentation/manual/working/commonGuide/filters/GzipEncoding.md links to `resources/confs/play-filters-helpers/reference.conf`, but `documentation/manual/working/commonGuide/filters/resources/confs/play-filters-helpers/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/filters/GzipEncoding.md:17
documentation/manual/working/commonGuide/production/ProductionConfiguration.md links to `/confs/play-pekko-http-server/reference.conf`, but `confs/play-pekko-http-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/production/ProductionConfiguration.md:126
documentation/manual/working/commonGuide/production/ProductionConfiguration.md links to `/confs/play-netty-server/reference.conf`, but `confs/play-netty-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/production/ProductionConfiguration.md:130
documentation/manual/working/commonGuide/production/ProductionConfiguration.md links to `/confs/play-server/reference.conf`, but `confs/play-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/production/ProductionConfiguration.md:136
documentation/manual/working/commonGuide/production/cloud/ProductionHeroku.md documents the environment variable `DATABASE_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/manual/working/commonGuide/production/cloud/ProductionHeroku.md:237

What to do

Reconcile the README with reality: documentation/README.md links to `some/relative/path`, but `documentation/some/relative/path` does not exist; documentation/README.md links to `code/javaguide/pekko/JavaPekko.java`, but `documentation/code/javaguide/pekko/JavaPekko.java` does not exist; documentation/manual/hacking/BuildingFromSource.md changes into `playframework/documentation`, but no such folder exists; documentation/manual/tutorial/ImplementingHelloWorld.md names `app/views/hello.scala.html`, but no file or folder `app/views/hello.scala.html` exists; documentation/manual/working/commonGuide/configuration/ApplicationSecret.md documents the environment variable `APPLICATION_SECRET`, but no code, script or configuration file names it.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

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

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

441/620 types (71%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

What to do

Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.

Do you agree with this assessment?

P2 · Observability7.0 / 10Strong✓ 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.

What to do

Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.

Do you agree with this assessment?

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.

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

What to do

Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

PF1 · Benchmark discipline9.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — core/play-microbenchmark/src/test/scala/play/api/mvc/RequestHeader_01_ReadHeaderValue.scala

What to do

Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.

Do you agree with this assessment?

PF2 · Allocation hygiene6.1 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 31 use(s) across 135,476 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

Do you agree with this assessment?

S1 · Web-Security Posture2.0 / 10Critical✓ Tool-verified

Other · Security — Read from this repository's Scala source and the Java beside it: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. This repository serves HTTP itself (core/play-java/src/main/java/play/routing/RoutingDslComponentsFromContext.java:16 — `BuiltInComponentsFromContext`), so its Scala source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Scala spelling appears in production source, not proven on every route. A Play application is credited the security headers Play's default `SecurityHeadersFilter` sends unless its build or configuration switches that filter off, and its cookies the HttpOnly flag Play sets by default.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `trustAllManager`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on. (×2) — dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:138, transport/server/play-server/src/main/scala/play/core/server/ssl/DefaultSSLEngineProvider.scala:96
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — core/play/src/main/scala/play/api/libs/Codecs.scala:17, core/play/src/main/scala/play/api/libs/Codecs.scala:18
`//code.jquery.com/jquery-2.2.0.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — dev-mode/play-docs-sbt-plugin/src/main/twirl/org/playframework/docs/sbtplugin/translationReport.scala.html:11

What to do

Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:138` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `trustAllManager`)), `transport/server/play-server/src/main/scala/play/core/server/ssl/DefaultSSLEngineProvider.scala:96` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `core/play/src/main/scala/play/api/libs/Codecs.scala:17` (MessageDigest.getInstance("SHA-1")), `core/play/src/main/scala/play/api/libs/Codecs.scala:18` (MessageDigest.getInstance("MD5")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader3.5 / 10Weak✓ Tool-verified

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

`sizeOfBody` is read from the bytes being parsed at line 67 (`readInt`), then used to size a `new Array[Byte]` at line 68 — and nowhere in its scope is `sizeOfBody` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `sizeOfBody` against the bytes actually remaining and a maximum the format allows before allocating. — cache/play-cache/src/main/scala/play/api/cache/SerializableResult.scala:68

What to do

Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness5.9 / 10Adequate✓ Tool-verified

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

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

`scala.io.Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(scala.io.Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — documentation/manual/working/scalaGuide/main/ws/code/ScalaWSSpec.scala:240

What to do

Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

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

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X3 · Exception handling7.3 / 10Strong✓ 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.

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — core/play-java/src/main/java/play/libs/Time.java:1540, transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:214, web/play-java-forms/src/main/java/play/data/Form.java:1698
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — core/play/src/main/java/play/i18n/Lang.java:64, web/play-java-forms/src/main/java/play/data/DynamicForm.java:196, web/play-java-forms/src/main/java/play/data/DynamicForm.java:214, …
`case NonFatal(_)` 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. — project/BuildSettings.scala:41

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

X4 · Structured logging4.7 / 10Weak✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

`warn` at line 203 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play-configuration/src/main/scala/play/api/Configuration.scala:203
`warn` at line 282 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/Logger.scala:282
`warn` at line 283 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/Logger.scala:283
`warn` at line 89 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/data/Form.scala:89
`warn` at line 184 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/http/HttpConfiguration.scala:184
`debug` at line 299 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/http/HttpConfiguration.scala:299
`info` at line 63 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/internal/libs/concurrent/CoordinatedShutdownSupport.scala:63
`debug` at line 223 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/libs/Files.scala:223
`debug` at line 274 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/play/src/main/scala/play/api/libs/concurrent/Pekko.scala:274
`info` at line 35 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — documentation/manual/working/scalaGuide/main/application/code/AccumulatorFlowFilter.scala:35
`info` at line 174 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — transport/client/play-ahc-ws/src/main/scala/play/api/test/WSTestClient.scala:174
`debug` at line 195 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — transport/client/play-ahc-ws/src/main/scala/play/api/test/WSTestClient.scala:195
`debug` at line 200 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — transport/client/play-ahc-ws/src/main/scala/play/api/test/WSTestClient.scala:200
`debug` at line 43 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — transport/server/play-server/src/main/scala/play/core/server/SelfSigned.scala:43
`debug` at line 47 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — transport/server/play-server/src/main/scala/play/core/server/SelfSigned.scala:47
`debug` at line 51 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — core/play/src/main/java/play/core/cookie/encoding/CookieDecoder.java:51
`debug` at line 64 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — core/play/src/main/java/play/core/cookie/encoding/CookieDecoder.java:64
`debug` at line 78 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — core/play/src/main/java/play/core/cookie/encoding/CookieDecoder.java:78
`error` at line 129 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — core/play/src/main/java/play/http/JsonHttpErrorHandler.java:129
`error` at line 230 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — core/play/src/main/java/play/http/DefaultHttpErrorHandler.java:230
`debug` at line 426 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — documentation/manual/working/javaGuide/main/ws/code/javaguide/ws/JavaWS.java:426
`error` at line 517 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — documentation/manual/working/javaGuide/main/ws/code/javaguide/ws/JavaWS.java:517

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

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

Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.

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

No build over this repository's 444 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.

What to do

On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	57%	Adequate — gated by X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	75%	Adequate — gated by D26	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	50%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	69%	Adequate	Acceptable, with room to improve.
Security	44%	Weak — gated by D29, D36, S1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	49%	Weak	Below par — needs attention.
Performance	80%	Strong	Strongest area.

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

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

X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 5 control(s) we could not find positive evidence for

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

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

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

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

AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~76334 lines of test source are present (.java, .scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 5 dependency(ies) and leaving 3 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — Not scored — this repository's 5 declared JVM dependency coordinate(s) were read from its 2 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 5 of them (HTTP 429 Too Many Requests from https://repo1.maven.org/maven2/org/assertj/assertj-core/3.27.7/assertj-core-3.27.7.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 176 value object(s); 7 domain event(s); its domain events are published by services or handlers — no domain entity raises one
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 and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
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.
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.

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 — 41 finding(s)

D29 · Static Analysis (SAST) · 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

D34 · Knowledge Freshness · Orphaned knowledge · ×6

Orphaned knowledge core/play-java/src/main/java/play/libs/Time.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/play/src/main/scala/play/api/data/Forms.scala:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/play/src/main/java/play/Logger.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/play/src/main/scala/play/api/mvc/Cookie.scala:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge web/play-java-forms/src/main/java/play/data/validation/Constraints.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/play/src/main/java/play/mvc/Result.java:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.

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

<html> without a lang core/play/src/main/scala/views/defaultpages/todo.scala.html:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang core/play/src/main/scala/views/play20/manual.scala.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang documentation/manual/tutorial/code/javaguide/hello/main.scala.html:4 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

AC2 · Forms & labels · <input> without a programmatic label · ×2

<input> without a programmatic label documentation/manual/working/javaGuide/main/upload/code/javaguide/fileupload/views/uploadForm.scala.html:5 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label documentation/manual/working/scalaGuide/main/upload/code/scalaguide/templates/views/uploadForm.scala.html:5 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

S1 · Web-Security Posture · TLS certificate validation disabled · ×2

TLS certificate validation disabled dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:138 — an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `trustAllManager`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on.
TLS certificate validation disabled transport/server/play-server/src/main/scala/play/core/server/ssl/DefaultSSLEngineProvider.scala:96 — an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `trustAllManager`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on.

AC2 · Forms & labels · <select> without a programmatic label · ×1

<select> without a programmatic label core/play/src/main/scala/views/play20/manual.scala.html:17 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

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

REDACTED

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

REDACTED

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

REDACTED

Serious — 266 finding(s)

D17 · Explicit Debt · TodoComment · ×17

TodoComment core/play-guice/src/main/scala/play/api/libs/concurrent/ActorModule.scala:27 — // TODO: Define ConfiguredActor's behavior using the injected configuration. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play-integration-test/src/test/scala/play/it/http/UriHandlingSpec.scala:129 — // TODO: Disabled the (secure) pekko-http2 test, an URI parsing bug causes requests to be stuck forever, never reaching Play: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play-integration-test/src/test/scala/play/it/http/ScalaResultsHandlingSpec.scala:124 — // todo fix the ExecutionContext. Not sure where to get it from nicely — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play-integration-test/src/test/scala/play/it/http/ScalaResultsHandlingSpec.scala:127 — // todo not sure where to get this one from in this context, either — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play/src/main/java/play/components/CryptoComponents.java:17 — // TODO Should this be part of the interface? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play/src/main/java/play/mvc/BodyParser.java:891 — // TODO have this transformations in Scala is easier. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play/src/main/scala/play/api/libs/concurrent/Pekko.scala:252 — // TODO: deprecate this setting (see https://github.com/playframework/playframework/issues/8442)
TodoComment core/play/src/main/scala/play/api/mvc/RangeResult.scala:149 — // TODO this should be configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/play/src/main/scala/play/api/mvc/RangeResult.scala:156 — // TODO this should be configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment documentation/manual/working/javaGuide/main/http/code/javaguide/http/JavaBodyParsers.java:199 — // TODO: when streaming upload has been implemented, pass the source as the body — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment persistence/play-jdbc-evolutions/src/test/scala/play/api/db/evolutions/EvolutionsSpec.scala:17 — // TODO: functional test with InvalidDatabaseRevision exception — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment testkit/play-test/src/main/scala/play/api/test/Helpers.scala:246 — // TODO: After removing that method we can rename (and deprecate) writeableOf_AnyContentAsMultipartFormWithBoundary (remove ...WithBoundary) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment transport/server/play-pekko-http-server/src/main/scala/play/core/server/PekkoHttpServer.scala:253 — // TODO: pass in Inet.SocketOption and LoggerAdapter params? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment transport/server/play-server/src/main/scala/play/core/server/Server.scala:132 — // TODO: `copyRequestHeader` is a misleading name here since it is also populating the request with attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:247 — // TODO: Make this method return a Future[Application] so we don't need to block more than one thread. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala:189 — // TODO rewrite BodyHandler such that it emits sub-source then we can avoid all these dancing around — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment web/play-openid/src/main/scala/play/api/libs/openid/OpenIdClient.scala:278 — // TODO: Verify schema, namespace and support verification of XML signatures — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D3 · God Classes · TooManyMethods · ×17

TooManyMethods: Results core/play/src/main/java/play/mvc/Results.java:28 — TooManyMethods — 436 methods. The bar is 30 methods; this is 406 over it, 14.53× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: StatusHeader core/play/src/main/java/play/mvc/StatusHeader.java:31 — TooManyMethods — 110 methods. The bar is 30 methods; this is 80 over it, 3.67× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: AhcWSRequest REDACTED:24 — TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× the bar. Most of these members implement ws.WSRequest (31 of 44 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: RequestBuilder core/play/src/main/java/play/mvc/Http.java:1281 — TooManyMethods — 77 methods. The bar is 30 methods; this is 47 over it, 2.57× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Form web/play-java-forms/src/main/java/play/data/Form.java:79 — TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Forms core/play/src/main/scala/play/api/data/Forms.scala:26 — TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Result core/play/src/main/java/play/mvc/Result.java:36 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ALogger core/play/src/main/java/play/Logger.java:459 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: PlayBodyParsers core/play/src/main/scala/play/api/mvc/BodyParsers.scala:446 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Evolutions persistence/play-jdbc-evolutions/src/main/java/play/db/evolutions/Evolutions.java:13 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Accepted core/play/src/main/java/play/mvc/WebSocket.java:212 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: RoutesFileParser dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesFileParser.scala:143 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ResolvableType web/play-java-forms/src/main/java/play/data/internal/binding/core/ResolvableType.java:75 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: AbstractNestablePropertyAccessor web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:65 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: RequestHeader core/play/src/main/scala/play/api/mvc/RequestHeader.scala:24 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: CronExpression core/play-java/src/main/java/play/libs/Time.java:252 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ConcurrentReferenceHashMap web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:71 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.

D3 · God Classes · FileTooLong · ×11

FileTooLong: mvc/Http.java core/play/src/main/java/play/mvc/Http.java — FileTooLong — 1448 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 948 over it, 2.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: data/Form.java web/play-java-forms/src/main/java/play/data/Form.java — FileTooLong — 1265 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Form (79-2095). The bar is 500 significant lines; this is 765 over it, 2.53× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: mvc/Results.java core/play/src/main/java/play/mvc/Results.java — FileTooLong — 1032 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Results (28-5086). The bar is 500 significant lines; this is 532 over it, 2.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: libs/Time.java core/play-java/src/main/java/play/libs/Time.java — FileTooLong — 911 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Time (23-1562). The bar is 500 significant lines; this is 411 over it, 1.82× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: util/ConcurrentReferenceHashMap.java web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java — FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ConcurrentReferenceHashMap (71-1302). The bar is 500 significant lines; this is 132 over it, 1.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: mvc/BodyParser.java core/play/src/main/java/play/mvc/BodyParser.java — FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: BodyParser (56-917). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: mvc/StatusHeader.java core/play/src/main/java/play/mvc/StatusHeader.java — FileTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: StatusHeader (31-1947). The bar is 500 significant lines; this is 60 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: server/PekkoHttpServer.scala transport/server/play-pekko-http-server/src/main/scala/play/core/server/PekkoHttpServer.scala — FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: PekkoHttpServer (73-724). The bar is 500 significant lines; this is 42 over it, 1.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: beans/AbstractNestablePropertyAccessor.java web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java — FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: AbstractNestablePropertyAccessor (65-943). The bar is 500 significant lines; this is 32 over it, 1.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: mvc/BodyParsers.scala core/play/src/main/scala/play/api/mvc/BodyParsers.scala — FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: evolutions/EvolutionsApi.scala persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/EvolutionsApi.scala — FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

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

Page without a main landmark core/play/src/main/scala/views/defaultpages/badRequest.scala.html:6 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/defaultpages/devError.scala.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/defaultpages/devNotFound.scala.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/defaultpages/error.scala.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/defaultpages/notFound.scala.html:6 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/defaultpages/todo.scala.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/defaultpages/unauthorized.scala.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark core/play/src/main/scala/views/play20/manual.scala.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark dev-mode/play-docs-sbt-plugin/src/main/twirl/org/playframework/docs/sbtplugin/translationReport.scala.html:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark documentation/manual/tutorial/code/javaguide/hello/main.scala.html:4 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

D3 · God Classes · ClassTooLong · ×9

ClassTooLong: Form web/play-java-forms/src/main/java/play/data/Form.java:79 — ClassTooLong — 1195 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 795 over it, 2.99× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Results core/play/src/main/java/play/mvc/Results.java:28 — ClassTooLong — 1013 significant lines (blank, comment-only and punctuation-only lines excluded), 436 methods. The bar is 400 significant lines; this is 613 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Time core/play-java/src/main/java/play/libs/Time.java:23 — ClassTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 496 over it, 2.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ConcurrentReferenceHashMap web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:71 — ClassTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 208 over it, 1.52× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BodyParser core/play/src/main/java/play/mvc/BodyParser.java:56 — ClassTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 155 over it, 1.39× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StatusHeader core/play/src/main/java/play/mvc/StatusHeader.java:31 — ClassTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods. The bar is 400 significant lines; this is 137 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AbstractNestablePropertyAccessor web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:65 — ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 108 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Constraints web/play-java-forms/src/main/java/play/data/validation/Constraints.java:26 — ClassTooLong — 468 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 68 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebSocket core/play/src/main/java/play/mvc/WebSocket.java:35 — ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 12 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · MethodTooLong · ×7

MethodTooLong: WebSocketFlowHandler.webSocketProtocol transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:29 — MethodTooLong — webSocketProtocol runs 332 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 232 over it, 3.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebSocketFlowHandler.webSocketProtocol transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:39 — MethodTooLong — webSocketProtocol runs 327 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 227 over it, 3.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebSocketFlowHandler.webSocketProtocol transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:50 — MethodTooLong — webSocketProtocol runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebSocketFlowHandler.webSocketProtocol transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:58 — MethodTooLong — webSocketProtocol runs 314 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 214 over it, 3.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CronExpression.getTimeAfter core/play-java/src/main/java/play/libs/Time.java:1083 — MethodTooLong — getTimeAfter runs 265 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CronExpression.storeExpressionVals core/play-java/src/main/java/play/libs/Time.java:515 — MethodTooLong — storeExpressionVals runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScalaSirdRouter.Action documentation/manual/working/scalaGuide/advanced/routing/code/ScalaSirdRouter.scala:18 — MethodTooLong — Action runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

AX2 · Stateful singletons · Stateful singleton · ×6

Stateful singleton: DefaultHttpErrorHandler core/play/src/main/scala/play/api/http/HttpErrorHandler.scala:140 — `DefaultHttpErrorHandler` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (playEditor; e.g. `playEditor` in `setPlayEditor` at line 185). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt.
Stateful singleton: DefaultTemporaryFileReaper core/play/src/main/scala/play/api/libs/Files.scala:348 — `DefaultTemporaryFileReaper` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (playTempFolder; e.g. `playTempFolder` in `updateTempFolder` at line 364). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt.
Stateful singleton: InlineCache core/play/src/main/scala/play/utils/InlineCache.scala:41 — `InlineCache` is one shared instance (Play controller: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (cache; e.g. `cache` in `fresh` at line 72). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt.
Stateful singleton: ApplicationEvolutions persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/ApplicationEvolutions.scala:27 — `ApplicationEvolutions` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (invalidDatabaseRevisions; e.g. `invalidDatabaseRevisions` in `start` at line 71). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt.
Stateful singleton: InstanceController dev-mode/sbt-plugin/src/sbt-test/play-sbt-plugin/routes-compiler-no-package-declaration-in-routes-file/app/router/InstanceController.scala:10 — `InstanceController` is one shared instance (Play controller: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (invoked; e.g. `invoked` in `index` at line 14). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt.
Stateful singleton: InstanceController dev-mode/sbt-plugin/src/sbt-test/play-sbt-plugin/routes-compiler-routes-compilation/app/controllers/InstanceController.scala:10 — `InstanceController` is one shared instance (Play controller: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (invoked; e.g. `invoked` in `index` at line 14). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt.

D17 · Explicit Debt · FixmeComment · ×6

FixmeComment cache/play-cache/src/main/scala/play/api/cache/Cached.scala:200 — // FIXME: Surely Duration.Inf is a better marker for eternity than 0? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cache/play-ehcache/src/test/scala/play/api/cache/CachedSpec.scala:74 — // FIXME: Do this properly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment core/play/src/main/scala/play/api/controllers/Assets.scala:843 — // FIXME stream.available does not necessarily return the length of the file. According to the docs "It is never — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment core/play/src/main/scala/play/core/j/ClassLoaderExecutionContext.scala:46 — // FIXME: Make calling this an error once SI-7383 is fixed
FixmeComment transport/server/play-pekko-http-server/src/main/scala/play/core/server/pekkohttp/PekkoModelConversion.scala:250 — // FIXME: should do something with the content-length? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment transport/server/play-pekko-http-server/src/main/scala/play/core/server/pekkohttp/PekkoModelConversion.scala:254 — // FIXME: do something with trailing headers? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5

Duplicated block (8 lines × 2) core/play/src/main/scala/play/api/mvc/Render.scala:35 — core/play/src/main/scala/play/api/mvc/Render.scala:35-42 | core/play/src/main/scala/play/api/mvc/Render.scala:66-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/scala/play/api/mvc/Render.scala:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) core/play/src/main/scala/play/utils/Colors.scala:24 — core/play/src/main/scala/play/utils/Colors.scala:24-31 | dev-mode/sbt-plugin/src/main/scala/play/sbt/Colors.scala:24-32 — before extracting anything, compare `core/play/src/main/scala/play/utils/Colors.scala` and `dev-mode/sbt-plugin/src/main/scala/play/sbt/Colors.scala` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) core/play-java/src/main/java/play/libs/Time.java:529 — core/play-java/src/main/java/play/libs/Time.java:529-536 | core/play-java/src/main/java/play/libs/Time.java:545-552 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:529` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) web/play-java-forms/src/main/java/play/data/Form.java:993 — web/play-java-forms/src/main/java/play/data/Form.java:993-1000 | web/play-java-forms/src/main/java/play/data/Form.java:1037-1044 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `web/play-java-forms/src/main/java/play/data/Form.java:993` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) web/play-java-forms/src/main/java/play/data/DynamicForm.java:265 — web/play-java-forms/src/main/java/play/data/DynamicForm.java:265-272 | web/play-java-forms/src/main/java/play/data/Form.java:849-856 — before extracting anything, compare `web/play-java-forms/src/main/java/play/data/DynamicForm.java` and `web/play-java-forms/src/main/java/play/data/Form.java` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5

Duplicated block (5 lines × 2) transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:180 — transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:180-184 | transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala:306-310 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) core/play-java/src/main/java/play/libs/Time.java:1418 — core/play-java/src/main/java/play/libs/Time.java:1418-1422 | core/play-java/src/main/java/play/libs/Time.java:1445-1449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:1418` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) core/play/src/main/java/play/mvc/Result.java:398 — core/play/src/main/java/play/mvc/Result.java:398-402 | core/play/src/main/java/play/mvc/WebSocket.java:667-671 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `Http.Request` in one and `Http.RequestHeader` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) web/play-java-forms/src/main/java/play/data/DynamicForm.java:280 — web/play-java-forms/src/main/java/play/data/DynamicForm.java:280-284 | web/play-java-forms/src/main/java/play/data/Form.java:893-897 — before extracting anything, compare `web/play-java-forms/src/main/java/play/data/DynamicForm.java` and `web/play-java-forms/src/main/java/play/data/Form.java` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `web/play-java-forms/src/main/java/play/data/DynamicForm.java:280` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:244 — web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:244-248 | web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:417-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:244` 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.

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

Low cohesion: CSRFActionHelper (LCOM4 5) web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala:400 — CSRFActionHelper's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ScalaStreamController (LCOM4 5) documentation/manual/working/scalaGuide/main/async/code/scalaguide/async/scalastream/ScalaStream.scala:24 — ScalaStreamController's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NettyServer (LCOM4 4) transport/server/play-netty-server/src/main/scala/play/core/server/NettyServer.scala:77 — NettyServer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ReloadCache (LCOM4 4) transport/server/play-server/src/main/scala/play/core/server/common/ReloadCache.scala:31 — ReloadCache's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ServerResultUtils (LCOM4 4) transport/server/play-server/src/main/scala/play/core/server/common/ServerResultUtils.scala:25 — ServerResultUtils's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×5

Swallowed exception (caught, then discarded) core/play/src/main/java/play/i18n/Lang.java:64 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) project/BuildSettings.scala:41 — `case NonFatal(_)` 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) web/play-java-forms/src/main/java/play/data/DynamicForm.java:196 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) web/play-java-forms/src/main/java/play/data/DynamicForm.java:214 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) web/play-java-forms/src/main/java/play/data/internal/binding/beans/CachedIntrospectionResults.java:315 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×3

Duplicated block (8 lines × 3) web/play-filters-helpers/src/main/scala/play/filters/csp/CSPConfig.scala:88 — web/play-filters-helpers/src/main/scala/play/filters/csp/CSPConfig.scala:88-95 | web/play-filters-helpers/src/main/scala/play/filters/csrf/csrf.scala:136-143 | web/play-filters-helpers/src/main/scala/play/filters/ip/IPFilter.scala:232-239 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 3) core/play-java/src/main/java/play/libs/Time.java:1256 — core/play-java/src/main/java/play/libs/Time.java:1256-1264 | core/play-java/src/main/java/play/libs/Time.java:1300-1307 | core/play-java/src/main/java/play/libs/Time.java:1343-1350 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:1256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) cache/play-cache/src/main/java/play/cache/NamedCacheImpl.java:28 — cache/play-cache/src/main/java/play/cache/NamedCacheImpl.java:28-35 | core/play/src/main/java/play/inject/NamedImpl.java:34-41 | persistence/play-jdbc-api/src/main/java/play/db/NamedDatabaseImpl.java:28-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3

Duplicated block (6 lines × 2) core/play/src/main/scala/play/api/i18n/Messages.scala:151 — core/play/src/main/scala/play/api/i18n/Messages.scala:151-156 | dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesFileParser.scala:149-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) documentation/manual/working/scalaGuide/advanced/embedding/code/ScalaNettyEmbeddingPlay.scala:141 — documentation/manual/working/scalaGuide/advanced/embedding/code/ScalaNettyEmbeddingPlay.scala:141-146 | documentation/manual/working/scalaGuide/advanced/embedding/code/ScalaPekkoEmbeddingPlay.scala:192-197 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) dev-mode/play-run-support/src/main/java/play/runsupport/DevServerSettings.java:120 — dev-mode/play-run-support/src/main/java/play/runsupport/DevServerSettings.java:120-125 | dev-mode/play-run-support/src/main/java/play/runsupport/DevServerSettings.java:130-135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

X3 · Exception handling · Swallowed exception (empty catch) · ×3

Swallowed exception (empty catch) core/play-java/src/main/java/play/libs/Time.java:1540 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:214 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) web/play-java-forms/src/main/java/play/data/Form.java:1698 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×2

Focus outline removed in CSS without a :focus replacement documentation/style/main.css:5 — `object` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement documentation/style/main.css:13 — `:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.

D1 · Cyclomatic Complexity · DevServerStart.mainDev (cyclomatic 22) · ×2

DevServerStart.mainDev (cyclomatic 22) transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:88 — DevServerStart.mainDev has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (DevServerStart.mainDev) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DevServerStart.mainDev (cyclomatic 22) transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:164 — DevServerStart.mainDev has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (DevServerStart.mainDev) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · DevServerStart.mainDev (cognitive 23) · ×2

DevServerStart.mainDev (cognitive 23) transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:88 — DevServerStart.mainDev has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (14 pts), error handling 5, match/switch 3 (4 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (DevServerStart.mainDev) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DevServerStart.mainDev (cognitive 23) transport/server/play-server/src/main/scala/play/core/server/DevServerStart.scala:164 — DevServerStart.mainDev has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (14 pts), error handling 5, match/switch 3 (4 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (DevServerStart.mainDev) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

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

REDACTED
REDACTED

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (4 members, 50+ identical tokens) core/play/src/main/java/play/libs/F.java:107 — core/play/src/main/java/play/libs/F.java:107-119 | core/play/src/main/java/play/libs/F.java:164-179 | core/play/src/main/java/play/libs/F.java:227-245 | core/play/src/main/java/play/libs/F.java:298-319 — 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) web/play-java-forms/src/main/java/play/data/DynamicForm.java:375 — web/play-java-forms/src/main/java/play/data/DynamicForm.java:375-390 | web/play-java-forms/src/main/java/play/data/DynamicForm.java:393-406 | web/play-java-forms/src/main/java/play/data/DynamicForm.java:414-427 | web/play-java-forms/src/main/java/play/data/DynamicForm.java:435-448 — 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 (11 lines × 2) · ×2

Duplicated block (11 lines × 2) dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:287 — dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:287-297 | dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:308-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dev-mode/sbt-scripted-tools/src/main/scala/play/sbt/scriptedtools/ScriptedTools.scala:287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) dev-mode/gradle-plugin/src/main/java/play/gradle/task/RoutesCompile.java:75 — dev-mode/gradle-plugin/src/main/java/play/gradle/task/RoutesCompile.java:75-85 | dev-mode/gradle-plugin/src/main/java/play/gradle/task/RoutesCompile.java:97-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dev-mode/gradle-plugin/src/main/java/play/gradle/task/RoutesCompile.java:75` 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 (10 lines × 2) · ×2

Duplicated block (10 lines × 2) documentation/manual/working/javaGuide/main/http/code/javaguide/http/JavaErrorHandling.scala:16 — documentation/manual/working/javaGuide/main/http/code/javaguide/http/JavaErrorHandling.scala:16-25 | documentation/manual/working/scalaGuide/main/http/code/ScalaErrorHandling.scala:15-24 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) web/play-java-forms/src/main/java/play/data/DynamicForm.java:299 — web/play-java-forms/src/main/java/play/data/DynamicForm.java:299-308 | web/play-java-forms/src/main/java/play/data/Form.java:940-949 — before extracting anything, compare `web/play-java-forms/src/main/java/play/data/DynamicForm.java` and `web/play-java-forms/src/main/java/play/data/Form.java` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2

Duplicated block (5 lines × 3) dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesGenerator.scala:188 — dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesGenerator.scala:188-192 | dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesGenerator.scala:216-220 | dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesGenerator.scala:244-248 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesGenerator.scala:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) core/play/src/main/java/play/libs/F.java:155 — core/play/src/main/java/play/libs/F.java:155-159 | core/play/src/main/java/play/libs/F.java:218-222 | core/play/src/main/java/play/libs/F.java:288-292 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/play/src/main/java/play/libs/F.java:223` calls `hashCode` and `core/play/src/main/java/play/libs/F.java:160` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2

Duplicated block (9 lines × 3) core/play-java/src/main/java/play/libs/XPath.java:84 — core/play-java/src/main/java/play/libs/XPath.java:84-92 | core/play-java/src/main/java/play/libs/XPath.java:113-121 | core/play-java/src/main/java/play/libs/XPath.java:150-158 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/XPath.java:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) core/play/src/main/java/play/mvc/BodyParser.java:126 — core/play/src/main/java/play/mvc/BodyParser.java:126-134 | core/play/src/main/java/play/mvc/BodyParser.java:169-177 | core/play/src/main/java/play/mvc/BodyParser.java:182-190 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/java/play/mvc/BodyParser.java:126` 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 (9 lines × 2) · ×2

Duplicated block (9 lines × 2) web/play-java-forms/src/main/java/play/data/Form.java:2018 — web/play-java-forms/src/main/java/play/data/Form.java:2018-2026 | web/play-java-forms/src/main/java/play/data/Form.java:2052-2060 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `web/play-java-forms/src/main/java/play/data/Form.java:2018` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) web/play-java-forms/src/main/java/play/data/validation/Constraints.java:713 — web/play-java-forms/src/main/java/play/data/validation/Constraints.java:713-721 | web/play-java-forms/src/main/java/play/data/validation/Constraints.java:787-795 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (7 lines × 2) core/play/src/main/java/play/http/DefaultHttpErrorHandler.java:229 — core/play/src/main/java/play/http/DefaultHttpErrorHandler.java:229-235 | core/play/src/main/java/play/http/JsonHttpErrorHandler.java:128-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) web/play-java-forms/src/main/java/play/data/DynamicForm.java:288 — web/play-java-forms/src/main/java/play/data/DynamicForm.java:288-294 | web/play-java-forms/src/main/java/play/data/Form.java:915-921 — before extracting anything, compare `web/play-java-forms/src/main/java/play/data/DynamicForm.java` and `web/play-java-forms/src/main/java/play/data/Form.java` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

S1 · Web-Security Posture · Weak hash algorithm · ×2

Weak hash algorithm core/play/src/main/scala/play/api/libs/Codecs.scala:17 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm core/play/src/main/scala/play/api/libs/Codecs.scala:18 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.

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

Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 37 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · WebSocketFlowHandler.webSocketProtocol (cyclomatic 79) · ×1

WebSocketFlowHandler.webSocketProtocol (cyclomatic 79) transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:58 — WebSocketFlowHandler.webSocketProtocol has cyclomatic complexity 79 (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 · CronExpression.getTimeAfter (cyclomatic 63) · ×1

CronExpression.getTimeAfter (cyclomatic 63) core/play-java/src/main/java/play/libs/Time.java:1083 — CronExpression.getTimeAfter has cyclomatic complexity 63 (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 · CronExpression.storeExpressionVals (cyclomatic 62) · ×1

CronExpression.storeExpressionVals (cyclomatic 62) core/play-java/src/main/java/play/libs/Time.java:515 — CronExpression.storeExpressionVals has cyclomatic complexity 62 (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 · CronExpression.addToSet (cyclomatic 54) · ×1

CronExpression.addToSet (cyclomatic 54) core/play-java/src/main/java/play/libs/Time.java:920 — CronExpression.addToSet has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · BodyPartParser.createLogic (cyclomatic 48) · ×1

BodyPartParser.createLogic (cyclomatic 48) core/play/src/main/scala/play/core/parsers/Multipart.scala:377 — BodyPartParser.createLogic has cyclomatic complexity 48 (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 · TypeConverterDelegate.convertIfNecessary (cyclomatic 38) · ×1

TypeConverterDelegate.convertIfNecessary (cyclomatic 38) web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java:98 — TypeConverterDelegate.convertIfNecessary has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ClassUtils.isAssignable (cyclomatic 26) · ×1

ClassUtils.isAssignable (cyclomatic 26) core/play/src/main/java/play/libs/reflect/ClassUtils.java:90 — ClassUtils.isAssignable 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 · Form.field (cyclomatic 26) · ×1

Form.field (cyclomatic 26) web/play-java-forms/src/main/java/play/data/Form.java:1641 — Form.field 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 · CronExpression.checkNext (cyclomatic 24) · ×1

CronExpression.checkNext (cyclomatic 24) core/play-java/src/main/java/play/libs/Time.java:685 — CronExpression.checkNext 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 · AbstractNestablePropertyAccessor.getPropertyValue (cyclomatic 23) · ×1

AbstractNestablePropertyAccessor.getPropertyValue (cyclomatic 23) web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:477 — AbstractNestablePropertyAccessor.getPropertyValue has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GeneratedRouter.call (cyclomatic 22) · ×1

GeneratedRouter.call (cyclomatic 22) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:433 — GeneratedRouter.call has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · AnyContent.apply (cyclomatic 22) · ×1

AnyContent.apply (cyclomatic 22) core/play/src/main/java/play/mvc/BodyParser.java:119 — AnyContent.apply has cyclomatic complexity 22 (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 · Formats.parse (cyclomatic 22) · ×1

Formats.parse (cyclomatic 22) web/play-java-forms/src/main/java/play/data/format/Formats.java:80 — Formats.parse has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GeneratedRouter.call (cyclomatic 21) · ×1

GeneratedRouter.call (cyclomatic 21) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:407 — GeneratedRouter.call has cyclomatic complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · NettyModelConversion.convertResult (cyclomatic 21) · ×1

NettyModelConversion.convertResult (cyclomatic 21) transport/server/play-netty-server/src/main/scala/play/core/server/netty/NettyModelConversion.scala:245 — NettyModelConversion.convertResult has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ClientCookieDecoder.decode (cyclomatic 21) · ×1

ClientCookieDecoder.decode (cyclomatic 21) core/play/src/main/java/play/core/cookie/encoding/ClientCookieDecoder.java:51 — ClientCookieDecoder.decode has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GeneratedRouter.call (cyclomatic 20) · ×1

GeneratedRouter.call (cyclomatic 20) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:382 — GeneratedRouter.call has cyclomatic complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · IPFilterConfig.parseMatcher (cyclomatic 20) · ×1

IPFilterConfig.parseMatcher (cyclomatic 20) web/play-filters-helpers/src/main/scala/play/filters/ip/IPFilter.scala:129 — IPFilterConfig.parseMatcher has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ServerCookieDecoder.decode (cyclomatic 20) · ×1

ServerCookieDecoder.decode (cyclomatic 20) core/play/src/main/java/play/core/cookie/encoding/ServerCookieDecoder.java:62 — ServerCookieDecoder.decode has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GeneratedRouter.call (cyclomatic 19) · ×1

GeneratedRouter.call (cyclomatic 19) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:358 — GeneratedRouter.call has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · Tuple5.equals (cyclomatic 19) · ×1

Tuple5.equals (cyclomatic 19) core/play/src/main/java/play/libs/F.java:298 — Tuple5.equals has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ObjectUtils.arrayEquals (cyclomatic 19) · ×1

ObjectUtils.arrayEquals (cyclomatic 19) web/play-java-forms/src/main/java/play/data/internal/binding/util/ObjectUtils.java:171 — ObjectUtils.arrayEquals has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · RequestHeader.initialRequestTarget (cyclomatic 18) · ×1

RequestHeader.initialRequestTarget (cyclomatic 18) core/play/src/main/scala/play/api/mvc/RequestHeader.scala:565 — RequestHeader.initialRequestTarget has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · GeneratedRouter.call (cyclomatic 18) · ×1

GeneratedRouter.call (cyclomatic 18) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:335 — GeneratedRouter.call has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · ForwardedHeaderHandlerConfig.forwardedHeaders (cyclomatic 18) · ×1

ForwardedHeaderHandlerConfig.forwardedHeaders (cyclomatic 18) transport/server/play-server/src/main/scala/play/core/server/common/ForwardedHeaderHandler.scala:297 — ForwardedHeaderHandlerConfig.forwardedHeaders 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 · CachedIntrospectionResults.<init> (cyclomatic 18) · ×1

CachedIntrospectionResults.<init> (cyclomatic 18) web/play-java-forms/src/main/java/play/data/internal/binding/beans/CachedIntrospectionResults.java:201 — CachedIntrospectionResults.<init> 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 · TypeConverterDelegate.convertToTypedMap (cyclomatic 18) · ×1

TypeConverterDelegate.convertToTypedMap (cyclomatic 18) web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java:352 — TypeConverterDelegate.convertToTypedMap 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 · GeneratedRouter.call (cyclomatic 17) · ×1

GeneratedRouter.call (cyclomatic 17) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:313 — GeneratedRouter.call has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · GuiceableModuleConversions.guice (cyclomatic 16) · ×1

GuiceableModuleConversions.guice (cyclomatic 16) core/play-guice/src/main/scala/play/api/inject/guice/GuiceInjectorBuilder.scala:374 — GuiceableModuleConversions.guice has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · PlayBodyParsers.anyContent (cyclomatic 16) · ×1

PlayBodyParsers.anyContent (cyclomatic 16) core/play/src/main/scala/play/api/mvc/BodyParsers.scala:941 — PlayBodyParsers.anyContent has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GeneratedRouter.call (cyclomatic 16) · ×1

GeneratedRouter.call (cyclomatic 16) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:292 — GeneratedRouter.call has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · FieldParser.parse (cyclomatic 16) · ×1

FieldParser.parse (cyclomatic 16) transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala:376 — FieldParser.parse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Tuple4.equals (cyclomatic 16) · ×1

Tuple4.equals (cyclomatic 16) core/play/src/main/java/play/libs/F.java:227 — Tuple4.equals has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · TypeConverterDelegate.convertToTypedCollection (cyclomatic 16) · ×1

TypeConverterDelegate.convertToTypedCollection (cyclomatic 16) web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java:292 — TypeConverterDelegate.convertToTypedCollection has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D15 · Churn × Complexity Hotspots · Hotspot · ×1

Hotspot: transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:58 — transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in WebSocketFlowHandler.webSocketProtocol at line 58. 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 00:50:53 +02:00' --until='2026-10-23 00:50:53 +02:00' --full-history --no-merges -- transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala`: 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 · GeneratedRouter.call (cognitive 231) · ×1

GeneratedRouter.call (cognitive 231) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:433 — GeneratedRouter.call has cognitive complexity 231 (threshold 15). Drivers by points: loops 21 (231 pts) (nesting depth added 210). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 210) · ×1

GeneratedRouter.call (cognitive 210) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:407 — GeneratedRouter.call has cognitive complexity 210 (threshold 15). Drivers by points: loops 20 (210 pts) (nesting depth added 190). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 190) · ×1

GeneratedRouter.call (cognitive 190) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:382 — GeneratedRouter.call has cognitive complexity 190 (threshold 15). Drivers by points: loops 19 (190 pts) (nesting depth added 171). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 171) · ×1

GeneratedRouter.call (cognitive 171) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:358 — GeneratedRouter.call has cognitive complexity 171 (threshold 15). Drivers by points: loops 18 (171 pts) (nesting depth added 153). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 153) · ×1

GeneratedRouter.call (cognitive 153) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:335 — GeneratedRouter.call has cognitive complexity 153 (threshold 15). Drivers by points: loops 17 (153 pts) (nesting depth added 136). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · CronExpression.getTimeAfter (cognitive 144) · ×1

CronExpression.getTimeAfter (cognitive 144) core/play-java/src/main/java/play/libs/Time.java:1083 — CronExpression.getTimeAfter has cognitive complexity 144 (threshold 15). Drivers by points: if/else 53 (123 pts), boolean chains 16, loops 2 (5 pts) (nesting depth added 73). 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 · GeneratedRouter.call (cognitive 136) · ×1

GeneratedRouter.call (cognitive 136) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:313 — GeneratedRouter.call has cognitive complexity 136 (threshold 15). Drivers by points: loops 16 (136 pts) (nesting depth added 120). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · CronExpression.storeExpressionVals (cognitive 122) · ×1

CronExpression.storeExpressionVals (cognitive 122) core/play-java/src/main/java/play/libs/Time.java:515 — CronExpression.storeExpressionVals has cognitive complexity 122 (threshold 15). Drivers by points: if/else 46 (99 pts), boolean chains 18, error handling 1 (5 pts) (nesting depth added 57). 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 · GeneratedRouter.call (cognitive 120) · ×1

GeneratedRouter.call (cognitive 120) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:292 — GeneratedRouter.call has cognitive complexity 120 (threshold 15). Drivers by points: loops 15 (120 pts) (nesting depth added 105). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · WebSocketFlowHandler.webSocketProtocol (cognitive 113) · ×1

WebSocketFlowHandler.webSocketProtocol (cognitive 113) transport/server/play-server/src/main/scala/play/core/server/common/WebSocketFlowHandler.scala:58 — WebSocketFlowHandler.webSocketProtocol has cognitive complexity 113 (threshold 15). Drivers by points: if/else 54 (80 pts), match/switch 12 (21 pts), boolean chains 10, 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 · GeneratedRouter.call (cognitive 105) · ×1

GeneratedRouter.call (cognitive 105) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:272 — GeneratedRouter.call has cognitive complexity 105 (threshold 15). Drivers by points: loops 14 (105 pts) (nesting depth added 91). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 91) · ×1

GeneratedRouter.call (cognitive 91) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:253 — GeneratedRouter.call has cognitive complexity 91 (threshold 15). Drivers by points: loops 13 (91 pts) (nesting depth added 78). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 78) · ×1

GeneratedRouter.call (cognitive 78) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:235 — GeneratedRouter.call has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · CronExpression.addToSet (cognitive 72) · ×1

CronExpression.addToSet (cognitive 72) core/play-java/src/main/java/play/libs/Time.java:920 — CronExpression.addToSet has cognitive complexity 72 (threshold 15). Drivers by points: if/else 32 (50 pts), boolean chains 21, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BodyPartParser.createLogic (cognitive 70) · ×1

BodyPartParser.createLogic (cognitive 70) core/play/src/main/scala/play/core/parsers/Multipart.scala:377 — BodyPartParser.createLogic has cognitive complexity 70 (threshold 15). Drivers by points: if/else 44 (55 pts), error handling 6, match/switch 4 (5 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · TypeConverterDelegate.convertIfNecessary (cognitive 70) · ×1

TypeConverterDelegate.convertIfNecessary (cognitive 70) web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java:98 — TypeConverterDelegate.convertIfNecessary has cognitive complexity 70 (threshold 15). Drivers by points: if/else 29 (59 pts), boolean chains 8, error handling 1 (3 pts) (nesting depth added 32). 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 · GeneratedRouter.call (cognitive 66) · ×1

GeneratedRouter.call (cognitive 66) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:218 — GeneratedRouter.call has cognitive complexity 66 (threshold 15). Drivers by points: loops 11 (66 pts) (nesting depth added 55). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · Form.field (cognitive 56) · ×1

Form.field (cognitive 56) web/play-java-forms/src/main/java/play/data/Form.java:1641 — Form.field has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (29 pts), error handling 3 (11 pts), loops 3 (9 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 55) · ×1

GeneratedRouter.call (cognitive 55) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:202 — GeneratedRouter.call has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · ClientCookieDecoder.decode (cognitive 50) · ×1

ClientCookieDecoder.decode (cognitive 50) core/play/src/main/java/play/core/cookie/encoding/ClientCookieDecoder.java:51 — ClientCookieDecoder.decode has cognitive complexity 50 (threshold 15). Drivers by points: if/else 15 (34 pts), ternaries 2 (8 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AbstractNestablePropertyAccessor.getPropertyValue (cognitive 47) · ×1

AbstractNestablePropertyAccessor.getPropertyValue (cognitive 47) web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:477 — AbstractNestablePropertyAccessor.getPropertyValue has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (34 pts), loops 2 (6 pts), error handling 5, boolean chains 2 (nesting depth added 23). 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 · GeneratedRouter.call (cognitive 45) · ×1

GeneratedRouter.call (cognitive 45) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:187 — GeneratedRouter.call has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · ServerCookieDecoder.decode (cognitive 44) · ×1

ServerCookieDecoder.decode (cognitive 44) core/play/src/main/java/play/core/cookie/encoding/ServerCookieDecoder.java:62 — ServerCookieDecoder.decode has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (30 pts), loops 3 (6 pts), ternaries 1 (5 pts), boolean chains 3 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CronExpression.checkNext (cognitive 42) · ×1

CronExpression.checkNext (cognitive 42) core/play-java/src/main/java/play/libs/Time.java:685 — CronExpression.checkNext has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (35 pts), boolean chains 5, error handling 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ClassUtils.isAssignable (cognitive 40) · ×1

ClassUtils.isAssignable (cognitive 40) core/play/src/main/java/play/libs/reflect/ClassUtils.java:90 — ClassUtils.isAssignable has cognitive complexity 40 (threshold 15). Drivers by points: if/else 18 (33 pts), boolean chains 7 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RequestHeader.initialRequestTarget (cognitive 38) · ×1

RequestHeader.initialRequestTarget (cognitive 38) core/play/src/main/scala/play/api/mvc/RequestHeader.scala:565 — RequestHeader.initialRequestTarget has cognitive complexity 38 (threshold 15). Drivers by points: loops 3 (18 pts), if/else 8 (9 pts), match/switch 3 (9 pts), boolean chains 2 (nesting depth added 22). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 36) · ×1

GeneratedRouter.call (cognitive 36) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:173 — GeneratedRouter.call has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · Segment.restructure (cognitive 36) · ×1

Segment.restructure (cognitive 36) web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java:682 — Segment.restructure has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 5 (12 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AbstractCORSPolicy.handlePreFlightCORSRequest (cognitive 32) · ×1

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

D2 · Cognitive Complexity · IPFilterConfig.parseMatcher (cognitive 32) · ×1

IPFilterConfig.parseMatcher (cognitive 32) web/play-filters-helpers/src/main/scala/play/filters/ip/IPFilter.scala:129 — IPFilterConfig.parseMatcher has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (19 pts), error handling 3 (7 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · NettyModelConversion.convertResult (cognitive 31) · ×1

NettyModelConversion.convertResult (cognitive 31) transport/server/play-netty-server/src/main/scala/play/core/server/netty/NettyModelConversion.scala:245 — NettyModelConversion.convertResult has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (27 pts), match/switch 3 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RequireCSRFCheckAction.call (cognitive 31) · ×1

RequireCSRFCheckAction.call (cognitive 31) web/play-filters-helpers/src/main/java/play/filters/csrf/RequireCSRFCheckAction.java:73 — RequireCSRFCheckAction.call has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 4 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · PropertyDescriptorUtils.determineBasicProperties (cognitive 29) · ×1

PropertyDescriptorUtils.determineBasicProperties (cognitive 29) web/play-java-forms/src/main/java/play/data/internal/binding/beans/PropertyDescriptorUtils.java:59 — PropertyDescriptorUtils.determineBasicProperties has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 2 (6 pts), boolean chains 4, loops 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.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 28) · ×1

GeneratedRouter.call (cognitive 28) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:160 — GeneratedRouter.call has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · Formats.parse (cognitive 28) · ×1

Formats.parse (cognitive 28) web/play-java-forms/src/main/java/play/data/format/Formats.java:80 — Formats.parse has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14, ternaries 7 (14 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 · ForwardedHeaderHandlerConfig.forwardedHeaders (cognitive 24) · ×1

ForwardedHeaderHandlerConfig.forwardedHeaders (cognitive 24) transport/server/play-server/src/main/scala/play/core/server/common/ForwardedHeaderHandler.scala:297 — ForwardedHeaderHandlerConfig.forwardedHeaders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6, match/switch 2 (3 pts) (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · AbstractNestablePropertyAccessor.processKeyedProperty (cognitive 24) · ×1

AbstractNestablePropertyAccessor.processKeyedProperty (cognitive 24) web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:211 — AbstractNestablePropertyAccessor.processKeyedProperty has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 3 (9 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CachedIntrospectionResults.<init> (cognitive 24) · ×1

CachedIntrospectionResults.<init> (cognitive 24) web/play-java-forms/src/main/java/play/data/internal/binding/beans/CachedIntrospectionResults.java:201 — CachedIntrospectionResults.<init> has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 6, ternaries 1 (3 pts), loops 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Tuple5.equals (cognitive 23) · ×1

Tuple5.equals (cognitive 23) core/play/src/main/java/play/libs/F.java:298 — Tuple5.equals has cognitive complexity 23 (threshold 15). Drivers by points: if/else 18 (23 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · CachedIntrospectionResults.introspectInterfaces (cognitive 23) · ×1

CachedIntrospectionResults.introspectInterfaces (cognitive 23) web/play-java-forms/src/main/java/play/data/internal/binding/beans/CachedIntrospectionResults.java:261 — CachedIntrospectionResults.introspectInterfaces has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BasicPropertyDescriptor.getWriteMethod (cognitive 23) · ×1

BasicPropertyDescriptor.getWriteMethod (cognitive 23) web/play-java-forms/src/main/java/play/data/internal/binding/beans/PropertyDescriptorUtils.java:173 — BasicPropertyDescriptor.getWriteMethod has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · PlayBodyParsers.anyContent (cognitive 22) · ×1

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

D2 · Cognitive Complexity · CSRFAction.extractTokenFromMultipartFormDataBody (cognitive 22) · ×1

CSRFAction.extractTokenFromMultipartFormDataBody (cognitive 22) web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala:228 — CSRFAction.extractTokenFromMultipartFormDataBody has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AnyContent.apply (cognitive 22) · ×1

AnyContent.apply (cognitive 22) core/play/src/main/java/play/mvc/BodyParser.java:119 — AnyContent.apply has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (7 pts), ternaries 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ResolvableType.getGenerics (cognitive 22) · ×1

ResolvableType.getGenerics (cognitive 22) web/play-java-forms/src/main/java/play/data/internal/binding/core/ResolvableType.java:431 — ResolvableType.getGenerics has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (8 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 · Field.indexes (cognitive 22) · ×1

Field.indexes (cognitive 22) web/play-java-forms/src/main/java/play/data/Form.java:1996 — Field.indexes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GeneratedRouter.call (cognitive 21) · ×1

GeneratedRouter.call (cognitive 21) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:148 — GeneratedRouter.call has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: core/play/src/main/scala/play/core/routing/GeneratedRouter.scala holds 16 of the 73 methods over the threshold — including the worst — and 1496 of the 2504 points over it (60%), 4.7× the next-largest file (core/play-java/src/main/java/play/libs/Time.java at 320). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · ForwardedHeaderHandler.parse (cognitive 21) · ×1

ForwardedHeaderHandler.parse (cognitive 21) transport/server/play-server/src/main/scala/play/core/server/common/ForwardedHeaderHandler.scala:136 — ForwardedHeaderHandler.parse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 4 (9 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TypeConverterDelegate.convertToTypedMap (cognitive 21) · ×1

TypeConverterDelegate.convertToTypedMap (cognitive 21) web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java:352 — TypeConverterDelegate.convertToTypedMap has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 5, boolean chains 4, error handling 3 (4 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · PatternMatchUtils.simpleMatch (cognitive 21) · ×1

PatternMatchUtils.simpleMatch (cognitive 21) web/play-java-forms/src/main/java/play/data/internal/binding/util/PatternMatchUtils.java:44 — PatternMatchUtils.simpleMatch has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RouterBuilderHelper.build (cognitive 20) · ×1

RouterBuilderHelper.build (cognitive 20) core/play-java/src/main/scala/play/routing/RouterBuilderHelper.scala:22 — RouterBuilderHelper.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 3 (7 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FieldParser.parse (cognitive 20) · ×1

FieldParser.parse (cognitive 20) transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala:376 — FieldParser.parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AbstractNestablePropertyAccessor.getPropertyNameTokens (cognitive 20) · ×1

AbstractNestablePropertyAccessor.getPropertyNameTokens (cognitive 20) web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:803 — AbstractNestablePropertyAccessor.getPropertyNameTokens has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ObjectUtils.nullSafeHashCode (cognitive 20) · ×1

ObjectUtils.nullSafeHashCode (cognitive 20) web/play-java-forms/src/main/java/play/data/internal/binding/util/ObjectUtils.java:231 — ObjectUtils.nullSafeHashCode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (20 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DatabaseEvolutions.evolve (cognitive 19) · ×1

DatabaseEvolutions.evolve (cognitive 19) persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/EvolutionsApi.scala:368 — DatabaseEvolutions.evolve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (4 pts), error handling 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ByteSequenceParser.parseNumber (cognitive 19) · ×1

ByteSequenceParser.parseNumber (cognitive 19) transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:307 — ByteSequenceParser.parseNumber has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Tuple4.equals (cognitive 19) · ×1

Tuple4.equals (cognitive 19) core/play/src/main/java/play/libs/F.java:227 — Tuple4.equals has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (19 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · Formats.parseNumber (cognitive 19) · ×1

Formats.parseNumber (cognitive 19) web/play-java-forms/src/main/java/play/data/format/Formats.java:223 — Formats.parseNumber has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 9 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CSRFConfig.fromConfiguration (cognitive 18) · ×1

CSRFConfig.fromConfiguration (cognitive 18) web/play-filters-helpers/src/main/scala/play/filters/csrf/csrf.scala:107 — CSRFConfig.fromConfiguration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · GzipFilterConfig.fromConfiguration (cognitive 18) · ×1

GzipFilterConfig.fromConfiguration (cognitive 18) web/play-filters-helpers/src/main/scala/play/filters/gzip/GzipFilter.scala:230 — GzipFilterConfig.fromConfiguration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 4). 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 · TypeConverterDelegate.convertToTypedCollection (cognitive 18) · ×1

TypeConverterDelegate.convertToTypedCollection (cognitive 18) web/play-java-forms/src/main/java/play/data/internal/binding/beans/TypeConverterDelegate.java:292 — TypeConverterDelegate.convertToTypedCollection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5, boolean chains 4, error handling 3 (4 pts), ternaries 3 (4 pts), loops 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ObjectUtils.arrayEquals (cognitive 18) · ×1

ObjectUtils.arrayEquals (cognitive 18) web/play-java-forms/src/main/java/play/data/internal/binding/util/ObjectUtils.java:171 — ObjectUtils.arrayEquals has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 9. 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 · GuiceableModuleConversions.guice (cognitive 17) · ×1

GuiceableModuleConversions.guice (cognitive 17) core/play-guice/src/main/scala/play/api/inject/guice/GuiceInjectorBuilder.scala:374 — GuiceableModuleConversions.guice has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 4 (6 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · BinderMacros.withAnyValParam (cognitive 17) · ×1

BinderMacros.withAnyValParam (cognitive 17) core/play/src/main/scala-3/play/api/mvc/macros/BinderMacros.scala:21 — BinderMacros.withAnyValParam has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 2 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · UriEncoding.decodePathSegment (cognitive 17) · ×1

UriEncoding.decodePathSegment (cognitive 17) core/play/src/main/scala/play/utils/UriEncoding.scala:105 — UriEncoding.decodePathSegment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ObjectUtils.nullSafeConciseToString (cognitive 17) · ×1

ObjectUtils.nullSafeConciseToString (cognitive 17) web/play-java-forms/src/main/java/play/data/internal/binding/util/ObjectUtils.java:587 — ObjectUtils.nullSafeConciseToString has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · CSRFAction.apply (cognitive 16) · ×1

CSRFAction.apply (cognitive 16) web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala:62 — CSRFAction.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BodyHandler.createLogic (cognitive 16) · ×1

BodyHandler.createLogic (cognitive 16) web/play-filters-helpers/src/main/scala/play/filters/csrf/CSRFActions.scala:332 — BodyHandler.createLogic has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · RedirectHttpsFilter.apply (cognitive 16) · ×1

RedirectHttpsFilter.apply (cognitive 16) web/play-filters-helpers/src/main/scala/play/filters/https/RedirectHttpsFilter.scala:56 — RedirectHttpsFilter.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MethodUtils.getMatchingAccessibleMethod (cognitive 16) · ×1

MethodUtils.getMatchingAccessibleMethod (cognitive 16) core/play/src/main/java/play/libs/reflect/MethodUtils.java:149 — MethodUtils.getMatchingAccessibleMethod has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, error handling 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultJPAApi.withTransaction (cognitive 16) · ×1

DefaultJPAApi.withTransaction (cognitive 16) persistence/play-java-jpa/src/main/java/play/db/jpa/DefaultJPAApi.java:151 — DefaultJPAApi.withTransaction has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

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

REDACTED

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

REDACTED

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

REDACTED

D4 · Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (12 members, 50+ identical tokens) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:202 — core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:202-216 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:218-233 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:235-251 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:253-270 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:272-290 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:292-311 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:313-333 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:335-356 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:358-380 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:382-405 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:407-431 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:433-458 — These 12 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 12 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 12 times.

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

Duplicated block (26 lines × 2) documentation/manual/working/commonGuide/pekko/code/scalaguide/pekko/typed/fp/multi/AppModule.scala:21 — documentation/manual/working/commonGuide/pekko/code/scalaguide/pekko/typed/fp/multi/AppModule.scala:21-46 | documentation/manual/working/commonGuide/pekko/code/scalaguide/pekko/typed/oo/multi/AppModule.scala:21-46 — before extracting anything, compare `documentation/manual/working/commonGuide/pekko/code/scalaguide/pekko/typed/fp/multi/AppModule.scala` and `documentation/manual/working/commonGuide/pekko/code/scalaguide/pekko/typed/oo/multi/AppModule.scala` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (10–11 lines × 12) · ×1

Duplicated block (10–11 lines × 12) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:203 — core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:203-212 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:219-229 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:236-246 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:254-264 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:273-283 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:293-303 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:314-324 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:336-346 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:359-369 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:383-393 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:408-418 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:434-444 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:203` 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 (9–10 lines × 2) · ×1

Duplicated block (9–10 lines × 2) core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:419 — core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:419-427 | core/play/src/main/scala/play/core/routing/GeneratedRouter.scala:445-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1

Duplicated block (8–9 lines × 2) transport/server/play-netty-server/src/main/scala/play/core/server/netty/NettyModelConversion.scala:192 — transport/server/play-netty-server/src/main/scala/play/core/server/netty/NettyModelConversion.scala:192-200 | transport/server/play-pekko-http-server/src/main/scala/play/core/server/pekkohttp/PekkoModelConversion.scala:158-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `transport/server/play-netty-server/src/main/scala/play/core/server/netty/NettyModelConversion.scala:192` 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.

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

Duplicated block (224 lines × 2) documentation/manual/working/scalaGuide/main/cache/code/ScalaCache.scala:24 — documentation/manual/working/scalaGuide/main/cache/code/ScalaCache.scala:24-247 | documentation/manual/working/scalaGuide/main/cache/code/ScalaEhCache.scala:24-247 — before extracting anything, compare `documentation/manual/working/scalaGuide/main/cache/code/ScalaCache.scala` and `documentation/manual/working/scalaGuide/main/cache/code/ScalaEhCache.scala` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `documentation/manual/working/scalaGuide/main/cache/code/ScalaCache.scala:24` 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 (50–52 lines × 2) · ×1

Duplicated block (50–52 lines × 2) core/play/src/main/java/play/core/cookie/encoding/ClientCookieDecoder.java:78 — core/play/src/main/java/play/core/cookie/encoding/ClientCookieDecoder.java:78-127 | core/play/src/main/java/play/core/cookie/encoding/ServerCookieDecoder.java:93-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/java/play/core/cookie/encoding/ClientCookieDecoder.java:78` 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.

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

Duplicated block (27 lines × 2) core/play-java/src/main/java/play/libs/Time.java:1181 — core/play-java/src/main/java/play/libs/Time.java:1181-1207 | core/play-java/src/main/java/play/libs/Time.java:1217-1243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:1181` 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 (23 lines × 2) · ×1

Duplicated block (23 lines × 2) core/play-java/src/main/java/play/libs/Time.java:854 — core/play-java/src/main/java/play/libs/Time.java:854-876 | core/play-java/src/main/java/play/libs/Time.java:880-902 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

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

Duplicated block (19 lines × 2) core/play-java/src/main/java/play/libs/Time.java:1271 — core/play-java/src/main/java/play/libs/Time.java:1271-1289 | core/play-java/src/main/java/play/libs/Time.java:1360-1378 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:1271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (14 lines × 2) core/play-java/src/main/java/play/libs/Time.java:759 — core/play-java/src/main/java/play/libs/Time.java:759-772 | core/play-java/src/main/java/play/libs/Time.java:785-798 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:759` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1

Duplicated block (12 lines × 4) web/play-java-forms/src/main/java/play/data/DynamicForm.java:379 — web/play-java-forms/src/main/java/play/data/DynamicForm.java:379-390 | web/play-java-forms/src/main/java/play/data/DynamicForm.java:395-406 | web/play-java-forms/src/main/java/play/data/DynamicForm.java:416-427 | web/play-java-forms/src/main/java/play/data/DynamicForm.java:437-448 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `web/play-java-forms/src/main/java/play/data/DynamicForm.java:379` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (7 lines × 3) core/play-java/src/main/java/play/libs/Time.java:1283 — core/play-java/src/main/java/play/libs/Time.java:1283-1290 | core/play-java/src/main/java/play/libs/Time.java:1335-1341 | core/play-java/src/main/java/play/libs/Time.java:1372-1378 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play-java/src/main/java/play/libs/Time.java:1283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (5 lines × 4) · ×1

Duplicated block (5 lines × 4) core/play/src/main/java/play/libs/F.java:112 — core/play/src/main/java/play/libs/F.java:112-116 | core/play/src/main/java/play/libs/F.java:169-173 | core/play/src/main/java/play/libs/F.java:232-236 | core/play/src/main/java/play/libs/F.java:303-307 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/java/play/libs/F.java:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (4–5 lines × 3) · ×1

Duplicated block (4–5 lines × 3) core/play/src/main/java/play/libs/F.java:174 — core/play/src/main/java/play/libs/F.java:174-177 | core/play/src/main/java/play/libs/F.java:238-242 | core/play/src/main/java/play/libs/F.java:309-313 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/java/play/libs/F.java:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (43 lines × 2) · ×1

Duplicated block (43 lines × 2) core/play/src/main/java/play/libs/concurrent/ClassLoaderExecution.java:1 — core/play/src/main/java/play/libs/concurrent/ClassLoaderExecution.java:1-55 | core/play/src/main/java/play/libs/concurrent/HttpExecution.java:1-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/play/src/main/java/play/libs/concurrent/ClassLoaderExecution.java:1` 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.

IC1 · Incompleteness & stubs · Hollow method · ×1

Hollow method — returns a constant without doing the work documentation/manual/working/javaGuide/main/http/code/javaguide/http/JavaActions.java:121 — `render` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1

Third-party script without Subresource Integrity dev-mode/play-docs-sbt-plugin/src/main/twirl/org/playframework/docs/sbtplugin/translationReport.scala.html:11 — `//code.jquery.com/jquery-2.2.0.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup.

X15 · Unvalidated length from an untrusted reader · Length read from the parsed input is spent without ever being bounded · ×1

Length read from the parsed input is spent without ever being bounded cache/play-cache/src/main/scala/play/api/cache/SerializableResult.scala:68 — `sizeOfBody` is read from the bytes being parsed at line 67 (`readInt`), then used to size a `new Array[Byte]` at line 68 — and nowhere in its scope is `sizeOfBody` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `sizeOfBody` against the bytes actually remaining and a maximum the format allows before allocating.

X18 · Disposal-pattern correctness · Disposable created and abandoned in the function that made it · ×1

Disposable created and abandoned in the function that made it documentation/manual/working/scalaGuide/main/ws/code/ScalaWSSpec.scala:240 — `scala.io.Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(scala.io.Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.

Minor — 258 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×157

Orphaned file dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/templates/package.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file web/play-filters-helpers/src/main/scala/play/filters/csrf/csrf.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play-java/src/main/java/play/routing/RoutingDsl.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/api/data/format/Format.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file web/play-openid/src/main/scala/play/api/libs/openid/OpenIdClient.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/api/Application.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/api/Logger.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/java/play/libs/reflect/MemberUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/utils/UriEncoding.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/java/play/http/DefaultHttpErrorHandler.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/api/ApplicationLoader.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/api/inject/Binding.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/java/play/libs/reflect/ClassUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play-guice/src/main/scala/play/api/inject/guice/GuiceApplicationBuilder.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/java/play/libs/F.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cache/play-ehcache/src/main/scala/play/api/cache/ehcache/EhCacheApi.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cache/play-caffeine-cache/src/main/scala/play/api/cache/caffeine/CaffeineCacheApi.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file web/play-filters-helpers/src/main/scala/play/filters/csp/CSPReportActionBuilder.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/api/data/validation/Validation.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file transport/client/play-ahc-ws/src/main/scala/play/api/libs/ws/ahc/AhcWSModule.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/core/formatters/Multipart.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/RoutesGenerator.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/scala/play/utils/Reflect.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/java/play/core/cookie/encoding/ClientCookieDecoder.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/play/src/main/java/play/ApplicationLoader.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 132 more in this group — see findings.md.

M4 · Documentation accuracy · README/code drift · ×40

README/code drift documentation/README.md:17 — documentation/README.md links to `some/relative/path`, but `documentation/some/relative/path` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/README.md:27 — documentation/README.md links to `code/javaguide/pekko/JavaPekko.java`, but `documentation/code/javaguide/pekko/JavaPekko.java` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/hacking/BuildingFromSource.md:50 — documentation/manual/hacking/BuildingFromSource.md changes into `playframework/documentation`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/tutorial/ImplementingHelloWorld.md:82 — documentation/manual/tutorial/ImplementingHelloWorld.md names `app/views/hello.scala.html`, but no file or folder `app/views/hello.scala.html` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/ApplicationSecret.md:33 — documentation/manual/working/commonGuide/configuration/ApplicationSecret.md documents the environment variable `APPLICATION_SECRET`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsJDBC.md:33 — documentation/manual/working/commonGuide/configuration/SettingsJDBC.md links to `/confs/play-jdbc/reference.conf`, but `confs/play-jdbc/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsLogger.md:11 — documentation/manual/working/commonGuide/configuration/SettingsLogger.md links to `/confs/play-logback/logback-play-dev.xml`, but `confs/play-logback/logback-play-dev.xml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsLogger.md:15 — documentation/manual/working/commonGuide/configuration/SettingsLogger.md links to `/confs/play-logback/logback-play-default.xml`, but `confs/play-logback/logback-play-default.xml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsNetty.md:13 — documentation/manual/working/commonGuide/configuration/SettingsNetty.md links to `/confs/play-netty-server/reference.conf`, but `confs/play-netty-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsNetty.md:17 — documentation/manual/working/commonGuide/configuration/SettingsNetty.md links to `/confs/play-server/reference.conf`, but `confs/play-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md:9 — documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md links to `/confs/play-pekko-http-server/reference.conf`, but `confs/play-pekko-http-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md:13 — documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md links to `/confs/play-server/reference.conf`, but `confs/play-server/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md:30 — documentation/manual/working/commonGuide/configuration/SettingsPekkoHttp.md links to `/confs/play-pekko-http2-support/reference.conf`, but `confs/play-pekko-http2-support/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/SettingsSession.md:30 — documentation/manual/working/commonGuide/configuration/SettingsSession.md links to `/confs/play/reference.conf`, but `confs/play/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/ThreadPools.md:46 — documentation/manual/working/commonGuide/configuration/ThreadPools.md links to `api/java/play/libs/concurrent/ClassLoaderExecutionContext.html`, but `documentation/manual/working/commonGuide/configuration/api/java/play/libs/concurrent/ClassLoaderExecutionContext.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/configuration/WsCache.md:90 — documentation/manual/working/commonGuide/configuration/WsCache.md links to `/confs/play-ahc-ws/reference.conf`, but `confs/play-ahc-ws/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:146 — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/java/play/db/Database.html`, but `documentation/manual/working/commonGuide/database/api/java/play/db/Database.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:146 — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/scala/play/api/db/Database.html`, but `documentation/manual/working/commonGuide/database/api/scala/play/api/db/Database.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:178 — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/java/play/libs/concurrent/CustomExecutionContext.html`, but `documentation/manual/working/commonGuide/database/api/java/play/libs/concurrent/CustomExecutionContext.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:178 — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `api/scala/play/api/libs/concurrent/CustomExecutionContext.html`, but `documentation/manual/working/commonGuide/database/api/scala/play/api/libs/concurrent/CustomExecutionContext.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md:208 — documentation/manual/working/commonGuide/database/AccessingAnSQLDatabase.md links to `resources/confs/play-jdbc/reference.conf`, but `documentation/manual/working/commonGuide/database/resources/confs/play-jdbc/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/filters/AllowedHostsFilter.md:23 — documentation/manual/working/commonGuide/filters/AllowedHostsFilter.md links to `resources/confs/play-filters-helpers/reference.conf`, but `documentation/manual/working/commonGuide/filters/resources/confs/play-filters-helpers/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/filters/CorsFilter.md:19 — documentation/manual/working/commonGuide/filters/CorsFilter.md links to `resources/confs/play-filters-helpers/reference.conf`, but `documentation/manual/working/commonGuide/filters/resources/confs/play-filters-helpers/reference.conf` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/filters/CspFilter.md:17 — documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/scala/play/filters/csp/CSPFilter.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/filters/csp/CSPFilter.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/manual/working/commonGuide/filters/CspFilter.md:27 — documentation/manual/working/commonGuide/filters/CspFilter.md links to `api/scala/play/filters/csp/CSPComponents.html`, but `documentation/manual/working/commonGuide/filters/api/scala/play/filters/csp/CSPComponents.html` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
+ 15 more in this group — see findings.md.

X4 · Structured logging · Interpolated log message defeats structured logging · ×22

Interpolated log message defeats structured logging core/play-configuration/src/main/scala/play/api/Configuration.scala:203 — `warn` at line 203 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/Logger.scala:282 — `warn` at line 282 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/Logger.scala:283 — `warn` at line 283 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/data/Form.scala:89 — `warn` at line 89 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/http/HttpConfiguration.scala:184 — `warn` at line 184 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/http/HttpConfiguration.scala:299 — `debug` at line 299 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/internal/libs/concurrent/CoordinatedShutdownSupport.scala:63 — `info` at line 63 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/libs/Files.scala:223 — `debug` at line 223 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/scala/play/api/libs/concurrent/Pekko.scala:274 — `debug` at line 274 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging documentation/manual/working/scalaGuide/main/application/code/AccumulatorFlowFilter.scala:35 — `info` at line 35 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging transport/client/play-ahc-ws/src/main/scala/play/api/test/WSTestClient.scala:174 — `info` at line 174 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging transport/client/play-ahc-ws/src/main/scala/play/api/test/WSTestClient.scala:195 — `debug` at line 195 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging transport/client/play-ahc-ws/src/main/scala/play/api/test/WSTestClient.scala:200 — `debug` at line 200 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging transport/server/play-server/src/main/scala/play/core/server/SelfSigned.scala:43 — `debug` at line 43 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging transport/server/play-server/src/main/scala/play/core/server/SelfSigned.scala:47 — `debug` at line 47 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging core/play/src/main/java/play/core/cookie/encoding/CookieDecoder.java:51 — `debug` at line 51 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging core/play/src/main/java/play/core/cookie/encoding/CookieDecoder.java:64 — `debug` at line 64 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging core/play/src/main/java/play/core/cookie/encoding/CookieDecoder.java:78 — `debug` at line 78 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging core/play/src/main/java/play/http/JsonHttpErrorHandler.java:129 — `error` at line 129 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging core/play/src/main/java/play/http/DefaultHttpErrorHandler.java:230 — `error` at line 230 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging documentation/manual/working/javaGuide/main/ws/code/javaguide/ws/JavaWS.java:426 — `debug` at line 426 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging documentation/manual/working/javaGuide/main/ws/code/javaguide/ws/JavaWS.java:517 — `error` at line 517 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.

X10 · Duplicated predicate · Duplicated predicate · ×10

Duplicated predicate web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java:817 — `key.length() > 1 && ((key.startsWith("'") && key.endsWith("'")) || (key.startsWith("\"") && key.endsWith("\"")))` appears character-identically in 2 files — web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java, web/play-java-forms/src/main/java/play/data/internal/binding/beans/PropertyAccessorUtils.java. 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 transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:413 — `!atEnd && (current == ' ' || current == '\t')` appears character-identically in 2 files — transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala, transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala. 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 core/play/src/main/scala/play/api/mvc/request/RequestAuthority.scala:300 — `(char >= 'A' && char <= 'Z') || (char >= 'a' && char <= 'z')` appears character-identically in 2 files — core/play/src/main/scala/play/api/mvc/request/RequestAuthority.scala, core/play/src/main/scala/play/api/mvc/request/Scheme.scala. 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 transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:404 — `(char >= 'A' && char <= 'Z') || (char >= 'a' && char <= 'z') || (char >= '0' && char <= '9') || char == '+' || char == '/'` appears character-identically in 2 files — transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala, transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala. 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 transport/server/play-server/src/main/scala/play/core/server/common/Rfc7239HeaderParser.scala:168 — `(char >= 'a' && char <= 'z') || (char >= 'A' && char <= 'Z') || (char >= '0' && char <= '9') || "!#$%&'*+-.^_`|~".indexOf(char) >= 0` appears character-identically in 2 files — transport/server/play-server/src/main/scala/play/core/server/common/Rfc7239HeaderParser.scala, transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala. 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 web/play-filters-helpers/src/main/scala/play/filters/csp/CSPConfig.scala:91 — `blacklistModifiers.isEmpty || blacklistModifiers.exists(rh.hasRouteModifier)` appears character-identically in 3 files — web/play-filters-helpers/src/main/scala/play/filters/csp/CSPConfig.scala, web/play-filters-helpers/src/main/scala/play/filters/csrf/csrf.scala, web/play-filters-helpers/src/main/scala/play/filters/ip/IPFilter.scala. 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 core/play/src/main/scala/play/api/mvc/request/ClientCertificateInfo.scala:55 — `chain != null && chain.forall(_ != null)` appears character-identically in 2 files — core/play/src/main/scala/play/api/mvc/request/ClientCertificateInfo.scala, core/play/src/main/scala/play/api/mvc/request/XForwardedClientCert.scala. 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 core/play/src/main/scala/play/api/mvc/Request.scala:322 — `clientCertificate != null && clientCertificate.forall(_ != null)` appears character-identically in 2 files — core/play/src/main/scala/play/api/mvc/Request.scala, core/play/src/main/scala/play/api/mvc/RequestHeader.scala. 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 transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala:183 — `input.available() == 0 && Arrays.equals(certificate.getEncoded, bytes)` appears character-identically in 2 files — transport/server/play-server/src/main/scala/play/core/server/common/Rfc9440ClientCertificateParser.scala, transport/server/play-server/src/main/scala/play/core/server/common/XForwardedClientCertHeaderParser.scala. 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 core/play/src/main/scala/play/api/mvc/Request.scala:326 — `xForwardedClientCertificates != null && xForwardedClientCertificates.forall(_ != null)` appears character-identically in 2 files — core/play/src/main/scala/play/api/mvc/Request.scala, core/play/src/main/scala/play/api/mvc/RequestHeader.scala. 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.

AX6 · Interface segregation · Fat interface · ×6

Fat interface: WSRequest (66 abstract methods) transport/client/play-ws/src/main/java/play/libs/ws/WSRequest.java:26 — `WSRequest` declares 66 abstract methods: `addCookie`, `addCookie`, `addCookies`, `addHeader`, `addQueryParameter`, `delete`, `execute`, `execute`, `get`, `getHeaders`, `getQueryParameters`, `getUrl`, `head`, `options`, `patch`, `patch`, `patch`, `patch`, `patch`, `patch`, `patch`, `post`, `post`, `post`, `post`, `post`, `post`, `post`, `put`, `put`, `put`, `put`, `put`, `put`, `put`, `query`, `query`, `query`, `query`, `query`, and 26 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 66 declarations carry 31 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 31 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: WSResponse (18 abstract methods) transport/client/play-ws/src/main/java/play/libs/ws/WSResponse.java:17 — `WSResponse` declares 18 abstract methods: `asByteArray`, `asJson`, `asXml`, `getAllHeaders`, `getBody`, `getBody`, `getBodyAsBytes`, `getBodyAsSource`, `getBodyAsStream`, `getContentType`, `getCookie`, `getCookies`, `getHeaderValues`, `getHeaders`, `getSingleHeader`, `getStatus`, `getStatusText`, `getUnderlying`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 18 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Cookie (19 abstract methods) core/play/src/main/java/play/core/cookie/encoding/Cookie.java:19 — `Cookie` declares 19 abstract methods: `domain`, `isHttpOnly`, `isPartitioned`, `isSecure`, `maxAge`, `name`, `path`, `sameSite`, `setDomain`, `setHttpOnly`, `setMaxAge`, `setPartitioned`, `setPath`, `setSameSite`, `setSecure`, `setValue`, `setWrap`, `value`, `wrap`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: RequestHeader (28 abstract methods) core/play/src/main/java/play/mvc/Http.java:829 — `RequestHeader` declares 28 abstract methods: `acceptLanguages`, `acceptedTypes`, `accepts`, `addAttr`, `addAttrs`, `addAttrs`, `addAttrs`, `addAttrs`, `asScala`, `attrs`, `charset`, `contentType`, `cookie`, `cookies`, `getCookie`, `getHeaders`, `getQueryString`, `hasBody`, `headers`, `method`, `path`, `queryString`, `queryString`, `removeAttr`, `uri`, `version`, `withAttrs`, `withBody`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 28 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: MessagesApi (16 abstract members) core/play/src/main/scala/play/api/i18n/Messages.scala:337 — `MessagesApi` declares 16 abstract members under just 13 distinct name(s): `messages`, `preferred`, `preferred`, `preferred`, `apply`, `apply`, `translate`, `isDefinedAt`, `setLang`, `withoutLang`, `langCookieName`, `langCookieMaxAge`, `langCookieSecure`, `langCookieHttpOnly`, `langCookieSameSite`, `langCookiePartitioned`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: WSRequest (41 abstract members) transport/client/play-ws/src/main/scala/play/api/libs/ws/WSRequest.scala:19 — `WSRequest` declares 41 abstract members: `withHeaders`, `withHttpHeaders`, `withQueryString`, `withQueryStringParameters`, `addCookies`, `withCookies`, `method`, `body`, `headers`, `queryString`, `calc`, `auth`, `followRedirects`, `requestTimeout`, `virtualHost`, `proxyServer`, `sign`, `withAuth`, `withFollowRedirects`, `withRequestTimeout`, `withRequestFilter`, `withVirtualHost`, `withProxyServer`, `withBody`, `withMethod`, `get`, `post`, `post`, `post`, `patch`, `patch`, `patch`, `put`, `put`, `put`, `query`, `delete`, `head`, `options`, `execute`, and 1 more. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 41 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

D19 · Documentation Quality · Documentation · ×3

Documentation: no project overview README.md — The title 'Play Framework - The High Velocity Web Framework' is a branding banner with no description of what the project does or its scope. Add an overview paragraph explaining the Play framework's purpose, target audience (new users), and the value it brings.
Documentation: no installation or build instructions README.md — There are no installation/build/run commands in the document. Document how to set up the project: add build.sbt, run sbt clean test, or invoke the Play CLI from the root.
Documentation: no usage examples README.md — There are no usage examples of the Play framework in the document. Add a short 'How to run Play' example showing how to start a new project or invoke the command line.

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

REDACTED
REDACTED

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

REDACTED
REDACTED

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 101 significant file(s) lose their only recent owner: core/play/src/main/java/play/mvc/Http.java, web/play-java-forms/src/main/java/play/data/Form.java, project/BuildSettings.scala, core/play/src/main/scala/play/api/controllers/Assets.scala, web/play-java-forms/src/main/java/play/data/internal/binding/util/ConcurrentReferenceHashMap.java, web/play-java-forms/src/main/java/play/data/internal/binding/beans/AbstractNestablePropertyAccessor.java, persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/EvolutionsApi.scala, core/play/src/main/java/play/mvc/WebSocket.java (+93 more). Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (106 single-owned of 348 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 348 of the 745 production source files in this repository met that bar). They are anonymized user #2 (4 file(s)), anonymized user #3 (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: core/play/src/main/scala/play/api/data/Form.scala, core/play/src/main/scala/play/api/http/HttpErrorHandler.scala, core/play/src/main/scala/play/api/http/MediaRange.scala, core/play/src/main/scala/play/api/http/AcceptEncoding.scala, core/play/src/main/scala/play/api/mvc/Binders.scala.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 2 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 2.0/10. The most over is `(repository root)` (102726 LoC, 1655 module-visible types across 166 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

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

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 157 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: dev-mode/play-routes-compiler/src/main/scala/play/routes/compiler/templates/package.scala, core/play-java/src/main/java/play/routing/RoutingDsl.java, core/play/src/main/java/play/libs/reflect/MemberUtils.java, core/play/src/main/scala/play/utils/UriEncoding.scala, core/play/src/main/java/play/libs/reflect/ClassUtils.java, core/play/src/main/java/play/libs/F.java, core/play/src/main/scala/play/core/formatters/Multipart.scala, web/play-filters-helpers/src/main/scala/play/filters/csrf/csrf.scala (and 149 more) (163 orphaned of 354 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 354 of the 745 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

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

REDACTED

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

REDACTED

IC1 · Incompleteness & stubs · Empty method body · ×1

Empty method body documentation/manual/releases/release31/migration31/code/WebSocketCloseMigration.java:19 — `recordAbnormalClosure` has an empty body — confirm it's an intentional no-op and not an unfinished method.

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.

P10 · Library API & versioning · Large public API surface · ×1

Large public API surface — 441/620 types (71%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

P3 · Security & performance tooling · No SAST · ×1

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

PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1

Benchmarks don't track allocations core/play-microbenchmark/src/test/scala/play/api/mvc/RequestHeader_01_ReadHeaderValue.scala — A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.

X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1

Scala's null is not held to the type system everywhere — No build over this repository's 444 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.

X9 · Subsumed condition operand · Subsumed condition operand · ×1

Subsumed condition operand persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/Evolutions.scala:160 — `p.startsWith("..")` can never decide this `||` — every value satisfying `p.startsWith("..")` also satisfies `p.startsWith(".")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-19f81665f8144313856ce2eee4d9a5c2/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-19f81665f8144313856ce2eee4d9a5c2/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	36	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-414f55c5d3be434494648cd73e29a024	0	artifacts/raw/osv-scanner.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `core/play/src/main/scala/play/api/mvc/Render.scala`, `core/play/src/main/scala/play/api/mvc/Results.scala`, `documentation/manual/working/scalaGuide/advanced/routing/code/ScalaSirdRouter.scala`, `documentation/manual/working/scalaGuide/main/ws/code/ScalaWSSpec.scala`, `persistence/play-jdbc-evolutions/src/main/scala/play/api/db/evolutions/ApplicationEvolutions.scala`, … (+1 more) — so the PII/GDPR sweep did not cover them at all.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-414f55c5d3be434494648cd73e29a024	0	artifacts/raw/osv-scanner.json

Run 01a16767-f3ce-7961-bb14-47c64ef22f69 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 57% · Adequate · gated by X5 ·

At a glance — Architecture · 75% · Adequate · gated by D26 ·

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

At a glance — Readiness · 69% · Adequate ·

At a glance — Security · 44% · Weak · gated by D29, D36, S1 ·

At a glance — Accessibility · 49% · Weak ·

At a glance — Performance · 80% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts