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

japgolly/scalajs-react

Measured 26 October 2026, 06:39 UTC, at code version f84ebe5

No regression since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 50out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 4 since the last survey

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

Architecture 90 Adequate Performance 83 Strong Security and Compliance 80 Adequate Maturity 70 Adequate Code Health 60 Adequate Production Readiness 57 Adequate Accessibility 34 Weak

A medium codebase: 32,254 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Accessibility, 34

Findings by how serious they are

18 critical 201 serious 21 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 06:39 UTC

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

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

66of 66 dimensions measured by tools.
226of 240 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
66dimensions across 7 lenses, read from 32,254 lines of product code in 8 projects.
Chapters

Executive summary

japgolly/scalajs-react falls short of our standard for production, in part because it has pages that don't say their language. It scores 50 out of 100 and is rated Weak, and nine of its 18 critical findings are security problems.

Accessibility, at 34, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 10 points. Structuring the pages comes next, worth about 8 points. Raising Accessibility to 70 would lift the score to about 62.

Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and two parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, updating the vulnerable packages and having someone learn the forgotten files would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The four pages that don't say their language need their language set.

The product code is 32,254 lines, about €41,000 to rebuild.

Code Health 60 Adequate, capped by Nullable reference types Architecture 90 Adequate, capped by Project Cohesion Maturity 70 Adequate, capped by Architecture documentation Production Readiness 57 Adequate, capped by Observability and Security & performance tooling Security and Compliance 80 Adequate, capped by Supply-chain Provenance & Signing Accessibility 34 Weak, capped by Page structure and Visual & motion safety Performance 83 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.
Accessibility 34 · counts for 46%Production Readiness 57 · counts for 25%Code Health 60 · counts for 14%Maturity 70 · counts for 8%Security and Compliance 80 · counts for 4%Performance 83 · counts for 2%Architecture 90 · counts for 1%

If Accessibility rose from 34 to 70, the lowest score rated Strong, the score would rise from 50 to about 62.

