Public report of e-athena/basic-platform, published 22 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, 22 October 2026, 23:32 UTC · Survey ID cd_46aee8888beb46528c6aa17f9817a922

e-athena/basic-platform

Measured 22 October 2026, 23:24 UTC, at code version f2908dd

Regression: 3 dimensions fell since the last survey Code coverage: not measuredTest reliability: not measured

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

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

Test reliability is not measured: The JavaScript/TypeScript half of a polyglot suite was not re-run.

CAI score 28out of 100 At risk No change 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.

Event-Driven 88 Strong Architecture 79 Strong Performance 60 Adequate Code Health 53 Adequate Security and Compliance 41 Weak Maturity 40 Weak Accessibility 31 Weak Domain Modelling 27 Weak Production Readiness 21 Critical

A medium codebase: 50,655 lines of product code in 23 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 21

Findings by how serious they are

216 critical 524 serious 245 minor

8 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
22 October 2026, 23:24 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.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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 ▸

100of 104 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
930of 985 findings point to an exact file and line, so you can open each one in the code. The other 55 concern the repository as a whole, such as missing documentation.
104dimensions across 9 lenses, read from 50,655 lines of product code in 23 projects.
Chapters

Executive summary

e-athena/basic-platform scores 28 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 21 and is rated Critical. Its REDACTED Scanning 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 5 Leaked secret finding(s) in REDACTED Scanning and to resolve the 55 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 28 to about 34.

216 findings are critical: 90 in Dependency Vulnerabilities, 40 in Domain ↔ infrastructure boundary, 22 in Integration-event coupling, 20 in Aggregate boundaries, ten in Dependency Hygiene, five in Keyboard semantics, five in REDACTED Scanning, five in Secrets (history), four in IaC & Container Security, two in Change Coupling, two in Coupling, two in Dependency direction, two in Forms & labels, two in Test Reliability, two in Text alternatives, one in Circular Imports, one in Outbox / dual-write and one in Project dependency cycles.

Watchdog couldn't measure Documentation Quality, Navigability and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 50,655 lines, which would take an estimated 0.5 person-years, around €73,000, to rebuild.

Code Health 53 Adequate, capped by God Classes and Dead Code Architecture 79 Strong Maturity 40 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 21 ⚠ Critical, capped by REDACTED Scanning, Dependency Hygiene, CI/CD gates, Security & performance tooling and Outbound HTTP resilience Security and Compliance 41 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities and Data Protection Domain Modelling 27 Weak, capped by Aggregate boundaries, Strongly-typed ids, Integration-event coupling, Encapsulated state and Domain ↔ infrastructure boundary Event-Driven 88 Strong Accessibility 31 Weak, capped by Forms & labels and Keyboard semantics Performance 60 Adequate

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 21 · counts for 45%Domain Modelling 27 · counts for 25%Accessibility 31 · counts for 14%Maturity 40 · counts for 8%Security and Compliance 41 · counts for 4%Code Health 53 · counts for 2%Performance 60 · counts for 1%Architecture 79 · counts for 1%Event-Driven 88 · counts for 0%

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

Code composition: what the lines of code are
Business logic 28%Supporting code 64%Tests 8%
New since the last survey: 127 findings

