Public report of UdashFramework/udash-core, published 21 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, 21 October 2026, 08:15 UTC · Survey ID cd_d348c702a237432d94d2d0fc9316c612

UdashFramework/udash-core

Measured 21 October 2026, 08:03 UTC, at code version fa96305

Knowledge freshness: not measured

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

CAI score 42out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 1 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.

Performance 81 Strong Security and Compliance 81 Adequate Architecture 60 Adequate Maturity 59 Adequate Code Health 34 Weak Production Readiness 34 Weak

A small codebase: 11,381 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 34

Findings by how serious they are

27 critical 177 serious 45 minor

10 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
21 October 2026, 08:03 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 ▸

72of 75 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
226of 249 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
75dimensions across 6 lenses, read from 11,381 lines of product code in 6 projects.
Chapters

Executive summary

UdashFramework/udash-core scores 42 out of 100 and is rated Weak, while four of its six lenses score higher still: Security and Compliance at 81, Architecture at 60 and Maturity at 59, all rated Adequate, and Performance at 81, rated Strong.

The score is lower than those four because the weakest lens counts most, and here that is Production Readiness, which scores 34 and is rated Weak. Its Dependency Hygiene dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion, and if Production Readiness rose to 70, the score would rise from 42 to about 50.

27 findings are critical: 21 in Static Analysis (SAST), four in Circular Imports, one in Change Coupling and one in Dependency Vulnerabilities.

Watchdog couldn't measure 9 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 11,381 lines, which would take an estimated 0.1 person-years, around €17,000, to rebuild.

Code Health 34 Weak, capped by Type Safety, Dead Code and Nullable reference types Architecture 60 Adequate, capped by Project Cohesion and Circular Imports Maturity 59 Adequate, capped by Architecture documentation Production Readiness 34 Weak, capped by Test Coverage, Dependency Hygiene and Security & performance tooling Security and Compliance 81 Adequate, capped by Supply-chain Provenance & Signing Performance 81 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.
Production Readiness 34 · counts for 46%Code Health 34 · counts for 25%Maturity 59 · counts for 14%Architecture 60 · counts for 8%Security and Compliance 81 · counts for 4%Performance 81 · counts for 2%

If Production Readiness rose from 34 to 70, the lowest score rated Strong, the score would rise from 42 to about 50.

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

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

  • Dependency Vulnerabilities · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Large Files · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js: 1624 lines of code project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js
  • Large Files · project/target/node-modules/webjars/source-map/lib/source-map-consumer.js: 1020 lines of code project/target/node-modules/webjars/source-map/lib/source-map-consumer.js
  • Large Files · project/target/node-modules/webjars/npm/lib/install.js: 804 lines of code project/target/node-modules/webjars/npm/lib/install.js
  • Large Files · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js: 794 lines of code project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js
  • Large Files · project/target/node-modules/webjars/npm/lib/install/deps.js: 655 lines of code project/target/node-modules/webjars/npm/lib/install/deps.js
  • Large Files · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js: 554 lines of code project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js
  • Large Files · project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js: 522 lines of code project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js
  • Large Files · project/target/node-modules/webjars/npm/lib/ls.js: 459 lines of code project/target/node-modules/webjars/npm/lib/ls.js
  • Large Files · project/target/node-modules/webjars/tslib/tslib.js: 445 lines of code project/target/node-modules/webjars/tslib/tslib.js
  • Large Files · project/target/node-modules/webjars/npm/lib/npm.js: 427 lines of code project/target/node-modules/webjars/npm/lib/npm.js
  • Large Files · project/target/node-modules/webjars/source-map/lib/util.js: 427 lines of code project/target/node-modules/webjars/source-map/lib/util.js
  • Large Files · project/target/node-modules/webjars/npm/lib/utils/tar.js: 401 lines of code project/target/node-modules/webjars/npm/lib/utils/tar.js

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: 433 findings