Code composition: what the lines of code are
Product code 73%Tests 27%
New since the last survey: 38 findings

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

  • Cognitive Complexity · RoutingRulesF.fromRule (cognitive 20) library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRulesF.scala
  • Cognitive Complexity · ReusabilityMacros.deriveInnerSumType (cognitive 19) library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ReusabilityMacros.scala
  • Code Duplication · Duplicated block (39 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (21 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (20 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (15 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (14 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (14 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (12 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (11 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala
  • Code Duplication · Duplicated block (11 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala
  • Code Duplication · Duplicated block (5 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (7 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala
  • Churn × Complexity Hotspots · Repeated repair: library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Churn × Complexity Hotspots · Repeated repair: library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Churn × Complexity Hotspots · Repeated repair: library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala
  • Churn × Complexity Hotspots · Repeated repair: library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala
  • Dependency Vulnerabilities · REDACTED
  • Knowledge Freshness · Orphaned knowledge library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/HtmlTags.scala
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.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: 12 findings

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

  • Code Duplication · Duplicated block (29 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (22 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (20 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (12 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (6 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (6 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala
  • Code Duplication · Duplicated block (6 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala
  • Code Duplication · Duplicated block (11 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala
  • Code Duplication · Duplicated block (5 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala
  • Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €41,000 · Estimate
Cost to rebuild€14,000 to €69,000, for 228 to 723 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 50. 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.
SizeMedium: 32,254 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

1
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.
Raises the score by about 10 points · Medium effort · Visual & motion safety
2
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 8 points · Medium effort · Page structure
3
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Raises the score by about 6 points · Medium effort · A11y enforcement

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 €41,000 to build again, about 0.3 person-years of work. Its weakest lens is Accessibility, at 34 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 10 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, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch codehealth-iso-0658a825d462488cade7595a8284e0db codehealth-iso-0658a825d462488cade7595a8284e0db downstream-tests/generic generic downstream-tests/js js downstream-tests/macros macros downstream-tests/js->downstream-tests/macros downstream-tests/jsCBIO jsCBIO downstream-tests/jsCBIO->downstream-tests/macros downstream-tests/jsCE jsCE downstream-tests/jsCE->downstream-tests/macros downstream-tests/root root library/scalajs-react scalajs-react

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.

153 modules, with 410 dependencies between them. 2 loops run through 56 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 113 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 ghpages.GhPages2 japgolly.scalajs.react.Children3 japgolly.scalajs.react.UpdateSnapshot4 japgolly.scalajs.react.callback.AsyncCallback5 japgolly.scalajs.react.hooks.HookCtx6 japgolly.scalajs.react.util7 japgolly.scalajs.react.util.Effect8 japgolly.scalajs.react.NonEmptyRef9 japgolly.scalajs.react.StateAccess10 japgolly.scalajs.react.extra.Px11 japgolly.scalajs.react.vdom.Attr12 japgolly.scalajs.react.extra.internal.StateSnapshot.withReuse13 japgolly.scalajs.react.vdom14 japgolly.scalajs.react.component.builder15 japgolly.scalajs.react.extra.router16 japgolly.scalajs.react.feature17 japgolly.scalajs.react.component.builder.ComponentBuilder18 japgolly.scalajs.react.hooks.Hooks19 japgolly.scalajs.react.hooks.Api20 japgolly.scalajs.react.hooks.CustomHook.Builder21 japgolly.scalajs.react.component.ScalaFn22 japgolly.scalajs.react.component.ReactForwardRefInternals23 japgolly.scalajs.react.Ref24 japgolly.scalajs.react.hooks25 japgolly.scalajs.react.extra.internal26 japgolly.scalajs.react.extra27 japgolly.scalajs.react.extra.internal.StateSnapshot28 japgolly.scalajs.react.facade29 japgolly.scalajs.react.internal.monocle30 japgolly.scalajs.react.facade.React31 japgolly.scalajs.react.callback32 japgolly.scalajs.react.internal33 japgolly.scalajs.react.CtorType34 japgolly.scalajs.react35 japgolly.scalajs.react.component.JsFn36 japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentP37 japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentPC38 japgolly.scalajs.react.component.Generic39 japgolly.scalajs.react.component40 japgolly.scalajs.react.component.Template
1 ghpages.GhPages
2 japgolly.scalajs.react.Children2
3 japgolly.scalajs.react.UpdateSnapshot2
4 japgolly.scalajs.react.callback.AsyncCallback16
5 japgolly.scalajs.react.hooks.HookCtx2
6 japgolly.scalajs.react.util914
7 japgolly.scalajs.react.util.Effect3
8 japgolly.scalajs.react.NonEmptyRef31
9 japgolly.scalajs.react.StateAccess53
10 japgolly.scalajs.react.extra.Px1106
11 japgolly.scalajs.react.vdom.Attr46145
12 japgolly.scalajs.react.extra.internal.StateSnapshot.withReuse11315
13 japgolly.scalajs.react.vdom153
14 japgolly.scalajs.react.component.builder114131
15 japgolly.scalajs.react.extra.router13102311
16 japgolly.scalajs.react.feature221921
17 japgolly.scalajs.react.component.builder.ComponentBuilder1313121211
18 japgolly.scalajs.react.hooks.Hooks2110112112212
19 japgolly.scalajs.react.hooks.Api24212202123227
20 japgolly.scalajs.react.hooks.CustomHook.Builder43
21 japgolly.scalajs.react.component.ScalaFn1111113
22 japgolly.scalajs.react.component.ReactForwardRefInternals23321
23 japgolly.scalajs.react.Ref4811
24 japgolly.scalajs.react.hooks685111512115
25 japgolly.scalajs.react.extra.internal12111
26 japgolly.scalajs.react.extra11212113
27 japgolly.scalajs.react.extra.internal.StateSnapshot113111
28 japgolly.scalajs.react.facade2171315
29 japgolly.scalajs.react.internal.monocle111
30 japgolly.scalajs.react.facade.React111
31 japgolly.scalajs.react.callback6111
32 japgolly.scalajs.react.internal1111223
33 japgolly.scalajs.react.CtorType259
34 japgolly.scalajs.react121526233121142711
35 japgolly.scalajs.react.component.JsFn11411213
36 japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentP2412222
37 japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentPC2412222
38 japgolly.scalajs.react.component.Generic19113111242
39 japgolly.scalajs.react.component11171411222106879
40 japgolly.scalajs.react.component.Template15522
Uses a module listed above itPart of a loopThe module itself
1 ghpages.GhPages2 japgolly.scalajs.react.Children3 japgolly.scalajs.react.UpdateSnapshot4 japgolly.scalajs.react.callback.AsyncCallback5 japgolly.scalajs.react.hooks.HookCtx6 japgolly.scalajs.react.util7 japgolly.scalajs.react.util.Effect8 japgolly.scalajs.react.NonEmptyRef9 japgolly.scalajs.react.StateAccess10 japgolly.scalajs.react.extra.Px11 japgolly.scalajs.react.vdom.Attr12 japgolly.scalajs.react.extra.internal.StateSnapshot.withReuse13 japgolly.scalajs.react.vdom14 japgolly.scalajs.react.component.builder15 japgolly.scalajs.react.extra.router16 japgolly.scalajs.react.feature17 japgolly.scalajs.react.component.builder.ComponentBuilder18 japgolly.scalajs.react.hooks.Hooks19 japgolly.scalajs.react.hooks.Api20 japgolly.scalajs.react.hooks.CustomHook.Builder21 japgolly.scalajs.react.component.ScalaFn22 japgolly.scalajs.react.component.ReactForwardRefInternals23 japgolly.scalajs.react.Ref24 japgolly.scalajs.react.hooks25 japgolly.scalajs.react.extra.internal26 japgolly.scalajs.react.extra27 japgolly.scalajs.react.extra.internal.StateSnapshot28 japgolly.scalajs.react.facade29 japgolly.scalajs.react.internal.monocle30 japgolly.scalajs.react.facade.React31 japgolly.scalajs.react.callback32 japgolly.scalajs.react.internal33 japgolly.scalajs.react.CtorType34 japgolly.scalajs.react35 japgolly.scalajs.react.component.JsFn36 japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentP37 japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentPC38 japgolly.scalajs.react.component.Generic39 japgolly.scalajs.react.component40 japgolly.scalajs.react.component.Templateghpages.GhPages1japgolly.scalajs.react.Children2japgolly.scalajs.react.UpdateSnapshot3japgolly.scalajs.react.callback.AsyncCallback4japgolly.scalajs.react.hooks.HookCtx5japgolly.scalajs.react.util6japgolly.scalajs.react.util.Effect7japgolly.scalajs.react.NonEmptyRef8japgolly.scalajs.react.StateAccess9japgolly.scalajs.react.extra.Px10japgolly.scalajs.react.vdom.Attr11japgolly.scalajs.react.extra.internal.StateSnapshot.withReuse12japgolly.scalajs.react.vdom13japgolly.scalajs.react.component.builder14japgolly.scalajs.react.extra.router15japgolly.scalajs.react.feature16japgolly.scalajs.react.component.builder.ComponentBuilder17japgolly.scalajs.react.hooks.Hooks18japgolly.scalajs.react.hooks.Api19japgolly.scalajs.react.hooks.CustomHook.Builder20japgolly.scalajs.react.component.ScalaFn21japgolly.scalajs.react.component.ReactForwardRefInternals22japgolly.scalajs.react.Ref23japgolly.scalajs.react.hooks24japgolly.scalajs.react.extra.internal25japgolly.scalajs.react.extra26japgolly.scalajs.react.extra.internal.StateSnapshot27japgolly.scalajs.react.facade28japgolly.scalajs.react.internal.monocle29japgolly.scalajs.react.facade.React30japgolly.scalajs.react.callback31japgolly.scalajs.react.internal32japgolly.scalajs.react.CtorType33japgolly.scalajs.react34japgolly.scalajs.react.component.JsFn35japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentP36japgolly.scalajs.react.hooks.HookComponentBuilder.ComponentPC37japgolly.scalajs.react.component.Generic38japgolly.scalajs.react.component39japgolly.scalajs.react.component.Template4022162914331531106461451131515311413113102311221921131312121121101121122122421220212322743111111323321481168511151211512111112121131131112171315111111611111112232591215262331211427111141121324122222412222191131112421117141122210687915522+113 more modules (most-connected shown)

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

The Good
D1 · Scala Cyclomatic Complexity 8.6 D3 · Scala God Classes 7.4 D4 · Scala Code Duplication 9.2 D17 · Scala Explicit Debt 9.7 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.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 X18 · Repo Disposal-pattern correctness 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 X30 · Repo Support guard that admits what it rejects 10.0
The Bad
D2 · Scala Cognitive Complexity 5.3
The Ugly
X3 · Repo Exception handling 4.9 X5 · Repo Nullable reference types 2.0

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

The Good
D5 · Scala Coupling 9.0 D6 · Scala Cohesion (LCOM4) 9.4 D35 · Scala Change Coupling 10.0 AX10 · Repo Code composition 9.7 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 Ugly
D26 · Scala Project Cohesion 0.0

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

The Good
D15 · Scala Churn × Complexity Hotspots 10.0 D19 · Scala Documentation Quality 10.0 D34 · Scala Knowledge Freshness 9.3 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Ugly
M2 · Repo Architecture documentation 3.0

At a glance — Readiness · 57% · Adequate · gated by P2, P3 ·

The Good
D9 · Scala Test Distribution 10.0 D12 · Scala Dependency Hygiene 9.6 D13 · Scala Secret Scanning 10.0 D14 · Scala License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P6 · Repo Release Hygiene 10.0
The Ugly
P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 3.0

At a glance — Security · 80% · Adequate · gated by D36 ·

The Good
D28 · Scala Secrets (history) 10.0 D29 · Scala Static Analysis (SAST) 8.4 D30 · Scala Dependency Vulnerabilities 8.8 D43 · Scala Malicious Dependencies 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 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
D36 · Scala Supply-chain Provenance & Signing 2.5

At a glance — Accessibility · 34% · Weak · gated by AC3, AC6 ·

The Good
AC2 · Repo Forms & labels 10.0
The Ugly
AC3 · Repo Page structure 2.5 AC6 · Repo Visual & motion safety 1.0 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 83% · Strong ·

The Good
PF2 · Repo Allocation hygiene 7.1 PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection7High / Critical
A03:2025 — Software Supply Chain Failures7High / Critical

Roadmap

First, address visual and motion safety by ensuring visible focus styles, respecting reduced-motion preferences, and fixing low-contrast colors. Next, correct page structure issues by adding required language attributes, titles, landmarks, and proper heading hierarchy. Then, enforce accessibility standards by integrating linting and automated testing into the development workflow and CI pipeline. Finally, improve observability by implementing user-accessible diagnostic logging and add static analysis to CI to prevent security regressions.

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

Do thisHelpsEffortDimension
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.+10.0 ptsMediumVisual & motion safety
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+7.6 ptsMediumPage structure
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.+5.6 ptsMediumA11y enforcement
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.+2.8 ptsMediumObservability
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.+2.2 ptsMediumSecurity & performance tooling
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.+2.1 ptsMediumNullable reference types
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Dsl.scala, HtmlTags.scala.+0.8 ptsLowKnowledge Freshness
Swallowed exception (caught, then discarded)+1.4 ptsMediumException handling

File quality

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

FileScoreBandWorst signal
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ReusabilityMacros.scala6.0MixedExplicit Debt: TodoComment
library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/Api.scala6.0MixedExplicit Debt: TodoComment
library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackOption.scala6.0MixedExplicit Debt: TodoComment
library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala6.0MixedExplicit Debt: TodoComment
library/tests/src/test/scala/japgolly/scalajs/react/core/ScalaBuilderTest.scala6.6MixedExplicit Debt: TodoComment
library/extra/src/main/scala-3/japgolly/scalajs/react/extra/internal/RouterMacros.scala6.7MixedExplicit Debt: TodoComment
library/tests/src/test/scala/japgolly/scalajs/react/core/HooksTest.scala6.9MixedExplicit Debt: TodoComment
library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/Generic.scala6.9MixedExplicit Debt: TodoComment
library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala7.0MixedCyclomatic Complexity: Px.apply22 (cyclomatic 23)
library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala7.0MixedGod Classes: TooManyMethods: AsyncCallback
library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala7.0MixedGod Classes: TooManyMethods: CallbackTo
library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala7.2MixedCode Duplication: Duplicated block (13 lines × 2)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED7.2MixedDependency Vulnerabilities: High CVE: REDACTED
library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/vdom/Attr.scala7.3MixedExplicit Debt: TodoComment
library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala7.4MixedGod Classes: TooManyMethods: AsyncCallback
library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRulesF.scala7.8MixedCyclomatic Complexity: RoutingRulesF.fromRule (cyclomatic 28)

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

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

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

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

Could not be resolved — 12

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. 66 of 66 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 66 dimensions across the health lenses
D1D2D3D4D5D6D9D12D13D14D15D17D19D26D28D29D30D34D35D36D43AC2AC3AC6AC7AX10AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P6PF2PF3S1X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a176ef-59c8-70fd-b670-35b522d737ae.

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 (.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 (`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 (`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 (.scala) and this repository declares an sbt build (repository root, 83 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares an sbt build (build.sbt), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (80 contributor(s) across 3614 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 79 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • 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 (library/project/plugins.sbt), 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 REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — not measured this run — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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. `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/Callback.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackOption.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala`, `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ReusabilityMacros.scala`, … (+9 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.
  • D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • 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: 6 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.
  • 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.

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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • 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.

Dimensions

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

9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RoutingRulesF.fromRule at 28.

RoutingRulesF.fromRule (cyclomatic 28)library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRulesF.scala:90
Px.apply22 (cyclomatic 23)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:525
Px.apply21 (cyclomatic 22)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:522
Px.apply20 (cyclomatic 21)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:519
Px.apply19 (cyclomatic 20)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:516

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

What to do

  1. Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RoutingRulesF.fromRule (cyclomatic 28), Px.apply22 (cyclomatic 23), Px.apply21 (cyclomatic 22). — 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 9 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. 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.

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

22 method(s) exceeded the cognitive complexity threshold of 15; the worst was Px.apply22 at 253.

Px.apply22 (cognitive 253)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:525
Px.apply21 (cognitive 231)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:522
Px.apply20 (cognitive 210)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:519
Px.apply19 (cognitive 190)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:516
Px.apply18 (cognitive 171)library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:513

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

What to do

  1. Bring the 22 bodies over 15 down to 15 or less in Cognitive Complexity — start with Px.apply22 (cognitive 253), Px.apply21 (cognitive 231), Px.apply20 (cognitive 210). — 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 22 together lifts Cognitive Complexity from 5.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. 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.

D3 · God Classes7.4 / 10Strong✓ Tool-verified

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

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

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

24 god class(es) detected.

TooManyMethods: HtmlAttrs · ×20library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/HtmlAttrs.scala:9
FileTooLong: hooks/StepBoilerplate.scala · ×4library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/StepBoilerplate.scala

What to do

  1. Resolve the 20 TooManyMethods finding(s) in God Classes — start with AsyncCallback.scala (4), Api.scala (2), CallbackTo.scala (2). — One of this dimension's main actionable groups (20 warning-level).
  2. Resolve the 4 FileTooLong finding(s) in God Classes — start with AsyncCallback.scala (2), StepBoilerplate.scala, HtmlAttrs.scala. — One of this dimension's main actionable groups (4 warning-level).
  3. 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.

D4 · Code Duplication9.2 / 10Stronggated by 56 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.2 / 10 · rule-coverage 100% · ceiling Verified

56 duplicated block group(s) detected.

Duplicated block (8 lines × 2) · ×9library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:697
Duplicated block (5 lines × 2) · ×8library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsBaseComponentTemplate.scala:49
Duplicated block (7 lines × 2) · ×6library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsFn.scala:130
Duplicated block (14 lines × 2) · ×4library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:645
Duplicated block (10 lines × 2) · ×3library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:707

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

What to do

  1. Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with AsyncCallback.scala (5), CallbackTo.scala (3), JsFn.scala. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 8 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AsyncCallback.scala (4), JsBaseComponentTemplate.scala, ScalaVersionSpecificReusability.scala. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with AsyncCallback.scala (2), JsFn.scala, ComponentBuilder.scala. — One of this dimension's main actionable groups (6 warning-level).
  4. 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.

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

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

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

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

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

8 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; 1 module(s) off the main sequence, with abstractness counted on 4 of the 8 (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).

Off the main sequence: downstream-tests/macros

What to do

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

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

D6 · Cohesion (LCOM4)9.4 / 10Stronggated by 1 serious finding✓ 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.4 / 10 · rule-coverage 100% · ceiling Verified

1 of 21 classes have LCOM4 above 3.

Low cohesion: ScalaJsReactConfigMacros (LCOM4 4)library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/internal/ScalaJsReactConfigMacros.scala:10

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ScalaJsReactConfigMacros.scala. — One of this dimension's main actionable groups (1 warning-level).
  2. 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.

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

2 test methods: 2 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 2 test case(s) across 1 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.

D12 · Dependency Hygiene9.6 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

3 outdated direct production npm dependency(ies) of 4 graded, 1 pinning defect(s), across 3 REDACTED (3 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

One package at two majors across the workspace: jsdom
Outdated (npm): jsdomdownstream-tests/package.json:3
Outdated (npm): react · ×2

What to do

  1. Resolve the 1 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 4 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 4 production dependency(ies) this repository's committed lockfile resolves, across 3 product REDACTED manifest(s). Its 5 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares an sbt build (build.sbt), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window. Repeated repair below the complexity floor: library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala (11 of 15 changes were fixes); library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala (11 of 15 changes were fixes); library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala (5 of 6 changes were fixes)

Repeated repair: library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala · ×4library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:183

What to do

  1. Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AsyncCallback.scala (2), Reusability.scala, StateSnapshot.scala. — One of this dimension's main actionable groups (4 warning-level).

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

D17 · Explicit Debt9.7 / 10Stronggated by 52 serious findings✓ Tool-verified

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

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

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

52 deducted task-comment markers across 32254 LoC (0.2/KLoC) → score 9.7. 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 · ×48library/util/src/main/scala-3/japgolly/scalajs/react/util/NotAllowed.scala:9
FixmeComment · ×3library/tests/src/test/scala/japgolly/scalajs/react/core/ScalaBuilderTest.scala:87
HackCommentlibrary/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/VdomBuilder.scala:21

What to do

  1. Resolve the 48 TodoComment finding(s) in Explicit Debt — start with ReusabilityMacros.scala (8), React.scala (4), HooksTest.scala (3). — One of this dimension's main actionable groups (48 warning-level).
  2. Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with ScalaBuilderTest.scala (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 HackComment finding(s) in Explicit Debt — start with VdomBuilder.scala. — One of this dimension's main actionable groups (1 warning-level).
  4. 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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

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

Projects may be oversized for their cohesion

What to do

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)8.4 / 10Adequategated by 7 critical findings✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Documented

7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 6 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 12 file(s) — `downstream-tests/js/src/main/scala-3/downstream/DownstreamConfig1.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/Callback.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackOption.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala`, … (+7 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. 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.

D30 · Dependency Vulnerabilities8.8 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

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

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

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

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

9 of 125 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Dsl.scala. Counted over 125 of the 289 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Dsl.scala:1
Orphaned file · ×7library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRule.scala:1
Further orphaned files (smaller)

What to do

  1. Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Dsl.scala, HtmlTags.scala. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with RoutingRule.scala, react17.scala, Router.scala. — One of this dimension's main actionable groups (7 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & 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
REDACTED
REDACTED
REDACTED

What to do

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

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

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC3 · Page structure2.5 / 10Critical✓ 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. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×4) — js-sandbox/index.html:2, library/ghpages/html/dev2.html:2, library/ghpages/html/dev3.html:2, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×4) — library/ghpages/html/dev2.html:2, library/ghpages/html/dev3.html:2, library/ghpages/html/prod.html:2, …
  • An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. (×3) — library/ghpages/html/dev2.html:2, library/ghpages/html/dev3.html:2, library/ghpages/html/prod.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — library/ghpages/html/toc.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety1.0 / 10Critical✓ 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.

  • `a.list-group-item-warning:hover,a.list-group-item-warning:focus` sets color: #c09853 on background-color: #faf2cc — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — library/ghpages/res/bootstrap.css:7
  • `.dropdown-toggle: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. — library/ghpages/res/bootstrap.css:7
  • `.dropdown-menu>.active>a` 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. — library/ghpages/res/bootstrap.css:7
  • `.open>a` 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. — library/ghpages/res/bootstrap.css:7
  • `.btn-group.open .dropdown-toggle` 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. — library/ghpages/res/bootstrap.css:7
  • `.navbar-toggle: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. — library/ghpages/res/bootstrap.css:7
  • `.modal` 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. — library/ghpages/res/bootstrap.css:7
  • `.modal-content` 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. — library/ghpages/res/bootstrap.css:7
  • `.carousel-control: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. — library/ghpages/res/bootstrap.css:7
  • `.collapsing` moves (`transition-property: height, visibility`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ghpages/res/bootstrap.css:7
  • `.progress-bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ghpages/res/bootstrap.css:7
  • `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ghpages/res/bootstrap.css:7
  • `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ghpages/res/bootstrap.css:7
  • `.carousel-inner>.item` moves (`transition: .6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ghpages/res/bootstrap.css:7
  • `.carousel-inner>.item` moves (`transition: transform .6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — library/ghpages/res/bootstrap.css:7

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.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

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

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

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

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

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

  • `MouseLike` declares 16 abstract members: `screenX`, `screenY`, `clientX`, `clientY`, `pageX`, `pageY`, `movementX`, `movementY`, `altKey`, `ctrlKey`, `metaKey`, `shiftKey`, `button`, `buttons`, `defaultPrevented`, `toJs`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/SimEvent.scala:264

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, 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.

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

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

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

What to do

  • Add a 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 1 of 3 project(s) that lack one — worth up to 0.7 pts.
M2 · Architecture documentation3.0 / 10Weak✓ Tool-verified

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

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

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

What to do

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

Maturity · Maturity — Whether the 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.

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

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.

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

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

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

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

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

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

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

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

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

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

What to do

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

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

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

  • No static application security testing detected. For this repository's stack, add 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 2368 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.
  • Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.

PF2 · Allocation hygiene7.1 / 10Strong✓ 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 85 use(s) across 38,665 production line(s) (~2.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
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.

S1 · Web-Security Posture8.0 / 10Strong✓ 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. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are read from a Scala server this repository runs itself, and its Scala source runs none: no HTTP-server artifact in its build and no server package imported or server bound in its production source. What serves its HTTP is outside the Scala source, and only what this card names about it was assessed.

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.

  • `https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.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. 6 such include(s) across the repository's markup. — library/ghpages/html/dev2.html:12

What to do

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

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.

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.

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.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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

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

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

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

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

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

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.

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.

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.

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.

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.

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.

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.

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

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for` 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.

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

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

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

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

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

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

X3 · Exception handling4.9 / 10Weak✓ Tool-verified

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

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

  • `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — library/util/src/main/scala/japgolly/scalajs/react/util/ConsoleHijack.scala:100, library/util/src/main/scala/japgolly/scalajs/react/util/JsUtil.scala:30, library/coreGeneric/src/main/scala/japgolly/scalajs/react/ReactCaughtError.scala:19
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — library/util/src/main/scala/japgolly/scalajs/react/util/Util.scala:62, library/callback/src/main/scala/japgolly/scalajs/react/callback/Timer.scala:23

What to do

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

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

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

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

Other · Code Health — Whether 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 250 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.

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement 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.

LensScoreRatingImpact
Code Health60%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture90%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity70%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness57%Adequate — gated by P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security80%Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility34%Weak — gated by AC3, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance83%StrongStrongest 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 — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.

  • 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 — 50 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 applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~11824 lines of test source are present (.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
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Scala not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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 — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • 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) — 14 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • 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): 105 value object(s); 2 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
  • 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, Python source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`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
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X2 Cancellation propagation — no C# was loaded; this repository's Scala and Python 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 Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 18 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · <html> without a lang · ×4
  • <html> without a lang library/ghpages/html/dev2.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 library/ghpages/html/dev3.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 library/ghpages/html/prod.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 library/ghpages/html/toc.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document <title> is empty · ×3
  • Document <title> is empty library/ghpages/html/dev2.html:2 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
  • Document <title> is empty library/ghpages/html/dev3.html:2 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
  • Document <title> is empty library/ghpages/html/prod.html:2 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Dsl.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 library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/HtmlTags.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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 201 finding(s)
D17 · Explicit Debt · TodoComment · ×48
  • TodoComment library/util/src/main/scala-3/japgolly/scalajs/react/util/NotAllowed.scala:9 — // TODO: [3] Make erased class — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/vdom/Attr.scala:32 — // TODO: [3] Make erased class — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/util/src/main/scala/japgolly/scalajs/react/util/JsUtil.scala:11 — // TODO: Add to microlibs and maybe ReactTestUtils — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/tests/src/test/scala-3/japgolly/scalajs/react/core/ScalaSpecificHooksTest.scala:10 — // TODO: https://github.com/lampepfl/dotty/issues/12663
  • TodoComment library/tests/src/test/scala-2/japgolly/scalajs/react/core/ScalaSpecificHooksTest.scala:10 — // TODO: https://github.com/lampepfl/dotty/issues/12663
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/HooksTest.scala:34 — // TODO: https://github.com/lampepfl/dotty/issues/12663
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/HooksTest.scala:52 — // TODO: https://github.com/lampepfl/dotty/issues/12663
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/HooksTest.scala:129 — // TODO: https://github.com/lampepfl/dotty/issues/12663
  • TodoComment library/tests/src/test/scala-2/japgolly/scalajs/react/core/ReusabilityTest2.scala:8 — // TODO: Re-enable ReusabilityTest2 for Scala 3 after — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/MiscTest.scala:194 — // TODO: https://github.com/lampepfl/dotty/issues/12247
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/ScalaBuilderTest.scala:46 — // TODO: https://github.com/lampepfl/dotty/issues/12247
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/MonocleTest.scala:29 — // TODO I can't think of how to fix this without crazy typeclasses or f-bounded types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/test/TestUtil.scala:26 — // TODO erm... not really. Only allow in raw testing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/extra/router/Router2Test.scala:168 — // todo: should this be necessary? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/RenderableTest.scala:19 — // TODO: Add undefined — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/vdom/PrefixedTest.scala:128 — // TODO: https://github.com/lampepfl/dotty/issues/12264
  • TodoComment library/tests/src/test/scala/japgolly/scalajs/react/core/vdom/UnprefixedTest.scala:126 — // TODO: https://github.com/lampepfl/dotty/issues/12264
  • TodoComment library/project/GenHooks.scala:35 — // val i12663_pre = s"({ type F[A] = $s[A]})#F" // TODO: https://github.com/lampepfl/dotty/issues/12663
  • TodoComment library/ghpages/src/main/scala/ghpages/examples/StateSnapshotExample1.scala:10 — // TODO: Remove [Name] from .initialState[Name](Name("John", "Wick")) after Scala 3 bugfix — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:77 — // TODO: https://github.com/lampepfl/dotty/issues/12115
  • TodoComment library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:94 — // TODO https://github.com/lampepfl/dotty/issues/12115
  • TodoComment library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:96 — // TODO: ComponentClass[Props, _ <: js.Object] | — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:124 — // TODO: type ElementType = String | ComponentType[_ <: js.Object] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment library/extra/src/main/scala-3/japgolly/scalajs/react/extra/internal/RouterMacros.scala:17 — // TODO: https://github.com/lampepfl/dotty/issues/12509
  • TodoComment library/extra/src/main/scala/japgolly/scalajs/react/extra/internal/AjaxF.scala:107 — // TODO Prevent before withTimeout — 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.
  • + 23 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×20
  • TooManyMethods: HtmlAttrs library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/HtmlAttrs.scala:9 — TooManyMethods — 282 methods. The bar is 30 methods; this is 252 over it, 9.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SvgAttrs library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/SvgAttrs.scala:6 — TooManyMethods — 177 methods. The bar is 30 methods; this is 147 over it, 5.90× 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: HtmlTags library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/HtmlTags.scala:8 — TooManyMethods — 108 methods. The bar is 30 methods; this is 78 over it, 3.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Reusability library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala:75 — TooManyMethods — 93 methods. The bar is 30 methods; this is 63 over it, 3.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: HookCtx library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/HookCtx.scala:13 — TooManyMethods — 86 methods. The bar is 30 methods; this is 56 over it, 2.87× 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: Primary library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/Api.scala:54 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× 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: Simulation library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/Simulation.scala:24 — TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AsyncCallback library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:632 — TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: AsyncCallback library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:642 — TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CallbackTo library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:244 — TooManyMethods — 77 methods. The bar is 30 methods; this is 47 over it, 2.57× 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: CallbackTo library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:282 — TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× 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: RouterConfigDsl library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Dsl.scala:267 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UseCallbackArgInstances library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/UseCallbackBoilerplate.scala:16 — 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: Simulate library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/Simulate.scala:8 — 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: FireEvent library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala:6 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: AsyncCallback library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:13 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× 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: AsyncCallback library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:14 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× 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: Secondary library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/Api.scala:760 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MouseLike library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/SimEvent.scala:264 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CallbackOption library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackOption.scala:143 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×9
  • Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:697 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:697-704 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:707-714 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:697` 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) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1143 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1143-1150 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:1149-1156 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsFn.scala:145 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsFn.scala:145-152 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsForwardRef.scala:171-178 — 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 (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:47 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:47-54 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:48-55 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:936 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:936-943 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:948-955 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:967 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:967-974 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:979-986 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:139 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:139-146 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:143-150 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:365 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:365-372 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:400-407 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:474 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:474-481 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:509-516 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×8
  • Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css:7 — `.dropdown-toggle: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.
  • Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css:7 — `.dropdown-menu>.active>a` 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 library/ghpages/res/bootstrap.css:7 — `.open>a` 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 library/ghpages/res/bootstrap.css:7 — `.btn-group.open .dropdown-toggle` 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 library/ghpages/res/bootstrap.css:7 — `.navbar-toggle: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.
  • Focus outline removed in CSS without a :focus replacement library/ghpages/res/bootstrap.css:7 — `.modal` 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 library/ghpages/res/bootstrap.css:7 — `.modal-content` 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 library/ghpages/res/bootstrap.css:7 — `.carousel-control: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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×8
  • Duplicated block (5 lines × 2) library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsBaseComponentTemplate.scala:49 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsBaseComponentTemplate.scala:49-53 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsForwardRef.scala:80-84 — 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 (5 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/ScalaVersionSpecificReusability.scala:8 — library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/ScalaVersionSpecificReusability.scala:8-12 | library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ScalaVersionSpecificReusability.scala:8-12 — 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 (5 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:66 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:66-70 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:67-71 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:272 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:272-276 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:273-277 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1063 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1063-1067 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:1069-1073 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:72 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:72-76 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:76-80 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1199 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1199-1203 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:1205-1209 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) library/coreGeneric/src/main/scala/japgolly/scalajs/react/NonEmptyRef.scala:96 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/NonEmptyRef.scala:96-100 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/Ref.scala:119-123 — 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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×6
  • Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css:7 — `.collapsing` moves (`transition-property: height, visibility`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css:7 — `.progress-bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css:7 — `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css:7 — `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css:7 — `.carousel-inner>.item` moves (`transition: .6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard library/ghpages/res/bootstrap.css:7 — `.carousel-inner>.item` moves (`transition: transform .6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×6
  • Duplicated block (7 lines × 2) library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsFn.scala:130 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsFn.scala:130-136 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsForwardRef.scala:156-162 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:240 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:240-246 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:241-247 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1070 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1070-1076 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:1076-1082 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:123 — library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:123-129 | library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:128-134 — before extracting anything, compare `library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` and `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7 lines × 2) library/coreGeneric/src/main/scala/japgolly/scalajs/react/NonEmptyRef.scala:108 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/NonEmptyRef.scala:108-114 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/Ref.scala:136-142 — 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) library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsBaseComponentTemplate.scala:68 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsBaseComponentTemplate.scala:68-74 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/JsForwardRef.scala:111-117 — 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.
AC3 · Page structure · Page without a main landmark · ×5
  • Page without a main landmark js-sandbox/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark library/ghpages/html/dev2.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark library/ghpages/html/dev3.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark library/ghpages/html/prod.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark library/ghpages/html/toc.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D15 · Churn × Complexity Hotspots · Repeated repair · ×4
  • Repeated repair: library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:183 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala changed 15 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is AsyncCallback.traverse_ at line 183), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix `AsyncCallback.traverse_` (and `sequence_` / `awaitAll`) not propagating cancellation state across tasks and overwriting earlier errors with later ones”; “Fix case of `AsyncCallback.cancel` cancelling prematurely before execution and not running `onCancel` finalisers”; “Fix `AsyncCallback.handleError` and `.maybeHandleError` not catching synchronous exceptions thrown by the recovery function or checking for cancellation”; “Fix `AsyncCallback.flatMap` and `.map` still evaluating its function after cancellation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 15:52:29 +11:00' --until='2026-10-23 15:52:29 +11:00' --full-history --no-merges -- library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.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.
  • Repeated repair: library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:184 — library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala changed 15 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is AsyncCallback.traverse_ at line 184), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix `AsyncCallback.traverse_` (and `sequence_` / `awaitAll`) not propagating cancellation state across tasks and overwriting earlier errors with later ones”; “Fix case of `AsyncCallback.cancel` cancelling prematurely before execution and not running `onCancel` finalisers”; “Fix `AsyncCallback.handleError` and `.maybeHandleError` not catching synchronous exceptions thrown by the recovery function or checking for cancellation”; “Fix `AsyncCallback.flatMap` and `.map` still evaluating its function after cancellation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 15:52:29 +11:00' --until='2026-10-23 15:52:29 +11:00' --full-history --no-merges -- library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.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.
  • Repeated repair: library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala:178 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.scala changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Reusability.byScalaDuration at line 178), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix comparison of `scd.Duration.Undefined`”; “Fix `Reusability.ShouldComponentUpdateResult.log` log message to remove a literal `s"`”; “Fix `Reusability.double` and `float` violating reflexivity when comparing infinities”; “Fix `Reusability.byScalaDuration` and `scalaDuration` throwing `IllegalArgumentException`”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 15:52:29 +11:00' --until='2026-10-23 15:52:29 +11:00' --full-history --no-merges -- library/coreGeneric/src/main/scala/japgolly/scalajs/react/Reusability.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.
  • Repeated repair: library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala:53 — library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is withReuse.useStateSnapshotWithReuse at line 53), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix `useStateSnapshotWithReuse` to run callbacks on non-updates”; “Fix `useStateSnapshot{,WithReuse}` callbacks not executing when state is unchanged”; “Fix `useStateSnapshot{,WithReuse}` executing multiple callbacks in reverse order”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 15:52:29 +11:00' --until='2026-10-23 15:52:29 +11:00' --full-history --no-merges -- library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.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.
D3 · God Classes · FileTooLong · ×4
  • FileTooLong: hooks/StepBoilerplate.scala library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/StepBoilerplate.scala — FileTooLong — 1112 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 612 over it, 2.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: callback/AsyncCallback.scala library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala — FileTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 129 over it, 1.26× 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: callback/AsyncCallback.scala library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala — FileTooLong — 626 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 126 over it, 1.25× 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: vdom/HtmlAttrs.scala library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/HtmlAttrs.scala — FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×4
  • Duplicated block (14 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:645 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:645-658 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:655-668 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:772 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:772-785 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:782-795 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:411 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:411-424 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:413-426 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:463 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:463-476 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:465-478 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D17 · Explicit Debt · FixmeComment · ×3
  • FixmeComment library/tests/src/test/scala/japgolly/scalajs/react/core/ScalaBuilderTest.scala:87 — // FIXME see https://github.com/scala/bug/issues/11660
  • FixmeComment library/tests/src/test/scala/japgolly/scalajs/react/core/ScalaBuilderTest.scala:94 — // //FIXME ScalaBuilderTest.scala:81:56: cyclic aliasing or subtyping involving type SnapshotValue — 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 library/tests/src/test/scala/japgolly/scalajs/react/core/ScalaBuilderTest.scala:100 — // //FIXME ScalaBuilderTest.scala:86:56: cyclic aliasing or subtyping involving type SnapshotValue — 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 (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:707 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:707-716 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:717-726 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:707` 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 (10 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackOption.scala:63 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackOption.scala:63-72 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackOption.scala:63-72 — 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 (10 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:607 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:607-616 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:644-653 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) library/coreGeneric/src/main/scala/japgolly/scalajs/react/StateAccess.scala:153 — library/coreGeneric/src/main/scala/japgolly/scalajs/react/StateAccess.scala:153-161 | library/coreGeneric/src/main/scala/japgolly/scalajs/react/StateAccess.scala:197-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1167 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1167-1175 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:1173-1181 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:51 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:51-59 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:55-63 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:495 — library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:495-500 | library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:501-506 — before extracting anything, compare `library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` and `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:29 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:29-34 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:30-35 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:279 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:279-284 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:280-285 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) library/util/src/main/scala/japgolly/scalajs/react/util/ConsoleHijack.scala:100 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/util/src/main/scala/japgolly/scalajs/react/util/JsUtil.scala:30 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) library/coreGeneric/src/main/scala/japgolly/scalajs/react/ReactCaughtError.scala:19 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D36 · Supply-chain Provenance & Signing REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:788 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:788-802 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:798-812 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackOption.scala:76 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackOption.scala:76-90 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackOption.scala:76-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:372 — library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:372-384 | library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:377-389 — before extracting anything, compare `library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` and `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:423` calls `nowarn` and `library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:418` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:393 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala:393-405 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala:428-440 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/CallbackTo.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1089 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:1089-1100 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:1095-1106 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:575 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:575-586 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:577-588 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:808 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:808-818 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:818-828 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (11 lines × 2) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:287 — library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:287-297 | library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala:292-302 — before extracting anything, compare `library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` and `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/component/builder/ComponentBuilder.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
X3 · Exception handling · Swallowed exception (empty catch) · ×2
  • Swallowed exception (empty catch) library/util/src/main/scala/japgolly/scalajs/react/util/Util.scala:62 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) library/callback/src/main/scala/japgolly/scalajs/react/callback/Timer.scala:23 — 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 · Low contrast colour pair in CSS (2.4 · ×1
  • Low contrast colour pair in CSS (2.4:1) library/ghpages/res/bootstrap.css:7 — `a.list-group-item-warning:hover,a.list-group-item-warning:focus` sets color: #c09853 on background-color: #faf2cc — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 6 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 · RoutingRulesF.fromRule (cyclomatic 28) · ×1
  • RoutingRulesF.fromRule (cyclomatic 28) library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRulesF.scala:90 — RoutingRulesF.fromRule has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · Px.apply22 (cyclomatic 23) · ×1
  • Px.apply22 (cyclomatic 23) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:525 — Px.apply22 has cyclomatic complexity 23 (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 · Px.apply21 (cyclomatic 22) · ×1
  • Px.apply21 (cyclomatic 22) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:522 — Px.apply21 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 · Px.apply20 (cyclomatic 21) · ×1
  • Px.apply20 (cyclomatic 21) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:519 — Px.apply20 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 · Px.apply19 (cyclomatic 20) · ×1
  • Px.apply19 (cyclomatic 20) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:516 — Px.apply19 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 · Px.apply18 (cyclomatic 19) · ×1
  • Px.apply18 (cyclomatic 19) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:513 — Px.apply18 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 · Px.apply17 (cyclomatic 18) · ×1
  • Px.apply17 (cyclomatic 18) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:510 — Px.apply17 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 · Px.apply16 (cyclomatic 17) · ×1
  • Px.apply16 (cyclomatic 17) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:507 — Px.apply16 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 · Px.apply15 (cyclomatic 16) · ×1
  • Px.apply15 (cyclomatic 16) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:504 — Px.apply15 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.
D12 · Dependency Hygiene · One package at two majors across the workspace · ×1
  • One package at two majors across the workspace: jsdom — `jsdom` is maintained at 2 different major versions inside this one repository — major 25 in downstream-tests/package.json; major 26 in library/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
D17 · Explicit Debt · HackComment · ×1
  • HackComment library/coreGeneric/src/main/scala/japgolly/scalajs/react/vdom/VdomBuilder.scala:21 — // Hack because Attr.ValueType.Fn takes a js.Any => Unit. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · Px.apply22 (cognitive 253) · ×1
  • Px.apply22 (cognitive 253) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:525 — Px.apply22 has cognitive complexity 253 (threshold 15). Drivers by points: loops 22 (253 pts) (nesting depth added 231). 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply21 (cognitive 231) · ×1
  • Px.apply21 (cognitive 231) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:522 — Px.apply21 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply20 (cognitive 210) · ×1
  • Px.apply20 (cognitive 210) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:519 — Px.apply20 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply19 (cognitive 190) · ×1
  • Px.apply19 (cognitive 190) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:516 — Px.apply19 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply18 (cognitive 171) · ×1
  • Px.apply18 (cognitive 171) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:513 — Px.apply18 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply17 (cognitive 153) · ×1
  • Px.apply17 (cognitive 153) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:510 — Px.apply17 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply16 (cognitive 136) · ×1
  • Px.apply16 (cognitive 136) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:507 — Px.apply16 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply15 (cognitive 120) · ×1
  • Px.apply15 (cognitive 120) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:504 — Px.apply15 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply14 (cognitive 105) · ×1
  • Px.apply14 (cognitive 105) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:501 — Px.apply14 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply13 (cognitive 91) · ×1
  • Px.apply13 (cognitive 91) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:498 — Px.apply13 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply12 (cognitive 78) · ×1
  • Px.apply12 (cognitive 78) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:495 — Px.apply12 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply11 (cognitive 66) · ×1
  • Px.apply11 (cognitive 66) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:492 — Px.apply11 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply10 (cognitive 55) · ×1
  • Px.apply10 (cognitive 55) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:489 — Px.apply10 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply9 (cognitive 45) · ×1
  • Px.apply9 (cognitive 45) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:486 — Px.apply9 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply8 (cognitive 36) · ×1
  • Px.apply8 (cognitive 36) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:483 — Px.apply8 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · Px.apply7 (cognitive 28) · ×1
  • Px.apply7 (cognitive 28) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:480 — Px.apply7 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · withReuse.useStateSnapshotWithReuse (cognitive 27) · ×1
  • withReuse.useStateSnapshotWithReuse (cognitive 27) library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala:53 — withReuse.useStateSnapshotWithReuse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 4 (10 pts), match/switch 1 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Px.apply6 (cognitive 21) · ×1
  • Px.apply6 (cognitive 21) library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala:477 — Px.apply6 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: library/extra/src/main/scala/japgolly/scalajs/react/extra/Px.scala holds 17 of the 22 methods over the threshold — including the worst — and 1734 of the 1760 points over it (99%), 144.5× the next-largest file (library/extra/src/main/scala/japgolly/scalajs/react/extra/StateSnapshot.scala at 12). 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 · RoutingRulesF.fromRule (cognitive 20) · ×1
  • RoutingRulesF.fromRule (cognitive 20) library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRulesF.scala:90 — RoutingRulesF.fromRule has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 3 (6 pts), boolean chains 1 (nesting depth added 9). 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 · ReusabilityMacros.deriveInnerSumType (cognitive 19) · ×1
  • ReusabilityMacros.deriveInnerSumType (cognitive 19) library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ReusabilityMacros.scala:345 — ReusabilityMacros.deriveInnerSumType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ReusabilityMacros.deriveInnerCaseClass (cognitive 18) · ×1
  • ReusabilityMacros.deriveInnerCaseClass (cognitive 18) library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ReusabilityMacros.scala:434 — ReusabilityMacros.deriveInnerCaseClass has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 9). 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 · RouterWithPropsConfigF._detectErrors (cognitive 17) · ×1
  • RouterWithPropsConfigF._detectErrors (cognitive 17) library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RouterWithPropsConfigF.scala:170 — RouterWithPropsConfigF._detectErrors has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 1 (4 pts), loops 1 (nesting depth added 11). 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1
  • Duplicated block (39 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:184 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:184-222 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:185-223 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) library/extra/src/main/scala-3/japgolly/scalajs/react/extra/internal/RouterMacros.scala:56 — library/extra/src/main/scala-3/japgolly/scalajs/react/extra/internal/RouterMacros.scala:56-79 | library/extra/src/main/scala-3/japgolly/scalajs/react/extra/internal/RouterMacros.scala:95-118 — 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 (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:484 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:484-506 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:486-508 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:287 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:287-307 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:288-308 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:890 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:890-909 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:902-921 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:144 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala:144-159 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala:145-160 — before extracting anything, compare `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/AsyncCallback.scala` and `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 330 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (166 lines × 2) · ×1
  • Duplicated block (166 lines × 2) library/callback/src/main/scala-2/japgolly/scalajs/react/callback/Callback.scala:25 — library/callback/src/main/scala-2/japgolly/scalajs/react/callback/Callback.scala:25-202 | library/callback/src/main/scala-3/japgolly/scalajs/react/callback/Callback.scala:39-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `library/callback/src/main/scala-2/japgolly/scalajs/react/callback/Callback.scala:25` 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 (97 lines × 2) · ×1
  • Duplicated block (97 lines × 2) library/coreBundleCBIO/src/main/scala/japgolly/scalajs/react/internal/ReactCallbackExtensions.scala:11 — library/coreBundleCBIO/src/main/scala/japgolly/scalajs/react/internal/ReactCallbackExtensions.scala:11-107 | library/coreBundleCallback/src/main/scala/japgolly/scalajs/react/internal/ReactCallbackExtensions.scala:11-107 — before extracting anything, compare `library/coreBundleCBIO/src/main/scala/japgolly/scalajs/react/internal/ReactCallbackExtensions.scala` and `library/coreBundleCallback/src/main/scala/japgolly/scalajs/react/internal/ReactCallbackExtensions.scala` as WHOLE FILES: 100% 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. Read the line range as the matched WINDOW rather than a finished unit: at `library/coreBundleCBIO/src/main/scala/japgolly/scalajs/react/internal/ReactCallbackExtensions.scala:11` 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 (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) library/extraExtMonocle2/src/main/scala/japgolly/scalajs/react/ReactMonocle.scala:12 — library/extraExtMonocle2/src/main/scala/japgolly/scalajs/react/ReactMonocle.scala:12-33 | library/extraExtMonocle3/src/main/scala/japgolly/scalajs/react/ReactMonocle.scala:12-33 — before extracting anything, compare `library/extraExtMonocle2/src/main/scala/japgolly/scalajs/react/ReactMonocle.scala` and `library/extraExtMonocle3/src/main/scala/japgolly/scalajs/react/ReactMonocle.scala` as WHOLE FILES: 100% 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. Read the line range as the matched WINDOW rather than a finished unit: at `library/extraExtMonocle2/src/main/scala/japgolly/scalajs/react/ReactMonocle.scala:12` 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 lines × 3) · ×1
  • Duplicated block (50 lines × 3) library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/Hooks.scala:20 — library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/Hooks.scala:20-91 | library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21-261 | library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala:12-61 — before extracting anything, compare `library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala` and `library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 723 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21` 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. 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 (50 lines × 4) · ×1
  • Duplicated block (50 lines × 4) library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/Hooks.scala:20 — library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/Hooks.scala:20-91 | library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21-261 | library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/events.scala:13-241 | library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala:12-61 — before extracting anything, compare `library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala` and `library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 723 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21` 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. 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 (50 lines × 2) · ×1
  • Duplicated block (50 lines × 2) library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21 — library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21-261 | library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala:12-61 — before extracting anything, compare `library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala` and `library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/facade/FireEvent.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 723 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `library/facadeMain/src/main/scala/japgolly/scalajs/react/facade/React.scala:21` 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. 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: downstream-tests/macros — downstream-tests/macros: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: ScalaJsReactConfigMacros (LCOM4 4) library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/internal/ScalaJsReactConfigMacros.scala:10 — ScalaJsReactConfigMacros'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.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity library/ghpages/html/dev2.html:12 — `https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.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. 6 such include(s) across the repository's markup.
Minor — 19 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×7
  • Orphaned file library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRule.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 library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/react17.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 library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Router.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 library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/Delayed.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 library/extra/src/main/scala/japgolly/scalajs/react/extra/router/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 library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/extra.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 library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Urls.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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch library/coreGeneric/src/main/scala/japgolly/scalajs/react/ReactCaughtError.scala:19 — `rawErrorString` swallows every exception into `""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch case or in the Scaladoc, and the row stops firing.
  • Silent fallback default in catch library/util/src/main/scala/japgolly/scalajs/react/util/JsUtil.scala:30 — `safeToString` swallows every exception into `"?"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch case or in the Scaladoc, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: MouseLike (16 abstract members) library/testingLibraryDom/src/main/scala/japgolly/scalajs/react/testing_library/dom/SimEvent.scala:264 — `MouseLike` declares 16 abstract members: `screenX`, `screenY`, `clientX`, `clientY`, `pageX`, `pageY`, `movementX`, `movementY`, `altKey`, `ctrlKey`, `metaKey`, `shiftKey`, `button`, `buttons`, `defaultPrevented`, `toJs`. 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. 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.
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): jsdom downstream-tests/package.json:3 — jsdom is pinned at 26.1.0; registry.npmjs.org publishes 30.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `library` (31522 LoC, 1257 module-visible types across 64 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.
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 7 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: library/extra/src/main/scala/japgolly/scalajs/react/extra/router/RoutingRule.scala, library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/react17.scala, library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Router.scala, library/coreGeneric/src/main/scala/japgolly/scalajs/react/component/Delayed.scala, library/extra/src/main/scala/japgolly/scalajs/react/extra/router/package.scala, library/coreGeneric/src/main/scala/japgolly/scalajs/react/hooks/extra.scala, library/extra/src/main/scala/japgolly/scalajs/react/extra/router/Urls.scala (9 orphaned of 125 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 125 of the 289 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
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add 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 2368 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.
X10 · Duplicated predicate · Duplicated predicate · ×1
  • Duplicated predicate library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/ScalaJsReactConfig.scala:18 — `P.updateNeeded(i.currentProps, i.nextProps) || S.updateNeeded(i.currentState, i.nextState)` appears character-identically in 2 files — library/coreGeneric/src/main/scala-2/japgolly/scalajs/react/ScalaJsReactConfig.scala, library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ScalaJsReactConfig.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.
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 250 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.
Minor — 2 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×2
  • Outdated (npm): react — react is pinned at 19.3.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-dom — react-dom is pinned at 19.3.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2ea09d3e2d114320a49386e8dbd0bab9/history.json --exit-code 0 --source .0artifacts/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-2ea09d3e2d114320a49386e8dbd0bab9/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude react-umd .7artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update2artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 14 file(s) — `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/AsyncCallback.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/Callback.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackOption.scala`, `library/callback/src/main/scala-3/japgolly/scalajs/react/callback/CallbackTo.scala`, `library/coreGeneric/src/main/scala-3/japgolly/scalajs/react/ReusabilityMacros.scala`, … (+9 more) — so the PII/GDPR sweep did not cover them at all.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a176ef-59c8-70fd-b670-35b522d737ae · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 18 · Warnings: 201 · Recommendations: 19 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 06:39 UTC.

Downloadable artifacts

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

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