These 127 critical or serious findings weren't in the previous survey, on 8 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

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

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

  • Coupling · Off the main sequence: BasicPlatform.Infrastructure
  • Coupling · Off the main sequence: App.Infrastructure
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Code Duplication · Wholesale file copy (61 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/signalr/connection.ts
  • Code Duplication · Wholesale file copy (59 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/bn-BD/pages.ts
  • Code Duplication · Wholesale file copy (59 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/en-US/pages.ts
  • Code Duplication · Wholesale file copy (58 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/id-ID/pages.ts
  • Code Duplication · Duplicated block with local edits (58 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationColumnPermission/index.tsx
  • Code Duplication · Wholesale file copy (57 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/pt-BR/pages.ts
  • Code Duplication · Duplicated block with local edits (54 matched lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/index.tsx
  • Code Duplication · Wholesale file copy (54 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-CN/settings.ts
  • Code Duplication · Wholesale file copy (54 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-TW/settings.ts
  • Code Duplication · Duplicated block (52 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/index.tsx
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/bn-BD/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/en-US/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/fa-IR/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/id-ID/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/ja-JP/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/pt-BR/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-CN/menu.ts
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-TW/menu.ts
  • Code Duplication · Wholesale file copy (50 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/bn-BD/settings.ts
  • Code Duplication · Wholesale file copy (50 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/ja-JP/settings.ts
  • Code Duplication · Duplicated block (50 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/DataPermissionForm.tsx
  • Code Duplication · Duplicated block (48 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrganizationTree/index.tsx
  • Code Duplication · Duplicated block (48 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/components/DemoPie.tsx
  • Code Duplication · Duplicated block (47 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrganizationTree/index.tsx
  • Code Duplication · Duplicated block (45 lines × 3 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx
  • Code Duplication · Duplicated block (45 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/components/OrgModal/index.tsx
  • Code Duplication · Duplicated block (45 lines × 4 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx
  • Code Duplication · Duplicated block (44 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/index.tsx
  • Code Duplication · Duplicated block with local edits (40 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/ViewDrawer.tsx
  • Code Duplication · Duplicated block (39 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/request.ts
  • Code Duplication · Duplicated block (37 lines × 4 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx
  • Code Duplication · Duplicated block (37 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Admin.tsx
  • Code Duplication · Duplicated block (37 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/service-worker.js
  • Code Duplication · Duplicated block (37 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block with local edits (36 matched lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx
  • Code Duplication · Duplicated block (36 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RegionTree/index.tsx
  • Code Duplication · Duplicated block (35 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/store.ts
  • Code Duplication · Duplicated block (34 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx
  • Code Duplication · Duplicated block (33 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/AuthorizationForm.tsx
  • Code Duplication · Duplicated block (31 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/index.tsx
  • Code Duplication · Duplicated block (30 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/ViewModal.tsx
  • Code Duplication · Duplicated block (29 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/filter.ts
  • Code Duplication · Duplicated block (28 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/UserModal/index.tsx
  • Code Duplication · Duplicated block (28 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/index.tsx
  • Code Duplication · Duplicated block (28 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/components/DemoLine.tsx
  • Code Duplication · Duplicated block (28 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/components/ViewModal.tsx
  • Code Duplication · Duplicated block (28 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/index.tsx
  • Code Duplication · Duplicated block (27 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/components/DemoColumn.tsx
  • Code Duplication · Duplicated block (27 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/ViewModal.tsx
  • Code Duplication · Duplicated block (26 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx
  • Code Duplication · Duplicated block (26 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/index.tsx
  • Code Duplication · Duplicated block (25 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/storage.ts
  • Code Duplication · Duplicated block (24 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Position/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block (22 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationAuthorization/index.tsx
  • Code Duplication · Duplicated block (22 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/components/ViewModal.tsx
  • Code Duplication · Duplicated block (21 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/menu.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block (21 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/components/CreateOrUpdateSuperAdminForm.tsx
  • Code Duplication · Duplicated block (20 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/jest.config.ts
  • Code Duplication · Duplicated block (20 lines × 3 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx
  • Code Duplication · Duplicated block (20 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/token.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (18 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/IconStatus/index.tsx
  • Code Duplication · Duplicated block (17 lines × 3 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx
  • Code Duplication · Duplicated block (17 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/index.tsx
  • Code Duplication · Duplicated block (16 lines × 3 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/index.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/access.ts
  • Code Duplication · Duplicated block (15 lines × 3 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Dashboard/Workbench/components/DemoDecompositionTreeGraph.tsx
  • Code Duplication · Duplicated block (15 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/AuthorizationForm.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/index.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/services/ant-design-pro/system/org.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/FixMenuItemIcon/index.tsx
  • Code Duplication · Duplicated block (13 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/components/CreateOrUpdateForm.tsx
  • Code Duplication · Duplicated block (13 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/index.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/components/ColumnPermissionForm.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/404.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) BasicPlatform.WebAPI/ArcoApp/src/utils/utils.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/FixIcon/index.tsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/HeaderDropdown/index.tsx
  • Code Duplication · Duplicated block (10 lines × 7 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/index.tsx
Rebuild cost: about €73,000 · Estimate
Cost to rebuild€24,000 to €120,000, for 404 to 1,286 hours of work, about 0.5 person-years for one engineer
Difficulty of the problemVery high, 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 28. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 50,655 lines of product code
Comment linesThe estimate prices 43,527 lines. Comment lines count towards the size of 50,655 lines but aren't priced as work.

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.

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 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2).
Raises the score by about 6 points · Low effort · REDACTED Scanning
2
Resolve the 55 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (55).
Raises the score by about 5 points · Medium effort · Dependency Hygiene
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 3 points · Medium effort · CI/CD gates

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 €73,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 21 (Critical). 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.
One cause behind 24 Domain Modelling findings · Common cause
24 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (13 findings) · Rich vs anemic model (1 finding) · Strongly-typed ids (10 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 5 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 1,488 lines over the last 90 days, which is about 6,035 lines a year. At that pace, the extra work comes to an estimated 0.3 to 2.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch Gateway Gateway WebAPI WebAPI ctx:AppService.FreeSql AppService.FreeSql FreeSql WebAPI->ctx:AppService.FreeSql ctx:Domain.EventHandler Domain.EventHandler EventHandler WebAPI->ctx:Domain.EventHandler ctx:ProcessManager ProcessManager ProcessManager WebAPI->ctx:ProcessManager CMS.WebAPI CMS.WebAPI ctx:CMS CMS AppService · Domain · FreeSql · IntegratedEventHandler CMS.WebAPI->ctx:CMS CRM.WebAPI CRM.WebAPI ctx:CRM CRM Commands · Domain · EventHandlers · ProcessManagers … CRM.WebAPI->ctx:CRM ctx:Infrastructure Infrastructure Infrastructure ctx:AppService AppService AppService ctx:Domain Domain Domain ctx:AppService->ctx:Domain ctx:AppService.FreeSql->ctx:AppService ctx:BasicPlatform.Infrastructure BasicPlatform.Infrastructure Infrastructure ctx:Domain->ctx:BasicPlatform.Infrastructure ctx:Domain.EventHandler->ctx:Domain ctx:ProcessManager->ctx:AppService ctx:CRM->ctx:Infrastructure

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.

206 modules, with 208 dependencies between them. One loop runs through 4 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 166 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 App.Infrastructure.Models2 Apps.CMS.CMS_WebAPI.CMSWeb.src.components.OrgModal.components.TransferForm3 BasicPlatform.AppService4 BasicPlatform.AppService.ExternalPages.Models5 BasicPlatform.AppService.Organizations6 BasicPlatform.AppService.Positions7 BasicPlatform.AppService.Resources.Models8 BasicPlatform_WebAPI.ArcoApp.src.types.global9 App.Infrastructure.Messaging.Requests10 BasicPlatform.AppService.Applications.Models11 BasicPlatform.AppService.ExternalPages.Requests12 BasicPlatform.AppService.ExternalPages.Responses13 BasicPlatform.AppService.Roles.Models14 BasicPlatform.AppService.Tenants.Requests15 BasicPlatform.AppService.Tenants.Responses16 BasicPlatform.AppService.Users.Models17 BasicPlatform.AppService.WebSettings.Models18 BasicPlatform.Domain.Models.Users19 BasicPlatform.WebAPI.Services20 App.Infrastructure.Services21 BasicPlatform.AppService.Applications.Requests22 BasicPlatform.AppService.Applications.Responses23 BasicPlatform.AppService.ExternalPages24 BasicPlatform.AppService.Roles.Requests25 BasicPlatform.AppService.Roles.Responses26 BasicPlatform.AppService.Tenants27 BasicPlatform.AppService.Users.Requests28 BasicPlatform.AppService.Users.Responses29 BasicPlatform.Domain.Models.Organizations30 App.Infrastructure.Services.Impls31 BasicPlatform.AppService.Applications32 BasicPlatform.AppService.FreeSql.ExternalPages33 BasicPlatform.AppService.Roles34 BasicPlatform.AppService.Users35 BasicPlatform.AppService.FreeSql.Applications36 BasicPlatform.AppService.FreeSql.Roles37 BasicPlatform.AppService.FreeSql.Users38 BasicPlatform.WebAPI.Controllers39 BasicPlatform.WebAPI.Controllers.Developer40 BasicPlatform.WebAPI.Controllers.System
1 App.Infrastructure.Models
2 Apps.CMS.CMS_WebAPI.CMSWeb.src.components.OrgModal.components.TransferForm
3 BasicPlatform.AppService
4 BasicPlatform.AppService.ExternalPages.Models
5 BasicPlatform.AppService.Organizations
6 BasicPlatform.AppService.Positions
7 BasicPlatform.AppService.Resources.Models
8 BasicPlatform_WebAPI.ArcoApp.src.types.global
9 App.Infrastructure.Messaging.Requests1
10 BasicPlatform.AppService.Applications.Models2
11 BasicPlatform.AppService.ExternalPages.Requests2
12 BasicPlatform.AppService.ExternalPages.Responses2
13 BasicPlatform.AppService.Roles.Models2
14 BasicPlatform.AppService.Tenants.Requests1
15 BasicPlatform.AppService.Tenants.Responses1
16 BasicPlatform.AppService.Users.Models2
17 BasicPlatform.AppService.WebSettings.Models1
18 BasicPlatform.Domain.Models.Users2
19 BasicPlatform.WebAPI.Services1
20 App.Infrastructure.Services33
21 BasicPlatform.AppService.Applications.Requests1
22 BasicPlatform.AppService.Applications.Responses1
23 BasicPlatform.AppService.ExternalPages12
24 BasicPlatform.AppService.Roles.Requests14
25 BasicPlatform.AppService.Roles.Responses12
26 BasicPlatform.AppService.Tenants12
27 BasicPlatform.AppService.Users.Requests115
28 BasicPlatform.AppService.Users.Responses116
29 BasicPlatform.Domain.Models.Organizations1
30 App.Infrastructure.Services.Impls336
31 BasicPlatform.AppService.Applications111
32 BasicPlatform.AppService.FreeSql.ExternalPages421
33 BasicPlatform.AppService.Roles212
34 BasicPlatform.AppService.Users111318
35 BasicPlatform.AppService.FreeSql.Applications1411
36 BasicPlatform.AppService.FreeSql.Roles28211
37 BasicPlatform.AppService.FreeSql.Users1113138111
38 BasicPlatform.WebAPI.Controllers111121141213
39 BasicPlatform.WebAPI.Controllers.Developer1124126
40 BasicPlatform.WebAPI.Controllers.System61114225211218211261139
Uses a module listed above itPart of a loopThe module itself
1 App.Infrastructure.Models2 Apps.CMS.CMS_WebAPI.CMSWeb.src.components.OrgModal.components.TransferForm3 BasicPlatform.AppService4 BasicPlatform.AppService.ExternalPages.Models5 BasicPlatform.AppService.Organizations6 BasicPlatform.AppService.Positions7 BasicPlatform.AppService.Resources.Models8 BasicPlatform_WebAPI.ArcoApp.src.types.global9 App.Infrastructure.Messaging.Requests10 BasicPlatform.AppService.Applications.Models11 BasicPlatform.AppService.ExternalPages.Requests12 BasicPlatform.AppService.ExternalPages.Responses13 BasicPlatform.AppService.Roles.Models14 BasicPlatform.AppService.Tenants.Requests15 BasicPlatform.AppService.Tenants.Responses16 BasicPlatform.AppService.Users.Models17 BasicPlatform.AppService.WebSettings.Models18 BasicPlatform.Domain.Models.Users19 BasicPlatform.WebAPI.Services20 App.Infrastructure.Services21 BasicPlatform.AppService.Applications.Requests22 BasicPlatform.AppService.Applications.Responses23 BasicPlatform.AppService.ExternalPages24 BasicPlatform.AppService.Roles.Requests25 BasicPlatform.AppService.Roles.Responses26 BasicPlatform.AppService.Tenants27 BasicPlatform.AppService.Users.Requests28 BasicPlatform.AppService.Users.Responses29 BasicPlatform.Domain.Models.Organizations30 App.Infrastructure.Services.Impls31 BasicPlatform.AppService.Applications32 BasicPlatform.AppService.FreeSql.ExternalPages33 BasicPlatform.AppService.Roles34 BasicPlatform.AppService.Users35 BasicPlatform.AppService.FreeSql.Applications36 BasicPlatform.AppService.FreeSql.Roles37 BasicPlatform.AppService.FreeSql.Users38 BasicPlatform.WebAPI.Controllers39 BasicPlatform.WebAPI.Controllers.Developer40 BasicPlatform.WebAPI.Controllers.SystemApp.Infrastructure.Models1Apps.CMS.CMS_WebAPI.CMSWeb.src.components.OrgModal.components.TransferForm2BasicPlatform.AppService3BasicPlatform.AppService.ExternalPages.Models4BasicPlatform.AppService.Organizations5BasicPlatform.AppService.Positions6BasicPlatform.AppService.Resources.Models7BasicPlatform_WebAPI.ArcoApp.src.types.global8App.Infrastructure.Messaging.Requests9BasicPlatform.AppService.Applications.Models10BasicPlatform.AppService.ExternalPages.Requests11BasicPlatform.AppService.ExternalPages.Responses12BasicPlatform.AppService.Roles.Models13BasicPlatform.AppService.Tenants.Requests14BasicPlatform.AppService.Tenants.Responses15BasicPlatform.AppService.Users.Models16BasicPlatform.AppService.WebSettings.Models17BasicPlatform.Domain.Models.Users18BasicPlatform.WebAPI.Services19App.Infrastructure.Services20BasicPlatform.AppService.Applications.Requests21BasicPlatform.AppService.Applications.Responses22BasicPlatform.AppService.ExternalPages23BasicPlatform.AppService.Roles.Requests24BasicPlatform.AppService.Roles.Responses25BasicPlatform.AppService.Tenants26BasicPlatform.AppService.Users.Requests27BasicPlatform.AppService.Users.Responses28BasicPlatform.Domain.Models.Organizations29App.Infrastructure.Services.Impls30BasicPlatform.AppService.Applications31BasicPlatform.AppService.FreeSql.ExternalPages32BasicPlatform.AppService.Roles33BasicPlatform.AppService.Users34BasicPlatform.AppService.FreeSql.Applications35BasicPlatform.AppService.FreeSql.Roles36BasicPlatform.AppService.FreeSql.Users37BasicPlatform.WebAPI.Controllers38BasicPlatform.WebAPI.Controllers.Developer39BasicPlatform.WebAPI.Controllers.System401222211212133111214121211511613361114212121113181411282111113138111111121141213112412661114225211218211261139+166 more modules (most-connected shown)

At a glance — Code Health · 53% · Adequate · gated by D3, R7 ·

The Good
D4 · .NET / C# Code Duplication 9.1 D17 · .NET / C# Explicit Debt 9.7 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 9.8 R10 · React / TS Code Duplication 7.9 R2 · React / TS Cyclomatic Complexity 9.3 R3 · React / TS Large Files 9.3 X1 · Repo Async correctness 7.4 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 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 10.0
The Bad
D1 · .NET / C# Cyclomatic Complexity 5.9 D2 · .NET / C# Cognitive Complexity 5.5 X2 · Repo Cancellation propagation 6.7 X5 · Repo Nullable reference types 6.0
The Ugly
D3 · .NET / C# God Classes 0.0 R7 · React / TS Dead Code 0.0

At a glance — Architecture · 79% · Strong ·

The Good
D5 · .NET / C# Coupling 9.3 D6 · .NET / C# Cohesion (LCOM4) 7.8 D23 · .NET / C# Boundary Type-Coupling 10.0 D26 · .NET / C# Project Cohesion 10.0 D35 · .NET / C# Change Coupling 9.8 AX10 · Repo Code composition 7.1 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.8 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0 R11 · React / TS Import Boundaries 9.5 R9 · React / TS Circular Imports 8.3
The Bad
AX4 · Repo Dependency direction 5.7

At a glance — Maturity · 40% · Weak · gated by D34, M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 7.0 M4 · Repo Documentation accuracy 8.0
The Bad
M1 · Repo Documentation (README) 6.0 M3 · Repo Folder & project structure 6.0
The Ugly
D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 21% · Critical · gated by D13, R8, P1, P3, P7 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P2 · Repo Observability 7.4 R6 · React / TS Tooling 10.0
The Bad
D12 · .NET / C# Dependency Hygiene 6.8 P4 · Repo Deployment & Rollback 5.0
The Ugly
D13 · .NET / C# REDACTED Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 41% · Weak · gated by D29, D30, C1 ·

The Good
D31 · .NET / C# IaC & Container Security 8.1 D43 · .NET / C# Malicious Dependencies 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 Bad
D28 · .NET / C# Secrets (history) 5.0 D44 · .NET / C# Platform End-of-Life 6.0 C2 · Repo Access Controls 5.0 S1 · Repo Web-Security Posture 6.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 0.8 D30 · .NET / C# Dependency Vulnerabilities 0.0 C1 · Repo Data Protection 2.0

At a glance — Domain Modelling · 27% · Weak · gated by DM1, DM2, DM3, DM5, DM6 ·

The Good
DM12 · Repo Ambient inputs in the domain 9.1 DM4 · Repo Rich vs anemic model 9.5 DM8 · Repo Value-object opportunities 9.9 DM9 · Repo Scattered domain decisions 10.0
The Ugly
DM1 · Repo Aggregate boundaries 1.0 DM11 · Repo Constructible invalid state 4.6 DM2 · Repo Strongly-typed ids 3.0 DM3 · Repo Integration-event coupling 2.9 DM5 · Repo Encapsulated state 1.0 DM6 · Repo Domain ↔ infrastructure boundary 3.1

At a glance — Event-Driven · 88% · Strong ·

The Good
ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0 ED3 · Repo Event naming 9.9 ED4 · Repo Outbox / dual-write 7.3

At a glance — Accessibility · 31% · Weak · gated by AC2, AC4 ·

The Bad
AC3 · Repo Page structure 5.3 AC6 · Repo Visual & motion safety 6.2
The Ugly
AC1 · Repo Text alternatives 4.9 AC2 · Repo Forms & labels 2.4 AC4 · Repo Keyboard semantics 1.0 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures179High / Critical
A05:2025 — Injection48Medium
A02:2025 — Security Misconfiguration13High / Critical
A07:2025 — Authentication Failures11High / Critical

Roadmap

Immediately resolve the five leaked secrets in configuration files and eliminate all deprecated dependencies to secure the codebase. Establish a CI pipeline that builds and tests on every push, integrating static analysis tools to prevent security regressions from merging. Finally, clean up the dependency tree by removing unused packages and explicitly declaring all imports to ensure maintainability.

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

Do thisHelpsEffortDimension
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2).+5.7 ptsLowREDACTED Scanning
Resolve the 55 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (55).+5.2 ptsMediumDependency Hygiene
Add a CI workflow that builds and runs the test suite on every push/PR.+3.4 ptsMediumCI/CD gates
Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+3.4 ptsMediumSecurity & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+3.4 ptsMediumDependency Hygiene
Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.+2.1 ptsMediumOutbound HTTP resilience
Resolve the 1 No ADRs found finding(s) in ADR Quality.+0.9 ptsLowADR Quality
Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.+1.7 ptsMediumAggregate boundaries

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.5SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.6SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED1.6SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs3.9SlopChange Coupling: Boundary-crossing change coupling: UserQueryService.cs ↔ REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED5.1MixedDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED5.6MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedDependency Vulnerabilities: High CVE: REDACTED

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

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

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

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

Could not be resolved — 8

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. 100 of 104 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 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 — 104 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D17D20D21D23D24D26D28D29D30D31D34D35D39D43D44AC1AC2AC3AC4AC6AC7AX10AX3AX4AX5AX6AX8AX9C1C2DM1DM11DM12DM2DM3DM4DM5DM6DM8DM9ED1ED2ED3ED4ED5GD1IC1M1M2M3M4P1P2P3P4P7PF3R1R10R11R2R3R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 930 of 985 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ 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 01a165ee-7777-73b7-985c-86a417e914c9.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D10 Test Quality — measured, with a gap in what it reached — 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. The 16 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 3 test source file(s) (.tsx, .rs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D12 Dependency Hygiene — 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 npm dependencies as well as NuGet ones — manifests: REDACTED, BasicPlatform.WebAPI/ArcoApp/package.json, BasicPlatform.WebAPI/ConsoleApp/package.json — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read them, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 160 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'REDACTED' with message: The IncludeOpenAPIAnalyzers property and its associated MVC API analyzers are deprecated and will be removed in a future release.
  • D17 Explicit Debt — 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. The 10 deducted marker(s) and the 0.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .tsx (18,303 lines, 42% of production source), .ts (8,306 lines, 19% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 4 task marker(s) (TODO/FIXME/HACK/XXX) across 4 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
  • D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • AXR1 Runtime accessibility — 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. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped.
  • DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • 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. 107 further occurrence(s) are not listed individually; the score already reflects all 147.
  • 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. 362 further occurrence(s) are not listed individually; the score already reflects all 402.
  • X2 Cancellation propagation — 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. 59 further occurrence(s) are not listed individually; the score already reflects all 99.

Repo exclusion declarations: 117 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.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • 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.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • 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.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • 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".

The LLM boundary

LLM-set scores this run (4): D21, D24, ED5, 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 Complexity5.9 / 10Adequate✓ Tool-verified

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

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

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

27 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.ProTablePlus at 110. A further 1 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 ViewModal.ViewModal at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/ViewModal.tsx (ViewModal.ViewModal at 20). 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.

RulerItem.RulerItem::getValueDom (cyclomatic 38) · ×3BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:162
index.EditTableColumnForm (cyclomatic 17) · ×2Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:14
index.ProTablePlus (cyclomatic 110)BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54
index.ProTablePlus (cyclomatic 100)Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50
index.ProTableListPlus (cyclomatic 41)Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:18

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with index.ProTablePlus (cyclomatic 110), index.ProTablePlus (cyclomatic 100). — 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 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

31 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.ProTablePlus at 137.

RulerItem.RulerItem::getValueDom (cognitive 58) · ×3BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:162
index.EditTableColumnForm (cognitive 20) · ×2Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:14
index.ProTablePlus (cognitive 137)BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54
index.ProTablePlus (cognitive 125)Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50
index.ProTableListPlus (cognitive 52)Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:18

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with index.ProTablePlus (cognitive 137), index.ProTablePlus (cognitive 125). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.5 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 Classes0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

42 god class(es) detected.

FunctionTooLong: index.ProTablePlus · ×41BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54
ClassTooLong: UserQueryServiceBasicPlatform.AppService.FreeSql/Users/UserQueryService.cs

What to do

  1. Resolve the 41 FunctionTooLong finding(s) in God Classes — start with index.tsx (28), CreateOrUpdateForm.tsx (6), app.tsx (2). — One of this dimension's main actionable groups (41 warning-level).
  2. Resolve the 1 ClassTooLong finding(s) in God Classes — start with UserQueryService.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.1 / 10Stronggated by 34 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.1 / 10 · rule-coverage 100% · ceiling Verified

34 duplicated block group(s) detected. Measured on part of this repository only: .tsx, .ts (60% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (29 lines × 2) · ×3BasicPlatform.AppService/Applications/Requests/CreateApplicationRequest.cs:23
Duplicated block (24 lines × 2) · ×2BasicPlatform.AppService/Users/Responses/GetUserAccessRecordPagingResponse.cs:24
Duplicated block (20 lines × 3) · ×2BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:11
Duplicated block (11 lines × 2) · ×2BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:132
Duplicated block (56 lines × 2)Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs:21

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

What to do

  1. Resolve the 3 Duplicated block (29 lines × 2) finding(s) in Code Duplication — start with CreateApplicationRequest.cs, ApplicationCreatedEvent.cs, WebSettingModel.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Duplicated block (24 lines × 2) finding(s) in Code Duplication — start with GetUserAccessRecordPagingResponse.cs, UserQueryService.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (20 lines × 3) finding(s) in Code Duplication — start with RoleColumnPermission.cs, UserColumnPermission.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling9.3 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

23 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Layer violation: Domain → Infrastructure · ×2BasicPlatform.Domain/BasicPlatform.Domain.csproj:18
Off the main sequence: CMS.Domain · ×2Apps/CMS/CMS.Domain/CMS.Domain.csproj:1

What to do

  1. Resolve the 2 Layer violation finding(s) in Coupling — start with BasicPlatform.Domain.csproj, CRM.Domain.csproj. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 2 Off the main sequence finding(s) in Coupling — start with CMS.Domain.csproj, CRM.Domain.csproj. — One of this dimension's main actionable groups (2 warning-level).
  3. Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

3 of 16 classes have LCOM4 above 3.

Low cohesion: UtilController (LCOM4 7) · ×3REDACTED:8

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED, Role.cs, User.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

20 test methods: 20 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 4 `it`/`test` case(s) across 2 test file(s) declaring at least one beside 16 .NET test method(s); its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D12 · Dependency Hygiene6.8 / 10Adequate✓ 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 6.8 / 10 · rule-coverage 100% · ceiling Verified

27 outdated, 0 vulnerable, 1 deprecated, 2 prerelease packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.

Deprecated: Microsoft.Extensions.PlatformAbstractions · ×4REDACTED:14
Prerelease dependency: Athena.All.FreeSql · ×2
Deprecated: registry.npmmirror.com/@babel/plugin-proposal-class-properties · ×55REDACTED:1711
Outdated: Microsoft.AspNetCore.Authentication.JwtBearer · ×3REDACTED:21
Outdated: Athena.Infrastructure.Domain · ×24

What to do

  1. Resolve the 55 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (55). — One of this dimension's main actionable groups (55 recommendation-level).
  2. Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
  4. Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

5 secret(s) detected.

REDACTED

What to do

  1. Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
  2. Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.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 270 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 29 direct `PackageReference`(s), and 221 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

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

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

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

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

10 deducted debt markers + unmeasured dead symbols across 17348 LoC in the .NET projects (0.1/KLoC) → score 9.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .tsx, .ts (60% of production source) was not read, and carries at least 4 uncounted task marker(s) in 4 file(s).

CommentedOutCode · ×10BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:170

What to do

  1. Resolve the 10 CommentedOutCode finding(s) in Explicit Debt — start with DeleteUserRequest.cs (3), EventTrackingConfigController.cs (2), ApplicationQueryService.cs. — One of this dimension's main actionable groups (10 warning-level).
  2. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

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 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types leak across context boundaries (10 contexts).

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment ValueStrong◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

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

12 valuable / 0 redundant across 200 sampled comments.

What to do

  1. Improve Comment Value — currently 7.0/10. — 12 valuable / 0 redundant across 200 sampled comments.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 23 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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

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

Method: REDACTED 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 5.0 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)0.8 / 10Critical✓ Tool-verified

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

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

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

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

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

REDACTED
REDACTED

What to do

  1. Resolve the 45 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (22), REDACTED (13), REDACTED (5). — One of this dimension's main actionable groups (45 warning-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

179 finding(s): 16 critical, 74 high, 79 medium, 10 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D31 · IaC & Container Security8.1 / 10Adequategated by 4 critical findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

13 finding(s): 0 critical, 4 high, 5 medium, 4 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

66 of 66 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs. Counted over 66 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×65REDACTED:1
Dormant codebase
Most significant orphaned fileBasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:1

What to do

  1. Resolve the 65 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), REDACTED (2), UserRequestHandler.cs. — One of this dimension's main actionable groups (65 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with UserQueryService.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.8 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: index.tsx↔index.tsx 80%; UserRequestHandler.cs↔REDACTED 79%; index.tsx↔index.tsx 73%

Boundary-crossing change coupling: UserRequestHandler.cs ↔ REDACTED · ×2BasicPlatform.AppService.FreeSql/Users/UserRequestHandler.cs:1
Change coupling: UserQueryService.cs ↔ UserRequestHandler.cs · ×4BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:1
Change-coupling hub: index.tsx → IUserQueryService.cs, index.tsx, index.tsxBasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with UserRequestHandler.cs, UserQueryService.cs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 4 Change coupling finding(s) in Change Coupling — start with UserQueryService.cs, index.tsx, app.tsx. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with index.tsx. — One of this dimension's main actionable groups (1 warning-level).

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

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

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

1 of 694 first-party methods have an oversized IL body.

IL efficiency: 1 authored method(s) exceed the IL budgetBasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:186

✓ On the Gold path — maintain.

Detailed fixes: d39_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-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 23 platform declaration(s) and 0 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.

End-of-life runtime: .NET net7.0REDACTED:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

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

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

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

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

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — BasicPlatform.WebAPI/ArcoApp/src/views/dashboard/workplace/components/carousel.vue:10, BasicPlatform.WebAPI/ArcoApp/src/views/login/components/banner.vue:9

What to do

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

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

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

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

  • This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×23) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:193, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:225, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:267, …
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/index.tsx:20, BasicPlatform.WebAPI/ConsoleApp/src/components/RightContent/index.tsx:21

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.3 / 10Adequate✓ Tool-verified

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — BasicPlatform.WebAPI/ArcoApp/index.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×3) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:159, Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:403, BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:161
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/index.tsx:20, BasicPlatform.WebAPI/ConsoleApp/src/components/RightContent/index.tsx:21
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — BasicPlatform.WebAPI/ArcoApp/src/components/global-setting/index.vue:2, BasicPlatform.WebAPI/ArcoApp/src/components/message-box/list.vue:17, BasicPlatform.WebAPI/ArcoApp/src/components/tab-bar/tab-item.vue:7

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety6.2 / 10Adequate✓ Tool-verified

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

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

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

  • `.ant-spin` moves (`transition: transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/public/scripts/loading.js:57, BasicPlatform.WebAPI/ConsoleApp/public/scripts/loading.js:57
  • `.ant-spin` moves (`transition: transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86), -webkit-transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/public/scripts/loading.js:58, BasicPlatform.WebAPI/ConsoleApp/public/scripts/loading.js:58
  • `.ant-spin-dot-spin` moves (`animation: antRotate 1.2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/public/scripts/loading.js:127, BasicPlatform.WebAPI/ConsoleApp/public/scripts/loading.js:127

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

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

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition7.1 / 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.

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

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

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

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

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

  • The namespaces BasicPlatform.Domain.Models.Organizations ↔ BasicPlatform.Domain.Models.Positions ↔ BasicPlatform.Domain.Models.Roles ↔ BasicPlatform.Domain.Models.Users depend on each other. The lightest dependency in the cycle is BasicPlatform.Domain.Models.Organizations → BasicPlatform.Domain.Models.Roles (BasicPlatform.Domain.Models.Organizations.OrganizationRole → BasicPlatform.Domain.Models.Roles.Role, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — BasicPlatform.Domain/Models/Organizations/OrganizationRole.cs:1

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction5.7 / 10Adequate✓ 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.

  • `BasicPlatform.Domain` is a Domain project but references `BasicPlatform.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — BasicPlatform.Domain/BasicPlatform.Domain.csproj:18
  • This Domain file depends on the Infrastructure project `BasicPlatform.Infrastructure`: it names `BasicPlatform.Infrastructure.Enums`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — BasicPlatform.Domain/GlobalUsings.cs:10
  • This Domain file depends on the Infrastructure project `BasicPlatform.Infrastructure`: it names `ExternalPageType`. The inward dependency rule is broken here. It is named again on lines 100, 138. Depend on an abstraction the inner layer owns, implemented in the outer one. — BasicPlatform.Domain/Models/ExternalPage.cs:35
  • `CRM.Domain` is a Domain project but references `App.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — Apps/CRM/CRM.Domain/CRM.Domain.csproj:10

What to do

  • Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.8 / 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.

  • `IUserQueryService` declares 20 members: `GetPagingAsync`, `GetAccessRecordPagingAsync`, `GetAsync`, `GetTenantSuperAdminAsync`, `GetByUserNameAsync`, `GetIdsByRoleIdAsync`, `GetCurrentUserAsync`, `GetSelectListAsync`, `GetAllSelectListAsync`, `GetIdByUserNameAsync`, `GetUserResourceAsync`, `GetCurrentUserExternalPagesAsync`, `GetUserExternalPagesAsync`, `GetResourceCodeInfoAsync`, `GetResourceCodesAsync`, `GetCurrentUserCustomColumnsAsync`, `GetUserCustomColumnsAsync`, `GetDataPermissionsAsync`, `GetColumnPermissionsAsync`, `GetColumnPermissionsByModuleNameAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — BasicPlatform.AppService/Users/IUserQueryService.cs:11

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

C1 · Data Protection2.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls5.0 / 10Adequate✓ Tool-verified

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

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

  • Authorization IS enforced here (via [Authorize]/guards) — this is NOT a claim that endpoints are unprotected. What's missing is NAMED policies (AddAuthorization/AddPolicy, RequireRole/RequireClaim, RequireAuthorization): the access rules are implicit rather than named and testable. Recommendation, not a defect — name the rules so they're reviewable.
  • This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable. (×7) — Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:16, BasicPlatform.WebAPI/Controllers/FileController.cs:20, BasicPlatform.WebAPI/Controllers/SsoController.cs:44, …
  • [AllowAnonymous] (8) outweighs [Authorize] (7) — review whether the open surface is intended.

What to do

  • Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization.
  • Review the [AllowAnonymous] surface — keep anonymous endpoints deliberate and documented so the open surface stays intentional.
DM1 · Aggregate boundaries1.0 / 10Critical✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

  • `ExternalPage` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/ExternalPage.cs:69
  • `ExternalPage` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/ExternalPage.cs:74
  • `Resource` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Resource.cs:36
  • `Resource` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Resource.cs:41
  • `Application` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Applications/Application.cs:71
  • `Application` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Applications/Application.cs:76
  • `Organization` references the aggregate root `User` directly (via `Leader`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Organizations/Organization.cs:56
  • `Organization` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Organizations/Organization.cs:66
  • `Organization` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Organizations/Organization.cs:71
  • `Position` references the aggregate root `Organization` directly (via `Organization`) — hold its `OrganizationId` instead. — BasicPlatform.Domain/Models/Positions/Position.cs:23
  • `Position` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Positions/Position.cs:57
  • `Position` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Positions/Position.cs:68
  • `Role` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Roles/Role.cs:46
  • `Role` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Roles/Role.cs:51
  • `RoleGroup` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Roles/RoleGroup.cs:36
  • `RoleGroup` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Roles/RoleGroup.cs:41
  • `User` references the aggregate root `Organization` directly (via `Organization`) — hold its `OrganizationId` instead. — BasicPlatform.Domain/Models/Users/User.cs:72
  • `User` references the aggregate root `Position` directly (via `Position`) — hold its `PositionId` instead. — BasicPlatform.Domain/Models/Users/User.cs:83
  • `UserGroup` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Users/UserGroup.cs:34
  • `UserGroup` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead. — BasicPlatform.Domain/Models/Users/UserGroup.cs:39

What to do

  • Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM11 · Constructible invalid state4.6 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `ExternalPage`'s public constructor takes `parentId`, `ownerId`, `name`, `path`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ExternalPage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/ExternalPage.cs:96
  • `Resource`'s public constructor takes `appId`, `key`, `sort`, `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Resource` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/Resource.cs:58
  • `Application`'s public constructor takes `environment`, `name`, `clientId`, `frontendUrl`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Application` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/Applications/Application.cs:98
  • `Organization`'s public constructor takes `parentId`, `name`, `leaderId`, `remarks`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Organization` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/Organizations/Organization.cs:90
  • `Position`'s public constructor takes `organizationId`, `name`, `remarks`, `sort`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Position` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/Positions/Position.cs:87
  • `Role`'s public constructor takes `name`, `dataScopeCustom`, `remarks`, `createdUserId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Role` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/Roles/Role.cs:68
  • `User`'s public constructor takes `id`, `userName`, `password`, `avatar`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/Users/User.cs:154
  • `WebSetting`'s public constructor takes `logo`, `ico`, `name`, `shortName`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `WebSetting` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:58
  • `Article`'s public constructor takes `title`, `summary`, `content`, `author`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Article` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — Apps/CMS/CMS.Domain/Models/Articles/Article.cs:111
  • `Customer`'s public constructor takes `name`, `phoneNumber`, `telephone`, `industry`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Customer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — Apps/CRM/CRM.Domain/Customers/Customer.cs:38

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain9.1 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

  • `Application` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Applications/Application.cs:186
  • `Article` reads `DateTime.Now` inside `Publish`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Apps/CMS/CMS.Domain/Models/Articles/Article.cs:195
  • `Organization` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Organizations/Organization.cs:129
  • `Position` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Positions/Position.cs:123
  • `Role` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Roles/Role.cs:108
  • `RoleGroup` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Roles/RoleGroup.cs:47
  • `TestEventHandler` reads `DateTime.Now` inside `Handle`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Apps/CMS/CMS.AppService.FreeSql/DomainEventHandlers/TestEventHandler.cs:25
  • `User` reads `DateTime.Now` inside `StatusChange`, `Update`, `UpdateLoginInfo`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Users/User.cs:190
  • `UserGroup` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — BasicPlatform.Domain/Models/Users/UserGroup.cs:45

What to do

  • Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

  • `ExternalPage.ParentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/ExternalPage.cs:14
  • `ExternalPage.OwnerId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/ExternalPage.cs:21
  • `Resource.AppId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Resource.cs:14
  • `Resource.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Resource.cs:20
  • `Application.ClientId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Applications/Application.cs:26
  • `Organization.ParentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Organizations/Organization.cs:16
  • `Organization.LeaderId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Organizations/Organization.cs:50
  • `Position.OrganizationId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Positions/Position.cs:17
  • `User.OrganizationId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Users/User.cs:66
  • `User.PositionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — BasicPlatform.Domain/Models/Users/User.cs:77

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling2.9 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether cross-context integration events stay loosely coupled — no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.

Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.

  • `ApplicationStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Applications/Events/ApplicationStatusChangedEvent.cs:11
  • `OrganizationCreatedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Organizations/Events/OrganizationCreatedEvent.cs:31
  • `OrganizationStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Organizations/Events/OrganizationStatusChangedEvent.cs:11
  • `PositionCreatedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Positions/Events/PositionCreatedEvent.cs:26
  • `PositionStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Positions/Events/PositionStatusChangedEvent.cs:11
  • `RoleColumnPermissionAssignedEvent.Permissions` exposes `RoleColumnPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Roles/Events/RoleColumnPermissionAssignedEvent.cs:11
  • `RoleCreatedEvent.DataScope` exposes `RoleDataScope`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Roles/Events/RoleCreatedEvent.cs:21
  • `RoleDataPermissionAssignedEvent.Permissions` exposes `RoleDataPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Roles/Events/RoleDataPermissionAssignedEvent.cs:11
  • `RoleResourceAssignedEvent.Resources` exposes `RoleResource`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Roles/Events/RoleResourceAssignedEvent.cs:11
  • `RoleStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Roles/Events/RoleStatusChangedEvent.cs:11
  • `RoleUpdatedEvent.DataScope` exposes `RoleDataScope`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Roles/Events/RoleUpdatedEvent.cs:21
  • `TenantCreatedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:58
  • `TenantCreatedEvent.Applications` exposes `TenantApplication`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:68
  • `TenantResourceAssignedEvent.Resources` exposes `TenantResource`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Tenants/Events/TenantResourceAssignedEvent.cs:11
  • `TenantStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Tenants/Events/TenantStatusChangedEvent.cs:11
  • `TenantUpdatedEvent.Applications` exposes `TenantApplication`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Tenants/Events/TenantUpdatedEvent.cs:63
  • `UserColumnPermissionAssignedEvent.Permissions` exposes `UserColumnPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Users/Events/UserColumnPermissionAssignedEvent.cs:13
  • `UserCreatedEvent.Gender` exposes `Gender`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Users/Events/UserCreatedEvent.cs:22
  • `UserDataPermissionAssignedEvent.Permissions` exposes `UserDataPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Users/Events/UserDataPermissionAssignedEvent.cs:11
  • `UserResourceAssignedEvent.Resources` exposes `UserResource`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead. — BasicPlatform.Domain/Models/Users/Events/UserResourceAssignedEvent.cs:11
  • `UserStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Users/Events/UserStatusChangedEvent.cs:11
  • `UserUpdatedEvent.Gender` exposes `Gender`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead. — BasicPlatform.Domain/Models/Users/Events/UserUpdatedEvent.cs:27

What to do

  • Keep integration events to primitives + shared-contract types; never reference a producer-domain enum or type, so services evolve independently.
DM4 · Rich vs anemic model9.5 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `Customer` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Apps/CRM/CRM.Domain/Customers/Customer.cs:8

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state1.0 / 10Critical✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

  • `ExternalPage` exposes publicly writable state (ParentId, OwnerId, Name, Type, Path, Icon, and 5 more). — BasicPlatform.Domain/Models/ExternalPage.cs:8
  • `Resource` exposes publicly writable state (AppId, Key, Sort, Status, CreatedUser, LastUpdatedUser). — BasicPlatform.Domain/Models/Resource.cs:8
  • `Application` exposes publicly writable state (Environment, Name, ClientId, ClientSecret, UseDefaultClientSecret, FrontendUrl, and 7 more). — BasicPlatform.Domain/Models/Applications/Application.cs:9
  • `Organization` exposes publicly writable state (ParentId, Parent, ParentPath, Name, Remarks, Status, and 5 more). — BasicPlatform.Domain/Models/Organizations/Organization.cs:9
  • `Position` exposes publicly writable state (OrganizationId, Organization, Name, Remarks, Status, Sort, and 2 more). — BasicPlatform.Domain/Models/Positions/Position.cs:10
  • `Role` exposes publicly writable state (Name, Remarks, Status, DataScope, DataScopeCustom, CreatedUser, and 1 more). — BasicPlatform.Domain/Models/Roles/Role.cs:9
  • `RoleGroup` exposes publicly writable state (Name, Remarks, Status, CreatedUser, LastUpdatedUser). — BasicPlatform.Domain/Models/Roles/RoleGroup.cs:8
  • `Tenant` exposes publicly writable state (Name, Code, IsolationLevel, ContactName, ContactPhoneNumber, ContactEmail, and 6 more). — BasicPlatform.Domain/Models/Tenants/Tenant.cs:6
  • `User` exposes publicly writable state (UserName, Password, Avatar, RealName, Gender, NickName, and 15 more). — BasicPlatform.Domain/Models/Users/User.cs:10
  • `UserGroup` exposes publicly writable state (Name, Remarks, Status, CreatedUser, LastUpdatedUser). — BasicPlatform.Domain/Models/Users/UserGroup.cs:6
  • `WebSetting` exposes publicly writable state (Logo, Ico, Name, ShortName, Description, CopyRight). — BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:8
  • `Article` exposes publicly writable state (Title, Summary, Content, Author, Source, SourceUrl, and 8 more). — Apps/CMS/CMS.Domain/Models/Articles/Article.cs:8
  • `Customer` exposes publicly writable state (Name, PhoneNumber, Telephone, Industry). — Apps/CRM/CRM.Domain/Customers/Customer.cs:8

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary3.1 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

  • `Article` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — Apps/CMS/CMS.Domain/Models/Articles/Article.cs:8
  • `Customer` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — Apps/CRM/CRM.Domain/Customers/Customer.cs:8
  • `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×7) — BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:41, BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:72, BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:74, …
  • `Application` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Applications/Application.cs:9
  • `ExternalPage` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/ExternalPage.cs:8
  • `ExternalPage` (domain layer) names `ExternalPageType` from `BasicPlatform.Infrastructure.Enums` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×3) — BasicPlatform.Domain/Models/ExternalPage.cs:35, BasicPlatform.Domain/Models/ExternalPage.cs:100, BasicPlatform.Domain/Models/ExternalPage.cs:138
  • `Organization` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Organizations/Organization.cs:9
  • `OrganizationRole` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Organizations/OrganizationRole.cs:8
  • `Position` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Positions/Position.cs:10
  • `Resource` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Resource.cs:8
  • `Role` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/Role.cs:9
  • `RoleColumnPermission` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:8
  • `RoleDataPermission` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleDataPermission.cs:6
  • `RoleGroup` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleGroup.cs:8
  • `RoleGroupRole` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleGroupRole.cs:6
  • `RoleGroupUser` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleGroupUser.cs:8
  • `RoleResource` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleResource.cs:6
  • `RoleUser` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Roles/RoleUser.cs:8
  • `Tenant` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Tenants/Tenant.cs:6
  • `TenantApplication` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Tenants/TenantApplication.cs:6
  • `TenantResource` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Tenants/TenantResource.cs:6
  • `User` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/User.cs:10
  • `UserAccessRecord` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserAccessRecord.cs:6
  • `UserAppointment` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserAppointment.cs:9
  • `UserColumnPermission` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserColumnPermission.cs:8
  • `UserCustomColumn` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserCustomColumn.cs:6
  • `UserDataPermission` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserDataPermission.cs:6
  • `UserGroup` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserGroup.cs:6
  • `UserGroupRole` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserGroupRole.cs:8
  • `UserGroupUser` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserGroupUser.cs:6
  • `UserResource` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/Users/UserResource.cs:8
  • `WebSetting` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:8

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM8 · Value-object opportunities9.9 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

  • The parameters [copyright, description, ico, logo, name, shortname] travel together across 4 signatures — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:58

What to do

  • Extract recurring primitive parameter clusters into value objects so the concept (and its rules) lives in one place.
DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

ED3 · Event naming9.9 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

  • `UserPasswordResetEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — BasicPlatform.Domain/Models/Users/Events/UserPasswordResetEvent.cs:6

What to do

  • Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write7.3 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

  • `ArticleRequestHandler.Handle` writes to the database while `ArticleRequestHandler.Handle` publishes to the message bus in the same command-handling flow, with no outbox referenced on either path. Splitting the persist and the publish across sibling methods (or two collaborating actors) doesn't make them atomic — a crash between the two either loses the message or emits a phantom event. Use the transactional outbox pattern so the message is committed in the same transaction as the state change and dispatched afterwards. — Apps/CMS/CMS.AppService.FreeSql/Articles/ArticleRequestHandler.cs:51

What to do

  • Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ED5 · Idempotency10.0 / 10Exemplary◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

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

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in 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: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

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.

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×12) — BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:67, BasicPlatform.Domain/Models/Users/User.cs:356, BasicPlatform.Domain/Models/Users/User.cs:357, …

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

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

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

What to do

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

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure6.0 / 10Adequate✓ 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.

  • Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
  • Only 9/23 projects share a common root namespace — the code's module identity is inconsistent.

What to do

  • Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
  • Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy8.0 / 10Strong◐ Sampled · advisory

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

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

  • BasicPlatform.WebAPI/ConsoleApp/README.md runs `npm run tauri build`, but no REDACTED declares a `tauri` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — BasicPlatform.WebAPI/ConsoleApp/README.md:72

What to do

  • Reconcile the README with reality: BasicPlatform.WebAPI/ConsoleApp/README.md runs `npm run tauri build`, but no REDACTED declares a `tauri` script.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability7.4 / 10Strong✓ Tool-verified

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

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

  • Only 5/11 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 11, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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

  • Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.

  • Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

What to do

  • Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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

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

  • The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.

What to do

  • Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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.

  • 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:108, BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:161, BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:221

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety9.8 / 10Exemplary✓ 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.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication7.9 / 10Strong✓ 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.

  • Apps/CMS/CMS.WebAPI/CMSWeb/ and BasicPlatform.WebAPI/ConsoleApp/ are near-verbatim copies of each other: 111 files are byte-identical under the same relative paths (~5746 lines; the trees hold 176 and 250 files). That is one structural fact, not 111 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — Apps/CMS/CMS.WebAPI/CMSWeb/config/oneapi.json:1
  • 126 duplicated blocks under the repository root have copies in at least two of the sibling directories Apps, BasicPlatform.WebAPI — 81 of them are reported below, and 45 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 126 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 126 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 126 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:5
  • 23 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ have copies in at least two of the sibling directories ExternalPage, Organization, Position, Role, ServerInfo, Tenant (+2 more sibling(s) not listed) — 18 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 23 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:35
  • 14 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/pages/ have copies in at least two of the sibling directories Dashboard, Developer, System — 10 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx:54
  • 7 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/components/ have copies in at least two of the sibling directories AdvancedSearch, ApplicationAuthorization, ApplicationColumnPermission, ApplicationDataPermission, ColumnPermission, DataPermission (+3 more sibling(s) not listed) — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:27
  • 7 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/ have copies in at least two of the sibling directories Application, EventStorage, EventTracking, Log — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/components/ViewModal.tsx:66
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:5 · BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:5 — these 2 files are line-for-line copies of one another — 345 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:5
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:60 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:60 — the two spans are one implementation copied and then locally edited — 1254 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:60
  • Apps/CMS/CMS.WebAPI/CMSWeb/types/cache/mock/login.mock.cache.js:1 · BasicPlatform.WebAPI/ConsoleApp/types/cache/mock/login.mock.cache.js:1 — these 2 files are line-for-line copies of one another — 276 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. — Apps/CMS/CMS.WebAPI/CMSWeb/types/cache/mock/login.mock.cache.js:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:1 — these 3 files are line-for-line copies of one another — 255 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:35 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:43 — the two spans are one implementation copied and then locally edited — 1162 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:35
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:1 — these 2 files are line-for-line copies of one another — 183 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts:46 · BasicPlatform.WebAPI/ConsoleApp/src/utils/utils.ts:42 — the two spans are one implementation copied and then locally edited — 1160 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts:46
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:56 · BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:35 — the two spans are one implementation copied and then locally edited — 944 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:56
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx:1 — these 2 files are line-for-line copies of one another — 165 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:97 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx:113 — the two spans are one implementation copied and then locally edited — 846 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:97
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx:1 — these 2 files are line-for-line copies of one another — 156 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:1 — these 2 files are line-for-line copies of one another — 134 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:1 — these 2 files are line-for-line copies of one another — 133 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Position/index.tsx:17 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:33 — the two spans are one implementation copied and then locally edited — 705 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Position/index.tsx:17
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/requestErrorConfig.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/requestErrorConfig.ts:1 — these 2 files are line-for-line copies of one another — 104 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/requestErrorConfig.ts:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Welcome.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/Welcome.tsx:1 — these 2 files are line-for-line copies of one another — 102 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Welcome.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/pet.ts:3 · BasicPlatform.WebAPI/ConsoleApp/src/services/swagger/pet.ts:3 — these 2 files are line-for-line copies of one another — 95 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/pet.ts:3
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx:1 · Apps/CMS/CMS.WebAPI/CMSWeb/src/components/UserModal/components/TransferForm.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/OrgModal/components/TransferForm.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/UserModal/components/TransferForm.tsx:1 — these 4 files are line-for-line copies of one another — 90 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateRootNodeForm.tsx:8 · BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx:11 — the two spans are one implementation copied and then locally edited — 552 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateRootNodeForm.tsx:8
  • BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:27 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx:21 — the two spans are one implementation copied and then locally edited — 430 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. — BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:27
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/Dashboard/Workbench/index.tsx:1 — these 2 files are line-for-line copies of one another — 82 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/index.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:44 · Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:51 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:44
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/AvatarDropdown.tsx:2 · BasicPlatform.WebAPI/ConsoleApp/src/components/RightContent/AvatarDropdown.tsx:2 — these 2 files are line-for-line copies of one another — 74 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/AvatarDropdown.tsx:2
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:47 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx:54 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:47
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/services/ant-design-pro/api.ts:7 · BasicPlatform.WebAPI/ConsoleApp/src/services/ant-design-pro/api.ts:6 — the two spans are one implementation copied and then locally edited — 485 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/services/ant-design-pro/api.ts:7
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/ExternalPages/index.tsx:10 · BasicPlatform.WebAPI/ConsoleApp/src/pages/ExternalPages/index.tsx:10 — 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/ExternalPages/index.tsx:10
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/ColumnPermissionForm.tsx:7 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/components/ColumnPermissionForm.tsx:8 — 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/ColumnPermissionForm.tsx:7
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/user.ts:3 · BasicPlatform.WebAPI/ConsoleApp/src/services/swagger/user.ts:3 — these 2 files are line-for-line copies of one another — 64 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/user.ts:3
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/ja-JP/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/ja-JP/pages.ts:1 — these 2 files are line-for-line copies of one another — 62 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/ja-JP/pages.ts:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-CN/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/zh-CN/pages.ts:1 — these 2 files are line-for-line copies of one another — 62 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-CN/pages.ts:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-TW/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/zh-TW/pages.ts:1 — these 2 files are line-for-line copies of one another — 62 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-TW/pages.ts:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/signalr/index.ts:23 · BasicPlatform.WebAPI/ConsoleApp/src/signalr/index.ts:23 — 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/signalr/index.ts:23
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/global.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/global.tsx:1 — these 2 files are line-for-line copies of one another — 61 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/global.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/fa-IR/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/fa-IR/pages.ts:1 — these 2 files are line-for-line copies of one another — 61 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/fa-IR/pages.ts:1

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.
R11 · Import Boundaries9.5 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:21 imports antd/lib/menu/hooks/useItems, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:21
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:24 imports antd/lib/menu/hooks/useItems, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:24

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity9.3 / 10Exemplary✓ Tool-verified

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

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

  • fetch has cyclomatic complexity 61 and cognitive complexity 105; 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. — BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:89
  • fetch has cyclomatic complexity 56 and cognitive complexity 98; 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:85
  • fetchColumns has cyclomatic complexity 56 and cognitive complexity 94; 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. — BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue:218
  • getValueDom has cyclomatic complexity 38 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 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. — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:162
  • fetch has cyclomatic complexity 33 and cognitive complexity 62; 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:29
  • getValueDom 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. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:188, BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:190
  • errorHandler has cyclomatic complexity 18 and cognitive complexity 20; 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/requestErrorConfig.ts:46
  • errorHandler has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — BasicPlatform.WebAPI/ConsoleApp/src/requestErrorConfig.ts:45
  • request has cyclomatic complexity 15 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 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. — BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:192
  • request has cyclomatic complexity 12 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 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. — Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:181
  • (anonymous) has cyclomatic complexity 12 and cognitive complexity 22; 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. — BasicPlatform.WebAPI/ArcoApp/src/router/guard/permission.ts:10
  • handleSubmit has cyclomatic complexity 12 and cognitive complexity 22; 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:157
  • (anonymous) has cyclomatic complexity 11 and cognitive complexity 17; 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. — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx:46
  • okHandle has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:48
  • ProTablePlus has cyclomatic complexity 11 and cognitive complexity 10; 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. (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54

What to do

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

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

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

  • BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue:1
  • BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx has 511 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:1
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx has 471 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED 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: REDACTED 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.

  • Unreachable from the 13 application, 41 tooling and 4 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (13 application, 41 tooling, 4 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 (×19) — BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue, BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx, …
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 10 in-repo import(s) from 10 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx and 7 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/index.tsx) — 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 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx) — 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 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 37 in-repo import(s) from 37 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/access.ts, BasicPlatform.WebAPI/ConsoleApp/src/app.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx and 34 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 — BasicPlatform.WebAPI/ConsoleApp/src/utils/utils.ts
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/components/CreateOrUpdateForm.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx) — 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 (×2) — BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx and 5 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 — Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationAuthorization/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/Authorization/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx) — 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 (×2) — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationColumnPermission/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/components/ColumnConfig.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationDataPermission/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/ViewModal.tsx
  • no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx) — 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 — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx

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.

  • Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. — BasicPlatform.WebAPI/ArcoApp/src/router/routes/types.ts:6
  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×10) — BasicPlatform.WebAPI/ArcoApp/src/main.ts:15, BasicPlatform.WebAPI/ArcoApp/src/main.ts:14, BasicPlatform.WebAPI/ArcoApp/src/App.vue:12, …
  • Declared in REDACTED 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. (×3)

What to do

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

  • BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx → BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx → BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx:7

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

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

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×4) — Apps/CMS/CMS.WebAPI/Program.cs:3, Apps/CRM/CRM.WebAPI/Program.cs:2, BasicPlatform.Gateway/Program.cs:3, …
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×4) — Apps/CMS/CMS.WebAPI/Program.cs:3, Apps/CRM/CRM.WebAPI/Program.cs:2, BasicPlatform.Gateway/Program.cs:3, …

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness7.4 / 10Strong✓ Tool-verified

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.

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×3) — BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:108, BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:161, BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:221

What to do

  • Sync-over-async (deadlock risk)
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.

X2 · Cancellation propagation6.7 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

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

  • Only 78/176 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×33) — BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:34, BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:81, BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:115, …
  • Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×6) — BasicPlatform.AppService.FreeSql/Commons/CommonService.cs:113, BasicPlatform.AppService.FreeSql/Commons/DefaultColumnPermissionService.cs:51, BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:50, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
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 `ArgumentNullException` 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 `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items 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.

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

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

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

X5 · Nullable reference types6.0 / 10Adequate✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

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

  • ~5.4 `!` suppressions per 1k syntax nodes — 286 suppression(s) across the 52573 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

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

Reference — by lens

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

LensScoreRatingImpact
Code Health53%Adequate — gated by D3, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture79%StrongSolid.
Maturity40%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness21%Critical — gated by D13, R8, P1, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security41%Weak — gated by D29, D30, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling27%Weak — gated by DM1, DM2, DM3, DM5, DM6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven88%StrongStrongest area.
Accessibility31%Weak — gated by AC2, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 34 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.

  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D11 Test Reliability — Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — other: measured (0 flaky); JavaScript/TypeScript (jest via `pnpm install --frozen-lockfile --ignore-scripts` in Apps/CMS/CMS.WebAPI/CMSWeb/; jest via `pnpm install --frozen-lockfile --ignore-scripts` in BasicPlatform.WebAPI/ConsoleApp/): not included — the dependency install for Apps/CMS/CMS.WebAPI/CMSWeb/ refused the committed lockfile (ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because REDACTED is absent), so the suite never ran. No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .py, .rs, .ts, .tsx, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D19 Documentation Quality — LLM evaluation failed
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .py, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the .NET half measured 0.2%; the JavaScript/TypeScript half could not be measured — the dependency install for Apps/CMS/CMS.WebAPI/CMSWeb/ refused the committed lockfile (ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because REDACTED is absent), so the suite never ran. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
  • DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • R4 Test Coverage — 4 test file(s) reach none of 269 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • 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 — 216 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×72
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 47 more in this group — see findings.md.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×40
  • Domain depends on infrastructure: Article Apps/CMS/CMS.Domain/Models/Articles/Article.cs:8 — `Article` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Customer Apps/CRM/CRM.Domain/Customers/Customer.cs:8 — `Customer` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:41 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:72 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:74 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:105 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:121 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:123 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CacheEventHandler BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:138 — `CacheEventHandler` (domain layer) names `CacheConstant` from `BasicPlatform.Infrastructure.Caches` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Application BasicPlatform.Domain/Models/Applications/Application.cs:9 — `Application` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ExternalPage BasicPlatform.Domain/Models/ExternalPage.cs:8 — `ExternalPage` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ExternalPage BasicPlatform.Domain/Models/ExternalPage.cs:35 — `ExternalPage` (domain layer) names `ExternalPageType` from `BasicPlatform.Infrastructure.Enums` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ExternalPage BasicPlatform.Domain/Models/ExternalPage.cs:100 — `ExternalPage` (domain layer) names `ExternalPageType` from `BasicPlatform.Infrastructure.Enums` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ExternalPage BasicPlatform.Domain/Models/ExternalPage.cs:138 — `ExternalPage` (domain layer) names `ExternalPageType` from `BasicPlatform.Infrastructure.Enums` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Organization BasicPlatform.Domain/Models/Organizations/Organization.cs:9 — `Organization` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: OrganizationRole BasicPlatform.Domain/Models/Organizations/OrganizationRole.cs:8 — `OrganizationRole` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Position BasicPlatform.Domain/Models/Positions/Position.cs:10 — `Position` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Resource BasicPlatform.Domain/Models/Resource.cs:8 — `Resource` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Role BasicPlatform.Domain/Models/Roles/Role.cs:9 — `Role` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleColumnPermission BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:8 — `RoleColumnPermission` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleDataPermission BasicPlatform.Domain/Models/Roles/RoleDataPermission.cs:6 — `RoleDataPermission` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleGroup BasicPlatform.Domain/Models/Roles/RoleGroup.cs:8 — `RoleGroup` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleGroupRole BasicPlatform.Domain/Models/Roles/RoleGroupRole.cs:6 — `RoleGroupRole` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleGroupUser BasicPlatform.Domain/Models/Roles/RoleGroupUser.cs:8 — `RoleGroupUser` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: RoleResource BasicPlatform.Domain/Models/Roles/RoleResource.cs:6 — `RoleResource` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • + 15 more in this group — see findings.md.
DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×20
  • Aggregate holds a reference to another aggregate: ExternalPage.CreatedUser BasicPlatform.Domain/Models/ExternalPage.cs:69 — `ExternalPage` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: ExternalPage.LastUpdatedUser BasicPlatform.Domain/Models/ExternalPage.cs:74 — `ExternalPage` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Resource.CreatedUser BasicPlatform.Domain/Models/Resource.cs:36 — `Resource` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Resource.LastUpdatedUser BasicPlatform.Domain/Models/Resource.cs:41 — `Resource` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Application.CreatedUser BasicPlatform.Domain/Models/Applications/Application.cs:71 — `Application` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Application.LastUpdatedUser BasicPlatform.Domain/Models/Applications/Application.cs:76 — `Application` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Organization.Leader BasicPlatform.Domain/Models/Organizations/Organization.cs:56 — `Organization` references the aggregate root `User` directly (via `Leader`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Organization.CreatedUser BasicPlatform.Domain/Models/Organizations/Organization.cs:66 — `Organization` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Organization.LastUpdatedUser BasicPlatform.Domain/Models/Organizations/Organization.cs:71 — `Organization` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Position.Organization BasicPlatform.Domain/Models/Positions/Position.cs:23 — `Position` references the aggregate root `Organization` directly (via `Organization`) — hold its `OrganizationId` instead.
  • Aggregate holds a reference to another aggregate: Position.CreatedUser BasicPlatform.Domain/Models/Positions/Position.cs:57 — `Position` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Position.LastUpdatedUser BasicPlatform.Domain/Models/Positions/Position.cs:68 — `Position` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Role.CreatedUser BasicPlatform.Domain/Models/Roles/Role.cs:46 — `Role` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Role.LastUpdatedUser BasicPlatform.Domain/Models/Roles/Role.cs:51 — `Role` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: RoleGroup.CreatedUser BasicPlatform.Domain/Models/Roles/RoleGroup.cs:36 — `RoleGroup` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: RoleGroup.LastUpdatedUser BasicPlatform.Domain/Models/Roles/RoleGroup.cs:41 — `RoleGroup` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: User.Organization BasicPlatform.Domain/Models/Users/User.cs:72 — `User` references the aggregate root `Organization` directly (via `Organization`) — hold its `OrganizationId` instead.
  • Aggregate holds a reference to another aggregate: User.Position BasicPlatform.Domain/Models/Users/User.cs:83 — `User` references the aggregate root `Position` directly (via `Position`) — hold its `PositionId` instead.
  • Aggregate holds a reference to another aggregate: UserGroup.CreatedUser BasicPlatform.Domain/Models/Users/UserGroup.cs:34 — `UserGroup` references the aggregate root `User` directly (via `CreatedUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: UserGroup.LastUpdatedUser BasicPlatform.Domain/Models/Users/UserGroup.cs:39 — `UserGroup` references the aggregate root `User` directly (via `LastUpdatedUser`) — hold its `UserId` instead.
D30 · Dependency Vulnerabilities · Critical CVE · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM3 · Integration-event coupling · Integration event couples to a producer-owned enum · ×13
  • Integration event couples to a producer-owned enum: ApplicationStatusChangedEvent.Status BasicPlatform.Domain/Models/Applications/Events/ApplicationStatusChangedEvent.cs:11 — `ApplicationStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: OrganizationCreatedEvent.Status BasicPlatform.Domain/Models/Organizations/Events/OrganizationCreatedEvent.cs:31 — `OrganizationCreatedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: OrganizationStatusChangedEvent.Status BasicPlatform.Domain/Models/Organizations/Events/OrganizationStatusChangedEvent.cs:11 — `OrganizationStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: PositionCreatedEvent.Status BasicPlatform.Domain/Models/Positions/Events/PositionCreatedEvent.cs:26 — `PositionCreatedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: PositionStatusChangedEvent.Status BasicPlatform.Domain/Models/Positions/Events/PositionStatusChangedEvent.cs:11 — `PositionStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: RoleCreatedEvent.DataScope BasicPlatform.Domain/Models/Roles/Events/RoleCreatedEvent.cs:21 — `RoleCreatedEvent.DataScope` exposes `RoleDataScope`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: RoleStatusChangedEvent.Status BasicPlatform.Domain/Models/Roles/Events/RoleStatusChangedEvent.cs:11 — `RoleStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: RoleUpdatedEvent.DataScope BasicPlatform.Domain/Models/Roles/Events/RoleUpdatedEvent.cs:21 — `RoleUpdatedEvent.DataScope` exposes `RoleDataScope`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: TenantCreatedEvent.Status BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:58 — `TenantCreatedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: TenantStatusChangedEvent.Status BasicPlatform.Domain/Models/Tenants/Events/TenantStatusChangedEvent.cs:11 — `TenantStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: UserCreatedEvent.Gender BasicPlatform.Domain/Models/Users/Events/UserCreatedEvent.cs:22 — `UserCreatedEvent.Gender` exposes `Gender`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: UserStatusChangedEvent.Status BasicPlatform.Domain/Models/Users/Events/UserStatusChangedEvent.cs:11 — `UserStatusChangedEvent.Status` exposes `Status`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: UserUpdatedEvent.Gender BasicPlatform.Domain/Models/Users/Events/UserUpdatedEvent.cs:27 — `UserUpdatedEvent.Gender` exposes `Gender`, a enum owned by the producer's domain assembly (`Athena.Infrastructure`) — carry the enum as a string/int instead.
DM3 · Integration-event coupling · Integration event couples to a producer-owned domain type · ×9
  • Integration event couples to a producer-owned domain type: RoleColumnPermissionAssignedEvent.Permissions BasicPlatform.Domain/Models/Roles/Events/RoleColumnPermissionAssignedEvent.cs:11 — `RoleColumnPermissionAssignedEvent.Permissions` exposes `RoleColumnPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: RoleDataPermissionAssignedEvent.Permissions BasicPlatform.Domain/Models/Roles/Events/RoleDataPermissionAssignedEvent.cs:11 — `RoleDataPermissionAssignedEvent.Permissions` exposes `RoleDataPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: RoleResourceAssignedEvent.Resources BasicPlatform.Domain/Models/Roles/Events/RoleResourceAssignedEvent.cs:11 — `RoleResourceAssignedEvent.Resources` exposes `RoleResource`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: TenantCreatedEvent.Applications BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:68 — `TenantCreatedEvent.Applications` exposes `TenantApplication`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: TenantResourceAssignedEvent.Resources BasicPlatform.Domain/Models/Tenants/Events/TenantResourceAssignedEvent.cs:11 — `TenantResourceAssignedEvent.Resources` exposes `TenantResource`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: TenantUpdatedEvent.Applications BasicPlatform.Domain/Models/Tenants/Events/TenantUpdatedEvent.cs:63 — `TenantUpdatedEvent.Applications` exposes `TenantApplication`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: UserColumnPermissionAssignedEvent.Permissions BasicPlatform.Domain/Models/Users/Events/UserColumnPermissionAssignedEvent.cs:13 — `UserColumnPermissionAssignedEvent.Permissions` exposes `UserColumnPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: UserDataPermissionAssignedEvent.Permissions BasicPlatform.Domain/Models/Users/Events/UserDataPermissionAssignedEvent.cs:11 — `UserDataPermissionAssignedEvent.Permissions` exposes `UserDataPermission`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
  • Integration event couples to a producer-owned domain type: UserResourceAssignedEvent.Resources BasicPlatform.Domain/Models/Users/Events/UserResourceAssignedEvent.cs:11 — `UserResourceAssignedEvent.Resources` exposes `UserResource`, a domain type owned by the producer's domain assembly (`BasicPlatform.Domain`) — carry the id as its primitive value instead.
D13 · REDACTED Scanning · Leaked secret · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×4
  • Click handler on a non-interactive <div> Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/index.tsx:20 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> BasicPlatform.WebAPI/ArcoApp/src/components/global-setting/index.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> BasicPlatform.WebAPI/ArcoApp/src/components/message-box/list.vue:17 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> BasicPlatform.WebAPI/ConsoleApp/src/components/RightContent/index.tsx:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D31 · IaC & Container Security · High IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×2
  • <img> without a text alternative BasicPlatform.WebAPI/ArcoApp/src/views/dashboard/workplace/components/carousel.vue:10 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative BasicPlatform.WebAPI/ArcoApp/src/views/login/components/banner.vue:9 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×2
  • Custom control with no accessible name on <div> Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/index.tsx:20 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> BasicPlatform.WebAPI/ConsoleApp/src/components/RightContent/index.tsx:21 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AX4 · Dependency direction · Dependency-rule violation · ×2
  • Dependency-rule violation: BasicPlatform.Domain (Domain) → BasicPlatform.Infrastructure (Infrastructure) BasicPlatform.Domain/BasicPlatform.Domain.csproj:18 — `BasicPlatform.Domain` is a Domain project but references `BasicPlatform.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • Dependency-rule violation: CRM.Domain (Domain) → App.Infrastructure (Infrastructure) Apps/CRM/CRM.Domain/CRM.Domain.csproj:10 — `CRM.Domain` is a Domain project but references `App.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
D11 · Test Reliability · Test suite cannot be installed from its own lockfile · ×2
  • Test suite cannot be installed from its own lockfile: Apps/CMS/CMS.WebAPI/CMSWeb/ — The jest suite in Apps/CMS/CMS.WebAPI/CMSWeb/ was never exercised because its dependency install refused the committed lockfile — the dependency install for Apps/CMS/CMS.WebAPI/CMSWeb/ refused the committed lockfile (ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because REDACTED is absent), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: BasicPlatform.WebAPI/ConsoleApp/ — The jest suite in BasicPlatform.WebAPI/ConsoleApp/ was never exercised because its dependency install refused the committed lockfile — the dependency install for BasicPlatform.WebAPI/ConsoleApp/ refused the committed lockfile (ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because REDACTED is absent), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: UserRequestHandler.cs ↔ REDACTED BasicPlatform.AppService.FreeSql/Users/UserRequestHandler.cs:1 — `BasicPlatform.AppService.FreeSql/Users/UserRequestHandler.cs` (context BasicPlatform.AppService.FreeSql) and `REDACTED` (context BasicPlatform.WebAPI) sit in DIFFERENT parts of the tree yet change together 79% of the time (11 of the 14 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 11 shared commits counted here, the most recent 3 are `fd1b0d89` #支持用户配置列权限及数据脱敏; `a6db0f7e` #完善应用模块。; `346a277e` #合并数据权限相关表，实现可针对用户配置数据权限。 — run `git show` on any of them.
  • Boundary-crossing change coupling: UserQueryService.cs ↔ REDACTED BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:1 — `BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs` (context BasicPlatform.AppService.FreeSql) and `REDACTED` (context BasicPlatform.WebAPI) 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 `fd1b0d89` #支持用户配置列权限及数据脱敏; `edd22b8e` #修复同步资源更新不正确问题 #删除重置资源接口 #修改编辑用户时组织部门选择一级不生效问题; `a6db0f7e` #完善应用模块。 — run `git show` on any of them.
D5 · Coupling · Layer violation · ×2
  • Layer violation: Domain → Infrastructure BasicPlatform.Domain/BasicPlatform.Domain.csproj:18 — BasicPlatform.Domain (Domain) references BasicPlatform.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
  • Layer violation: Domain → Infrastructure Apps/CRM/CRM.Domain/CRM.Domain.csproj:10 — CRM.Domain (Domain) references App.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×1
  • Click handler on a non-interactive <span> BasicPlatform.WebAPI/ArcoApp/src/components/tab-bar/tab-item.vue:7 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle BasicPlatform.Domain/Models/Organizations/OrganizationRole.cs:1 — The namespaces BasicPlatform.Domain.Models.Organizations ↔ BasicPlatform.Domain.Models.Positions ↔ BasicPlatform.Domain.Models.Roles ↔ BasicPlatform.Domain.Models.Users depend on each other. The lightest dependency in the cycle is BasicPlatform.Domain.Models.Organizations → BasicPlatform.Domain.Models.Roles (BasicPlatform.Domain.Models.Organizations.OrganizationRole → BasicPlatform.Domain.Models.Roles.Role, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
ED4 · Outbox / dual-write · Dual write (no outbox) · ×1
  • Dual write (no outbox): ArticleRequestHandler.Handle persists, ArticleRequestHandler.Handle publishes Apps/CMS/CMS.AppService.FreeSql/Articles/ArticleRequestHandler.cs:51 — `ArticleRequestHandler.Handle` writes to the database while `ArticleRequestHandler.Handle` publishes to the message bus in the same command-handling flow, with no outbox referenced on either path. Splitting the persist and the publish across sibling methods (or two collaborating actors) doesn't make them atomic — a crash between the two either loses the message or emits a phantom event. Use the transactional outbox pattern so the message is committed in the same transaction as the state change and dispatched afterwards.
R8 · Dependency Hygiene · Unlisted import '@/api' · ×1
  • Unlisted import '@/api' BasicPlatform.WebAPI/ArcoApp/src/main.ts:15 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/assets' · ×1
  • Unlisted import '@/assets' BasicPlatform.WebAPI/ArcoApp/src/main.ts:14 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/components' · ×1
  • Unlisted import '@/components' BasicPlatform.WebAPI/ArcoApp/src/App.vue:12 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/config' · ×1
  • Unlisted import '@/config' BasicPlatform.WebAPI/ArcoApp/src/store/modules/app/index.ts:5 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/hooks' · ×1
  • Unlisted import '@/hooks' BasicPlatform.WebAPI/ArcoApp/src/App.vue:13 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/layout' · ×1
  • Unlisted import '@/layout' BasicPlatform.WebAPI/ArcoApp/src/router/routes/base.ts:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/router' · ×1
  • Unlisted import '@/router' BasicPlatform.WebAPI/ArcoApp/src/router/routes/base.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/store' · ×1
  • Unlisted import '@/store' BasicPlatform.WebAPI/ArcoApp/src/directive/permission/index.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/utils' · ×1
  • Unlisted import '@/utils' BasicPlatform.WebAPI/ArcoApp/src/router/guard/index.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/views' · ×1
  • Unlisted import '@/views' BasicPlatform.WebAPI/ArcoApp/src/locale/en-US.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (2 files) · ×1
  • Import cycle (2 files) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx:7 — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx → BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx → BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx
Serious — 524 finding(s)
D30 · Dependency Vulnerabilities · Medium CVE · ×56
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 31 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 20 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×41
  • FunctionTooLong: index.ProTablePlus BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54 — FunctionTooLong — ProTablePlus runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.ProTablePlus Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50 — FunctionTooLong — ProTablePlus runs 364 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 264 over it, 3.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TableList BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:29 — FunctionTooLong — TableList runs 271 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 171 over it, 2.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CreateOrUpdateForm.CreateOrUpdateForm BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/components/CreateOrUpdateForm.tsx:17 — FunctionTooLong — CreateOrUpdateForm runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TableList BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx:18 — FunctionTooLong — TableList runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TableList BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:27 — FunctionTooLong — TableList runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TableList BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx:27 — FunctionTooLong — TableList runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TableList BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/index.tsx:19 — FunctionTooLong — TableList runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.AdvancedSearch BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx:21 — FunctionTooLong — AdvancedSearch runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Authorization BasicPlatform.WebAPI/ConsoleApp/src/components/Authorization/index.tsx:13 — FunctionTooLong — Authorization runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.EditTableColumnForm BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:14 — FunctionTooLong — EditTableColumnForm runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.EditTableColumnForm Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:14 — FunctionTooLong — EditTableColumnForm runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.DataPermission BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx:13 — FunctionTooLong — DataPermission runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ViewModal.ViewModal BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/ViewModal.tsx:17 — FunctionTooLong — ViewModal runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Center BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx:8 — FunctionTooLong — Center runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.QueryPolicyModal BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:23 — FunctionTooLong — QueryPolicyModal runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.AdvancedSearch Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:20 — FunctionTooLong — AdvancedSearch runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Center Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:8 — FunctionTooLong — Center runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ColumnConfig.ColumnConfig BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/components/ColumnConfig.tsx:27 — FunctionTooLong — ColumnConfig runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CreateOrUpdateForm.CreateOrUpdateForm BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx:19 — FunctionTooLong — CreateOrUpdateForm runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Center BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:9 — FunctionTooLong — Center runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Center Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:9 — FunctionTooLong — Center runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.TableList BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx:14 — FunctionTooLong — TableList runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ViewDrawer.ViewDrawer BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/components/ViewDrawer.tsx:15 — FunctionTooLong — ViewDrawer runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.ProTableListPlus Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:18 — FunctionTooLong — ProTableListPlus runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 16 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×33
  • Async method without CancellationToken: GetEnvironmentListAsync BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:81 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetSelectListAsync BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:115 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPagingAsync BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:133 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:147 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetByClientIdAsync BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:160 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetColumnsAsync BasicPlatform.AppService.FreeSql/Commons/CommonService.cs:37 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ColumnAuthAsync BasicPlatform.AppService.FreeSql/Commons/CommonService.cs:81 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPagingAsync BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetSelectListAsync BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTreeListAsync BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:89 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPagingAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetIdByNameAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:83 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTreeListAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:95 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTreeSelectListAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:111 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCascaderListAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:124 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetSelectListAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:140 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetParentPathAsync BasicPlatform.AppService.FreeSql/Organizations/OrganizationRequestHandler.cs:136 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetDataPermissionsAsync BasicPlatform.AppService.FreeSql/Roles/RoleQueryService.cs:205 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetColumnPermissionsAsync BasicPlatform.AppService.FreeSql/Roles/RoleQueryService.cs:217 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetConnectionStringAsync BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:168 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAsync BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:184 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPagingAsync BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:41 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 8 more in this group — see findings.md.
AC2 · Forms & labels · <Select> field component without a label · ×20
  • <Select> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:193 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:225 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:267 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:415 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:440 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:459 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:195 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:227 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:269 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:427 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:452 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:471 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/components/ColumnConfig.tsx:104 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/components/ColumnConfig.tsx:169 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:165 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:209 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:265 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:413 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:438 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:457 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
DM5 · Encapsulated state · Mutable entity · ×13
  • Mutable entity: ExternalPage BasicPlatform.Domain/Models/ExternalPage.cs:8 — `ExternalPage` exposes publicly writable state (ParentId, OwnerId, Name, Type, Path, Icon, and 5 more).
  • Mutable entity: Resource BasicPlatform.Domain/Models/Resource.cs:8 — `Resource` exposes publicly writable state (AppId, Key, Sort, Status, CreatedUser, LastUpdatedUser).
  • Mutable entity: Application BasicPlatform.Domain/Models/Applications/Application.cs:9 — `Application` exposes publicly writable state (Environment, Name, ClientId, ClientSecret, UseDefaultClientSecret, FrontendUrl, and 7 more).
  • Mutable entity: Organization BasicPlatform.Domain/Models/Organizations/Organization.cs:9 — `Organization` exposes publicly writable state (ParentId, Parent, ParentPath, Name, Remarks, Status, and 5 more).
  • Mutable entity: Position BasicPlatform.Domain/Models/Positions/Position.cs:10 — `Position` exposes publicly writable state (OrganizationId, Organization, Name, Remarks, Status, Sort, and 2 more).
  • Mutable entity: Role BasicPlatform.Domain/Models/Roles/Role.cs:9 — `Role` exposes publicly writable state (Name, Remarks, Status, DataScope, DataScopeCustom, CreatedUser, and 1 more).
  • Mutable entity: RoleGroup BasicPlatform.Domain/Models/Roles/RoleGroup.cs:8 — `RoleGroup` exposes publicly writable state (Name, Remarks, Status, CreatedUser, LastUpdatedUser).
  • Mutable entity: Tenant BasicPlatform.Domain/Models/Tenants/Tenant.cs:6 — `Tenant` exposes publicly writable state (Name, Code, IsolationLevel, ContactName, ContactPhoneNumber, ContactEmail, and 6 more).
  • Mutable entity: User BasicPlatform.Domain/Models/Users/User.cs:10 — `User` exposes publicly writable state (UserName, Password, Avatar, RealName, Gender, NickName, and 15 more).
  • Mutable entity: UserGroup BasicPlatform.Domain/Models/Users/UserGroup.cs:6 — `UserGroup` exposes publicly writable state (Name, Remarks, Status, CreatedUser, LastUpdatedUser).
  • Mutable entity: WebSetting BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:8 — `WebSetting` exposes publicly writable state (Logo, Ico, Name, ShortName, Description, CopyRight).
  • Mutable entity: Article Apps/CMS/CMS.Domain/Models/Articles/Article.cs:8 — `Article` exposes publicly writable state (Title, Summary, Content, Author, Source, SourceUrl, and 8 more).
  • Mutable entity: Customer Apps/CRM/CRM.Domain/Customers/Customer.cs:8 — `Customer` exposes publicly writable state (Name, PhoneNumber, Telephone, Industry).
D17 · Explicit Debt · CommentedOutCode · ×10
  • CommentedOutCode BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:170 — 15 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.AppService/Users/Models/UserDataPermissionModel.cs:48 — 3 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.AppService/Users/Requests/DeleteUserRequest.cs:17 — 3 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.AppService/Users/Requests/DeleteUserRequest.cs:31 — 3 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.AppService/Users/Requests/DeleteUserRequest.cs:45 — 3 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.Domain/Models/Users/User.cs:356 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:140 — 6 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.WebAPI/Controllers/Developer/EventTrackingConfigController.cs:87 — 6 consecutive commented-code lines
  • CommentedOutCode BasicPlatform.WebAPI/Controllers/Developer/EventTrackingConfigController.cs:117 — 5 consecutive commented-code lines
  • CommentedOutCode REDACTED:219 — 20 consecutive commented-code lines
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM11 · Constructible invalid state · Constructible in an invalid state · ×10
  • Constructible in an invalid state: ExternalPage BasicPlatform.Domain/Models/ExternalPage.cs:96 — `ExternalPage`'s public constructor takes `parentId`, `ownerId`, `name`, `path`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ExternalPage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Resource BasicPlatform.Domain/Models/Resource.cs:58 — `Resource`'s public constructor takes `appId`, `key`, `sort`, `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Resource` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Application BasicPlatform.Domain/Models/Applications/Application.cs:98 — `Application`'s public constructor takes `environment`, `name`, `clientId`, `frontendUrl`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Application` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Organization BasicPlatform.Domain/Models/Organizations/Organization.cs:90 — `Organization`'s public constructor takes `parentId`, `name`, `leaderId`, `remarks`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Organization` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Position BasicPlatform.Domain/Models/Positions/Position.cs:87 — `Position`'s public constructor takes `organizationId`, `name`, `remarks`, `sort`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Position` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Role BasicPlatform.Domain/Models/Roles/Role.cs:68 — `Role`'s public constructor takes `name`, `dataScopeCustom`, `remarks`, `createdUserId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Role` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: User BasicPlatform.Domain/Models/Users/User.cs:154 — `User`'s public constructor takes `id`, `userName`, `password`, `avatar`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: WebSetting BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:58 — `WebSetting`'s public constructor takes `logo`, `ico`, `name`, `shortName`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `WebSetting` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Article Apps/CMS/CMS.Domain/Models/Articles/Article.cs:111 — `Article`'s public constructor takes `title`, `summary`, `content`, `author`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Article` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Customer Apps/CRM/CRM.Domain/Customers/Customer.cs:38 — `Customer`'s public constructor takes `name`, `phoneNumber`, `telephone`, `industry`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Customer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×9
  • Domain type reads the wall clock: Application BasicPlatform.Domain/Models/Applications/Application.cs:186 — `Application` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: Article Apps/CMS/CMS.Domain/Models/Articles/Article.cs:195 — `Article` reads `DateTime.Now` inside `Publish`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: Organization BasicPlatform.Domain/Models/Organizations/Organization.cs:129 — `Organization` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: Position BasicPlatform.Domain/Models/Positions/Position.cs:123 — `Position` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: Role BasicPlatform.Domain/Models/Roles/Role.cs:108 — `Role` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: RoleGroup BasicPlatform.Domain/Models/Roles/RoleGroup.cs:47 — `RoleGroup` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: TestEventHandler Apps/CMS/CMS.AppService.FreeSql/DomainEventHandlers/TestEventHandler.cs:25 — `TestEventHandler` reads `DateTime.Now` inside `Handle`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: User BasicPlatform.Domain/Models/Users/User.cs:190 — `User` reads `DateTime.Now` inside `StatusChange`, `Update`, `UpdateLoginInfo`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: UserGroup BasicPlatform.Domain/Models/Users/UserGroup.cs:45 — `UserGroup` reads `DateTime.Now` inside `StatusChange`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×6
  • Animation without a prefers-reduced-motion guard Apps/CMS/CMS.WebAPI/CMSWeb/public/scripts/loading.js:57 — `.ant-spin` moves (`transition: transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Apps/CMS/CMS.WebAPI/CMSWeb/public/scripts/loading.js:58 — `.ant-spin` moves (`transition: transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86), -webkit-transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard Apps/CMS/CMS.WebAPI/CMSWeb/public/scripts/loading.js:127 — `.ant-spin-dot-spin` moves (`animation: antRotate 1.2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard BasicPlatform.WebAPI/ConsoleApp/public/scripts/loading.js:57 — `.ant-spin` moves (`transition: transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard BasicPlatform.WebAPI/ConsoleApp/public/scripts/loading.js:58 — `.ant-spin` moves (`transition: transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86), -webkit-transform 0.3s cubic-bezier(0.78, 0.14, 0.15, 0.86)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard BasicPlatform.WebAPI/ConsoleApp/public/scripts/loading.js:127 — `.ant-spin-dot-spin` moves (`animation: antRotate 1.2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
X2 · Cancellation propagation · Async local function without CancellationToken · ×6
  • Async local function without CancellationToken: QueryFunc BasicPlatform.AppService.FreeSql/Commons/CommonService.cs:113 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: QueryFunc BasicPlatform.AppService.FreeSql/Commons/DefaultColumnPermissionService.cs:51 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: QueryFunc BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:50 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: QueryFunc BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:131 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: QueryFunc BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:183 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: QueryFunc BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:243 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
D31 · IaC & Container Security · Medium IaC · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Deprecated · ×4
  • Deprecated: Microsoft.Extensions.PlatformAbstractions REDACTED:14 — Microsoft.Extensions.PlatformAbstractions 1.1.0 — Other,Legacy
  • Deprecated: registry.npmmirror.com/@types/classnames REDACTED:76 — registry.npmmirror.com/@types/classnames 2.3.1 (declared as `@types/classnames`), declared in REDACTED, is marked deprecated by its publisher: "This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint BasicPlatform.WebAPI/ArcoApp/package.json:65 — eslint 8.38.0, declared in BasicPlatform.WebAPI/ArcoApp/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: registry.npmmirror.com/@types/classnames BasicPlatform.WebAPI/ConsoleApp/package.json:79 — registry.npmmirror.com/@types/classnames 2.3.1 (declared as `@types/classnames`), declared in BasicPlatform.WebAPI/ConsoleApp/package.json, is marked deprecated by its publisher: "This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: UserQueryService.cs ↔ UserRequestHandler.cs BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:1 — `BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs` and `BasicPlatform.AppService.FreeSql/Users/UserRequestHandler.cs` change together 71% of the time (10 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `fd1b0d89` #支持用户配置列权限及数据脱敏; `a6db0f7e` #完善应用模块。; `346a277e` #合并数据权限相关表，实现可针对用户配置数据权限。 — run `git show` on any of them.
  • Change coupling: index.tsx ↔ index.tsx BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/index.tsx:1 — `BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/index.tsx` and `BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1e5e3fca` #前端添加queryDetail方法统一查询详情; `a0b39f97` #同步代码 (at that commit the files were still `BasicPlatform.WebAPI/ConsoleApp/src/pages/Organization/Org/index.tsx` and `BasicPlatform.WebAPI/ConsoleApp/src/pages/Permission/Role/index.tsx`); `6995b97c` #1、更新基础库，2、添加员工访问记录查询功能 (at that commit the files were still `BasicPlatform.WebAPI/ConsoleApp/src/pages/Organization/Org/index.tsx` and `BasicPlatform.WebAPI/ConsoleApp/src/pages/Permission/Role/index.tsx`) — run `git show` on any of them.
  • Change coupling: app.tsx ↔ index.tsx BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:1 — `BasicPlatform.WebAPI/ConsoleApp/src/app.tsx` and `BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `e5cb6fa5` #优化多租户的配置; `8bfbd632` #升级基础库，添加微前端支持; `2693be6a` # 删除前端TableList — run `git show` on any of them.
  • Change coupling: REDACTED ↔ REDACTED REDACTED:1 — `REDACTED` and `REDACTED` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `25cfdd5c` #资源管理支持查看子应用的资源 #支持同步子应用的资源; `21ae874f` # 同步代码 (at that commit the file was still `BasicPlatform.WebAPI/Controllers/UserController.cs`); `f93ad3fa` #同步后端代码 (at that commit the file was still `BasicPlatform.WebAPI/Controllers/UserController.cs`) — run `git show` on any of them.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×4
  • Sync-over-async blocking — 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:108 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:161 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:221 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
AC2 · Forms & labels · <DatePicker> field component without a label · ×3
  • <DatePicker> field component without a label Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:319 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <DatePicker> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:331 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <DatePicker> field component without a label BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:317 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC4 · Keyboard semantics · Anchor without href · ×3
  • Anchor without href Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:159 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:403 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:161 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D1 · Cyclomatic Complexity · RulerItem.RulerItem · ×3
  • RulerItem.RulerItem::getValueDom (cyclomatic 38) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:162 — RulerItem.RulerItem::getValueDom has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • RulerItem.RulerItem::getValueDom (cyclomatic 31) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:188 — RulerItem.RulerItem::getValueDom has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • RulerItem.RulerItem::getValueDom (cyclomatic 31) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:190 — RulerItem.RulerItem::getValueDom has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · RulerItem.RulerItem · ×3
  • RulerItem.RulerItem::getValueDom (cognitive 58) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:162 — RulerItem.RulerItem::getValueDom has cognitive complexity 58 (threshold 15). Drivers by points: if/else 17 (25 pts), ternaries 7 (19 pts), boolean chains 14 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • RulerItem.RulerItem::getValueDom (cognitive 46) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:188 — RulerItem.RulerItem::getValueDom has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (24 pts), ternaries 6 (14 pts), boolean chains 8 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • RulerItem.RulerItem::getValueDom (cognitive 46) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:190 — RulerItem.RulerItem::getValueDom has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (24 pts), ternaries 6 (14 pts), boolean chains 8 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×3
  • Duplicated block (29 lines × 2) BasicPlatform.AppService/Applications/Requests/CreateApplicationRequest.cs:23 — BasicPlatform.AppService/Applications/Requests/CreateApplicationRequest.cs:23-51 | BasicPlatform.Domain/Models/Applications/Application.cs:33-61 — before extracting anything, compare `BasicPlatform.AppService/Applications/Requests/CreateApplicationRequest.cs` and `BasicPlatform.Domain/Models/Applications/Application.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (29 lines × 2) BasicPlatform.Domain/Models/Applications/Events/ApplicationCreatedEvent.cs:28 — BasicPlatform.Domain/Models/Applications/Events/ApplicationCreatedEvent.cs:28-56 | BasicPlatform.Domain/Models/Applications/Events/ApplicationUpdatedEvent.cs:23-51 — before extracting anything, compare `BasicPlatform.Domain/Models/Applications/Events/ApplicationCreatedEvent.cs` and `BasicPlatform.Domain/Models/Applications/Events/ApplicationUpdatedEvent.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (29 lines × 2) BasicPlatform.AppService/WebSettings/Models/WebSettingModel.cs:8 — BasicPlatform.AppService/WebSettings/Models/WebSettingModel.cs:8-36 | BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:11-39 — before extracting anything, compare `BasicPlatform.AppService/WebSettings/Models/WebSettingModel.cs` and `BasicPlatform.Domain/Models/WebSettings/WebSetting.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: UtilController (LCOM4 7) REDACTED:8 — UtilController's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Role (LCOM4 6) BasicPlatform.Domain/Models/Roles/Role.cs:9 — Role's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: User (LCOM4 5) BasicPlatform.Domain/Models/Users/User.cs:10 — User's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R10 · Code Duplication · Wholesale file copy (62 identical lines × 2 files) · ×3
  • Wholesale file copy (62 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/ja-JP/pages.ts:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/ja-JP/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/ja-JP/pages.ts:1 — these 2 files are line-for-line copies of one another — 62 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.
  • Wholesale file copy (62 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-CN/pages.ts:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-CN/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/zh-CN/pages.ts:1 — these 2 files are line-for-line copies of one another — 62 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.
  • Wholesale file copy (62 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-TW/pages.ts:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/zh-TW/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/zh-TW/pages.ts:1 — these 2 files are line-for-line copies of one another — 62 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.
R7 · Dead Code · Dead file (~278 LoC) · ×3
  • Dead file (~278 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx) — 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 (~278 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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
  • Dead file (~278 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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
X1 · Async correctness · Sync-over-async (deadlock risk) · ×3
  • Sync-over-async (deadlock risk) BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:108 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:161 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:221 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
AX4 · Dependency direction · Dependency-rule violation · ×2
  • Dependency-rule violation: BasicPlatform.Domain (Domain) → BasicPlatform.Infrastructure (Infrastructure) BasicPlatform.Domain/GlobalUsings.cs:10 — This Domain file depends on the Infrastructure project `BasicPlatform.Infrastructure`: it names `BasicPlatform.Infrastructure.Enums`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: BasicPlatform.Domain (Domain) → BasicPlatform.Infrastructure (Infrastructure) BasicPlatform.Domain/Models/ExternalPage.cs:35 — This Domain file depends on the Infrastructure project `BasicPlatform.Infrastructure`: it names `ExternalPageType`. The inward dependency rule is broken here. It is named again on lines 100, 138. Depend on an abstraction the inner layer owns, implemented in the outer one.
D1 · Cyclomatic Complexity · index.EditTableColumnForm (cyclomatic 17) · ×2
  • index.EditTableColumnForm (cyclomatic 17) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:14 — index.EditTableColumnForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 103, 21, 25). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
  • index.EditTableColumnForm (cyclomatic 17) BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:14 — index.EditTableColumnForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 105, 23, 27). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D12 · Dependency Hygiene · Prerelease dependency · ×2
  • Prerelease dependency: Athena.All.FreeSql — Athena.All.FreeSql resolves to 7.0.4-preview.20231218.2, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Athena.Infrastructure.FreeSql.OTel — Athena.Infrastructure.FreeSql.OTel resolves to 7.0.0-preview.20231101.2, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D2 · Cognitive Complexity · index.EditTableColumnForm (cognitive 20) · ×2
  • index.EditTableColumnForm (cognitive 20) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:14 — index.EditTableColumnForm has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 103, 21, 25). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
  • index.EditTableColumnForm (cognitive 20) BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:14 — index.EditTableColumnForm has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6 (nesting depth added 4). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 105, 23, 27). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) BasicPlatform.AppService/Users/Responses/GetUserAccessRecordPagingResponse.cs:24 — BasicPlatform.AppService/Users/Responses/GetUserAccessRecordPagingResponse.cs:24-47 | BasicPlatform.Domain/Models/Users/UserAccessRecord.cs:25-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (24 lines × 2) BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:680 — BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:680-703 | BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:743-766 — 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 `BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:680` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:11 — BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:11-30 | BasicPlatform.Domain/Models/Roles/RoleDataPermission.cs:9-28 | BasicPlatform.Domain/Models/Roles/RoleResource.cs:9-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (20 lines × 3) BasicPlatform.Domain/Models/Users/UserColumnPermission.cs:11 — BasicPlatform.Domain/Models/Users/UserColumnPermission.cs:11-30 | BasicPlatform.Domain/Models/Users/UserDataPermission.cs:9-28 | BasicPlatform.Domain/Models/Users/UserResource.cs:11-30 — 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 (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:132 — BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:132-142 | BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:317-327 — 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) BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:142 — BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:142-152 | BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:345-355 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:356` calls `Where` and `BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:153` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: CMS.Domain Apps/CMS/CMS.Domain/CMS.Domain.csproj:1 — CMS.Domain: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: CRM.Domain Apps/CRM/CRM.Domain/CRM.Domain.csproj:1 — CRM.Domain: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
R10 · Code Duplication · Wholesale file copy (61 identical lines × 2 files) · ×2
  • Wholesale file copy (61 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/global.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/global.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/global.tsx:1 — these 2 files are line-for-line copies of one another — 61 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.
  • Wholesale file copy (61 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/fa-IR/pages.ts:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/locales/fa-IR/pages.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/locales/fa-IR/pages.ts:1 — these 2 files are line-for-line copies of one another — 61 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.
R11 · Import Boundaries · Boundary violation [package · ×2
  • Boundary violation [package:third-party-deep-import] BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:21 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:21 imports antd/lib/menu/hooks/useItems, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:24 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:24 imports antd/lib/menu/hooks/useItems, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
R2 · Cyclomatic Complexity · Complex function getValueDom (cyclomatic 31, cognitive 49) · ×2
  • Complex function getValueDom (cyclomatic 31, cognitive 49) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:188 — getValueDom 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.
  • Complex function getValueDom (cyclomatic 31, cognitive 49) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:190 — getValueDom 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 ProTablePlus (cyclomatic 11, cognitive 10) · ×2
  • Complex function ProTablePlus (cyclomatic 11, cognitive 10) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50 — ProTablePlus has cyclomatic complexity 11 and cognitive complexity 10; 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.
  • Complex function ProTablePlus (cyclomatic 11, cognitive 10) BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54 — ProTablePlus has cyclomatic complexity 11 and cognitive complexity 10; 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.
R7 · Dead Code · Dead file (~324 LoC) · ×2
  • Dead file (~324 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/types/cache/mock/login.mock.cache.js — no import path from any entry point (13 application, 41 tooling, 4 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
  • Dead file (~324 LoC) BasicPlatform.WebAPI/ConsoleApp/types/cache/mock/login.mock.cache.js — no import path from any entry point (13 application, 41 tooling, 4 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
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark BasicPlatform.WebAPI/ArcoApp/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 151 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · index.ProTablePlus (cyclomatic 110) · ×1
  • index.ProTablePlus (cyclomatic 110) BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54 — index.ProTablePlus has cyclomatic complexity 110 (threshold 15). Most of this is not in the body itself: 12 of the 110 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 89, a function literal at line 174, a function literal at line 237, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.ProTablePlus (cyclomatic 100) · ×1
  • index.ProTablePlus (cyclomatic 100) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50 — index.ProTablePlus has cyclomatic complexity 100 (threshold 15). Most of this is not in the body itself: 12 of the 100 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 85, a function literal at line 168, a function literal at line 223, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.ProTableListPlus (cyclomatic 41) · ×1
  • index.ProTableListPlus (cyclomatic 41) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:18 — index.ProTableListPlus has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 4 of the 41 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 29, 28, 196, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.Authorization (cyclomatic 41) · ×1
  • index.Authorization (cyclomatic 41) BasicPlatform.WebAPI/ConsoleApp/src/components/Authorization/index.tsx:13 — index.Authorization has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 14 of the 41 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 249, 108, 169, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.Login (cyclomatic 33) · ×1
  • index.Login (cyclomatic 33) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:103 — index.Login has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (handleSubmit, a function literal at line 111, fetchUserInfo, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.TableList (cyclomatic 30) · ×1
  • index.TableList (cyclomatic 30) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx:18 — index.TableList has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 206, 82, 120, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.AdvancedSearch (cyclomatic 27) · ×1
  • index.AdvancedSearch (cyclomatic 27) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx:21 — index.AdvancedSearch has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (onClose, a function literal at line 158, a function literal at line 37, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.TableList (cyclomatic 26) · ×1
  • index.TableList (cyclomatic 26) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx:27 — index.TableList has cyclomatic complexity 26 (threshold 15). Of this number, 18 points are the body's own statements and 8 belong to 5 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cyclomatic 24) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cyclomatic 24) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/components/CreateOrUpdateForm.tsx:17 — CreateOrUpdateForm.CreateOrUpdateForm has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 60, 21, 22, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.QueryPolicyModal (cyclomatic 22) · ×1
  • index.QueryPolicyModal (cyclomatic 22) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:23 — index.QueryPolicyModal has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (okHandle, a function literal at line 28, a function literal at line 182, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.TableList (cyclomatic 22) · ×1
  • index.TableList (cyclomatic 22) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:27 — index.TableList has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · app.layout (cyclomatic 21) · ×1
  • app.layout (cyclomatic 21) BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:149 — app.layout has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 192). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cyclomatic 20) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cyclomatic 20) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx:19 — CreateOrUpdateForm.CreateOrUpdateForm has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 143, 186, 28, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ResourceRequestHandler.Handle (cyclomatic 19) · ×1
  • ResourceRequestHandler.Handle (cyclomatic 19) BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:29 — ResourceRequestHandler.Handle has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.Login (cyclomatic 19) · ×1
  • index.Login (cyclomatic 19) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:97 — index.Login has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, fetchUserInfo, fetchApiResources, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.DataPermission (cyclomatic 19) · ×1
  • index.DataPermission (cyclomatic 19) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx:13 — index.DataPermission has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · NodeForm.NodeForm (cyclomatic 19) · ×1
  • NodeForm.NodeForm (cyclomatic 19) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx:15 — NodeForm.NodeForm has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 46, 112, 21, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.TableList (cyclomatic 19) · ×1
  • index.TableList (cyclomatic 19) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:29 — index.TableList has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 210, 113, 119, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.AdvancedSearch (cyclomatic 18) · ×1
  • index.AdvancedSearch (cyclomatic 18) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:20 — index.AdvancedSearch has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 116, 24, 173, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.ApplicationColumnPermission (cyclomatic 18) · ×1
  • index.ApplicationColumnPermission (cyclomatic 18) BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationColumnPermission/index.tsx:17 — index.ApplicationColumnPermission has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 56, 79, 57, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · app.layout (cyclomatic 17) · ×1
  • app.layout (cyclomatic 17) Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:136 — app.layout has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 181). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cyclomatic 17) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cyclomatic 17) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/components/CreateOrUpdateForm.tsx:28 — CreateOrUpdateForm.CreateOrUpdateForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 46, 143, 85, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D11 · Test Reliability · Test reliability not measured · ×1
  • Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile — Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — other: measured (0 flaky); JavaScript/TypeScript (jest via `pnpm install --frozen-lockfile --ignore-scripts` in Apps/CMS/CMS.WebAPI/CMSWeb/; jest via `pnpm install --frozen-lockfile --ignore-scripts` in BasicPlatform.WebAPI/ConsoleApp/): not included — the dependency install for Apps/CMS/CMS.WebAPI/CMSWeb/ refused the committed lockfile (ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because REDACTED is absent), so the suite never ran. No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
D2 · Cognitive Complexity · index.ProTablePlus (cognitive 137) · ×1
  • index.ProTablePlus (cognitive 137) BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:54 — index.ProTablePlus has cognitive complexity 137 (threshold 15). Drivers by points: if/else 37 (69 pts), boolean chains 48, ternaries 7 (11 pts), loops 4 (5 pts), error handling 2 (4 pts) (nesting depth added 39). Most of this is not in the body itself: 10 of the 137 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 89, a function literal at line 71, renderProDescriptionsItem, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.ProTablePlus (cognitive 125) · ×1
  • index.ProTablePlus (cognitive 125) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:50 — index.ProTablePlus has cognitive complexity 125 (threshold 15). Drivers by points: if/else 35 (65 pts), boolean chains 42, ternaries 7 (11 pts), loops 4 (5 pts), error handling 1 (2 pts) (nesting depth added 36). Most of this is not in the body itself: 10 of the 125 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 85, a function literal at line 67, renderProDescriptionsItem, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.ProTableListPlus (cognitive 52) · ×1
  • index.ProTableListPlus (cognitive 52) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:18 — index.ProTableListPlus has cognitive complexity 52 (threshold 15). Drivers by points: if/else 16 (32 pts), boolean chains 14, loops 3 (4 pts), ternaries 2 (nesting depth added 17). Most of this is not in the body itself: 3 of the 52 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 29, 28, 196, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.Authorization (cognitive 46) · ×1
  • index.Authorization (cognitive 46) BasicPlatform.WebAPI/ConsoleApp/src/components/Authorization/index.tsx:13 — index.Authorization has cognitive complexity 46 (threshold 15). Drivers by points: if/else 20 (28 pts), boolean chains 18 (nesting depth added 8). Most of this is not in the body itself: 9 of the 46 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 249, 108, 169, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · UserController.GetResourcesAsync (cognitive 38) · ×1
  • UserController.GetResourcesAsync (cognitive 38) REDACTED:241 — UserController.GetResourcesAsync has cognitive complexity 38 (threshold 15). Of this number, 36 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · app.layout (cognitive 38) · ×1
  • app.layout (cognitive 38) BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:149 — app.layout has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 7 (16 pts), if/else 8 (13 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 16). Most of this is not in the body itself: 7 of the 38 points are its own statements and the rest belongs to one function literal inside it that branches (line 192). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.AdvancedSearch (cognitive 38) · ×1
  • index.AdvancedSearch (cognitive 38) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx:21 — index.AdvancedSearch has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 5 (11 pts), boolean chains 9 (nesting depth added 15). Most of this is not in the body itself: 5 of the 38 points are its own statements and the rest belongs to 5 function items inside it that branch (onClose, a function literal at line 158, a function literal at line 37, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.TableList (cognitive 34) · ×1
  • index.TableList (cognitive 34) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx:18 — index.TableList has cognitive complexity 34 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 12 of the 34 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 206, 82, 120, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · app.layout (cognitive 30) · ×1
  • app.layout (cognitive 30) Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:136 — app.layout has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 6 (11 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 12). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 181). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ResourceRequestHandler.Handle (cognitive 29) · ×1
  • ResourceRequestHandler.Handle (cognitive 29) BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:29 — ResourceRequestHandler.Handle has cognitive complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 5 function literals inside it that branch. 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 · index.AdvancedSearch (cognitive 24) · ×1
  • index.AdvancedSearch (cognitive 24) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:20 — index.AdvancedSearch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 8, loops 2 (5 pts) (nesting depth added 8). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 116, 24, 173, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · NodeForm.NodeForm (cognitive 24) · ×1
  • NodeForm.NodeForm (cognitive 24) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx:15 — NodeForm.NodeForm has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 3 (6 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 46, 112, 21, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.TableList (cognitive 24) · ×1
  • index.TableList (cognitive 24) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:27 — index.TableList has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 185, 104, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cognitive 23) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cognitive 23) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/components/CreateOrUpdateForm.tsx:17 — CreateOrUpdateForm.CreateOrUpdateForm has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 9, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 60, 21, 22, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · permission.setupPermissionGuard (cognitive 22) · ×1
  • permission.setupPermissionGuard (cognitive 22) BasicPlatform.WebAPI/ArcoApp/src/router/guard/permission.ts:9 — permission.setupPermissionGuard has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 8). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 10). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.ApplicationColumnPermission (cognitive 22) · ×1
  • index.ApplicationColumnPermission (cognitive 22) BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationColumnPermission/index.tsx:17 — index.ApplicationColumnPermission has cognitive complexity 22 (threshold 15). Drivers by points: if/else 3 (6 pts), loops 3 (6 pts), ternaries 6, boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 22 points belong to 7 function literals inside it that branch (lines 79, 56, 23, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.TableList (cognitive 22) · ×1
  • index.TableList (cognitive 22) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:29 — index.TableList has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 210, 113, 119, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.Login · ×1
  • index.Login::handleSubmit (cognitive 22) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:157 — index.Login::handleSubmit has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (4 pts), boolean chains 3, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.ApplicationDataPermission (cognitive 20) · ×1
  • index.ApplicationDataPermission (cognitive 20) BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationDataPermission/index.tsx:11 — index.ApplicationDataPermission has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (8 pts), boolean chains 6, if/else 3 (6 pts) (nesting depth added 7). None of this is in the body itself: all 20 points belong to 5 function literals inside it that branch (lines 34, 64, 17, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cognitive 20) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cognitive 20) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx:19 — CreateOrUpdateForm.CreateOrUpdateForm has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 5). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 143, 28, 77, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cognitive 19) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cognitive 19) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/components/CreateOrUpdateForm.tsx:28 — CreateOrUpdateForm.CreateOrUpdateForm has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 6 (7 pts), boolean chains 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 46, 143, 85, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.Login (cognitive 18) · ×1
  • index.Login (cognitive 18) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:97 — index.Login has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, fetchUserInfo, fetchApiResources, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.DataPermission (cognitive 18) · ×1
  • index.DataPermission (cognitive 18) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx:13 — index.DataPermission has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (6 pts), ternaries 1 (nesting depth added 1). Of this number, 11 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · index.LoginRedirect (cognitive 18) · ×1
  • index.LoginRedirect (cognitive 18) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/LoginRedirect/index.tsx:8 — index.LoginRedirect has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 1 (4 pts), boolean chains 2, error handling 1 (nesting depth added 7). None of this is in the body itself: all 18 points belong to 3 function literals inside it that branch (lines 13, 12, 53). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.QueryPolicyModal · ×1
  • index.QueryPolicyModal::okHandle (cognitive 16) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:48 — index.QueryPolicyModal::okHandle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreateOrUpdateForm.CreateOrUpdateForm (cognitive 16) · ×1
  • CreateOrUpdateForm.CreateOrUpdateForm (cognitive 16) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/components/CreateOrUpdateForm.tsx:25 — CreateOrUpdateForm.CreateOrUpdateForm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 41, 145, 154, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: UserQueryService BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs — ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 9 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: index.tsx → IUserQueryService.cs, index.tsx, index.tsx BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx — `BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx` changes together with 3 other files — `BasicPlatform.AppService/Users/IUserQueryService.cs`, `BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Organization/index.tsx`, `BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication · Duplicated block (56 lines × 2) · ×1
  • Duplicated block (56 lines × 2) Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs:21 — Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs:21-76 | Apps/CMS/CMS.Domain/Models/Articles/Article.cs:25-80 — before extracting anything, compare `Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs` and `Apps/CMS/CMS.Domain/Models/Articles/Article.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Apps/CMS/CMS.Domain/Models/Articles/Article.cs:24` calls `MaxLength` and `Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs:16` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×1
  • Duplicated block (54 lines × 2) BasicPlatform.AppService/ExternalPages/Models/ExternalPageModel.cs:8 — BasicPlatform.AppService/ExternalPages/Models/ExternalPageModel.cs:8-61 | BasicPlatform.Domain/Models/ExternalPage.cs:11-64 — before extracting anything, compare `BasicPlatform.AppService/ExternalPages/Models/ExternalPageModel.cs` and `BasicPlatform.Domain/Models/ExternalPage.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×1
  • Duplicated block (50 lines × 2) BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:8 — BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:8-57 | BasicPlatform.Domain/Models/Tenants/Events/TenantUpdatedEvent.cs:8-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (43 lines × 3) · ×1
  • Duplicated block (43 lines × 3) Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:46 — Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:46-88 | REDACTED:58-100 | REDACTED:147-189 — before extracting anything, compare `Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs` and `REDACTED` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:46` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1
  • Duplicated block (39 lines × 2) Apps/CMS/CMS.Domain/Models/Articles/Article.cs:11 — Apps/CMS/CMS.Domain/Models/Articles/Article.cs:11-49 | Apps/CMS/CMS.Domain/Models/Articles/Events/ArticleCreatedEvent.cs:10-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) Apps/App.Infrastructure/Messaging/Requests/CreateUserRequest.cs:23 — Apps/App.Infrastructure/Messaging/Requests/CreateUserRequest.cs:23-59 | Apps/App.Infrastructure/Messaging/Requests/UpdateUserRequest.cs:22-58 — before extracting anything, compare `Apps/App.Infrastructure/Messaging/Requests/CreateUserRequest.cs` and `Apps/App.Infrastructure/Messaging/Requests/UpdateUserRequest.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (36 lines × 3) · ×1
  • Duplicated block (36 lines × 3) BasicPlatform.AppService/Roles/Models/RoleColumnPermissionModel.cs:16 — BasicPlatform.AppService/Roles/Models/RoleColumnPermissionModel.cs:16-51 | BasicPlatform.AppService/Users/Models/UserColumnPermissionModel.cs:16-51 | BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:35-70 — before extracting anything, compare `BasicPlatform.AppService/Roles/Models/RoleColumnPermissionModel.cs` and `BasicPlatform.AppService/Users/Models/UserColumnPermissionModel.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (34–35 lines × 2) · ×1
  • Duplicated block (34–35 lines × 2) REDACTED:283 — REDACTED:283-316 | REDACTED:370-404 — 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 `REDACTED:283` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs:8 — Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs:8-41 | Apps/CMS/CMS.AppService/Articles/Requests/CreateArticleRequest.cs:8-41 — before extracting anything, compare `Apps/CMS/CMS.AppService/Articles/Models/ArticleModel.cs` and `Apps/CMS/CMS.AppService/Articles/Requests/CreateArticleRequest.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) BasicPlatform.Domain/Models/Roles/RoleGroup.cs:12 — BasicPlatform.Domain/Models/Roles/RoleGroup.cs:12-41 | BasicPlatform.Domain/Models/Users/UserGroup.cs:10-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:32 — BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:32-59 | BasicPlatform.Domain/Models/Users/UserColumnPermission.cs:32-59 — 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 (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) Apps/App.Infrastructure/Services/Impls/DefaultCommonService.cs:35 — Apps/App.Infrastructure/Services/Impls/DefaultCommonService.cs:35-65 | BasicPlatform.AppService.FreeSql/Commons/CommonService.cs:43-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Apps/App.Infrastructure/Services/Impls/DefaultCommonService.cs:35` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) BasicPlatform.Domain/Models/Roles/RoleDataPermission.cs:30 — BasicPlatform.Domain/Models/Roles/RoleDataPermission.cs:30-56 | BasicPlatform.Domain/Models/Users/UserDataPermission.cs:30-56 — 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 (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) BasicPlatform.ProcessManager/RoleProcessManager.cs:38 — BasicPlatform.ProcessManager/RoleProcessManager.cs:38-63 | BasicPlatform.ProcessManager/UserProcessManager.cs:39-64 — 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 `BasicPlatform.ProcessManager/RoleProcessManager.cs:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25 lines × 4) · ×1
  • Duplicated block (25 lines × 4) BasicPlatform.AppService/Roles/Models/RoleColumnPermissionModel.cs:16 — BasicPlatform.AppService/Roles/Models/RoleColumnPermissionModel.cs:16-40 | BasicPlatform.AppService/Users/Models/UserColumnPermissionModel.cs:16-40 | BasicPlatform.Domain/Models/Roles/RoleColumnPermission.cs:35-59 | BasicPlatform.Domain/Models/Users/UserColumnPermission.cs:35-59 — before extracting anything, compare `BasicPlatform.AppService/Roles/Models/RoleColumnPermissionModel.cs` and `BasicPlatform.AppService/Users/Models/UserColumnPermissionModel.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) BasicPlatform.AppService/Users/Models/UserCustomColumnModel.cs:11 — BasicPlatform.AppService/Users/Models/UserCustomColumnModel.cs:11-35 | BasicPlatform.Domain/Models/Users/UserCustomColumn.cs:36-60 — before extracting anything, compare `BasicPlatform.AppService/Users/Models/UserCustomColumnModel.cs` and `BasicPlatform.Domain/Models/Users/UserCustomColumn.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:23 — Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:23-44 | REDACTED:27-48 — before extracting anything, compare `Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs` and `REDACTED` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:56 — BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:56-71 | BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:89-104 — 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 `BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `notification` to `RoleDataPermissionAssignedEvent` in one and `RoleColumnPermissionAssignedEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:116 — BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:116-131 | BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:247-263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageQueryService.cs:116` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `entities` to `IList<ExternalPage>` in one and `IList<Organization>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) BasicPlatform.AppService.FreeSql/Organizations/OrganizationRequestHandler.cs:47 — BasicPlatform.AppService.FreeSql/Organizations/OrganizationRequestHandler.cs:47-63 | BasicPlatform.AppService.FreeSql/Organizations/OrganizationRequestHandler.cs:95-111 — 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 `BasicPlatform.AppService.FreeSql/Organizations/OrganizationRequestHandler.cs:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `CreateOrganizationRequest` in one and `UpdateOrganizationRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (15–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) BasicPlatform.WebAPI/Controllers/Developer/ResourceController.cs:66 — BasicPlatform.WebAPI/Controllers/Developer/ResourceController.cs:66-80 | REDACTED:269-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BasicPlatform.WebAPI/Controllers/Developer/ResourceController.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:178 — BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:178-190 | BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:783-795 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:113 — BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:113-119 | BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:162-168 — 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 `BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (45 lines × 2) · ×1
  • Duplicated block (45 lines × 2) REDACTED:21 — REDACTED:21-65 | REDACTED:24-68 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) BasicPlatform.AppService/Roles/Models/RoleDataPermissionModel.cs:62 — BasicPlatform.AppService/Roles/Models/RoleDataPermissionModel.cs:62-70 | BasicPlatform.AppService/Users/Models/UserDataPermissionModel.cs:60-68 — before extracting anything, compare `BasicPlatform.AppService/Roles/Models/RoleDataPermissionModel.cs` and `BasicPlatform.AppService/Users/Models/UserDataPermissionModel.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net7.0 REDACTED:4 — REDACTED declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half measured 0.2%; the JavaScript/TypeScript half could not be measured — the dependency install for Apps/CMS/CMS.WebAPI/CMSWeb/ refused the committed lockfile (ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because REDACTED is absent), so the suite never ran. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM4 · Rich vs anemic model · Anemic entity · ×1
  • Anemic entity: Customer Apps/CRM/CRM.Domain/Customers/Customer.cs:8 — `Customer` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience — The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
R10 · Code Duplication · Forked directory tree (111 identical files, ~5746 lines × 2 trees) · ×1
  • Forked directory tree (111 identical files, ~5746 lines × 2 trees) Apps/CMS/CMS.WebAPI/CMSWeb/config/oneapi.json:1 — Apps/CMS/CMS.WebAPI/CMSWeb/ and BasicPlatform.WebAPI/ConsoleApp/ are near-verbatim copies of each other: 111 files are byte-identical under the same relative paths (~5746 lines; the trees hold 176 and 250 files). That is one structural fact, not 111 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (126 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (126 clone groups) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:5 — 126 duplicated blocks under the repository root have copies in at least two of the sibling directories Apps, BasicPlatform.WebAPI — 81 of them are reported below, and 45 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 126 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 126 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 126 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (23 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (23 clone groups) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:35 — 23 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ have copies in at least two of the sibling directories ExternalPage, Organization, Position, Role, ServerInfo, Tenant (+2 more sibling(s) not listed) — 18 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 23 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (14 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (14 clone groups) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx:54 — 14 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/pages/ have copies in at least two of the sibling directories Dashboard, Developer, System — 10 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 9 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 9 sibling directories (7 clone groups) BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:27 — 7 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/components/ have copies in at least two of the sibling directories AdvancedSearch, ApplicationAuthorization, ApplicationColumnPermission, ApplicationDataPermission, ColumnPermission, DataPermission (+3 more sibling(s) not listed) — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (7 clone groups) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/components/ViewModal.tsx:66 — 7 duplicated blocks under BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/ have copies in at least two of the sibling directories Application, EventStorage, EventTracking, Log — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (345 identical lines × 2 files) · ×1
  • Wholesale file copy (345 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:5 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:5 · BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:5 — these 2 files are line-for-line copies of one another — 345 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 (297 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (297 matched lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:60 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:60 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:60 — the two spans are one implementation copied and then locally edited — 1254 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 · Wholesale file copy (276 identical lines × 2 files) · ×1
  • Wholesale file copy (276 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/types/cache/mock/login.mock.cache.js:1 — Apps/CMS/CMS.WebAPI/CMSWeb/types/cache/mock/login.mock.cache.js:1 · BasicPlatform.WebAPI/ConsoleApp/types/cache/mock/login.mock.cache.js:1 — these 2 files are line-for-line copies of one another — 276 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 · Wholesale file copy (255 identical lines × 3 files) · ×1
  • Wholesale file copy (255 identical lines × 3 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:1 — these 3 files are line-for-line copies of one another — 255 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 (238 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (238 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:35 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:35 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:43 — the two spans are one implementation copied and then locally edited — 1162 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 · Wholesale file copy (183 identical lines × 2 files) · ×1
  • Wholesale file copy (183 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx:1 — these 2 files are line-for-line copies of one another — 183 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 (176 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (176 matched lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts:46 — Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts:46 · BasicPlatform.WebAPI/ConsoleApp/src/utils/utils.ts:42 — the two spans are one implementation copied and then locally edited — 1160 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 (171 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (171 matched lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:56 — Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:56 · BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:35 — the two spans are one implementation copied and then locally edited — 944 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 · Wholesale file copy (165 identical lines × 2 files) · ×1
  • Wholesale file copy (165 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx:1 — these 2 files are line-for-line copies of one another — 165 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 (164 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (164 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:97 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx:97 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx:113 — the two spans are one implementation copied and then locally edited — 846 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 · Wholesale file copy (156 identical lines × 2 files) · ×1
  • Wholesale file copy (156 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx:1 — these 2 files are line-for-line copies of one another — 156 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 · Wholesale file copy (134 identical lines × 2 files) · ×1
  • Wholesale file copy (134 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:1 — these 2 files are line-for-line copies of one another — 134 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 · Wholesale file copy (133 identical lines × 2 files) · ×1
  • Wholesale file copy (133 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:1 — these 2 files are line-for-line copies of one another — 133 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 (133 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (133 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Position/index.tsx:17 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Position/index.tsx:17 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx:33 — the two spans are one implementation copied and then locally edited — 705 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 · Wholesale file copy (104 identical lines × 2 files) · ×1
  • Wholesale file copy (104 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/requestErrorConfig.ts:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/requestErrorConfig.ts:1 · BasicPlatform.WebAPI/ConsoleApp/src/requestErrorConfig.ts:1 — these 2 files are line-for-line copies of one another — 104 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 · Wholesale file copy (102 identical lines × 2 files) · ×1
  • Wholesale file copy (102 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Welcome.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Welcome.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/Welcome.tsx:1 — these 2 files are line-for-line copies of one another — 102 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 · Wholesale file copy (95 identical lines × 2 files) · ×1
  • Wholesale file copy (95 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/pet.ts:3 — Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/pet.ts:3 · BasicPlatform.WebAPI/ConsoleApp/src/services/swagger/pet.ts:3 — these 2 files are line-for-line copies of one another — 95 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 · Wholesale file copy (90 identical lines × 4 files) · ×1
  • Wholesale file copy (90 identical lines × 4 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx:1 · Apps/CMS/CMS.WebAPI/CMSWeb/src/components/UserModal/components/TransferForm.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/OrgModal/components/TransferForm.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/components/UserModal/components/TransferForm.tsx:1 — these 4 files are line-for-line copies of one another — 90 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 (85 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (85 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateRootNodeForm.tsx:8 — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateRootNodeForm.tsx:8 · BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx:11 — the two spans are one implementation copied and then locally edited — 552 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 (84 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (84 matched lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:27 — BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:27 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx:21 — the two spans are one implementation copied and then locally edited — 430 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 · Wholesale file copy (82 identical lines × 2 files) · ×1
  • Wholesale file copy (82 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Dashboard/Workbench/index.tsx:1 · BasicPlatform.WebAPI/ConsoleApp/src/pages/Dashboard/Workbench/index.tsx:1 — these 2 files are line-for-line copies of one another — 82 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 (77 lines × 2 locations) · ×1
  • Duplicated block (77 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:44 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:44 · Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx:51 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Wholesale file copy (74 identical lines × 2 files) · ×1
  • Wholesale file copy (74 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/AvatarDropdown.tsx:2 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/RightContent/AvatarDropdown.tsx:2 · BasicPlatform.WebAPI/ConsoleApp/src/components/RightContent/AvatarDropdown.tsx:2 — these 2 files are line-for-line copies of one another — 74 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 (74 lines × 2 locations) · ×1
  • Duplicated block (74 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:47 — BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx:47 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx:54 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (71 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (71 matched lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/services/ant-design-pro/api.ts:7 — Apps/CMS/CMS.WebAPI/CMSWeb/src/services/ant-design-pro/api.ts:7 · BasicPlatform.WebAPI/ConsoleApp/src/services/ant-design-pro/api.ts:6 — the two spans are one implementation copied and then locally edited — 485 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 (68 lines × 2 locations) · ×1
  • Duplicated block (68 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/ExternalPages/index.tsx:10 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/ExternalPages/index.tsx:10 · BasicPlatform.WebAPI/ConsoleApp/src/pages/ExternalPages/index.tsx:10 — 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 (66 lines × 2 locations) · ×1
  • Duplicated block (66 lines × 2 locations) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/ColumnPermissionForm.tsx:7 — BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/ColumnPermissionForm.tsx:7 · BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/components/ColumnPermissionForm.tsx:8 — 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 · Wholesale file copy (64 identical lines × 2 files) · ×1
  • Wholesale file copy (64 identical lines × 2 files) Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/user.ts:3 — Apps/CMS/CMS.WebAPI/CMSWeb/src/services/swagger/user.ts:3 · BasicPlatform.WebAPI/ConsoleApp/src/services/swagger/user.ts:3 — these 2 files are line-for-line copies of one another — 64 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 (62 lines × 2 locations) · ×1
  • Duplicated block (62 lines × 2 locations) Apps/CMS/CMS.WebAPI/CMSWeb/src/signalr/index.ts:23 — Apps/CMS/CMS.WebAPI/CMSWeb/src/signalr/index.ts:23 · BasicPlatform.WebAPI/ConsoleApp/src/signalr/index.ts:23 — 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.
R2 · Cyclomatic Complexity · Complex function fetch (cyclomatic 61, cognitive 105) · ×1
  • Complex function fetch (cyclomatic 61, cognitive 105) BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:89 — fetch has cyclomatic complexity 61 and cognitive complexity 105; 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 fetch (cyclomatic 56, cognitive 98) · ×1
  • Complex function fetch (cyclomatic 56, cognitive 98) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:85 — fetch has cyclomatic complexity 56 and cognitive complexity 98; 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 fetchColumns (cyclomatic 56, cognitive 94) · ×1
  • Complex function fetchColumns (cyclomatic 56, cognitive 94) BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue:218 — fetchColumns has cyclomatic complexity 56 and cognitive complexity 94; 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 getValueDom (cyclomatic 38, cognitive 58) · ×1
  • Complex function getValueDom (cyclomatic 38, cognitive 58) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:162 — getValueDom has cyclomatic complexity 38 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 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 fetch (cyclomatic 33, cognitive 62) · ×1
  • Complex function fetch (cyclomatic 33, cognitive 62) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:29 — fetch has cyclomatic complexity 33 and cognitive complexity 62; 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 errorHandler (cyclomatic 18, cognitive 20) · ×1
  • Complex function errorHandler (cyclomatic 18, cognitive 20) Apps/CMS/CMS.WebAPI/CMSWeb/src/requestErrorConfig.ts:46 — errorHandler has cyclomatic complexity 18 and cognitive complexity 20; 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 errorHandler (cyclomatic 17, cognitive 16) · ×1
  • Complex function errorHandler (cyclomatic 17, cognitive 16) BasicPlatform.WebAPI/ConsoleApp/src/requestErrorConfig.ts:45 — errorHandler has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function request (cyclomatic 15, cognitive 31) · ×1
  • Complex function request (cyclomatic 15, cognitive 31) BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:192 — request has cyclomatic complexity 15 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 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 request (cyclomatic 12, cognitive 24) · ×1
  • Complex function request (cyclomatic 12, cognitive 24) Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:181 — request has cyclomatic complexity 12 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 22) · ×1
  • Complex function (anonymous) (cyclomatic 12, cognitive 22) BasicPlatform.WebAPI/ArcoApp/src/router/guard/permission.ts:10 — (anonymous) has cyclomatic complexity 12 and cognitive complexity 22; 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 handleSubmit (cyclomatic 12, cognitive 22) · ×1
  • Complex function handleSubmit (cyclomatic 12, cognitive 22) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:157 — handleSubmit has cyclomatic complexity 12 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 17) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 17) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx:46 — (anonymous) has cyclomatic complexity 11 and cognitive complexity 17; 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 okHandle (cyclomatic 11, cognitive 16) · ×1
  • Complex function okHandle (cyclomatic 11, cognitive 16) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx:48 — okHandle has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 · BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue · ×1
  • BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue: 558 lines of code BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue:1 — BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue has 558 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 · BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx · ×1
  • BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx: 547 lines of code BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx:1 — BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx has 547 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 · BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx · ×1
  • BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx: 523 lines of code BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx:1 — BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx has 523 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 · Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx · ×1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx: 521 lines of code Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx has 521 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 · Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx · ×1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx: 511 lines of code Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx has 511 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 · BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx · ×1
  • BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx: 509 lines of code BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx:1 — BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx has 509 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 · BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx · ×1
  • BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx: 471 lines of code BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx:1 — BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx has 471 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 · Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx · ×1
  • Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx: 404 lines of code Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx:1 — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx has 404 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 (~565 LoC) · ×1
  • Dead file (~565 LoC) BasicPlatform.WebAPI/ArcoApp/src/components/pro-table/index.vue — no import path from any entry point (13 application, 41 tooling, 4 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 (~555 LoC) · ×1
  • Dead file (~555 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 10 in-repo import(s) from 10 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Application/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventStorage/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx and 7 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 (~529 LoC) · ×1
  • Dead file (~529 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/Content/Article/index.tsx) — 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 (~527 LoC) · ×1
  • Dead file (~527 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx) — 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 (~515 LoC) · ×1
  • Dead file (~515 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx) — 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 (~513 LoC) · ×1
  • Dead file (~513 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx) — 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 (~488 LoC) · ×1
  • Dead file (~488 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~418 LoC) · ×1
  • Dead file (~418 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Login/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~395 LoC) · ×1
  • Dead file (~395 LoC) BasicPlatform.WebAPI/ConsoleApp/src/app.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~392 LoC) · ×1
  • Dead file (~392 LoC) BasicPlatform.WebAPI/ConsoleApp/src/utils/utils.ts — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 37 in-repo import(s) from 37 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/access.ts, BasicPlatform.WebAPI/ConsoleApp/src/app.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx and 34 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 (~384 LoC) · ×1
  • Dead file (~384 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/User/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~376 LoC) · ×1
  • Dead file (~376 LoC) BasicPlatform.WebAPI/ArcoApp/src/types/global.ts — no import path from any entry point (13 application, 41 tooling, 4 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 (~356 LoC) · ×1
  • Dead file (~356 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~355 LoC) · ×1
  • Dead file (~355 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~354 LoC) · ×1
  • Dead file (~354 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/components/CreateOrUpdateForm.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Tenant/index.tsx) — 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 (~340 LoC) · ×1
  • Dead file (~340 LoC) BasicPlatform.WebAPI/ArcoApp/src/utils/utils.ts — no import path from any entry point (13 application, 41 tooling, 4 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 (~334 LoC) · ×1
  • Dead file (~334 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~320 LoC) · ×1
  • Dead file (~320 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx) — 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 (~317 LoC) · ×1
  • Dead file (~317 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/SearchModal.tsx) — 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 (~315 LoC) · ×1
  • Dead file (~315 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx and 5 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 (~314 LoC) · ×1
  • Dead file (~314 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/Authorization/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationAuthorization/index.tsx) — 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 (~308 LoC) · ×1
  • Dead file (~308 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/System/ExternalPage/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~296 LoC) · ×1
  • Dead file (~296 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx) — 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 (~290 LoC) · ×1
  • Dead file (~290 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx) — 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 (~287 LoC) · ×1
  • Dead file (~287 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/components/ColumnConfig.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationColumnPermission/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx) — 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 (~286 LoC) · ×1
  • Dead file (~286 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx) — 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 (~275 LoC) · ×1
  • Dead file (~275 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/Dashboard/Workbench/components/DemoDecompositionTreeGraph.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~269 LoC) · ×1
  • Dead file (~269 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/index.tsx) — 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 (~266 LoC) · ×1
  • Dead file (~266 LoC) BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/components/ApplicationDataPermission/index.tsx) — 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 (~250 LoC) · ×1
  • Dead file (~250 LoC) BasicPlatform.WebAPI/ArcoApp/src/components/navbar/index.vue — no import path from any entry point (13 application, 41 tooling, 4 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 (~238 LoC) · ×1
  • Dead file (~238 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/components/ViewModal.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/Log/index.tsx) — 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 (~215 LoC) · ×1
  • Dead file (~215 LoC) BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/NodeForm.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx) — 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 (~210 LoC) · ×1
  • Dead file (~210 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 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 (~208 LoC) · ×1
  • Dead file (~208 LoC) Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx — no import path from any entry point (13 application, 41 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unlisted import '*.vue' · ×1
  • Unlisted import '*.vue' BasicPlatform.WebAPI/ArcoApp/src/router/routes/types.ts:6 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
R8 · Dependency Hygiene · Unused dependency '@ant-design/colors' · ×1
  • Unused dependency '@ant-design/colors' — Declared in REDACTED 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 '@umijs/fabric' · ×1
  • Unused dependency '@umijs/fabric' — Declared in REDACTED 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 '@umijs/route-utils' · ×1
  • Unused dependency '@umijs/route-utils' — Declared in REDACTED 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.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 221 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×65
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Users/UserRequestHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.WebAPI/Services/Impls/DefaultSubApplicationService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Commons/DefaultDataPermissionService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.Domain/Models/Users/User.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Organizations/OrganizationQueryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Roles/RoleQueryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.Domain/Models/Tenants/Tenant.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Roles/RoleRequestHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Applications/ApplicationQueryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.WebAPI/Controllers/System/RoleController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Apps/App.Infrastructure/Services/Impls/DefaultUserService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Resources/ResourceRequestHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.WebAPI/Controllers/System/TenantController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/Tenants/TenantRequestHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.Domain.EventHandler/CacheEventHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.Domain/Models/Applications/Application.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.WebAPI/Controllers/System/OrganizationController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Apps/CMS/CMS.Domain/Models/Articles/Article.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService/Users/IUserQueryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file BasicPlatform.AppService.FreeSql/ExternalPages/ExternalPageRequestHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 40 more in this group — see findings.md.
D12 · Dependency Hygiene · Deprecated · ×55
  • Deprecated: registry.npmmirror.com/@babel/plugin-proposal-class-properties REDACTED:1711 — registry.npmmirror.com/@babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/@floating-ui/react-dom-interactions REDACTED:3979 — registry.npmmirror.com/@floating-ui/react-dom-interactions 0.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package renamed to @floating-ui/react". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/@formatjs/intl-unified-numberformat REDACTED:4081 — registry.npmmirror.com/@formatjs/intl-unified-numberformat 3.3.7 is resolved in REDACTED and is marked deprecated by its publisher: "We have renamed the package to @formatjs/intl-numberformat". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/@formatjs/intl-utils REDACTED:4090 — registry.npmmirror.com/@formatjs/intl-utils 2.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/@stylelint/postcss-css-in-js REDACTED:4749 — registry.npmmirror.com/@stylelint/postcss-css-in-js 0.37.3 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/@stylelint/postcss-css-in-js REDACTED:4766 — registry.npmmirror.com/@stylelint/postcss-css-in-js 0.38.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/@stylelint/postcss-markdown REDACTED:4783 — registry.npmmirror.com/@stylelint/postcss-markdown 0.36.2 is resolved in REDACTED and is marked deprecated by its publisher: "Use the original unforked package instead: postcss-markdown". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/abab REDACTED:7012 — registry.npmmirror.com/abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/core-js REDACTED:8850 — registry.npmmirror.com/core-js 1.2.7 is resolved in REDACTED and is marked deprecated by its publisher: "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/core-js REDACTED:8857 — registry.npmmirror.com/core-js 2.6.12 is resolved in REDACTED and is marked deprecated by its publisher: "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/date-format REDACTED:9303 — registry.npmmirror.com/date-format 0.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "0.x is no longer supported. Please upgrade to 4.x or higher.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/domexception REDACTED:9734 — registry.npmmirror.com/domexception 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/flatten REDACTED:11410 — registry.npmmirror.com/flatten 1.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "flatten is deprecated in favor of utility frameworks such as lodash.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/har-validator REDACTED:11984 — registry.npmmirror.com/har-validator 5.1.5 is resolved in REDACTED and is marked deprecated by its publisher: "this library is no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/intl-messageformat-parser REDACTED:12559 — registry.npmmirror.com/intl-messageformat-parser 3.6.4 is resolved in REDACTED and is marked deprecated by its publisher: "We've written a new parser that's 6x faster and is backwards compatible. Please use @formatjs/icu-messageformat-parser". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/log4js REDACTED:14370 — registry.npmmirror.com/log4js 1.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "1.x is no longer supported. Please upgrade to 6.x or higher.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/querystring REDACTED:16908 — registry.npmmirror.com/querystring 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "The querystring API is considered Legacy. new code should use the URLSearchParams API instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/react-native-swipeout REDACTED:18473 — registry.npmmirror.com/react-native-swipeout 2.3.6 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Use at your own risk or consider using https://github.com/software-mansion/react-native-gesture-handler". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/react-router-redux REDACTED:18636 — registry.npmmirror.com/react-router-redux 5.0.0-alpha.9 is resolved in REDACTED and is marked deprecated by its publisher: "This project is no longer maintained.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/request REDACTED:19029 — registry.npmmirror.com/request 2.88.2 is resolved in REDACTED and is marked deprecated by its publisher: "request has been deprecated, see https://github.com/request/request/issues/3142". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/stable REDACTED:20113 — registry.npmmirror.com/stable 0.1.8 is resolved in REDACTED and is marked deprecated by its publisher: "Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/streamroller REDACTED:20185 — registry.npmmirror.com/streamroller 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "0.x is no longer supported. Please upgrade to 3.x or higher.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: registry.npmmirror.com/uuid REDACTED:21769 — registry.npmmirror.com/uuid 3.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @types/vfile-message REDACTED:1064 — @types/vfile-message 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: resolve-url REDACTED:7082 — resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • + 30 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate BasicPlatform.AppService/Roles/Models/RoleDataPermissionModel.cs:63 — `_policies == null && !string.IsNullOrEmpty(Policy)` appears character-identically in 2 files — BasicPlatform.AppService/Roles/Models/RoleDataPermissionModel.cs, BasicPlatform.AppService/Users/Models/UserDataPermissionModel.cs. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx:125 — `!filter.key || !filter.operator || !filter.value` appears character-identically in 3 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx:190 — `!value || getFieldValue('newPassword') === value` appears character-identically in 4 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Center/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/pages/User/Settings/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Center/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Settings/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:476 — `!x.hideInDescriptions && x.dataIndex !== 'option'` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:184 — `(await initialState?.fetchApiResources?.()) || []` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx, BasicPlatform.WebAPI/ConsoleApp/src/app.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx:195 — `(await initialState?.fetchExternalPages?.()) || []` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/app.tsx, BasicPlatform.WebAPI/ConsoleApp/src/app.tsx. 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 REDACTED:3 — `APP_NAV_THEME_KEY || 'basic_platform_nav_theme'` appears character-identically in 2 files — REDACTED, REDACTED. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/token.ts:5 — `APP_SESSION_CODE_KEY || 'basic_platform_session_code'` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/token.ts, BasicPlatform.WebAPI/ConsoleApp/src/utils/token.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:70 — `cur.groupDescription && !group.description` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/access.ts:14 — `currentUser && currentUser.userName === 'root'` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/access.ts, BasicPlatform.WebAPI/ConsoleApp/src/access.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx:133 — `dataSources.length > 0 && currentSegmented !== ''` appears character-identically in 2 files — BasicPlatform.WebAPI/ConsoleApp/src/components/ColumnPermission/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx:121 — `find.fixed !== item.fixed && find.fixed !== undefined` appears character-identically in 3 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:149 — `find.hideInDescriptions || item.hideInDescriptions` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx. 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 BasicPlatform.WebAPI/ConsoleApp/src/app.tsx:167 — `initialState?.webSetting?.logo || 'https://cdn.gzwjz.com/FmzrX15jYA03KMVfbgMJnk-P6WGl.png'` appears character-identically in 2 files — BasicPlatform.WebAPI/ConsoleApp/src/app.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/User/Login/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx:25 — `item.fixed !== 'left' && item.fixed !== 'right'` appears character-identically in 5 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/EditTableColumnForm/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTableListPlus/index.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/EditTableColumnForm/index.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:192 — `item.operator !== undefined && item.operator === 'in'` appears character-identically in 3 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx:146 — `item.title!.indexOf(inputValue) !== -1 || item.description!.indexOf(inputValue) !== -1` appears character-identically in 4 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/UserModal/components/TransferForm.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/OrgModal/components/TransferForm.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/UserModal/components/TransferForm.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:299 — `item.value === '' || item.value === undefined || item.value?.split(',')?.length !== 2` appears character-identically in 3 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx:231 — `item.value === undefined || item.value === ''` appears character-identically in 3 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/AdvancedSearch/components/RulerItem.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/AdvancedSearch/components/RulerItem.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/DataPermission/components/QueryPolicyModal/components/RulerItem.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts:76 — `modules === undefined || modules === null || modules?.length === 0` appears character-identically in 3 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/utils/utils.ts, BasicPlatform.WebAPI/ArcoApp/src/utils/utils.ts, BasicPlatform.WebAPI/ConsoleApp/src/utils/utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Apps/CMS/CMS.WebAPI/CMSWeb/mock/user.ts:123 — `password === 'ant.design' && username === 'admin'` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/mock/user.ts, BasicPlatform.WebAPI/ConsoleApp/mock/user.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Apps/CMS/CMS.WebAPI/CMSWeb/mock/user.ts:132 — `password === 'ant.design' && username === 'user'` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/mock/user.ts, BasicPlatform.WebAPI/ConsoleApp/mock/user.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx:121 — `props.mode === 'single' && nextTargetKeys.length > 1` appears character-identically in 4 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/OrgModal/components/TransferForm.tsx, Apps/CMS/CMS.WebAPI/CMSWeb/src/components/UserModal/components/TransferForm.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/OrgModal/components/TransferForm.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/UserModal/components/TransferForm.tsx. 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 BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx:29 — `props.open && props.values !== undefined` appears character-identically in 2 files — BasicPlatform.WebAPI/ConsoleApp/src/pages/Developer/EventTracking/Config/components/CreateOrUpdateForm.tsx, BasicPlatform.WebAPI/ConsoleApp/src/pages/System/Role/components/CreateOrUpdateForm.tsx. 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 Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx:454 — `props.scrollY || window.innerHeight - 352` appears character-identically in 2 files — Apps/CMS/CMS.WebAPI/CMSWeb/src/components/ProTablePlus/index.tsx, BasicPlatform.WebAPI/ConsoleApp/src/components/ProTablePlus/index.tsx. 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.
IC1 · Incompleteness & stubs · Commented-out code · ×12
  • Commented-out code BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:67 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BasicPlatform.Domain/Models/Users/User.cs:356 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BasicPlatform.Domain/Models/Users/User.cs:357 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BasicPlatform.Domain/Models/Users/User.cs:358 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BasicPlatform.Domain/Models/Users/User.cs:359 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BasicPlatform.WebAPI/Controllers/Developer/EventTrackingConfigController.cs:87 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code BasicPlatform.WebAPI/Controllers/Developer/EventTrackingConfigController.cs:117 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:66 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:67 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:219 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:231 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:236 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D30 · Dependency Vulnerabilities · Low CVE · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM2 · Strongly-typed ids · Primitive id on a domain type · ×10
  • Primitive id on a domain type: ExternalPage.ParentId BasicPlatform.Domain/Models/ExternalPage.cs:14 — `ExternalPage.ParentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: ExternalPage.OwnerId BasicPlatform.Domain/Models/ExternalPage.cs:21 — `ExternalPage.OwnerId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Resource.AppId BasicPlatform.Domain/Models/Resource.cs:14 — `Resource.AppId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Resource.Key BasicPlatform.Domain/Models/Resource.cs:20 — `Resource.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Application.ClientId BasicPlatform.Domain/Models/Applications/Application.cs:26 — `Application.ClientId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Organization.ParentId BasicPlatform.Domain/Models/Organizations/Organization.cs:16 — `Organization.ParentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Organization.LeaderId BasicPlatform.Domain/Models/Organizations/Organization.cs:50 — `Organization.LeaderId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Position.OrganizationId BasicPlatform.Domain/Models/Positions/Position.cs:17 — `Position.OrganizationId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: User.OrganizationId BasicPlatform.Domain/Models/Users/User.cs:66 — `User.OrganizationId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: User.PositionId BasicPlatform.Domain/Models/Users/User.cs:77 — `User.PositionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
C2 · Access Controls · No named authorization policies · ×8
  • No named authorization policies — Authorization IS enforced here (via [Authorize]/guards) — this is NOT a claim that endpoints are unprotected. What's missing is NAMED policies (AddAuthorization/AddPolicy, RequireRole/RequireClaim, RequireAuthorization): the access rules are implicit rather than named and testable. Recommendation, not a defect — name the rules so they're reviewable.
  • No named authorization policies Apps/CMS/CMS.WebAPI/Controllers/AccountController.cs:16 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
  • No named authorization policies BasicPlatform.WebAPI/Controllers/FileController.cs:20 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
  • No named authorization policies BasicPlatform.WebAPI/Controllers/SsoController.cs:44 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
  • No named authorization policies REDACTED:87 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
  • No named authorization policies REDACTED:135 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
  • No named authorization policies REDACTED:272 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
  • No named authorization policies REDACTED:356 — This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable.
S1 · Web-Security Posture · No security response headers detected · ×5
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected Apps/CMS/CMS.WebAPI/Program.cs:3 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected Apps/CRM/CRM.WebAPI/Program.cs:2 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected BasicPlatform.Gateway/Program.cs:3 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected BasicPlatform.WebAPI/Program.cs:2 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×5
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected Apps/CMS/CMS.WebAPI/Program.cs:3 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected Apps/CRM/CRM.WebAPI/Program.cs:2 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected BasicPlatform.Gateway/Program.cs:3 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected BasicPlatform.WebAPI/Program.cs:2 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
D31 · IaC & Container Security · Low IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Outdated · ×3
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:21 — Microsoft.AspNetCore.Authentication.JwtBearer 7.0.13 → 10.0.13 available (referenced by BasicPlatform.WebAPI).
  • Outdated: Serilog.AspNetCore REDACTED:13 — Serilog.AspNetCore 7.0.0 → 10.0.0 available (referenced by BasicPlatform.Gateway).
  • Outdated: coverlet.collector BasicPlatform.Test/BasicPlatform.Test.csproj:19 — coverlet.collector 6.0.0 → 10.1.0 available (referenced by BasicPlatform.Test).
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IUserQueryService (20 members) BasicPlatform.AppService/Users/IUserQueryService.cs:11 — `IUserQueryService` declares 20 members: `GetPagingAsync`, `GetAccessRecordPagingAsync`, `GetAsync`, `GetTenantSuperAdminAsync`, `GetByUserNameAsync`, `GetIdsByRoleIdAsync`, `GetCurrentUserAsync`, `GetSelectListAsync`, `GetAllSelectListAsync`, `GetIdByUserNameAsync`, `GetUserResourceAsync`, `GetCurrentUserExternalPagesAsync`, `GetUserExternalPagesAsync`, `GetResourceCodeInfoAsync`, `GetResourceCodesAsync`, `GetCurrentUserCustomColumnsAsync`, `GetUserCustomColumnsAsync`, `GetDataPermissionsAsync`, `GetColumnPermissionsAsync`, `GetColumnPermissionsByModuleNameAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
C2 · Access Controls · Anonymous-heavy surface · ×1
  • Anonymous-heavy surface — [AllowAnonymous] (8) outweighs [Authorize] (7) — review whether the open surface is intended.
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/`.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 66 of 66 significant files have no living knowledge — the codebase as a whole is dormant, not 66 separate risks. Counted over 66 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D34 · Knowledge Freshness · Most significant orphaned file · ×1
  • Most significant orphaned file BasicPlatform.AppService.FreeSql/Users/UserQueryService.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 1 authored method(s) exceed the IL budget BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:186 — 1 of 694 first-party methods compile to oversized IL bodies (> 250 instructions); worst: BasicPlatform.AppService.FreeSql.Tenants.TenantQueryService.GetAsync @ BasicPlatform.AppService.FreeSql/Tenants/TenantQueryService.cs:186, 265 IL instructions; that pulled this dimension to 10.0/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
DM8 · Value-object opportunities · Primitive data clump · ×1
  • Primitive data clump: [copyright, description, ico, logo, name, shortname] BasicPlatform.Domain/Models/WebSettings/WebSetting.cs:58 — The parameters [copyright, description, ico, logo, name, shortname] travel together across 4 signatures — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
ED3 · Event naming · Event not named in past tense · ×1
  • Event not named in past tense: UserPasswordResetEvent BasicPlatform.Domain/Models/Users/Events/UserPasswordResetEvent.cs:6 — `UserPasswordResetEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
M3 · Folder & project structure · No src/ separation · ×1
  • No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
M3 · Folder & project structure · Inconsistent root namespaces · ×1
  • Inconsistent root namespaces — Only 9/23 projects share a common root namespace — the code's module identity is inconsistent.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift BasicPlatform.WebAPI/ConsoleApp/README.md:72 — BasicPlatform.WebAPI/ConsoleApp/README.md runs `npm run tauri build`, but no REDACTED declares a `tauri` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 5/11 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 11, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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 rollback/health safety · ×1
  • No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 78/176 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~5.4 `!` suppressions per 1k syntax nodes — 286 suppression(s) across the 52573 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 24 finding(s)
D12 · Dependency Hygiene · Outdated · ×24
  • Outdated: Athena.Infrastructure.Domain — Athena.Infrastructure.Domain 7.0.7 → 8.1.0 available (referenced by BasicPlatform.Domain).
  • Outdated: Athena.Infrastructure — Athena.Infrastructure 7.0.6 → 8.0.0 available (referenced by BasicPlatform.Infrastructure).
  • Outdated: Athena.Infrastructure.EventTracking — Athena.Infrastructure.EventTracking 7.0.5 → 8.1.0 available (referenced by BasicPlatform.Infrastructure).
  • Outdated: Athena.InstantMessaging — Athena.InstantMessaging 7.0.0 → 8.0.0 available (referenced by BasicPlatform.Infrastructure).
  • Outdated: Flurl.Http — Flurl.Http 3.2.4 → 4.0.2 available (referenced by BasicPlatform.Infrastructure).
  • Outdated: NewLife.IP — NewLife.IP 2.0.2023.401 → 2.5.2026.804 available (referenced by BasicPlatform.Infrastructure).
  • Outdated: Athena.Infrastructure.DataPermission — Athena.Infrastructure.DataPermission 7.0.5 → 8.1.0 available (referenced by BasicPlatform.AppService).
  • Outdated: Athena.Infrastructure.FreeSql — Athena.Infrastructure.FreeSql 7.0.11 → 8.1.0 available (referenced by BasicPlatform.AppService.FreeSql).
  • Outdated: Athena.All.FreeSql — Athena.All.FreeSql 7.0.4-preview.20231218.2 → 8.1.4 available (referenced by BasicPlatform.WebAPI).
  • Outdated: Athena.Infrastructure.FreeSql.OTel — Athena.Infrastructure.FreeSql.OTel 7.0.0-preview.20231101.2 → 8.0.0 available (referenced by BasicPlatform.WebAPI).
  • Outdated: Athena.Infrastructure.Cors — Athena.Infrastructure.Cors 7.0.5 → 8.0.0 available (referenced by BasicPlatform.Gateway).
  • Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.2 → 13.0.4 available (referenced by BasicPlatform.Gateway).
  • Outdated: Serilog.Enrichers.Thread — Serilog.Enrichers.Thread 3.1.0 → 4.0.0 available (referenced by BasicPlatform.Gateway).
  • Outdated: Serilog.Sinks.Grafana.Loki — Serilog.Sinks.Grafana.Loki 8.2.0 → 9.0.2 available (referenced by BasicPlatform.Gateway).
  • Outdated: Yarp.ReverseProxy — Yarp.ReverseProxy 2.1.0 → 2.3.0 available (referenced by BasicPlatform.Gateway).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.7.2 → 18.11.0 available (referenced by BasicPlatform.Test).
  • Outdated: NUnit — NUnit 3.13.3 → 5.0.0 available (referenced by BasicPlatform.Test).
  • Outdated: NUnit.Analyzers — NUnit.Analyzers 3.9.0 → 4.15.0 available (referenced by BasicPlatform.Test).
  • Outdated: NUnit3TestAdapter — NUnit3TestAdapter 4.5.0 → 6.3.1 available (referenced by BasicPlatform.Test).
  • Outdated: Athena.Infrastructure.SubApplication — Athena.Infrastructure.SubApplication 7.0.6 → 8.1.0 available (referenced by CMS.AppService).
  • Outdated: Polly — Polly 8.2.0 → 8.8.0 available (referenced by CMS.WebAPI).
  • Outdated: NewLife.Core — NewLife.Core 10.6.2023.1101 → 11.19.2026.901 available (referenced by App.Infrastructure).
  • Outdated: Athena.Infrastructure.SqlSugar — Athena.Infrastructure.SqlSugar 7.0.5 → 8.0.0 available (referenced by CRM.CommandHandlers.SqlSugar).
  • Outdated: Athena.All.SqlSugar — Athena.All.SqlSugar 7.0.5 → 8.0.0 available (referenced by CRM.WebAPI).

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-58d7e7bc24d4436abfe3eb122033b012/history.json --exit-code 0 --source .2artifacts/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-58d7e7bc24d4436abfe3eb122033b012/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 .48artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list BasicPlatform.sln package --vulnerable --include-transitive --format json179artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .13artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.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 01a165ee-7777-73b7-985c-86a417e914c9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 34 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Phone — 20 field(s)
  • CreateUserRequest.PhoneNumber Apps/App.Infrastructure/Messaging/Requests/CreateUserRequest.cs:38
  • UpdateUserRequest.PhoneNumber Apps/App.Infrastructure/Messaging/Requests/UpdateUserRequest.cs:37
  • GetUserInfoResponse.PhoneNumber Apps/App.Infrastructure/Messaging/Responses/GetUserInfoResponse.cs:43
  • CreateCustomerCommand.PhoneNumber Apps/CRM/CRM.Commands/Customers/CreateCustomerCommand.cs:16
  • CreateCustomerCommand.Telephone Apps/CRM/CRM.Commands/Customers/CreateCustomerCommand.cs:21
  • Customer.PhoneNumber Apps/CRM/CRM.Domain/Customers/Customer.cs:21
  • Customer.Telephone Apps/CRM/CRM.Domain/Customers/Customer.cs:27
  • CustomerCreatedEvent.PhoneNumber Apps/CRM/CRM.Domain/Customers/Events/CustomerCreatedEvent.cs:18
  • CustomerCreatedEvent.Telephone Apps/CRM/CRM.Domain/Customers/Events/CustomerCreatedEvent.cs:24
  • TenantModel.ContactPhoneNumber BasicPlatform.AppService/Tenants/Models/TenantModel.cs:31
  • TenantQueryModel.ContactPhoneNumber BasicPlatform.AppService/Tenants/Models/TenantQueryModel.cs:36
  • UserModel.PhoneNumber BasicPlatform.AppService/Users/Models/UserModel.cs:42
  • UserQueryModel.PhoneNumber BasicPlatform.AppService/Users/Models/UserQueryModel.cs:49
  • TenantCreatedEvent.ContactPhoneNumber BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:26
  • TenantUpdatedEvent.ContactPhoneNumber BasicPlatform.Domain/Models/Tenants/Events/TenantUpdatedEvent.cs:26
  • Tenant.ContactPhoneNumber BasicPlatform.Domain/Models/Tenants/Tenant.cs:36
  • UserBasicUpdatedEvent.PhoneNumber BasicPlatform.Domain/Models/Users/Events/UserBasicUpdatedEvent.cs:16
  • UserCreatedEvent.PhoneNumber BasicPlatform.Domain/Models/Users/Events/UserCreatedEvent.cs:32
  • UserUpdatedEvent.PhoneNumber BasicPlatform.Domain/Models/Users/Events/UserUpdatedEvent.cs:37
  • User.PhoneNumber BasicPlatform.Domain/Models/Users/User.cs:53
Email — 14 field(s)
  • CreateUserRequest.Email Apps/App.Infrastructure/Messaging/Requests/CreateUserRequest.cs:44
  • UpdateUserRequest.Email Apps/App.Infrastructure/Messaging/Requests/UpdateUserRequest.cs:43
  • GetUserInfoResponse.Email Apps/App.Infrastructure/Messaging/Responses/GetUserInfoResponse.cs:49
  • TenantModel.ContactEmail BasicPlatform.AppService/Tenants/Models/TenantModel.cs:36
  • TenantQueryModel.ContactEmail BasicPlatform.AppService/Tenants/Models/TenantQueryModel.cs:42
  • UserModel.Email BasicPlatform.AppService/Users/Models/UserModel.cs:48
  • UserQueryModel.Email BasicPlatform.AppService/Users/Models/UserQueryModel.cs:56
  • TenantCreatedEvent.ContactEmail BasicPlatform.Domain/Models/Tenants/Events/TenantCreatedEvent.cs:31
  • TenantUpdatedEvent.ContactEmail BasicPlatform.Domain/Models/Tenants/Events/TenantUpdatedEvent.cs:31
  • Tenant.ContactEmail BasicPlatform.Domain/Models/Tenants/Tenant.cs:42
  • UserBasicUpdatedEvent.Email BasicPlatform.Domain/Models/Users/Events/UserBasicUpdatedEvent.cs:21
  • UserCreatedEvent.Email BasicPlatform.Domain/Models/Users/Events/UserCreatedEvent.cs:38
  • UserUpdatedEvent.Email BasicPlatform.Domain/Models/Users/Events/UserUpdatedEvent.cs:43
  • User.Email BasicPlatform.Domain/Models/Users/User.cs:61

Issues: 216 · Warnings: 524 · Recommendations: 221 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 23:24 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