These 433 critical or serious findings were in the previous survey, on 5 October 2026, and are gone from this one. The first 100 are listed here.

  • Supply-chain Provenance & Signing REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) project/target/node-modules/webjars/npm/lib/outdated.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) project/target/node-modules/webjars/npm/lib/owner.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) project/target/node-modules/webjars/source-map/lib/source-map-consumer.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/box-shadow.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-media-queries.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/npm/lib/outdated.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/npm/lib/owner.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/npm/lib/ping.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/npm/lib/utils/completion/installed-shallow.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) project/target/node-modules/webjars/npm/lib/utils/tar.js
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) project/target/node-modules/webjars/source-map/lib/source-node.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/has-inherit.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/rules-overlap.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) project/target/node-modules/webjars/npm/lib/bugs.js
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) project/target/node-modules/webjars/npm/lib/config/clear-credentials-by-uri.js
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) project/target/node-modules/webjars/npm/lib/install/deps.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/optimize.js
  • Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/extract-properties.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/restructure.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) project/target/node-modules/webjars/clone/clone.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) project/target/node-modules/webjars/npm/lib/outdated.js
  • Code Duplication · Duplicated block (5 lines × 3 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js
  • Code Duplication · Duplicated block (5 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/restore.js
  • Code Duplication · Duplicated block (5 lines × 3 locations) project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js
  • Code Duplication · Duplicated block (5 lines × 2 locations) project/target/node-modules/webjars/npm/lib/pack.js
  • Code Duplication · Duplicated block (5 lines × 2 locations) project/target/node-modules/webjars/npm/lib/run-script.js
  • Code Duplication · Duplicated block (5 lines × 3 locations) project/target/node-modules/webjars/tslib/tslib.es6.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clone/clone.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/writer/helpers.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/completion.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/clean.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/help.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/options/format.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/pack.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/options/optimization-level.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/help-search.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/inflate-shrinkwrap.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/publish.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/link.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/wrap-for-optimizing.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/value-optimizers/color/shorten-hex.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/save.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/options/compatibility.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/run-script.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/actions.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/reduce-non-adjacent.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/search/format-package-stream.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/dedupe.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/dist-tag.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/diff-trees.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/auth/legacy.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/source-map/lib/base64-vlq.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/optimize.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/cache.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/mutate-into-logical-tree.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/unbuild.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/reader/load-original-sources.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/access.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/utils/correct-mkdir.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/source-map/lib/array-set.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/es6-promise/lib/es6-promise/asap.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/fetch-package-metadata.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/unpublish.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/config/cmd-list.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/source-map/lib/quick-sort.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/doctor.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/reader/rewrite-url.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/source-map/lib/binary-search.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/config/pacote.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/search.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-media-queries.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/writer/source-maps.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/mkdirp/index.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/reader/rebase.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/utils/map-to-registry.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/action/extract.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/action/move.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/action/finalize.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/validate-tree.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/reorderable.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/bin/npm-cli.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/value-optimizers/color.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-non-adjacent-by-body.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/options/rounding-precision.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/utils/completion/installed-shallow.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise/race.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/action/remove.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/install/node.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/uninstall.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/source-map/lib/mapping-list.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/restore-from-optimizing.js
  • Test Coverage · No test reaches this file project/target/node-modules/webjars/npm/lib/rebuild.js
Rebuild cost: about €17,000 · Estimate
Cost to rebuild€5,700 to €28,000, for 94 to 299 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 11,381 lines of product code

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

Top priorities

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

1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
2
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
Raises the score by about 2 points · Low effort · Project Cohesion
3
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 3 points · Medium effort · Dead Code

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 €17,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 34 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

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.

199 modules, with 398 dependencies between them. 8 loops run through 43 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 159 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 bootstrap.button.UdashButton.ButtonTag2 bootstrap.collapse.UdashCollapse.CollapseEvent3 bootstrap.utils.BootstrapStyles4 core5 css6 logging7 bindings.inputs8 rest.raw9 web.commons.styles.components10 web.commons.views11 rest12 utils13 properties.single14 rpc.internals15 properties.model16 rpc17 properties18 properties.seq19 bindings.modifiers20 bindings21 component22 i18n23 web.commons.components24 bootstrap.carousel.UdashCarousel25 bootstrap.datepicker.UdashDatePicker26 bootstrap.utils27 rest.openapi28 web.guide.demos29 bootstrap.alert30 bootstrap.button31 bootstrap.carousel32 bootstrap.collapse33 bootstrap.datepicker34 bootstrap.form35 routing36 io.udash37 bootstrap.form.UdashForm38 bootstrap.form.FormElementsFactory39 web.guide40 web.homepage
1 bootstrap.button.UdashButton.ButtonTag
2 bootstrap.collapse.UdashCollapse.CollapseEvent
3 bootstrap.utils.BootstrapStyles
4 core
5 css
6 logging
7 bindings.inputs3962
8 rest.raw1113
9 web.commons.styles.components10
10 web.commons.views1241
11 rest104023
12 utils111
13 properties.single5245
14 rpc.internals11216
15 properties.model5
16 rpc713
17 properties31123
18 properties.seq8212
19 bindings.modifiers436
20 bindings111
21 component111
22 i18n11
23 web.commons.components21311
24 bootstrap.carousel.UdashCarousel11
25 bootstrap.datepicker.UdashDatePicker11
26 bootstrap.utils1111
27 rest.openapi18983
28 web.guide.demos2
29 bootstrap.alert1112141
30 bootstrap.button31143
31 bootstrap.carousel11211
32 bootstrap.collapse42
33 bootstrap.datepicker11231
34 bootstrap.form122132
35 routing152411
36 io.udash11111111
37 bootstrap.form.UdashForm12111
38 bootstrap.form.FormElementsFactory22211112
39 web.guide41212
40 web.homepage41129
Uses a module listed above itPart of a loopThe module itself
1 bootstrap.button.UdashButton.ButtonTag2 bootstrap.collapse.UdashCollapse.CollapseEvent3 bootstrap.utils.BootstrapStyles4 core5 css6 logging7 bindings.inputs8 rest.raw9 web.commons.styles.components10 web.commons.views11 rest12 utils13 properties.single14 rpc.internals15 properties.model16 rpc17 properties18 properties.seq19 bindings.modifiers20 bindings21 component22 i18n23 web.commons.components24 bootstrap.carousel.UdashCarousel25 bootstrap.datepicker.UdashDatePicker26 bootstrap.utils27 rest.openapi28 web.guide.demos29 bootstrap.alert30 bootstrap.button31 bootstrap.carousel32 bootstrap.collapse33 bootstrap.datepicker34 bootstrap.form35 routing36 io.udash37 bootstrap.form.UdashForm38 bootstrap.form.FormElementsFactory39 web.guide40 web.homepagebootstrap.button.UdashButton.ButtonTag1bootstrap.collapse.UdashCollapse.CollapseEvent2bootstrap.utils.BootstrapStyles3core4css5logging6bindings.inputs7rest.raw8web.commons.styles.components9web.commons.views10rest11utils12properties.single13rpc.internals14properties.model15rpc16properties17properties.seq18bindings.modifiers19bindings20component21i18n22web.commons.components23bootstrap.carousel.UdashCarousel24bootstrap.datepicker.UdashDatePicker25bootstrap.utils26rest.openapi27web.guide.demos28bootstrap.alert29bootstrap.button30bootstrap.carousel31bootstrap.collapse32bootstrap.datepicker33bootstrap.form34routing35io.udash36bootstrap.form.UdashForm37bootstrap.form.FormElementsFactory38web.guide39web.homepage403962111310124110402311152451121657133112382124361111111121311111111111898321112141311431121142112311221321524111111111112111222111124121241129+159 more modules (most-connected shown)

At a glance — Code Health · 34% · Weak · gated by R1, R7, X5 ·

The Good
D1 · Scala Cyclomatic Complexity 9.4 D2 · Scala Cognitive Complexity 8.8 D3 · Scala God Classes 9.3 D4 · Scala Code Duplication 9.8 D17 · Scala Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R10 · React / TS Code Duplication 9.0 R3 · React / TS Large Files 8.6 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 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0
The Ugly
R1 · React / TS Type Safety 0.1 R2 · React / TS Cyclomatic Complexity 4.0 R7 · React / TS Dead Code 0.0 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 60% · Adequate · gated by D26, R9 ·

The Good
D5 · Scala Coupling 10.0 D6 · Scala Cohesion (LCOM4) 10.0 D35 · Scala Change Coupling 10.0 AX10 · Repo Code composition 7.4 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0
The Ugly
D26 · Scala Project Cohesion 0.0 R9 · React / TS Circular Imports 1.2

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

The Good
D15 · Scala Churn × Complexity Hotspots 9.5 D16 · Scala Bus Factor 9.4 D21 · Scala Naming Consistency 10.0 M1 · Repo Documentation (README) 7.7 M3 · Repo Folder & project structure 10.0
The Bad
D19 · Scala Documentation Quality 6.0 M4 · Repo Documentation accuracy 6.0
The Ugly
D20 · Scala ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 34% · Weak · gated by R4, R8, P3 ·

The Good
D9 · Scala Test Distribution 10.0 D12 · Scala Dependency Hygiene 9.8 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 R5 · React / TS Dependency Freshness 9.8 R6 · React / TS Tooling 10.0
The Bad
P2 · Repo Observability 6.0 P4 · Repo Deployment & Rollback 5.0
The Ugly
P3 · Repo Security & performance tooling 1.0 R4 · React / TS Test Coverage 0.1 R8 · React / TS Dependency Hygiene 0.0

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

The Good
D28 · Scala Secrets (history) 10.0 D29 · Scala Static Analysis (SAST) 7.1 D30 · Scala Dependency Vulnerabilities 9.2 D43 · Scala Malicious Dependencies 10.0 D44 · Scala Platform End-of-Life 10.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 — Performance · 81% · Strong ·

The Good
PF1 · Repo Benchmark discipline 8.5 PF3 · Repo Async & latency hygiene 10.0
The Bad
PF2 · Repo Allocation hygiene 6.8

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 — Injection21High / Critical
A03:2025 — Software Supply Chain Failures8High / Critical

Roadmap

First, eliminate dead code and unused exports to reduce maintenance overhead and rebuild times. Next, migrate remaining JavaScript files to TypeScript and clean up dependencies by removing unused packages and correctly categorizing dev-only tools. Then, increase test coverage by adding tests for currently unreached modules to ensure code reliability. Finally, integrate static analysis security scanning into the CI pipeline to automatically block security regressions.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.+2.1 ptsLowADR Quality
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.+1.7 ptsLowProject Cohesion
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+3.3 ptsMediumDead Code
Migrate the remaining .js/.jsx files to TypeScript.+3.2 ptsMediumType Safety
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+3.1 ptsMediumDependency Hygiene
Add tests that import the unreached modules (directly or through their public entry).+3.1 ptsMediumTest Coverage
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.6 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.2 ptsMediumNullable reference types

File quality

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

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedDependency Vulnerabilities: High CVE: REDACTED
core/src/test/scala/io/udash/properties/PropertyTest.scala7.3MixedExplicit Debt: TodoComment
macros/src/main/scala/io/udash/macros/PropertyMacros.scala7.8MixedCyclomatic Complexity: PropertyMacros.reifyModelPart (cyclomatic 22)
rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala7.8MixedCyclomatic Complexity: RestServlet.service (cyclomatic 19)
rest/src/main/scala/io/udash/rest/raw/RawRest.scala7.8MixedCognitive Complexity: RawRest.resolveAndHandle (cognitive 26)
REDACTED7.9MixedDependency Vulnerabilities: Medium CVE: REDACTED
guide/backend/src/main/scala/io/udash/web/server/ApplicationServer.scala8.0Near-cleanChange Coupling: Boundary-crossing change coupling: ApplicationServer.scala ↔ REDACTED
rest/src/main/scala/io/udash/rest/SttpRestClient.scala8.2Near-cleanExplicit Debt: TodoComment
bootstrap4/.js/src/main/scala/io/udash/bootstrap/datepicker/UdashDatePicker.scala8.5Near-cleanCognitive Complexity: UdashDatePicker.optionsToJsDict (cognitive 26)
rpc/.jvm/src/main/scala/io/udash/rpc/AtmosphereService.scala8.5Near-cleanCognitive Complexity: AtmosphereService.handleRequest (cognitive 18)
bootstrap4/.js/src/main/scala/io/udash/bootstrap/utils/UdashIcons.scala8.5Near-cleanGod Classes: FileTooLong: utils/UdashIcons.scala
bootstrap4/.js/src/main/scala/io/udash/bootstrap/utils/BootstrapStyles.scala8.5Near-cleanGod Classes: FileTooLong: utils/BootstrapStyles.scala
rest/src/main/scala/io/udash/rest/raw/PlainValue.scala8.5Near-cleanCode Duplication: Duplicated block (6 lines × 2)
guide/shared/src/main/scala/io/udash/web/commons/styles/utils/MediaQueries.scala8.5Near-cleanCode Duplication: Duplicated block (23 lines × 2)
core/src/main/scala/io/udash/properties/seq/CombinedReadableSeqProperty.scala8.5Near-cleanCode Duplication: Duplicated block (14 lines × 4)
guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/demos/DateDemo.scala8.5Near-cleanCode Duplication: Duplicated block (9 lines × 3)
guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/FrontendBindingsView.scala8.5Near-cleanCode Duplication: Duplicated block (5 lines × 2)

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

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

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

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

Could not be resolved — 10

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

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

What we checked — 75 dimensions across the health lenses
D1D2D3D4D5D6D9D12D13D14D15D16D17D19D20D21D26D28D29D30D35D36D43D44AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF2PF3R1R10R2R3R4R5R6R7R8R9X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X5

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 249 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 measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a15d7c-4ef5-7f49-9311-82a1f86803a9.

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 reliability not included — the Scala suite (repository root, 66 test files) did not finish re-running within its budget: the sbt build did not finish re-running within its tier budget.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. 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: 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.
  • 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. `bootstrap4/.js/src/main/scala/io/udash/bootstrap/datepicker/UdashDatePicker.scala`, `bootstrap4/.js/src/main/scala/io/udash/bootstrap/form/UdashForm.scala`, `core/src/main/scala/io/udash/properties/CallbackSequencer.scala`, `scripts/authors.scala` 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.
  • D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 58 commits in the last 90 days, yet 51 of 61 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
  • AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in rpc/src/main/scala/io/udash/rpc/serialization/ExceptionCodecRegistry.scala, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 3 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 30 further occurrence(s) are not listed individually; the score already reflects all 70.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 291 further occurrence(s) are not listed individually; the score already reflects all 331.
  • R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 111 further occurrence(s) are not listed individually; the score already reflects all 151.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity9.4 / 10Stronggated by 2 serious findings✓ 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 9.4 / 10 · rule-coverage 100% · ceiling Prevented

2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PropertyMacros.reifyModelPart at 22. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being StatesToViewFactoryDef.matchStateToResolver at 35 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: guide/guide/.js/src/main/scala/io/udash/web/guide/StatesToViewFactoryDef.scala (StatesToViewFactoryDef.matchStateToResolver at 35), guide/guide/.js/src/main/scala/io/udash/web/guide/views/rpc/demos/GenCodecsDemoComponent.scala (GenCodecsDemoPresenter.onButtonClick at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

PropertyMacros.reifyModelPart (cyclomatic 22)macros/src/main/scala/io/udash/macros/PropertyMacros.scala:123
RestServlet.service (cyclomatic 19)rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala:157

What to do

  1. Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PropertyMacros.reifyModelPart (cyclomatic 22), RestServlet.service (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 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 Complexity8.8 / 10Strong✓ 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 8.8 / 10 · rule-coverage 100% · ceiling Prevented

6 method(s) exceeded the cognitive complexity threshold of 15; the worst was PropertyMacros.reifyModelPart at 31.

PropertyMacros.reifyModelPart (cognitive 31)macros/src/main/scala/io/udash/macros/PropertyMacros.scala:123
RestServlet.service (cognitive 28)rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala:157
UdashDatePicker.optionsToJsDict (cognitive 26)bootstrap4/.js/src/main/scala/io/udash/bootstrap/datepicker/UdashDatePicker.scala:123
RawRest.resolveAndHandle (cognitive 26)rest/src/main/scala/io/udash/rest/raw/RawRest.scala:277
RawRest.handleResolvedWithStreaming (cognitive 22)rest/src/main/scala/io/udash/rest/raw/RawRest.scala:152

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

What to do

  1. Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with PropertyMacros.reifyModelPart (cognitive 31), RestServlet.service (cognitive 28), UdashDatePicker.optionsToJsDict (cognitive 26). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 8.8 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 Classes9.3 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 over-large unit(s) detected — types, modules or files that carry too much.

FileTooLong: utils/UdashIcons.scala · ×2bootstrap4/.js/src/main/scala/io/udash/bootstrap/utils/UdashIcons.scala

What to do

  1. Resolve the 2 FileTooLong finding(s) in God Classes — start with UdashIcons.scala, BootstrapStyles.scala. — One of this dimension's main actionable groups (2 warning-level).
  2. 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.8 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

5 duplicated block group(s) detected.

Duplicated block (6 lines × 2)rest/src/main/scala/io/udash/rest/raw/PlainValue.scala:36
Duplicated block (23 lines × 2)guide/shared/src/main/scala/io/udash/web/commons/styles/utils/MediaQueries.scala:11
Duplicated block (14 lines × 4)core/src/main/scala/io/udash/properties/seq/CombinedReadableSeqProperty.scala:45
Duplicated block (9 lines × 3)guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/demos/DateDemo.scala:38
Duplicated block (5 lines × 2)guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/FrontendBindingsView.scala:49

What to do

  1. Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with PlainValue.scala. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Duplicated block (23 lines × 2) finding(s) in Code Duplication — start with MediaQueries.scala. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (14 lines × 4) finding(s) in Code Duplication — start with CombinedReadableSeqProperty.scala. — One of this dimension's main actionable groups (1 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 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 41 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

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

307 test methods: 305 unit, 2 integration, 0 BDD, 0 e2e. The Scala suite contributes 307 test case(s) across 39 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.8 / 10Exemplary✓ 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.8 / 10 · rule-coverage 100% · ceiling Verified

5 outdated direct sbt declarations. An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.

Outdated: ch.qos.logback:logback-classic · ×5

✓ On the Gold path — maintain.

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 20 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 2 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 1 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala (9×19=171)

Hotspot: rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scalarest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala:157

What to do

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

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

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

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

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

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

3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 44 of the 169 production source files in this repository: 108 are under the ~2,400-byte size floor this dimension measures over, and the remaining 17 have no attributable history left to measure.

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

✓ On the Gold path — maintain.

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

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

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

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

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

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

TodoComment · ×3core/src/test/scala/io/udash/properties/PropertyTest.scala:365

What to do

  1. Resolve the 3 TodoComment finding(s) in Explicit Debt — start with PropertyTest.scala (2), SttpRestClient.scala. — One of this dimension's main actionable groups (3 warning-level).
  2. 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 QualityAdequate◐ Sampled · advisory

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

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

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

The repository's single README is a well-structured overview of Udash (a Scala.js framework for beautiful web apps) with strong branding and an outline that promises much but clips mid-sentence. It describes the combined forces of Scala and JavaScript, the type-safe HTML/CSS/JS layer, compiled-to-JS efficiency, shared Scala code, and why Udash matters, then clips before covering installation, usage examples, contribution guidance, or a licence statement — all standard sections for a framework project.

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The repository's single README is a well-structured overview of Udash (a Scala.js framework for beautiful web apps) with strong branding and an outline that promises much but clips mid-sentence. It describes the combined forces of Scala and JavaScript, the type-safe HTML/CSS/JS layer, compiled-to-JS efficiency, shared Scala code, and why Udash matters, then clips before covering installation, usage examples, contribution guidance, or a licence statement — all standard sections for a framework project.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

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)7.1 / 10Adequategated by 21 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 7.1 / 10 · rule-coverage 100% · ceiling Documented

21 finding(s): 0 critical, 21 high, 0 medium, 0 low. 19 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 4 file(s) — `bootstrap4/.js/src/main/scala/io/udash/bootstrap/datepicker/UdashDatePicker.scala`, `bootstrap4/.js/src/main/scala/io/udash/bootstrap/form/UdashForm.scala`, `core/src/main/scala/io/udash/properties/CallbackSequencer.scala`, `scripts/authors.scala` (line 18, line 20, line 24, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED

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

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

D30 · Dependency Vulnerabilities9.2 / 10Adequategated by 1 critical finding✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED

What to do

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

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

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ 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

Strongest change-coupling: ApplicationServer.scala↔REDACTED 63%

Boundary-crossing change coupling: ApplicationServer.scala ↔ REDACTEDguide/backend/src/main/scala/io/udash/web/server/ApplicationServer.scala:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ApplicationServer.scala. — One of this dimension's main actionable groups (1 issue-level).

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

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

What to do

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition7.4 / 10Strong✓ 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 segregation10.0 / 10Exemplary✓ Tool-verified

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

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

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.7 / 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 2 of 15 project(s) that lack one — worth up to 0.3 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

Maturity · Maturity — Whether the 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 accuracy6.0 / 10Adequate◐ Sampled · advisory

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

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

  • project/target/node-modules/webjars/clean-css/README.md installs `clean-css-cli` (`npm install clean-css-cli`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — project/target/node-modules/webjars/clean-css/README.md:598
  • project/target/node-modules/webjars/clean-css/README.md runs `npm run check # to lint JS sources with [JSHint](https://github.com/jshint/jshint/)`, but no package.json declares a `check` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — project/target/node-modules/webjars/clean-css/README.md:960

What to do

  • Reconcile the README with reality: project/target/node-modules/webjars/clean-css/README.md installs `clean-css-cli` (`npm install clean-css-cli`), but no package.json declares it; project/target/node-modules/webjars/clean-css/README.md runs `npm run check # to lint JS sources with [JSHint](https://github.com/jshint/jshint/)`, but no package.json declares a `check` script.
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 · Observability6.0 / 10Adequate✓ 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.

  • Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `project/target/node-modules/webjars/mkdirp`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling1.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add 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 8113 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.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.

PF1 · Benchmark discipline8.5 / 10Strong✓ Tool-verified

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

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

  • A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/src/main/scala/io/udash/rest/StreamingRestApiBenchmark.scala

What to do

  • Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene6.8 / 10Adequate✓ Tool-verified

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

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

What to do

  • Raise allocation-aware density on the hot paths — currently 21 use(s) across 13,207 production line(s) (~1.6/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.

R1 · Type Safety0.1 / 10Critical✓ Tool-verified

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

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

  • 2 typed · 397 plain JS — the untyped files are project/target/node-modules/webjars/clean-css/index.js, project/target/node-modules/webjars/clean-css/lib/clean.js, project/target/node-modules/webjars/clean-css/lib/optimizer/clone.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js (+391 more).

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.0 / 10Exemplary✓ Tool-verified

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

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

  • project/target/node-modules/webjars/tslib/tslib.es6.js:17 · project/target/node-modules/webjars/tslib/tslib.es6.mjs:17 — these 2 files are line-for-line copies of one another — 245 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — project/target/node-modules/webjars/tslib/tslib.es6.js:17
  • project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:16 · project/target/node-modules/webjars/clean-css/lib/reader/load-original-sources.js:9 — the two spans are one implementation copied and then locally edited — 460 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:16
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:63 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:540 — the two spans are one implementation copied and then locally edited — 341 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:63
  • project/target/node-modules/webjars/source-map/lib/util.js:304 · project/target/node-modules/webjars/source-map/lib/util.js:343 · project/target/node-modules/webjars/source-map/lib/util.js:397 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — project/target/node-modules/webjars/source-map/lib/util.js:304
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:276 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:373 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:276
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:678 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:709 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:678
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:164 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:196 — 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. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:164
  • project/target/node-modules/webjars/npm/lib/config/pacote.js:89 · project/target/node-modules/webjars/npm/lib/utils/correct-mkdir.js:42 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — project/target/node-modules/webjars/npm/lib/config/pacote.js:89
  • project/target/node-modules/webjars/clean-css/lib/writer/simple.js:6 · project/target/node-modules/webjars/clean-css/lib/writer/source-maps.js:15 — the two spans are one implementation copied and then locally edited — 140 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — project/target/node-modules/webjars/clean-css/lib/writer/simple.js:6
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:516 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:537 — 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. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:516
  • project/target/node-modules/webjars/npm/lib/config.js:213 · project/target/node-modules/webjars/npm/lib/config.js:230 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/npm/lib/config.js:213
  • project/target/node-modules/webjars/npm/lib/install/exists.js:7 · project/target/node-modules/webjars/npm/lib/install/writable.js:9 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — project/target/node-modules/webjars/npm/lib/install/exists.js:7
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-media-queries.js:39 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-non-adjacent-by-selector.js:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-media-queries.js:39
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:344 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:365 — 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. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:344
  • project/target/node-modules/webjars/npm/lib/auth/legacy.js:28 · project/target/node-modules/webjars/npm/lib/auth/legacy.js:94 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/npm/lib/auth/legacy.js:28
  • project/target/node-modules/webjars/npm/lib/dist-tag.js:73 · project/target/node-modules/webjars/npm/lib/dist-tag.js:104 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/npm/lib/dist-tag.js:73
  • project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:650 · project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:795 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:650
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:42 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:55 — 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. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:42
  • project/target/node-modules/webjars/npm/lib/build.js:32 · project/target/node-modules/webjars/npm/lib/utils/lifecycle.js:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/npm/lib/build.js:32
  • project/target/node-modules/webjars/npm/lib/prefix.js:1 · project/target/node-modules/webjars/npm/lib/root.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — project/target/node-modules/webjars/npm/lib/prefix.js:1
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:125 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:579 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:125
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:74 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:171 — 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. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:74
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:131 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:181 — 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. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:131
  • project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:189 · project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:216 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:189
  • project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:262 · project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:316 — 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. — project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:262
  • project/target/node-modules/webjars/clean-css/lib/reader/rebase.js:13 · project/target/node-modules/webjars/clean-css/lib/reader/rebase.js:42 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/reader/rebase.js:13
  • project/target/node-modules/webjars/clean-css/lib/clean.js:88 · project/target/node-modules/webjars/clean-css/lib/clean.js:121 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/clean.js:88
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:3 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:14 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:185 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:3
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:3 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/outline.js:3 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:3
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-adjacent.js:17 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-non-adjacent-by-body.js:40 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-adjacent.js:17
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:300 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:750 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:300
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:452 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:704 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:452
  • project/target/node-modules/webjars/clean-css/lib/writer/helpers.js:104 · project/target/node-modules/webjars/clean-css/lib/writer/helpers.js:219 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/writer/helpers.js:104
  • project/target/node-modules/webjars/clean-css/lib/writer/one-time.js:13 · project/target/node-modules/webjars/clean-css/lib/writer/one-time.js:31 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/writer/one-time.js:13
  • project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:249 · project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:823 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:249
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:61 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:244 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:61
  • project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:1 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/border-radius.js:1 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/margin.js:1 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/outline.js:1 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:1
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:254 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:265 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:254
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:752 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:763 — 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. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:752
  • project/target/node-modules/webjars/mkdirp/index.js:12 · project/target/node-modules/webjars/mkdirp/index.js:59 — 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. — project/target/node-modules/webjars/mkdirp/index.js:12

What to do

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

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

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

  • intoTokens has cyclomatic complexity 256 and cognitive complexity 165; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:82
  • overrideProperties has cyclomatic complexity 114 and cognitive complexity 249; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/override-properties.js:246
  • removeWhitespace has cyclomatic complexity 71 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js:64
  • font has cyclomatic complexity 48 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:266
  • applyIgnores has cyclomatic complexity 48 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/npm/lib/utils/tar.js:65
  • exports has cyclomatic complexity 47 and cognitive complexity 96; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/minimist/index.js:23
  • canReorderSingle has cyclomatic complexity 47 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/reorderable.js:19
  • errorMessage has cyclomatic complexity 41 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/npm/lib/utils/error-message.js:8
  • makeArchy_ has cyclomatic complexity 39 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/npm/lib/ls.js:344
  • isAllowedResource has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/reader/is-allowed-resource.js:9
  • _clone has cyclomatic complexity 34 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clone/clone.js:73
  • step has cyclomatic complexity 34 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×3) — project/target/node-modules/webjars/tslib/tslib.es6.js:129, project/target/node-modules/webjars/tslib/tslib.es6.mjs:129, project/target/node-modules/webjars/tslib/tslib.js:178
  • extractPseudoFrom has cyclomatic complexity 34 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/is-mergeable.js:73
  • specificity has cyclomatic complexity 34 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/specificity.js:16
  • restructure has cyclomatic complexity 33 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/restructure.js:24
  • background has cyclomatic complexity 31 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:136
  • optimizeBody has cyclomatic complexity 29 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/optimize.js:58
  • background has cyclomatic complexity 29 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/restore.js:16

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files8.6 / 10Strong✓ Tool-verified

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

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

  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js has 1624 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js:1
  • project/target/node-modules/webjars/source-map/lib/source-map-consumer.js has 1020 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:1
  • project/target/node-modules/webjars/npm/lib/install.js has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/npm/lib/install.js:1
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:1
  • project/target/node-modules/webjars/npm/lib/install/deps.js has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/npm/lib/install/deps.js:1
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js has 554 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:1
  • project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js:1
  • project/target/node-modules/webjars/npm/lib/ls.js has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/npm/lib/ls.js:1
  • project/target/node-modules/webjars/tslib/tslib.js has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/tslib/tslib.js:1
  • project/target/node-modules/webjars/npm/lib/npm.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/npm/lib/npm.js:1
  • project/target/node-modules/webjars/source-map/lib/util.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/source-map/lib/util.js:1
  • project/target/node-modules/webjars/npm/lib/utils/tar.js has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — project/target/node-modules/webjars/npm/lib/utils/tar.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.1 / 10Critical✓ Tool-verified

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

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

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js:1, project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:1, project/target/node-modules/webjars/npm/lib/install.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness9.8 / 10Exemplary✓ Tool-verified

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

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

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

R7 · Dead Code0.0 / 10Critical✓ Tool-verified

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

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

  • 15 file(s) (~1333 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — project/target/node-modules/webjars/es6-promise
  • Unreachable from the 23 application, 10 tooling and 68 test entry point(s) detected in this repo. Gate removals on `npm run lint` — an undetected custom entry would make these reachable.
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (project/target/node-modules/webjars/npm/lib/dedupe.js, project/target/node-modules/webjars/npm/lib/install-test.js, project/target/node-modules/webjars/npm/lib/install/action/global-install.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 25 in-repo import(s) from 11 other file(s) do name it (project/target/node-modules/webjars/npm/lib/dedupe.js, project/target/node-modules/webjars/npm/lib/install.js, project/target/node-modules/webjars/npm/lib/install/actions.js and 8 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install/deps.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×17) — project/target/node-modules/webjars/npm/lib/ls.js, project/target/node-modules/webjars/npm/lib/outdated.js, project/target/node-modules/webjars/npm/lib/view.js, …
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/pack.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/utils/tar.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 16 in-repo import(s) from 16 other file(s) do name it (project/target/node-modules/webjars/npm/lib/build.js, project/target/node-modules/webjars/npm/lib/install/action/install.js, project/target/node-modules/webjars/npm/lib/install/action/move.js and 13 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/utils/lifecycle.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/search/all-package-search.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/search/all-package-metadata.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (project/target/node-modules/webjars/npm/lib/cache.js, project/target/node-modules/webjars/npm/lib/install/action/extract.js, project/target/node-modules/webjars/npm/lib/install/action/finalize.js and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/utils/gently-rm.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/action/build.js, project/target/node-modules/webjars/npm/lib/link.js, project/target/node-modules/webjars/npm/lib/unbuild.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/build.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/save.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/shrinkwrap.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/config/pacote.js, project/target/node-modules/webjars/npm/lib/publish.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/pack.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/deps.js, project/target/node-modules/webjars/npm/lib/install/read-shrinkwrap.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install/inflate-shrinkwrap.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install.js, project/target/node-modules/webjars/npm/lib/install/deps.js, project/target/node-modules/webjars/npm/lib/uninstall.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install/save.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 4 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install/actions.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/search.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/search/format-package-stream.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/dedupe.js, project/target/node-modules/webjars/npm/lib/install.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install/diff-trees.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/adduser.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/auth/legacy.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (project/target/node-modules/webjars/npm/lib/outdated.js, project/target/node-modules/webjars/npm/lib/pack.js, project/target/node-modules/webjars/npm/lib/publish.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/cache.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/ls.js, project/target/node-modules/webjars/npm/lib/outdated.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/install/mutate-into-logical-tree.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/action/move.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/unbuild.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/search/all-package-metadata.js, project/target/node-modules/webjars/npm/lib/utils/locker.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/utils/correct-mkdir.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 8 in-repo import(s) from 7 other file(s) do name it (project/target/node-modules/webjars/npm/lib/bugs.js, project/target/node-modules/webjars/npm/lib/docs.js, project/target/node-modules/webjars/npm/lib/doctor/get-latest-npm-version.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/fetch-package-metadata.js
  • no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 7 in-repo import(s) from 6 other file(s) do name it (project/target/node-modules/webjars/npm/lib/cache.js, project/target/node-modules/webjars/npm/lib/fetch-package-metadata.js, project/target/node-modules/webjars/npm/lib/install/action/extract.js and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — project/target/node-modules/webjars/npm/lib/config/pacote.js

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in project/target/node-modules/webjars/clean-css/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports1.2 / 10Critical✓ Tool-verified

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

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

  • project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise/resolve.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js (one verified cycle inside a mutually-dependent group of 3 files) — project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js:11
  • project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise/all.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js — project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js:17
  • project/target/node-modules/webjars/npm/bin/npm-cli.js → project/target/node-modules/webjars/npm/lib/npm.js → project/target/node-modules/webjars/npm/bin/npm-cli.js (one verified cycle inside a mutually-dependent group of 6 files) — project/target/node-modules/webjars/npm/bin/npm-cli.js:35
  • project/target/node-modules/webjars/npm/lib/cache.js → project/target/node-modules/webjars/npm/lib/config/pacote.js → project/target/node-modules/webjars/npm/lib/pack.js → project/target/node-modules/webjars/npm/lib/cache.js (one verified cycle inside a mutually-dependent group of 16 files) — project/target/node-modules/webjars/npm/lib/cache.js:12

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
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` 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 handling10.0 / 10Exemplary○ Nothing flagged

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.

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

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 Health34%Weak — gated by R1, R7, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture60%Adequate — gated by D26, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity59%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness34%Weak — gated by R4, R8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security81%Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance81%StrongStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

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

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

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 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 — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC7 A11y enforcement — Frontend below the scale floor (13 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — 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 — ~8389 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
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — 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) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 125 value object(s); 3 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 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
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • S1 Web-Security Posture — No web surface: 162 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository builds on an HTTP-server library (guide/backend/src/main/scala/io/udash/web/server/ApplicationServer.scala:19 — `org.eclipse.jetty.server`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • 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 was 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
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 27 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js:11 — project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise/resolve.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/-internal.js (one verified cycle inside a mutually-dependent group of 3 files)
  • Import cycle (2 files) project/target/node-modules/webjars/npm/bin/npm-cli.js:35 — project/target/node-modules/webjars/npm/bin/npm-cli.js → project/target/node-modules/webjars/npm/lib/npm.js → project/target/node-modules/webjars/npm/bin/npm-cli.js (one verified cycle inside a mutually-dependent group of 6 files)
R9 · Circular Imports · Import cycle (3 files) · ×2
  • Import cycle (3 files) project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js:17 — project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise/all.js → project/target/node-modules/webjars/es6-promise/lib/es6-promise/enumerator.js
  • Import cycle (3 files) project/target/node-modules/webjars/npm/lib/cache.js:12 — project/target/node-modules/webjars/npm/lib/cache.js → project/target/node-modules/webjars/npm/lib/config/pacote.js → project/target/node-modules/webjars/npm/lib/pack.js → project/target/node-modules/webjars/npm/lib/cache.js (one verified cycle inside a mutually-dependent group of 16 files)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: ApplicationServer.scala ↔ REDACTED guide/backend/src/main/scala/io/udash/web/server/ApplicationServer.scala:1 — `guide/backend/src/main/scala/io/udash/web/server/ApplicationServer.scala` (context guide) and `REDACTED` (context project) sit in DIFFERENT parts of the tree yet change together 63% of the time (12 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `6c4ebafd` Refactor logging configuration (remove Janino) and improve resource h…; `b742878e` Switch Jetty from legacy GzipHandler to CompressionHandler; `e89d2920` Fix resource base under Jetty 12.0.8+ — run `git show` on any of them.
Serious — 177 finding(s)
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/install.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/install/deps.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/ls.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/npm.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/source-map/lib/util.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/tslib/tslib.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/override-properties.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/utils/tar.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/utils/lifecycle.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/config/core.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/es6-promise/lib/es6-promise/promise.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/source-map/lib/source-map-generator.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/outdated.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/npm/lib/config/defaults.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/source-map/lib/source-node.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/tslib/tslib.es6.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/tslib/tslib.es6.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/restructure.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×7
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/clean.js:88 — project/target/node-modules/webjars/clean-css/lib/clean.js:88 · project/target/node-modules/webjars/clean-css/lib/clean.js:121 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:3 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:3 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/outline.js:3 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:300 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:300 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:750 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:452 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:452 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:704 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/writer/helpers.js:104 — project/target/node-modules/webjars/clean-css/lib/writer/helpers.js:104 · project/target/node-modules/webjars/clean-css/lib/writer/helpers.js:219 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/writer/one-time.js:13 — project/target/node-modules/webjars/clean-css/lib/writer/one-time.js:13 · project/target/node-modules/webjars/clean-css/lib/writer/one-time.js:31 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:249 — project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:249 · project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:823 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×6
  • Duplicated block (11 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:125 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:125 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:579 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (11 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:74 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:74 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:171 — 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 (11 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:131 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:131 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/remove-unused-at-rules.js:181 — 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 (11 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:189 — project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:189 · project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:216 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (11 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:262 — project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:262 · project/target/node-modules/webjars/clean-css/lib/reader/read-sources.js:316 — 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 (11 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/reader/rebase.js:13 — project/target/node-modules/webjars/clean-css/lib/reader/rebase.js:13 · project/target/node-modules/webjars/clean-css/lib/reader/rebase.js:42 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×4
  • Duplicated block (13 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:344 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:344 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:365 — 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 (13 lines × 2 locations) project/target/node-modules/webjars/npm/lib/auth/legacy.js:28 — project/target/node-modules/webjars/npm/lib/auth/legacy.js:28 · project/target/node-modules/webjars/npm/lib/auth/legacy.js:94 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) project/target/node-modules/webjars/npm/lib/dist-tag.js:73 — project/target/node-modules/webjars/npm/lib/dist-tag.js:73 · project/target/node-modules/webjars/npm/lib/dist-tag.js:104 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:650 — project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:650 · project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:795 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×4
  • Duplicated block (9 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:61 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:61 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:244 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:254 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:254 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:265 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:752 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:752 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:763 — 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 locations) project/target/node-modules/webjars/mkdirp/index.js:12 — project/target/node-modules/webjars/mkdirp/index.js:12 · project/target/node-modules/webjars/mkdirp/index.js:59 — 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.
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment core/src/test/scala/io/udash/properties/PropertyTest.scala:365 — //todo detect forced / touched? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment core/src/test/scala/io/udash/properties/PropertyTest.scala:721 — //TODO: Does it make sense to use LCCS? — 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 rest/src/main/scala/io/udash/rest/SttpRestClient.scala:114 — // TODO: uncool that we have to go through byte array for textual body — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×3
  • Duplicated block (12 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:42 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:42 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:55 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2 locations) project/target/node-modules/webjars/npm/lib/build.js:32 — project/target/node-modules/webjars/npm/lib/build.js:32 · project/target/node-modules/webjars/npm/lib/utils/lifecycle.js:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (12 lines × 2 locations) project/target/node-modules/webjars/npm/lib/prefix.js:1 — project/target/node-modules/webjars/npm/lib/prefix.js:1 · project/target/node-modules/webjars/npm/lib/root.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R2 · Cyclomatic Complexity · Complex function step (cyclomatic 34, cognitive 45) · ×3
  • Complex function step (cyclomatic 34, cognitive 45) project/target/node-modules/webjars/tslib/tslib.es6.js:129 — step has cyclomatic complexity 34 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function step (cyclomatic 34, cognitive 45) project/target/node-modules/webjars/tslib/tslib.es6.mjs:129 — step has cyclomatic complexity 34 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function step (cyclomatic 34, cognitive 45) project/target/node-modules/webjars/tslib/tslib.js:178 — step has cyclomatic complexity 34 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: utils/UdashIcons.scala bootstrap4/.js/src/main/scala/io/udash/bootstrap/utils/UdashIcons.scala — FileTooLong — 1582 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1082 over it, 3.16× 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: utils/BootstrapStyles.scala bootstrap4/.js/src/main/scala/io/udash/bootstrap/utils/BootstrapStyles.scala — FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1 over it, 1.00× 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.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×2
  • Duplicated block (22 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:276 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:276 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/merge-into-shorthands.js:373 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (22 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:678 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:678 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:709 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×2
  • Duplicated block (20 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:164 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:164 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:196 — 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 (20 lines × 2 locations) project/target/node-modules/webjars/npm/lib/config/pacote.js:89 — project/target/node-modules/webjars/npm/lib/config/pacote.js:89 · project/target/node-modules/webjars/npm/lib/utils/correct-mkdir.js:42 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×2
  • Duplicated block (15 lines × 2 locations) project/target/node-modules/webjars/npm/lib/config.js:213 — project/target/node-modules/webjars/npm/lib/config.js:213 · project/target/node-modules/webjars/npm/lib/config.js:230 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (15 lines × 2 locations) project/target/node-modules/webjars/npm/lib/install/exists.js:7 — project/target/node-modules/webjars/npm/lib/install/exists.js:7 · project/target/node-modules/webjars/npm/lib/install/writable.js:9 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R7 · Dead Code · Dead file (~313 LoC) · ×2
  • Dead file (~313 LoC) project/target/node-modules/webjars/npm/lib/search/all-package-metadata.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/search/all-package-search.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~313 LoC) project/target/node-modules/webjars/npm/lib/version.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~266 LoC) · ×2
  • Dead file (~266 LoC) project/target/node-modules/webjars/npm/lib/build.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/action/build.js, project/target/node-modules/webjars/npm/lib/link.js, project/target/node-modules/webjars/npm/lib/unbuild.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~266 LoC) project/target/node-modules/webjars/npm/lib/shrinkwrap.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/save.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~135 LoC) · ×2
  • Dead file (~135 LoC) project/target/node-modules/webjars/npm/lib/cache.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (project/target/node-modules/webjars/npm/lib/outdated.js, project/target/node-modules/webjars/npm/lib/pack.js, project/target/node-modules/webjars/npm/lib/publish.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~135 LoC) project/target/node-modules/webjars/npm/lib/install/mutate-into-logical-tree.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/ls.js, project/target/node-modules/webjars/npm/lib/outdated.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~118 LoC) · ×2
  • Dead file (~118 LoC) project/target/node-modules/webjars/npm/lib/fetch-package-metadata.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 8 in-repo import(s) from 7 other file(s) do name it (project/target/node-modules/webjars/npm/lib/bugs.js, project/target/node-modules/webjars/npm/lib/docs.js, project/target/node-modules/webjars/npm/lib/doctor/get-latest-npm-version.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~118 LoC) project/target/node-modules/webjars/npm/lib/unpublish.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
D1 · Cyclomatic Complexity · PropertyMacros.reifyModelPart (cyclomatic 22) · ×1
  • PropertyMacros.reifyModelPart (cyclomatic 22) macros/src/main/scala/io/udash/macros/PropertyMacros.scala:123 — PropertyMacros.reifyModelPart has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RestServlet.service (cyclomatic 19) · ×1
  • RestServlet.service (cyclomatic 19) rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala:157 — RestServlet.service has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala:157 — rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in RestServlet.service at line 157. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 12:34:15 +02:00' --until='2026-10-12 12:34:15 +02:00' --full-history --no-merges -- rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · PropertyMacros.reifyModelPart (cognitive 31) · ×1
  • PropertyMacros.reifyModelPart (cognitive 31) macros/src/main/scala/io/udash/macros/PropertyMacros.scala:123 — PropertyMacros.reifyModelPart has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 12, match/switch 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · RestServlet.service (cognitive 28) · ×1
  • RestServlet.service (cognitive 28) rest/.jvm/src/main/scala/io/udash/rest/RestServlet.scala:157 — RestServlet.service has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 4 (10 pts), error handling 3 (6 pts), match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UdashDatePicker.optionsToJsDict (cognitive 26) · ×1
  • UdashDatePicker.optionsToJsDict (cognitive 26) bootstrap4/.js/src/main/scala/io/udash/bootstrap/datepicker/UdashDatePicker.scala:123 — UdashDatePicker.optionsToJsDict has cognitive complexity 26 (threshold 15). Drivers by points: if/else 25, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · RawRest.resolveAndHandle (cognitive 26) · ×1
  • RawRest.resolveAndHandle (cognitive 26) rest/src/main/scala/io/udash/rest/raw/RawRest.scala:277 — RawRest.resolveAndHandle has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 7 (12 pts) (nesting depth added 14). 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 · RawRest.handleResolvedWithStreaming (cognitive 22) · ×1
  • RawRest.handleResolvedWithStreaming (cognitive 22) rest/src/main/scala/io/udash/rest/raw/RawRest.scala:152 — RawRest.handleResolvedWithStreaming has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 2 (3 pts), error handling 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AtmosphereService.handleRequest (cognitive 18) · ×1
  • AtmosphereService.handleRequest (cognitive 18) rpc/.jvm/src/main/scala/io/udash/rpc/AtmosphereService.scala:115 — AtmosphereService.handleRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) rest/src/main/scala/io/udash/rest/raw/PlainValue.scala:36 — rest/src/main/scala/io/udash/rest/raw/PlainValue.scala:36-41 | rest/src/main/scala/io/udash/rest/raw/PlainValue.scala:51-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rest/src/main/scala/io/udash/rest/raw/PlainValue.scala:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) guide/shared/src/main/scala/io/udash/web/commons/styles/utils/MediaQueries.scala:11 — guide/shared/src/main/scala/io/udash/web/commons/styles/utils/MediaQueries.scala:11-33 | guide/shared/src/main/scala/io/udash/web/guide/styles/utils/MediaQueries.scala:12-34 — 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 (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) core/src/main/scala/io/udash/properties/seq/CombinedReadableSeqProperty.scala:45 — core/src/main/scala/io/udash/properties/seq/CombinedReadableSeqProperty.scala:45-58 | core/src/main/scala/io/udash/properties/seq/ForwarderReadableSeqProperty.scala:75-88 | core/src/main/scala/io/udash/properties/single/CombinedProperty.scala:43-56 | core/src/main/scala/io/udash/properties/single/TransformedProperty.scala:43-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/demos/DateDemo.scala:38 — guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/demos/DateDemo.scala:38-46 | guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/demos/DateTimeLocalDemo.scala:40-48 | guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/demos/TimeDemo.scala:37-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/FrontendBindingsView.scala:49 — guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/FrontendBindingsView.scala:49-53 | guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/FrontendFormsView.scala:35-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `guide/guide/.js/src/main/scala/io/udash/web/guide/views/frontend/FrontendBindingsView.scala:49` 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.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 2 typed · 397 plain JS — the untyped files are project/target/node-modules/webjars/clean-css/index.js, project/target/node-modules/webjars/clean-css/lib/clean.js, project/target/node-modules/webjars/clean-css/lib/optimizer/clone.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js (+391 more).
R10 · Code Duplication · Wholesale file copy (245 identical lines × 2 files) · ×1
  • Wholesale file copy (245 identical lines × 2 files) project/target/node-modules/webjars/tslib/tslib.es6.js:17 — project/target/node-modules/webjars/tslib/tslib.es6.js:17 · project/target/node-modules/webjars/tslib/tslib.es6.mjs:17 — these 2 files are line-for-line copies of one another — 245 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (74 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (74 matched lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:16 — project/target/node-modules/webjars/clean-css/lib/reader/apply-source-maps.js:16 · project/target/node-modules/webjars/clean-css/lib/reader/load-original-sources.js:9 — the two spans are one implementation copied and then locally edited — 460 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (36 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (36 matched lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:63 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:63 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:540 — the two spans are one implementation copied and then locally edited — 341 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (28 lines × 3 locations) · ×1
  • Duplicated block (28 lines × 3 locations) project/target/node-modules/webjars/source-map/lib/util.js:304 — project/target/node-modules/webjars/source-map/lib/util.js:304 · project/target/node-modules/webjars/source-map/lib/util.js:343 · project/target/node-modules/webjars/source-map/lib/util.js:397 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (18 matched lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/writer/simple.js:6 — project/target/node-modules/webjars/clean-css/lib/writer/simple.js:6 · project/target/node-modules/webjars/clean-css/lib/writer/source-maps.js:15 — the two spans are one implementation copied and then locally edited — 140 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:516 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:516 · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:537 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-media-queries.js:39 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-media-queries.js:39 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-non-adjacent-by-selector.js:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (10 lines × 3 locations) · ×1
  • Duplicated block (10 lines × 3 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:3 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:3 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:14 · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/can-override.js:185 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (10 matched lines × 2 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-adjacent.js:17 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-adjacent.js:17 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/merge-non-adjacent-by-body.js:40 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (9 lines × 4 locations) · ×1
  • Duplicated block (9 lines × 4 locations) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:1 — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/background.js:1 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/border-radius.js:1 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/margin.js:1 · project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/property-optimizers/outline.js:1 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function intoTokens (cyclomatic 256, cognitive 165) · ×1
  • Complex function intoTokens (cyclomatic 256, cognitive 165) project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:82 — intoTokens has cyclomatic complexity 256 and cognitive complexity 165; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function overrideProperties (cyclomatic 114, cognitive 249) · ×1
  • Complex function overrideProperties (cyclomatic 114, cognitive 249) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/properties/override-properties.js:246 — overrideProperties has cyclomatic complexity 114 and cognitive complexity 249; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function removeWhitespace (cyclomatic 71, cognitive 58) · ×1
  • Complex function removeWhitespace (cyclomatic 71, cognitive 58) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js:64 — removeWhitespace has cyclomatic complexity 71 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function font (cyclomatic 48, cognitive 51) · ×1
  • Complex function font (cyclomatic 48, cognitive 51) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:266 — font has cyclomatic complexity 48 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function applyIgnores (cyclomatic 48, cognitive 46) · ×1
  • Complex function applyIgnores (cyclomatic 48, cognitive 46) project/target/node-modules/webjars/npm/lib/utils/tar.js:65 — applyIgnores has cyclomatic complexity 48 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 47, cognitive 96) · ×1
  • Complex function exports (cyclomatic 47, cognitive 96) project/target/node-modules/webjars/minimist/index.js:23 — exports has cyclomatic complexity 47 and cognitive complexity 96; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function canReorderSingle (cyclomatic 47, cognitive 31) · ×1
  • Complex function canReorderSingle (cyclomatic 47, cognitive 31) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/reorderable.js:19 — canReorderSingle has cyclomatic complexity 47 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function errorMessage (cyclomatic 41, cognitive 24) · ×1
  • Complex function errorMessage (cyclomatic 41, cognitive 24) project/target/node-modules/webjars/npm/lib/utils/error-message.js:8 — errorMessage has cyclomatic complexity 41 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function makeArchy_ (cyclomatic 39, cognitive 63) · ×1
  • Complex function makeArchy_ (cyclomatic 39, cognitive 63) project/target/node-modules/webjars/npm/lib/ls.js:344 — makeArchy_ has cyclomatic complexity 39 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function isAllowedResource (cyclomatic 35, cognitive 34) · ×1
  • Complex function isAllowedResource (cyclomatic 35, cognitive 34) project/target/node-modules/webjars/clean-css/lib/reader/is-allowed-resource.js:9 — isAllowedResource has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _clone (cyclomatic 34, cognitive 49) · ×1
  • Complex function _clone (cyclomatic 34, cognitive 49) project/target/node-modules/webjars/clone/clone.js:73 — _clone has cyclomatic complexity 34 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function extractPseudoFrom (cyclomatic 34, cognitive 29) · ×1
  • Complex function extractPseudoFrom (cyclomatic 34, cognitive 29) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/is-mergeable.js:73 — extractPseudoFrom has cyclomatic complexity 34 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function specificity (cyclomatic 34, cognitive 29) · ×1
  • Complex function specificity (cyclomatic 34, cognitive 29) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/specificity.js:16 — specificity has cyclomatic complexity 34 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function restructure (cyclomatic 33, cognitive 66) · ×1
  • Complex function restructure (cyclomatic 33, cognitive 66) project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/restructure.js:24 — restructure has cyclomatic complexity 33 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function background (cyclomatic 31, cognitive 49) · ×1
  • Complex function background (cyclomatic 31, cognitive 49) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:136 — background has cyclomatic complexity 31 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function optimizeBody (cyclomatic 29, cognitive 46) · ×1
  • Complex function optimizeBody (cyclomatic 29, cognitive 46) project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/optimize.js:58 — optimizeBody has cyclomatic complexity 29 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function background (cyclomatic 29, cognitive 32) · ×1
  • Complex function background (cyclomatic 29, cognitive 32) project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/restore.js:16 — background has cyclomatic complexity 29 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js · ×1
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js: 1624 lines of code project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js:1 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration.js has 1624 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/source-map/lib/source-map-consumer.js · ×1
  • project/target/node-modules/webjars/source-map/lib/source-map-consumer.js: 1020 lines of code project/target/node-modules/webjars/source-map/lib/source-map-consumer.js:1 — project/target/node-modules/webjars/source-map/lib/source-map-consumer.js has 1020 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/npm/lib/install.js · ×1
  • project/target/node-modules/webjars/npm/lib/install.js: 804 lines of code project/target/node-modules/webjars/npm/lib/install.js:1 — project/target/node-modules/webjars/npm/lib/install.js has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js · ×1
  • project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js: 794 lines of code project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js:1 — project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/npm/lib/install/deps.js · ×1
  • project/target/node-modules/webjars/npm/lib/install/deps.js: 655 lines of code project/target/node-modules/webjars/npm/lib/install/deps.js:1 — project/target/node-modules/webjars/npm/lib/install/deps.js has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js · ×1
  • project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js: 554 lines of code project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:1 — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js has 554 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js · ×1
  • project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js: 522 lines of code project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js:1 — project/target/node-modules/webjars/clean-css/lib/optimizer/validator.js has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/npm/lib/ls.js · ×1
  • project/target/node-modules/webjars/npm/lib/ls.js: 459 lines of code project/target/node-modules/webjars/npm/lib/ls.js:1 — project/target/node-modules/webjars/npm/lib/ls.js has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/tslib/tslib.js · ×1
  • project/target/node-modules/webjars/tslib/tslib.js: 445 lines of code project/target/node-modules/webjars/tslib/tslib.js:1 — project/target/node-modules/webjars/tslib/tslib.js has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/npm/lib/npm.js · ×1
  • project/target/node-modules/webjars/npm/lib/npm.js: 427 lines of code project/target/node-modules/webjars/npm/lib/npm.js:1 — project/target/node-modules/webjars/npm/lib/npm.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/source-map/lib/util.js · ×1
  • project/target/node-modules/webjars/source-map/lib/util.js: 427 lines of code project/target/node-modules/webjars/source-map/lib/util.js:1 — project/target/node-modules/webjars/source-map/lib/util.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · project/target/node-modules/webjars/npm/lib/utils/tar.js · ×1
  • project/target/node-modules/webjars/npm/lib/utils/tar.js: 401 lines of code project/target/node-modules/webjars/npm/lib/utils/tar.js:1 — project/target/node-modules/webjars/npm/lib/utils/tar.js has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~884 LoC) · ×1
  • Dead file (~884 LoC) project/target/node-modules/webjars/npm/lib/install.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (project/target/node-modules/webjars/npm/lib/dedupe.js, project/target/node-modules/webjars/npm/lib/install-test.js, project/target/node-modules/webjars/npm/lib/install/action/global-install.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~729 LoC) · ×1
  • Dead file (~729 LoC) project/target/node-modules/webjars/npm/lib/install/deps.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 25 in-repo import(s) from 11 other file(s) do name it (project/target/node-modules/webjars/npm/lib/dedupe.js, project/target/node-modules/webjars/npm/lib/install.js, project/target/node-modules/webjars/npm/lib/install/actions.js and 8 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~517 LoC) · ×1
  • Dead file (~517 LoC) project/target/node-modules/webjars/npm/lib/ls.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~454 LoC) · ×1
  • Dead file (~454 LoC) project/target/node-modules/webjars/npm/lib/utils/tar.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/pack.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~452 LoC) · ×1
  • Dead file (~452 LoC) project/target/node-modules/webjars/npm/lib/utils/lifecycle.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 16 in-repo import(s) from 16 other file(s) do name it (project/target/node-modules/webjars/npm/lib/build.js, project/target/node-modules/webjars/npm/lib/install/action/install.js, project/target/node-modules/webjars/npm/lib/install/action/move.js and 13 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~423 LoC) · ×1
  • Dead file (~423 LoC) project/target/node-modules/webjars/npm/lib/outdated.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~339 LoC) · ×1
  • Dead file (~339 LoC) project/target/node-modules/webjars/npm/lib/view.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~305 LoC) · ×1
  • Dead file (~305 LoC) project/target/node-modules/webjars/npm/lib/config.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~286 LoC) · ×1
  • Dead file (~286 LoC) project/target/node-modules/webjars/npm/lib/utils/gently-rm.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (project/target/node-modules/webjars/npm/lib/cache.js, project/target/node-modules/webjars/npm/lib/install/action/extract.js, project/target/node-modules/webjars/npm/lib/install/action/finalize.js and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~277 LoC) · ×1
  • Dead file (~277 LoC) project/target/node-modules/webjars/npm/lib/owner.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~248 LoC) · ×1
  • Dead file (~248 LoC) project/target/node-modules/webjars/npm/lib/completion.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~241 LoC) · ×1
  • Dead file (~241 LoC) project/target/node-modules/webjars/npm/lib/help.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~221 LoC) · ×1
  • Dead file (~221 LoC) project/target/node-modules/webjars/npm/lib/pack.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/config/pacote.js, project/target/node-modules/webjars/npm/lib/publish.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~212 LoC) · ×1
  • Dead file (~212 LoC) project/target/node-modules/webjars/npm/lib/help-search.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~204 LoC) · ×1
  • Dead file (~204 LoC) project/target/node-modules/webjars/npm/lib/install/inflate-shrinkwrap.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/deps.js, project/target/node-modules/webjars/npm/lib/install/read-shrinkwrap.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~203 LoC) · ×1
  • Dead file (~203 LoC) project/target/node-modules/webjars/npm/lib/publish.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~197 LoC) · ×1
  • Dead file (~197 LoC) project/target/node-modules/webjars/npm/lib/link.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~182 LoC) · ×1
  • Dead file (~182 LoC) project/target/node-modules/webjars/npm/lib/install/save.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install.js, project/target/node-modules/webjars/npm/lib/install/deps.js, project/target/node-modules/webjars/npm/lib/uninstall.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~181 LoC) · ×1
  • Dead file (~181 LoC) project/target/node-modules/webjars/npm/lib/run-script.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~179 LoC) · ×1
  • Dead file (~179 LoC) project/target/node-modules/webjars/npm/lib/install/actions.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 4 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~172 LoC) · ×1
  • Dead file (~172 LoC) project/target/node-modules/webjars/npm/lib/search/format-package-stream.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/search.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~160 LoC) · ×1
  • Dead file (~160 LoC) project/target/node-modules/webjars/npm/lib/dedupe.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~158 LoC) · ×1
  • Dead file (~158 LoC) project/target/node-modules/webjars/npm/lib/dist-tag.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~154 LoC) · ×1
  • Dead file (~154 LoC) project/target/node-modules/webjars/npm/lib/install/diff-trees.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/dedupe.js, project/target/node-modules/webjars/npm/lib/install.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~142 LoC) · ×1
  • Dead file (~142 LoC) project/target/node-modules/webjars/npm/lib/auth/legacy.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/adduser.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~130 LoC) · ×1
  • Dead file (~130 LoC) project/target/node-modules/webjars/npm/lib/unbuild.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (project/target/node-modules/webjars/npm/lib/install/action/move.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~129 LoC) · ×1
  • Dead file (~129 LoC) project/target/node-modules/webjars/npm/lib/access.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~123 LoC) · ×1
  • Dead file (~123 LoC) project/target/node-modules/webjars/npm/lib/utils/correct-mkdir.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (project/target/node-modules/webjars/npm/lib/search/all-package-metadata.js, project/target/node-modules/webjars/npm/lib/utils/locker.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~113 LoC) · ×1
  • Dead file (~113 LoC) project/target/node-modules/webjars/npm/lib/doctor.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~108 LoC) · ×1
  • Dead file (~108 LoC) project/target/node-modules/webjars/npm/lib/config/pacote.js — no import path from any entry point (23 application, 10 tooling, 68 test roots considered), but 7 in-repo import(s) from 6 other file(s) do name it (project/target/node-modules/webjars/npm/lib/cache.js, project/target/node-modules/webjars/npm/lib/fetch-package-metadata.js, project/target/node-modules/webjars/npm/lib/install/action/extract.js and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency 'ws' · ×1
  • Unused dependency 'ws' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'http-proxy' · ×1
  • Unused dependency 'http-proxy' — Declared in project/target/node-modules/webjars/clean-css/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'nock' · ×1
  • Unused dependency 'nock' — Declared in project/target/node-modules/webjars/clean-css/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Minor — 40 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:140 — `!(t = _.trys, t = t.length > 0 && t[t.length - 1]) && (op[0] === 6 || op[0] === 2)` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/install/inflate-shrinkwrap.js:22 — `!npm.config.get('shrinkwrap') || !npm.config.get('package-lock')` appears character-identically in 2 files — project/target/node-modules/webjars/npm/lib/install/inflate-shrinkwrap.js, project/target/node-modules/webjars/npm/lib/install/save.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/config/cmd-list.js:1 — `Object.assign || require('util')._extend` appears character-identically in 2 files — project/target/node-modules/webjars/npm/lib/config/cmd-list.js, project/target/node-modules/webjars/npm/lib/ls.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:45 — `Object.prototype.hasOwnProperty.call(s, p) && e.indexOf(p) < 0` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/less/lib/less/visitors/join-selector-visitor.js:52 — `atRuleNode.rules && atRuleNode.rules.length` appears character-identically in 2 files — project/target/node-modules/webjars/less/lib/less/visitors/join-selector-visitor.js, project/target/node-modules/webjars/less/lib/less/visitors/to-css-visitor.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:59 — `c > 3 && r && Object.defineProperty(target, key, r)` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/utils/gunzip-maybe.js:6 — `c[0] === 0x1F && c[1] === 0x8B && c[2] === 0x08` appears character-identically in 2 files — project/target/node-modules/webjars/npm/lib/utils/gunzip-maybe.js, project/target/node-modules/webjars/npm/lib/utils/tar.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js:123 — `character == Marker.DOUBLE_QUOTE && !isQuoted` appears character-identically in 2 files — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js, project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/is-mergeable.js:98 — `character == Marker.DOUBLE_QUOTE && level == Level.DOUBLE_QUOTE` appears character-identically in 2 files — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/is-mergeable.js, project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js:120 — `character == Marker.SINGLE_QUOTE && !isQuoted` appears character-identically in 2 files — project/target/node-modules/webjars/clean-css/lib/optimizer/level-1/tidy-rules.js, project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/is-mergeable.js:104 — `character == Marker.SINGLE_QUOTE && level == Level.SINGLE_QUOTE` appears character-identically in 2 files — project/target/node-modules/webjars/clean-css/lib/optimizer/level-2/is-mergeable.js, project/target/node-modules/webjars/clean-css/lib/tokenizer/tokenize.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js:43 — `descriptor.doubleValues && descriptor.defaultValue.length == 1` appears character-identically in 2 files — project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/break-up.js, project/target/node-modules/webjars/clean-css/lib/optimizer/configuration/restore.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:49 — `e.indexOf(p[i]) < 0 && Object.prototype.propertyIsEnumerable.call(s, p[i])` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/run-script.js:28 — `er && er.code !== 'ENOENT' && er.code !== 'ENOTDIR'` appears character-identically in 4 files — project/target/node-modules/webjars/npm/lib/run-script.js, project/target/node-modules/webjars/npm/lib/uninstall.js, project/target/node-modules/webjars/npm/lib/unpublish.js, project/target/node-modules/webjars/npm/lib/view.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/install.js:219 — `npm.config.get('dev') || (!/^prod(uction)?$/.test(npm.config.get('only')) && !npm.config.get('production')) || /^dev(elopment)?$/.test(npm.c…` appears character-identically in 2 files — project/target/node-modules/webjars/npm/lib/install.js, project/target/node-modules/webjars/npm/lib/install/inflate-shrinkwrap.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/ls.js:134 — `npm.config.get('production') || /^prod(uction)?$/.test(npm.config.get('only'))` appears character-identically in 3 files — project/target/node-modules/webjars/npm/lib/ls.js, project/target/node-modules/webjars/npm/lib/outdated.js, project/target/node-modules/webjars/npm/lib/prune.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:141 — `op[0] === 3 && (!t || (op[1] > t[0] && op[1] < t[3]))` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/less/lib/less/tree/anonymous.js:20 — `other.toCSS && this.toCSS() === other.toCSS()` appears character-identically in 2 files — project/target/node-modules/webjars/less/lib/less/tree/anonymous.js, project/target/node-modules/webjars/less/lib/less/tree/quoted.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:166 — `p !== "default" && !Object.prototype.hasOwnProperty.call(o, p)` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/npm/lib/install/action/finalize.js:24 — `pkg.package._requested || getRequested(pkg)` appears character-identically in 2 files — project/target/node-modules/webjars/npm/lib/install/action/finalize.js, project/target/node-modules/webjars/npm/lib/install/action/refresh-package-json.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:233 — `q.push([n, v, a, b]) > 1 || resume(n, v)` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:301 — `receiver === null || (typeof receiver !== "object" && typeof receiver !== "function")` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:80 — `result === null || typeof result !== "object"` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/tslib/tslib.es6.js:47 — `s != null && typeof Object.getOwnPropertySymbols === "function"` appears character-identically in 3 files — project/target/node-modules/webjars/tslib/tslib.es6.js, project/target/node-modules/webjars/tslib/tslib.es6.mjs, project/target/node-modules/webjars/tslib/tslib.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate project/target/node-modules/webjars/less/lib/less/tree/detached-ruleset.js:19 — `this.frames || utils.copyArray(context.frames)` appears character-identically in 2 files — project/target/node-modules/webjars/less/lib/less/tree/detached-ruleset.js, project/target/node-modules/webjars/less/lib/less/tree/mixin-definition.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift project/target/node-modules/webjars/clean-css/README.md:598 — project/target/node-modules/webjars/clean-css/README.md installs `clean-css-cli` (`npm install clean-css-cli`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift project/target/node-modules/webjars/clean-css/README.md:960 — project/target/node-modules/webjars/clean-css/README.md runs `npm run check # to lint JS sources with [JSHint](https://github.com/jshint/jshint/)`, but no package.json declares a `check` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: REDACTED. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (3 single-owned of 44 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 44 of the 169 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: rpc/src/main/scala/io/udash/rpc/companions.scala, guide/backend/src/main/scala/io/udash/web/server/ApplicationServer.scala.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (11381 LoC, 1311 module-visible types across 121 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `project/target/node-modules/webjars/mkdirp`.
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 8113 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.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1
  • Benchmarks don't track allocations benchmarks/src/main/scala/io/udash/rest/StreamingRestApiBenchmark.scala — A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1
  • Scala's null is not held to the type system everywhere — No build over this repository's 162 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 — 5 finding(s)
D12 · Dependency Hygiene · Outdated · ×5
  • Outdated: ch.qos.logback:logback-classic — `ch.qos.logback %% logback-classic` is declared at 1.5.38 in REDACTED, but 1.6.5 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.5.38 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.atmosphere:atmosphere-runtime — `org.atmosphere %% atmosphere-runtime` is declared at 2.7.16 in REDACTED, but 4.0.75 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.7.16 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.seleniumhq.selenium:selenium-java — `org.seleniumhq.selenium %% selenium-java` is declared at 4.50.0 in REDACTED, but 4.51.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 4.50.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.webjars:bootstrap — `org.webjars %% bootstrap` is declared at 4.1.3 in REDACTED, but 5.3.8 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 4.1.3 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.webjars:font-awesome — `org.webjars %% font-awesome` is declared at 5.10.1 in REDACTED, but 7.3.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 5.10.1 until the declaration is edited — there is no lockfile refresh that would move it.

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-d2b6a9b941d248f892d53d6513584ee5/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-d2b6a9b941d248f892d53d6513584ee5/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 .21artifacts/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 4 file(s) — `bootstrap4/.js/src/main/scala/io/udash/bootstrap/datepicker/UdashDatePicker.scala`, `bootstrap4/.js/src/main/scala/io/udash/bootstrap/form/UdashForm.scala`, `core/src/main/scala/io/udash/properties/CallbackSequencer.scala`, `scripts/authors.scala` — 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 01a15d7c-4ef5-7f49-9311-82a1f86803a9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 27 · Warnings: 177 · Recommendations: 40 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 08:03 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