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

IceEmblem/IEManageSystem

Measured 21 October 2026, 22:06 UTC, at code version fa0bc62

Code coverage: not measured

Code coverage is not measured: .NET and JavaScript/TypeScript suite (CouldNotMeasureEnvironment, CouldNotMeasureTestRunFailed).

CAI score 20out of 100 At risk Down 3 since the last survey

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

Architecture 63 Adequate Performance 60 Adequate Domain Modelling 52 Adequate Code Health 44 Weak Maturity 41 Weak Accessibility 38 Weak Production Readiness 14 Critical Security and Compliance 10 Critical

A medium codebase: 38,381 lines of product code in 15 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Security and Compliance, 10

Findings by how serious they are

175 critical 477 serious 241 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
21 October 2026, 22:06 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 ▸

98of 103 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
847of 893 findings point to an exact file and line, so you can open each one in the code. The other 46 concern the repository as a whole, such as missing documentation.
103dimensions across 8 lenses, read from 38,381 lines of product code in 15 projects.
Chapters

Executive summary

IceEmblem/IEManageSystem scores 20 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 Security and Compliance, which scores 10 and is rated Critical. Its Dependency Vulnerabilities dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 2 Leaked secret finding(s) in REDACTED Scanning and to resolve the 2 Vulnerable finding(s) in Dependency Hygiene, and if Security and Compliance rose to 70, the score would rise from 20 to about 29.

175 findings are critical: 107 in Dependency Vulnerabilities, 27 in Dependency Hygiene, 25 in Forms & labels, four in Keyboard semantics, three in Secrets (history), two in Explicit Debt, two in REDACTED Scanning, one in Circular Imports, one in Page structure, one in Project dependency cycles, one in Text alternatives and one in Web-Security Posture.

Watchdog couldn't measure 4 dimensions in this code, among them Test Reliability, Documentation Quality and Navigability, so they are left out of the score. The product code is 38,381 lines, which would take an estimated 0.3 person-years, around €37,000, to rebuild.

Code Health 44 Weak, capped by Type Safety and Nullable reference types Architecture 63 Adequate, capped by Boundary Type-Coupling and Import Boundaries Maturity 41 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 14 ⚠ Critical, capped by Dependency Hygiene, REDACTED Scanning, Test Coverage, Dependency Hygiene, CI/CD gates, Security & performance tooling and Schema migrations Security and Compliance 10 ⚠ Critical, capped by Static Analysis (SAST), Dependency Vulnerabilities, Data Protection, Access Controls and Web-Security Posture Domain Modelling 52 Adequate, capped by Strongly-typed ids and Repository granularity Accessibility 38 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.
Security and Compliance 10 · counts for 45%Production Readiness 14 · counts for 25%Accessibility 38 · counts for 14%Maturity 41 · counts for 8%Code Health 44 · counts for 4%Domain Modelling 52 · counts for 2%Performance 60 · counts for 1%Architecture 63 · counts for 1%

If Security and Compliance rose from 10 to 70, the lowest score rated Strong, the score would rise from 20 to about 29.

Code composition: what the lines of code are
Business logic 14%Supporting code 68%Tests 17%
New since the last survey: 186 findings

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

  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc REDACTED
  • Dependency Hygiene · Deprecated: xunit test/IEManageSystem.Tests/IEManageSystem.Tests.csproj
  • Dependency Hygiene · Deprecated: xunit REDACTED
  • Dependency Hygiene · Deprecated: xunit test/IEManageSystem.CommonInfrastructure.Tests/IEManageSystem.CommonInfrastructure.Tests.csproj
  • Dependency Hygiene · Deprecated: xunit test/IEManageSystem.Application.Tests/IEManageSystem.Application.Tests.csproj
  • Dependency Hygiene · Deprecated: xunit test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj
  • Dependency Hygiene · Deprecated: eslint REDACTED
  • Dependency Hygiene · Deprecated: react-native REDACTED
  • Dependency Hygiene · Deprecated: react-native src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json
  • Dependency Hygiene · Deprecated: metro-react-native-babel-preset src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json
  • Dependency Hygiene · Deprecated: native-base src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json
  • Dependency Hygiene · Deprecated: react-native-vector-icons src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json
  • Dependency Hygiene · Deprecated: bootstrap src/IEManageSystem.Web/ClientApp/src/WebApp/Common/package.json
  • Dependency Hygiene · Deprecated: html-webpack-plugin src/IEManageSystem.Web/ClientApp/src/WebApp/Common/package.json
  • Dependency Hygiene · Deprecated: react-native-web src/IEManageSystem.Web/ClientApp/src/WebApp/Common/package.json
  • Dependency Hygiene · Deprecated: video-react src/IEManageSystem.Web/ClientApp/src/WebApp/Common/package.json
  • Dependency Hygiene · Deprecated: babel-eslint REDACTED
  • Dependency Hygiene · Deprecated: eslint-loader REDACTED
  • Explicit Debt · Dead code: GetAppConfiguration src/IEManageSystem.Web/Configuration/HostingEnvironmentExtensions.cs
  • Explicit Debt · Dead code: Class1 src/UtilityAction/Class1.cs
  • Explicit Debt · Dead code: Regular src/UtilityAction/Other/Regular.cs
  • Explicit Debt · Dead code: ValidateModel src/UtilityAction/ValidateFun/ValidateModel.cs
  • Explicit Debt · Dead code: VerificationCode src/UtilityAction/ValidateFun/VerificationCode.cs
  • Explicit Debt · Dead code: GetMimeType src/UtilityAction/Web/FileContentType.cs
  • Explicit Debt · Dead code: GetImgMimeTypeList src/UtilityAction/Web/FileContentType.cs
  • Explicit Debt · Dead code: WebModelBinding src/UtilityAction/Web/WebModelBinding.cs
  • Explicit Debt · Dead code: WriteLogicCodeFile src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs
  • Explicit Debt · Dead code: _commentName src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs
  • Boundary Type-Coupling · Cross-context type ApiScopeNode (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/ApiAuthorization/ApiScopeNodeConfigure.cs
  • Boundary Type-Coupling · Cross-context type ApiScopeNode (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/ApiAuthorization/ApiScopeNodeConfigure.cs
  • Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ComponentDataConfigure.cs
  • Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ComponentDataConfigure.cs
  • Boundary Type-Coupling · Cross-context type CompositeMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/CompositeMenuConfigure.cs
  • Boundary Type-Coupling · Cross-context type CompositeMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/CompositeMenuConfigure.cs
  • Boundary Type-Coupling · Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ContentPagePeimissionCollectionConfigure.cs
  • Boundary Type-Coupling · Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ContentPagePeimissionCollectionConfigure.cs
  • Boundary Type-Coupling · Cross-context type LeafMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/LeafMenuConfigure.cs
  • Boundary Type-Coupling · Cross-context type LeafMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/LeafMenuConfigure.cs
  • Boundary Type-Coupling · Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/MenuBaseConfigure.cs
  • Boundary Type-Coupling · Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/MenuBaseConfigure.cs
  • Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) REDACTED
  • Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) REDACTED
  • Boundary Type-Coupling · Cross-context type Account (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) REDACTED
  • Boundary Type-Coupling · Cross-context type Account (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) REDACTED
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/PermissionConfigure.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/PermissionConfigure.cs
  • Boundary Type-Coupling · Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RoleConfigure.cs
  • Boundary Type-Coupling · Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RoleConfigure.cs
  • Boundary Type-Coupling · Cross-context type RolePermission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RolePermissionConfigure.cs
  • Boundary Type-Coupling · Cross-context type RolePermission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RolePermissionConfigure.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserConfigure.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserConfigure.cs
  • Boundary Type-Coupling · Cross-context type UserRole (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserRoleConfigure.cs
  • Boundary Type-Coupling · Cross-context type UserRole (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserRoleConfigure.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type ApiScope (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type CmsComponent (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type Logic (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/CheckPermissionService.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/DeletePageDataService.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/UpdateContentComponentDataService.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/UpdateContentComponentDataService.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs
  • Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Logics/IActuator.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs
  • Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs
  • Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs
  • Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs
  • Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs
  • Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/BaseActuator.cs
  • Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/BaseActuator.cs
  • Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/BaseActuator.cs

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

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

  • Coupling · Off the main sequence: IEManageSystem.JwtAuthentication
  • Coupling · Off the main sequence: UtilityAction
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc
  • Dependency Hygiene · Deprecated: xunit
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High 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: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Code Duplication · Duplicated block (17 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx
  • Code Duplication · Duplicated block (17 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx
  • Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/LogicManage/index.jsx
  • Code Duplication · Duplicated block (16 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ContainerConfig.js
  • Code Duplication · Duplicated block (15 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Module.js
  • Code Duplication · Duplicated block (15 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
  • Code Duplication · Duplicated block (15 lines × 4 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/SettingConfig.jsx
  • Code Duplication · Duplicated block (15 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/modules.js
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ComponentContainer.js
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/index.js
  • Code Duplication · Duplicated block (14 lines × 4 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECard/Data.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IETheme/index.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECard/DataConfig.jsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IESelect/SettingConfig.jsx
  • Code Duplication · Duplicated block (14 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/BtnLists.jsx
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/CurrentToolBtns.jsx
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/CurrentToolBtns.jsx
  • Code Duplication · Duplicated block (13 lines × 6 locations) REDACTED
  • Code Duplication · Duplicated block (13 lines × 7 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/Container/Setting.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEBottomNav/index.js
  • Code Duplication · Duplicated block (13 lines × 7 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/Container/SettingConfig.jsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/SettingConfig.jsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAudio/DataConfig.jsx
  • Code Duplication · Duplicated block (13 lines × 5 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx
  • Code Duplication · Duplicated block (13 lines × 5 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx
  • Code Duplication · Duplicated block (13 lines × 8 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/CommonStyleConfigComponent.jsx
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.jsx
  • Code Duplication · Duplicated block (13 lines × 5 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js
  • Code Duplication · Duplicated block (12 lines × 13 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/Setting.ts
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/RootComponentContainerBox/index.js
  • Code Duplication · Duplicated block (12 lines × 5 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/Container/Setting.ts
  • Code Duplication · Duplicated block (12 lines × 8 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/Container/Setting.ts
  • Code Duplication · Duplicated block (12 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEAnimation/Setting.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEAnimation/index.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IELine/index.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEInfoGroup/Component.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEVideo/SettingConfig.jsx
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseContainerComponent/ContainerConfigBtnComponent.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Home/PageContainer.jsx
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/MenuListManage/index.jsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Models/MenuModel.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEAudio/Data.ts
  • Code Duplication · Duplicated block (11 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEImg/Data.ts
  • Code Duplication · Duplicated block (11 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/SettingConfig.jsx
  • Code Duplication · Duplicated block (11 lines × 7 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/SettingConfig.jsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/SettingConfig.jsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/MenuListManage/index.jsx
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx
  • Code Duplication · Duplicated block (11 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ResourceForm/ResourceForm.jsx
  • Code Duplication · Duplicated block (10 lines × 5 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEAudio/index.js
  • Code Duplication · Duplicated block (10 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEAudio/index.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEButton/index.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECalendar/index.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECard/index.js
  • Code Duplication · Duplicated block (10 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECategoryLabel/index.js
  • Code Duplication · Duplicated block (10 lines × 26 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/Container/SettingConfig.jsx
  • Code Duplication · Duplicated block (10 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/SettingConfig.jsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/SettingConfig.jsx
  • Code Duplication · Duplicated block (10 lines × 5 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BasePageLeafComponent/PageLeafSettingConfig.jsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Home/PageContainer.jsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/BtnLists.jsx
  • Code Duplication · Duplicated block (10 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Init/InitSite.jsx
  • Code Duplication · Duplicated block (9 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/ComponentSettingConfig.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IocContainer/index.ts
Rebuild cost: about €37,000 · Estimate
Cost to rebuild€12,000 to €62,000, for 206 to 649 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 20. 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: 38,381 lines of product code
Comment linesThe estimate prices 37,691 lines. Comment lines count towards the size of 38,381 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 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Raises the score by about 7 points · Low effort · REDACTED Scanning
2
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.
Raises the score by about 5 points · Low effort · Dependency Hygiene
3
Resolve the 81 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (81).
Raises the score by about 7 points · Medium effort · Dependency Hygiene

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 €37,000 to build again, about 0.3 person-years of work. Its weakest lens is Security and Compliance, at 10 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
One cause behind 50 Domain Modelling findings · Common cause
50 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 (20 findings) · Rich vs anemic model (15 findings) · Strongly-typed ids (15 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 2 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 7 points for low effort, because it clears the 2 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

Architecture — module dependency graph

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

arch IEManageSystem.ApiAuthorization ApiAuthorization IEManageSystem.Core Core IEManageSystem.ApiAuthorization->IEManageSystem.Core IEManageSystem.Application Application IEManageSystem.Application->IEManageSystem.ApiAuthorization IEManageSystem.CMS CMS IEManageSystem.Application->IEManageSystem.CMS IEManageSystem.Common Common IEManageSystem.Application->IEManageSystem.Common IEManageSystem.Application->IEManageSystem.Core IEManageSystem.CMS->IEManageSystem.Core IEManageSystem.CommonInfrastructure CommonInfrastructure IEManageSystem.CommonInfrastructure->IEManageSystem.CMS UtilityAction UtilityAction IEManageSystem.Core->UtilityAction IEManageSystem.EntityFrameworkCore EntityFrameworkCore IEManageSystem.EntityFrameworkCore->IEManageSystem.ApiAuthorization IEManageSystem.EntityFrameworkCore->IEManageSystem.CMS IEManageSystem.EntityFrameworkCore->IEManageSystem.Common IEManageSystem.EntityFrameworkCore->IEManageSystem.Core IEManageSystem.JwtAuthentication JwtAuthentication IEManageSystem.Web Web IEManageSystem.Web->IEManageSystem.Application IEManageSystem.Web->IEManageSystem.CommonInfrastructure IEManageSystem.Web->IEManageSystem.EntityFrameworkCore IEManageSystem.Web->IEManageSystem.JwtAuthentication

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.

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

The table shows the 40 modules with the most connections; 527 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 IEManageSystem2 IEManageSystem.Dtos.CMS3 IEManageSystem.Dtos.Core4 IEManageSystem.JwtAuthentication5 IEManageSystem.Web6 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent7 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseConfig8 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig9 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentSettingModel10 src.IEManageSystem_Web.ClientApp.src.Common.Core.IEReduxs.Actions11 src.IEManageSystem_Web.ClientApp.src.Common.ice-common.BaseIERedux12 src.IEManageSystem_Web.ClientApp.src.Common.ice-common.Modules.BaseModule13 src.IEManageSystem_Web.ClientApp.src.Templates.IETemplateComponents.Container.IComponent14 IEManageSystem.CMS.DomainModel.Menus15 IEManageSystem.Entitys.Authorization.Roles16 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig17 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentModel18 IEManageSystem.Entitys.Authorization.Users19 IEManageSystem.CMS.DomainModel.PageDatas20 IEManageSystem.CMS.DomainModel.Pages21 IEManageSystem.CMS.DomainModel.ComponentDatas22 IEManageSystem.CMS.DomainModel23 IEManageSystem.CMS.DomainModel.Logics24 IEManageSystem.Configures.CMS25 IEManageSystem.CommonInfrastructure.CMS26 IEManageSystem.EntityFrameworkCore27 IEManageSystem.Repositorys28 IEManageSystem.Entitys.Authorization.Permissions29 IEManageSystem.Services.ManageHome.CMS.Menus30 IEManageSystem.Services.ManageHome.CMS.Pages31 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes32 IEManageSystem.Configures.Core33 IEManageSystem.Entitys.Authorization.LoginManagers34 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins35 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes36 IEManageSystem.Services.Accounts37 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes38 IEManageSystem.Web.Controllers39 IEManageSystem.Web.Controllers.CMS.Logics40 IEManageSystem.Web.Controllers.CMS.Pages
1 IEManageSystem
2 IEManageSystem.Dtos.CMS
3 IEManageSystem.Dtos.Core
4 IEManageSystem.JwtAuthentication
5 IEManageSystem.Web
6 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent
7 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseConfig
8 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig
9 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentSettingModel
10 src.IEManageSystem_Web.ClientApp.src.Common.Core.IEReduxs.Actions
11 src.IEManageSystem_Web.ClientApp.src.Common.ice-common.BaseIERedux
12 src.IEManageSystem_Web.ClientApp.src.Common.ice-common.Modules.BaseModule
13 src.IEManageSystem_Web.ClientApp.src.Templates.IETemplateComponents.Container.IComponent
14 IEManageSystem.CMS.DomainModel.Menus11
15 IEManageSystem.Entitys.Authorization.Roles3
16 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig1
17 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentModel1
18 IEManageSystem.Entitys.Authorization.Users61
19 IEManageSystem.CMS.DomainModel.PageDatas111
20 IEManageSystem.CMS.DomainModel.Pages1113
21 IEManageSystem.CMS.DomainModel.ComponentDatas1211
22 IEManageSystem.CMS.DomainModel2414
23 IEManageSystem.CMS.DomainModel.Logics2222
24 IEManageSystem.Configures.CMS3111
25 IEManageSystem.CommonInfrastructure.CMS33334
26 IEManageSystem.EntityFrameworkCore1111111111
27 IEManageSystem.Repositorys2
28 IEManageSystem.Entitys.Authorization.Permissions11
29 IEManageSystem.Services.ManageHome.CMS.Menus22412
30 IEManageSystem.Services.ManageHome.CMS.Pages4224131
31 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes11
32 IEManageSystem.Configures.Core221
33 IEManageSystem.Entitys.Authorization.LoginManagers111
34 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins1111
35 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes1132
36 IEManageSystem.Services.Accounts111
37 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes111
38 IEManageSystem.Web.Controllers11
39 IEManageSystem.Web.Controllers.CMS.Logics11
40 IEManageSystem.Web.Controllers.CMS.Pages212322
Uses a module listed above itPart of a loopThe module itself
1 IEManageSystem2 IEManageSystem.Dtos.CMS3 IEManageSystem.Dtos.Core4 IEManageSystem.JwtAuthentication5 IEManageSystem.Web6 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent7 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseConfig8 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig9 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentSettingModel10 src.IEManageSystem_Web.ClientApp.src.Common.Core.IEReduxs.Actions11 src.IEManageSystem_Web.ClientApp.src.Common.ice-common.BaseIERedux12 src.IEManageSystem_Web.ClientApp.src.Common.ice-common.Modules.BaseModule13 src.IEManageSystem_Web.ClientApp.src.Templates.IETemplateComponents.Container.IComponent14 IEManageSystem.CMS.DomainModel.Menus15 IEManageSystem.Entitys.Authorization.Roles16 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig17 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentModel18 IEManageSystem.Entitys.Authorization.Users19 IEManageSystem.CMS.DomainModel.PageDatas20 IEManageSystem.CMS.DomainModel.Pages21 IEManageSystem.CMS.DomainModel.ComponentDatas22 IEManageSystem.CMS.DomainModel23 IEManageSystem.CMS.DomainModel.Logics24 IEManageSystem.Configures.CMS25 IEManageSystem.CommonInfrastructure.CMS26 IEManageSystem.EntityFrameworkCore27 IEManageSystem.Repositorys28 IEManageSystem.Entitys.Authorization.Permissions29 IEManageSystem.Services.ManageHome.CMS.Menus30 IEManageSystem.Services.ManageHome.CMS.Pages31 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes32 IEManageSystem.Configures.Core33 IEManageSystem.Entitys.Authorization.LoginManagers34 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins35 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes36 IEManageSystem.Services.Accounts37 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes38 IEManageSystem.Web.Controllers39 IEManageSystem.Web.Controllers.CMS.Logics40 IEManageSystem.Web.Controllers.CMS.PagesIEManageSystem1IEManageSystem.Dtos.CMS2IEManageSystem.Dtos.Core3IEManageSystem.JwtAuthentication4IEManageSystem.Web5src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent6src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseConfig7src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig8src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentSettingModel9src.IEManageSystem_Web.ClientApp.src.Common.Core.IEReduxs.Actions10src.IEManageSystem_Web.ClientApp.src.Common.ice-common.BaseIERedux11src.IEManageSystem_Web.ClientApp.src.Common.ice-common.Modules.BaseModule12src.IEManageSystem_Web.ClientApp.src.Templates.IETemplateComponents.Container.IComponent13IEManageSystem.CMS.DomainModel.Menus14IEManageSystem.Entitys.Authorization.Roles15src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig16src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Models.Pages.PageComponentModel17IEManageSystem.Entitys.Authorization.Users18IEManageSystem.CMS.DomainModel.PageDatas19IEManageSystem.CMS.DomainModel.Pages20IEManageSystem.CMS.DomainModel.ComponentDatas21IEManageSystem.CMS.DomainModel22IEManageSystem.CMS.DomainModel.Logics23IEManageSystem.Configures.CMS24IEManageSystem.CommonInfrastructure.CMS25IEManageSystem.EntityFrameworkCore26IEManageSystem.Repositorys27IEManageSystem.Entitys.Authorization.Permissions28IEManageSystem.Services.ManageHome.CMS.Menus29IEManageSystem.Services.ManageHome.CMS.Pages30IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes31IEManageSystem.Configures.Core32IEManageSystem.Entitys.Authorization.LoginManagers33IEManageSystem.Services.ManageHome.AuthorizeManage.Admins34IEManageSystem.ApiAuthorization.DomainModel.ApiScopes35IEManageSystem.Services.Accounts36IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes37IEManageSystem.Web.Controllers38IEManageSystem.Web.Controllers.CMS.Logics39IEManageSystem.Web.Controllers.CMS.Pages4011311611111113121124142222311133334111111111121122412422413111221111111111321111111111212322+527 more modules (most-connected shown)

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

The Good
D1 · .NET / C# Cyclomatic Complexity 8.3 D2 · .NET / C# Cognitive Complexity 7.8 D4 · .NET / C# Code Duplication 9.6 D17 · .NET / C# Explicit Debt 9.0 D39 · .NET / C# IL Efficiency 9.9 GD1 · Repo Unfinished & placeholder code 10.0 R10 · React / TS Code Duplication 7.8 R2 · React / TS Cyclomatic Complexity 9.7 R3 · React / TS Large Files 9.7 R7 · React / TS Dead Code 9.7 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 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
IC1 · Repo Incompleteness & stubs 6.4 X18 · Repo Disposal-pattern correctness 5.2
The Ugly
D3 · .NET / C# God Classes 4.8 R1 · React / TS Type Safety 2.0 X2 · Repo Cancellation propagation 4.0 X3 · Repo Exception handling 4.5 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 63% · Adequate · gated by D23, R11 ·

The Good
D5 · .NET / C# Coupling 9.5 D6 · .NET / C# Cohesion (LCOM4) 10.0 D22 · .NET / C# Internal API Consistency 10.0 D26 · .NET / C# Project Cohesion 8.7 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 8.1 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 R9 · React / TS Circular Imports 8.1
The Ugly
D23 · .NET / C# Boundary Type-Coupling 0.0 R11 · React / TS Import Boundaries 0.0

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

The Good
D15 · .NET / C# Churn × Complexity Hotspots 9.9 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 9.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Bad
M1 · Repo Documentation (README) 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 · 14% · Critical · gated by D12, D13, R4, R8, P1, P3, P8 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D14 · .NET / C# License Compliance 10.0 P4 · Repo Deployment & Rollback 8.0
The Bad
P10 · Repo Library API & versioning 6.0 P2 · Repo Observability 5.0 P6 · Repo Release Hygiene 5.0 R6 · React / TS Tooling 6.7
The Ugly
D12 · .NET / C# Dependency Hygiene 2.9 D13 · .NET / C# REDACTED Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P8 · Repo Schema migrations 3.0 R4 · React / TS Test Coverage 0.5 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 10% · Critical · gated by D29, D30, C1, C2, S1 ·

The Good
D28 · .NET / C# Secrets (history) 7.0 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
The Bad
D44 · .NET / C# Platform End-of-Life 6.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 2.7 D30 · .NET / C# Dependency Vulnerabilities 0.0 C1 · Repo Data Protection 0.0 C2 · Repo Access Controls 0.0 S1 · Repo Web-Security Posture 1.0 X24 · Repo Document value interpolated into markup unescaped 2.7

At a glance — Domain Modelling · 52% · Adequate · gated by DM2, DM7 ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 9.4 DM11 · Repo Constructible invalid state 10.0 DM9 · Repo Scattered domain decisions 10.0
The Bad
DM5 · Repo Encapsulated state 6.5
The Ugly
DM2 · Repo Strongly-typed ids 3.0 DM4 · Repo Rich vs anemic model 4.5 DM7 · Repo Repository granularity 3.5

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

The Good
AC5 · Repo ARIA correctness 10.0
The Bad
AC1 · Repo Text alternatives 6.0 AC3 · Repo Page structure 5.5 AC6 · Repo Visual & motion safety 5.3 AC7 · Repo A11y enforcement 6.0
The Ugly
AC2 · Repo Forms & labels 2.2 AC4 · Repo Keyboard semantics 1.0

At a glance — Performance · 60% · Adequate ·

The Bad
PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.0 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 Failures152High / Critical
A05:2025 — Injection25Medium
A07:2025 — Authentication Failures6High / Critical

Roadmap

Immediately resolve the two leaked secrets in REDACTED and REDACTED to eliminate critical exposure risks. Address the eighty-one deprecated dependencies in REDACTED and the two vulnerable packages to ensure system stability and security. Implement encryption for sensitive data at rest and enforce strict default-deny access controls on all endpoints to protect against unauthorized access.

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

Do thisHelpsEffortDimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.+7.2 ptsLowREDACTED Scanning
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.+5.0 ptsLowDependency Hygiene
Resolve the 81 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (81).+7.1 ptsMediumDependency Hygiene
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED.+2.8 ptsLowPlatform End-of-Life
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.).+5.4 ptsMediumData Protection
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.+5.4 ptsMediumAccess Controls
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:80`.+4.8 ptsMediumWeb-Security Posture
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED.+2.1 ptsLowStatic Analysis (SAST)

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.8SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.2SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.9SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.1MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED5.0MixedREDACTED Scanning: Leaked secret: REDACTED
src/IEManageSystem.Core/IEManageSystem.Core.csproj5.5MixedCoupling: Off the main sequence: IEManageSystem.Core
REDACTED5.5MixedExplicit Debt: EmptyCatchBlock
src/UtilityAction/Web/WebModelBinding.cs5.8MixedExplicit Debt: EmptyCatchBlock
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs6.0MixedExplicit Debt: Dead code: WriteLogicCodeFile
REDACTED6.1MixedStatic Analysis (SAST): Medium: REDACTED
src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs6.3MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: 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 — 175

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

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

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. 98 of 103 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 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 — 103 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D17D20D21D22D23D24D26D28D29D30D34D35D39D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX3AX4AX5AX6AX8C1C2DM1DM10DM11DM2DM4DM5DM7DM9GD1IC1M1M2M3M4P1P10P2P3P4P6P8PF1PF2PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 847 of 893 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a16080-807e-73f6-b224-21c85673b470.

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 34 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 12 test source file(s) (.ts, .js) 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.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — unit: measured (0 flaky); JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in src/IEManageSystem.Web/ClientApp/): not included — the jest run in src/IEManageSystem.Web/ClientApp/ produced no per-test report (● Validation Error:). No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in src/IEManageSystem.Web/ClientApp/ was NOT MEASURED: the jest run in src/IEManageSystem.Web/ClientApp/ produced no per-test report (● Validation Error:). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • 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, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/package.json, src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/package.json, src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/package.json, src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/package.json, and others — 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-maintainer repository — bus factor is not applicable (2 contributor(s) across 244 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • 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 6 deducted marker(s) and the 0.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .jsx (11,666 lines, 31% of production source), .js (11,647 lines, 31% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. 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.
  • 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.
  • D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem.json`, `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem-zh-CHS.json`, `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem-tr.json`, `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem-en.json`, `src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/StateStuct.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • 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. Boot via AndroidApp (src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/android/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: .java:57) at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:39) ... 125 more FAILURE: Build failed with an exception. * What went wrong: Could not initialize class org.…; runtime evidence skipped (launch chosen because src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/android/app/build.gradle applies the Android application plugin and src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/android/gradlew builds it).
  • 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • 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.
  • 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. 112 further occurrence(s) are not listed individually; the score already reflects all 152.
  • R11 Import Boundaries — 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. 71 further occurrence(s) are not listed individually; the score already reflects all 111.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 493 further occurrence(s) are not listed individually; the score already reflects all 533.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • 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.
  • D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
  • 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.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • 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.
  • 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.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (5): D21, D22, D24, D26, 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 Complexity8.3 / 10Strong✓ Tool-verified

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

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

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

6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Header.default at 48.

Header.default (cyclomatic 48)src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
(anonymous) (cyclomatic 48)src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
exports (cyclomatic 42)src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91
ComponentContainerBox.getStyle (cyclomatic 37)src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20
ResourceList.getShowTexts (cyclomatic 16)src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30

What to do

  1. Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Header.default (cyclomatic 48), (anonymous) (cyclomatic 48), exports (cyclomatic 42). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  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 Complexity7.8 / 10Strong✓ Tool-verified

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

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

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

9 method(s) exceeded the cognitive complexity threshold of 15; the worst was ComponentContainerBox.getStyle at 61.

ComponentContainerBox.getStyle (cognitive 61)src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20
Header.default (cognitive 47)src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
(anonymous) (cognitive 47)src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
exports (cognitive 40)src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91
ResourceList.getShowTexts (cognitive 33)src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30

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

What to do

  1. Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with ComponentContainerBox.getStyle (cognitive 61), getStyle (cognitive 61), Header.default (cognitive 47). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cognitive Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  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 Classes4.8 / 10Weak✓ 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 4.8 / 10 · rule-coverage 100% · ceiling Prevented

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

MethodTooLong: BasicSettingConfig.render · ×7src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:19
FunctionTooLong: Header.default · ×6src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8

What to do

  1. Resolve the 7 MethodTooLong finding(s) in God Classes — start with SettingConfig.jsx (2), BasicSettingConfig.jsx, UserInfo.jsx. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 6 FunctionTooLong finding(s) in God Classes — start with Header.js, ListItem.js, Button.js. — One of this dimension's main actionable groups (6 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.6 / 10Stronggated by 10 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.6 / 10 · rule-coverage 100% · ceiling Verified

9 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. Measured on part of this repository only: .jsx, .js (62% 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 (11 lines × 2) · ×2src/IEManageSystem.Web/Conventions/IEApiConvention.cs:22
Members sharing a duplicated core (4 members, 50+ identical tokens)src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174
Duplicated block (17–20 lines × 4)src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174
Duplicated block (17 lines × 2)src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:91
Duplicated block (20 lines × 2)REDACTED:87

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

What to do

  1. Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with IEApiConvention.cs, AdminManageAppService.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with ApiScopeManager.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (17–20 lines × 4) finding(s) in Code Duplication — start with ApiScopeManager.cs. — One of this dimension's main actionable groups (1 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.5 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

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

Off the main sequence: IEManageSystem.Coresrc/IEManageSystem.Core/IEManageSystem.Core.csproj:1
Off the main sequence: IEManageSystem.Commonsrc/IEManageSystem.Common/IEManageSystem.Common.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with IEManageSystem.Core.csproj. — One of this dimension's main actionable groups (1 warning-level).
  2. 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)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 37 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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

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

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

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

44 test methods: 44 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 10 `it`/`test` case(s) across 7 test file(s) declaring at least one beside 34 .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, 1 mock references across 34 tests. Measured on the C# suite only — at least 12 test source file(s) (.ts, .js) went unread, so its test quality is unmeasured and is not in these counts.

Mock framework: NSubstitute

✓ On the Gold path — maintain.

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

D12 · Dependency Hygiene2.9 / 10Weak✓ 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 2.9 / 10 · rule-coverage 100% · ceiling Verified

36 outdated, 2 vulnerable, 19 deprecated packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.

Vulnerable: AngleSharp · ×2
Deprecated: Microsoft.AspNetCore.Diagnostics · ×37REDACTED:42
Deprecated: @babel/plugin-proposal-async-generator-functions · ×81REDACTED:652
Outdated: Abp.AspNetCore · ×21REDACTED:56
Outdated: Castle.Core · ×15

What to do

  1. Resolve the 81 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (81). — One of this dimension's main actionable groups (81 recommendation-level).
  2. Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 37 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (12), REDACTED (10), REDACTED (4). — One of this dimension's main actionable groups (37 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

2 secret(s) detected.

REDACTED

What to do

  1. Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 272 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 44 direct `PackageReference`(s), and 206 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 Hotspots9.9 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

Top hotspots: src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js (20×37=740); src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js (16×34=544); src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts (6×15=90)

Hotspot: src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js · ×3src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.js, webpack.config.js, Actions.ts. — One of this dimension's main actionable groups (3 warning-level).

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

D17 · Explicit Debt9.0 / 10Adequategated by 2 critical 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.0 / 10 · rule-coverage 100% · ceiling Prevented

6 deducted debt markers + 15 dead symbols across 10522 LoC in the .NET projects (0.5/KLoC) → score 9.0. Measured on the .NET source only: .jsx, .js (62% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

EmptyCatchBlock · ×2REDACTED:77
Dead code: GetAppConfiguration · ×15src/IEManageSystem.Web/Configuration/HostingEnvironmentExtensions.cs:9
TodoComment · ×3src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:81
CommentedOutCodesrc/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:65

What to do

  1. Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED, WebModelBinding.cs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 15 Dead code finding(s) in Explicit Debt — start with FileContentType.cs (2), WriteLogicCodeFile.cs (2), HostingEnvironmentExtensions.cs. — One of this dimension's main actionable groups (15 warning-level).
  3. Resolve the 3 TodoComment finding(s) in Explicit Debt — start with ActuatorFactory.cs (3). — One of this dimension's main actionable groups (3 warning-level).
  4. 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.

D22 · Internal API ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

0 API inconsistencies across 5 exposed types.

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

D23 · Boundary Type-Coupling0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Verified

73 domain type(s) cross context boundaries across 9 contexts.

Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) · ×11src/IEManageSystem.CMS/DomainModel/DeletePageDataService.cs:35
Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) · ×7src/IEManageSystem.ApiAuthorization/DomainModel/CheckPermissionService.cs:44
Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) · ×7src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:15
Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) · ×4src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:17
Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) · ×4src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:17

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

What to do

  1. Resolve the 11 Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) finding(s) in Boundary Type-Coupling — start with PageDataManager.cs (5), UpdateContentComponentDataService.cs (2), PageManager.cs (2). — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 7 Cross-context type Permission (IEManageSystem.Core →… finding(s) in Boundary Type-Coupling — start with ApiScopeNode.cs (3), ApiScopePermission.cs (2), CheckPermissionService.cs. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 7 Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) finding(s) in Boundary Type-Coupling — start with PageManager.cs (4), ContentPagePermissionCollection.cs (2), ContentPagePermission.cs. — One of this dimension's main actionable groups (7 warning-level).
  4. Stand up a CI pipeline, then gate Boundary Type-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 Verified — provenance only; does not change the score.

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

D24 · Comment ValueExemplary◐ 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 Exemplary / 10 · rule-coverage 100% · ceiling Documented

42 valuable / 0 redundant across 154 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Documented

1 of 15 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ 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 7.0 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 3 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 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)2.7 / 10Weak✓ Tool-verified

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

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

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

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

25 finding(s): 0 critical, 0 high, 25 medium, 0 low. semgrep hit a parse error in 6 file(s) — `src/IEManageSystem.Web/ClientApp/src/Assets/fonts/fontawesome/fa-brands-400.html` (line 1), `src/IEManageSystem.Web/ClientApp/src/Assets/fonts/fontawesome/fa-light-300.html` (line 1), `src/IEManageSystem.Web/ClientApp/src/Assets/fonts/fontawesome/fa-regular-400.html` (line 1), `src/IEManageSystem.Web/ClientApp/src/Assets/fonts/fontawesome/fa-solid-900.html` (line 1), `src/IEManageSystem.Web/ClientApp/src/Assets/fonts/gt-walsheim/GTWalsheimProTrial-Thin.html` (line 1), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 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

152 finding(s): 28 critical, 79 high, 35 medium, 10 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 78 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (70), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (78 issue-level).
  2. Resolve the 27 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (27 issue-level).
  3. Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d30_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

41 of 41 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/UtilityAction/Web/FileContentType.cs. Counted over 41 of the 336 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×40REDACTED:1
Dormant codebase
Most significant orphaned filesrc/UtilityAction/Web/FileContentType.cs:1

What to do

  1. Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, ApiScopeManager.cs, PageDataManageAppService.cs. — One of this dimension's main actionable groups (40 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 FileContentType.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 Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D39 · IL Efficiency9.9 / 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

3 of 614 first-party methods have an oversized IL body.

IL efficiency: 3 authored method(s) exceed the IL budgetsrc/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataQueryAppService.cs:53

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

End-of-life runtime: .NET netcoreapp3.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 alternatives6.0 / 10Adequate✓ 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. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IETab/Preview.jsx:6

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.2 / 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 <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×21) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:51, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:23, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:39, …
  • This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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. (×4) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEComment/Component.jsx:21, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseMenuComponent/MenuSettingConfig.jsx:40, src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ResourceForm/DateTime.jsx:11, …
  • This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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. (×7) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:35, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:132, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IESelect/Component.jsx:12, …
  • 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. (×3) — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:139, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:153, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/BtnLists.jsx:39
  • 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:81
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.jsx:9
  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×2) — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserTagNavTools/index.jsx:30, src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserTagNavTools/index.jsx:33

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.5 / 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="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — src/IEManageSystem.Web/ClientApp/public/index.html:2
  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/IEManageSystem.Web/ClientApp/src/WebApp/Adapters/WebView.tsx:13

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

  • This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/Component.jsx:136
  • An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECard/Component.jsx:13
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/Component.jsx:17, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:81, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:82

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety5.3 / 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.

  • `.picturemanage .custom-file-label::after` sets color: #fff on background-color: #28a745 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.css:22
  • `.IERankingList-item-icon` sets color: #fff on background-color: #db3964 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IERankingList/IERankingList.css:17
  • `.listbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:7
  • `.content-container > div > *` moves (`animation: toTop-fade-in 0.5s ease-out 0s 1 normal`) 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Layout/BodyDiv/BodyDiv.css:6
  • `.listbtn span:nth-child(1)` moves (`animation: span-first-off 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:30
  • `.listbtn span:nth-child(2)` moves (`animation: span-second-off 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:35
  • `.listbtn span:nth-child(3)` moves (`animation: span-third-off 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:40
  • `.listbtn.on span:nth-child(1)` moves (`animation: span-first-on 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:50
  • `.listbtn.on span:nth-child(2)` moves (`animation: span-second-on 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:55
  • `.listbtn.on span:nth-child(3)` moves (`animation: span-third-on 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:60
  • `.cms-menu label` moves (`transition: text-indent .15s, height .3s`) 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.css:26
  • `.star` moves (`animation: star-ani 6s infinite ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Account/account.css:37
  • `.star:after` moves (`animation: shooting-ani 3s infinite ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/IEManageSystem.Web/ClientApp/src/WebApp/Account/account.css:54

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 enforcement6.0 / 10Adequate✓ 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.

  • An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 193 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

  • Accessibility linting is already configured — assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition8.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 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes ↔ IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes ↔ IEManageSystem.CMS.DomainModel ↔ IEManageSystem.CMS.DomainModel.ComponentDatas ↔ IEManageSystem.CMS.DomainModel.Logics ↔ IEManageSystem.CMS.DomainModel.Menus ↔ IEManageSystem.CMS.DomainModel.PageDatas ↔ IEManageSystem.CMS.DomainModel.Pages ↔ IEManageSystem.EntityFrameworkCore ↔ IEManageSystem.Entitys.Authorization.Permissions ↔ IEManageSystem.Entitys.Authorization.Roles ↔ IEManageSystem.Entitys.Authorization.Users ↔ IEManageSystem.Repositorys depend on each other. The lightest dependency in the cycle is IEManageSystem.ApiAuthorization.DomainModel.ApiScopes → IEManageSystem.Repositorys (IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager → IEManageSystem.Repositorys.IEfRepository, 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. — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:6

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 direction10.0 / 10Exemplary✓ Tool-verified

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

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

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 segregation10.0 / 10Exemplary✓ Tool-verified

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

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

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.

C1 · Data Protection0.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 Controls0.0 / 10Critical✓ 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.

  • No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • `AccountController.RegisterAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/IEManageSystem.Web/Controllers/AccountController.cs:62
  • `AccountController.LoginAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/IEManageSystem.Web/Controllers/AccountController.cs:82
  • `LogicExecController.ExecLogic` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/IEManageSystem.Web/Controllers/CMS/Logics/LogicExecController.cs:24
  • `PageDataManageController.AddPageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:73
  • `PageDataManageController.UpdatePageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:85
  • `PageDataManageController.DeletePageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:99
  • `PageDataManageController.UpdateComponentData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:115
  • `PageDataManageController.ScorePageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:137
  • `PageDataQueryController.GetPagesOfUserCanAccessPost` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:59
  • `PageDataQueryController.GetPageDatas` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:108
  • `PageDataQueryController.GetPageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:143
  • `InitSiteController.Init` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:37
  • `UserController.GetUserScopeAccessAuthorities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:43

What to do

  • Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ 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.

DM10 · One transaction, one aggregate9.4 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

  • `PageManager.UpdateContentPagePermission` saves `Expression`, `ContentPagePermissionCollection` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:228
  • `MenuManager.UpdateRootMenu` saves `Expression`, `CompositeMenu` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/IEManageSystem.CMS/DomainModel/Menus/MenuManager.cs:119

What to do

  • Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state10.0 / 10Exemplary○ Nothing flagged

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.

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.

  • `RolePermission.RoleId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:13
  • `RolePermission.PermissionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:15
  • `User.TenantId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:87
  • `UserRole.UserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:25
  • `UserRole.RoleId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:27
  • `ApiScopePermission.ApiScopeId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:27
  • `ApiScopePermission.PermissionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:29
  • `ComponentSingleData.ComponentDataId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:25
  • `ContentComponentData.PageDataId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:24
  • `ContentPagePermission.PermissionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:12
  • `ContentPagePermission.ContentPagePermissionCollectionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:17
  • `MenuBase.CompositeMenuId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:28
  • `MenuBase.RootMenuId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:30
  • `Tag.PageDataId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:18
  • `SiteSetting.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. — src/IEManageSystem.Common/DomainModel/SiteSetting.cs:11

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model4.5 / 10Weak✓ 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.

  • `Permission` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.Core/Entitys/Authorization/Permissions/Permission.cs:9
  • `Role` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.Core/Entitys/Authorization/Roles/Role.cs:11
  • `RolePermission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:10
  • `UserRole` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:10
  • `Account` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.Core/Entitys/Authorization/Users/Accounts/Account.cs:11
  • `ApiScopePermission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:12
  • `CmsComponent` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/CmsComponent.cs:9
  • `ComponentSingleData` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:9
  • `ContentComponentData` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:11
  • `ContentPagePermission` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:10
  • `ContentPagePermissionCollection` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:12
  • `Logic` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/Logics/Logic.cs:8
  • `CompositeMenu` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/IEManageSystem.CMS/DomainModel/Menus/CompositeMenu.cs:7
  • `Tag` 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. — src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:9
  • `SiteSetting` 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. — src/IEManageSystem.Common/DomainModel/SiteSetting.cs:9

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 state6.5 / 10Adequate✓ 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.

  • `Permission` exposes publicly writable state (DisplayName, Describe). — src/IEManageSystem.Core/Entitys/Authorization/Permissions/Permission.cs:9
  • `Role` exposes publicly writable state (DisplayName, Describe, RolePermissions). — src/IEManageSystem.Core/Entitys/Authorization/Roles/Role.cs:11
  • `RolePermission` exposes publicly writable state (RoleId, PermissionId, Permission). — src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:10
  • `User` exposes publicly writable state (EmailAddress, Name, Phone, PersonSignature, RealName, IDNumber, and 5 more). — src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:16
  • `UserRole` exposes publicly writable state (Role). — src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:10
  • `Account` exposes publicly writable state (Password, SafetyProblem). — src/IEManageSystem.Core/Entitys/Authorization/Users/Accounts/Account.cs:11
  • `ApiScope` exposes publicly writable state (ApiManageScope, ApiQueryScope). — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScope.cs:13
  • `ApiScopePermission` exposes publicly writable state (ApiScopeId, PermissionId, Permission). — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:12
  • `ApiScopeNode` exposes publicly writable state (ApiScopePermissions). — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs:11
  • `CmsComponent` exposes publicly writable state (Name). — src/IEManageSystem.CMS/DomainModel/CmsComponent.cs:9
  • `ComponentSingleData` exposes publicly writable state (Name, SortIndex, Field1, Field2, Field3, Field4, and 3 more). — src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:9
  • `ContentComponentData` exposes publicly writable state (Sign, SingleDatas, PageData, PageDataId). — src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:11
  • `ContentPagePermission` exposes publicly writable state (PermissionId, Permission, ContentPagePermissionCollectionId, ContentPagePermissionCollection, IsManage). — src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:10
  • `ContentPagePermissionCollection` exposes publicly writable state (IsEnableQueryPermission, ContentPagePermissions, PageName). — src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:12
  • `Logic` exposes publicly writable state (Name, Code). — src/IEManageSystem.CMS/DomainModel/Logics/Logic.cs:8
  • `CompositeMenu` exposes publicly writable state (Menus). — src/IEManageSystem.CMS/DomainModel/Menus/CompositeMenu.cs:7
  • `MenuBase` exposes publicly writable state (Name, DisplayName, Icon, CompositeMenuId, RootMenuId, RootMenu, and 2 more). — src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:11
  • `PageData` exposes publicly writable state (Name, Title, Describe, Content, Images, Field1, and 8 more). — src/IEManageSystem.CMS/DomainModel/PageDatas/PageData.cs:18
  • `Tag` exposes publicly writable state (Name, DisplayName, PageData, PageDataId). — src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:9
  • `SiteSetting` exposes publicly writable state (Key, Value, DisplayName, Group). — src/IEManageSystem.Common/DomainModel/SiteSetting.cs:9

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).
DM7 · Repository granularity3.5 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

  • `IEfRepository` returns `IQueryable` from `ThenInclude`, `ThenInclude`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — src/IEManageSystem.Core/Repositorys/IEfRepository.cs:11

What to do

  • Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
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.

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 & stubs6.4 / 10Adequate✓ Tool-verified

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.

  • `Validate` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/IEManageSystem.Application/Services/Accounts/Dto/RegisterInput.cs:29
  • `GetRoles` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:42
  • `DeleteRole` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:67
  • `UpdateRole` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:74
  • `AddPermission` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:98
  • `RemovePermission` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:114
  • `GetUserInfo` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/Users/UserAppService.cs:108
  • `SetSafetyProblem` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/IEManageSystem.Application/Services/Users/UserAppService.cs:128
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/IMenuManageAppService.cs:13, src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/IMenuManageAppService.cs:15, src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:56

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • 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 15 of 15 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 structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy10.0 / 10Exemplary◐ 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.

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.
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

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

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

  • 269/269 types (100%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

What to do

  • Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
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 csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — 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 csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — 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 & Rollback8.0 / 10Strong✓ Tool-verified

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

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

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

  • `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. — REDACTED:113

What to do

  • Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.
PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

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

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

  • No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF2 · Allocation hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.

What to do

  • On hot paths, prefer Span<T>/ReadOnlySpan<T>, ArrayPool<T>, stackalloc and ValueTask to cut the allocations those paths would otherwise make.
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.

  • Only 0/13 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • `await _userManager.UserRepository.EnsureCollectionLoadedAsync(user, e => e.UserRoles)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:55
  • `await _permissionRepository.GetAllListAsync(e => permissionIds.Contains(e.Id))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:70, src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:93
  • `await SaveChanges()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:65, src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:118
  • `await _userManager.CreateUser(userName, password, name, tenantId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/IEManageSystem.Core/Entitys/Authorization/Users/AdminManager.cs:50, src/IEManageSystem.Core/Entitys/Authorization/Users/RegisterManager.cs:35
  • `await _UserManager.RegisterAsync(input.UserName, input.Password, input.EmailAddress...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:45
  • `await _LoginManager.LoginAsync(input.Username, input.Password, input.TenantId ?? 0)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:57
  • `await _adminManager.CreateAdmin(input.UserName, input.Password, input.Name, input.T...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:62
  • `await _roleManager.CreateRole(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:62
  • `await _userRepository.FirstOrDefaultAsync((int)(_abpSession.UserId ?? 0))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/IEManageSystem.Application/Services/Users/UserAppService.cs:50, src/IEManageSystem.Application/Services/Users/UserAppService.cs:149

What to do

  • In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
R1 · Type Safety2.0 / 10Critical✓ Tool-verified

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

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

  • 116 typed · 471 plain JS — the untyped files are src/IEManageSystem.Web/ClientApp/createModulesFile.js, src/IEManageSystem.Web/ClientApp/index.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContext/index.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponent.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js (+465 more).

What to do

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

  • 37 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/ have copies in at least two of the sibling directories Container, IEAnimation, IEAudio, IEBottomNav, IEButton, IECalendar (+23 more sibling(s) not listed) — 24 of them are reported below, and 13 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 37 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 37 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 37 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. — src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4
  • 25 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/ have copies in at least two of the sibling directories Container, IEAnimation, IEAudio, IEBottomNav, IEButton, IECard (+13 more sibling(s) not listed) — 20 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 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14
  • 13 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/ have copies in at least two of the sibling directories Common, RNApp, Templates, WebApp — 7 of them are reported below, and 6 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4
  • 12 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/WebApp/ have copies in at least two of the sibling directories Account, AuthorizeManage, CMSManage, Common, Init, Layout (+2 more sibling(s) not listed) — 3 of them are reported below, and 9 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AuthorizeManage.jsx:12
  • 11 of the duplicated blocks reported below have copies in at least two of the sibling directories AdminManage, AdminPermissionManage, AdminRoleManage, ApiScopePermission, Permission, RoleManage (+1 more sibling(s) not listed) under src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/. That concentration is one structural fact, not 11 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 11 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50
  • 9 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/ have copies in at least two of the sibling directories Component, Home, LogicManage, MenuListManage, PageEdit, PageManage (+4 more sibling(s) not listed) — 6 of them are reported below, and 3 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124
  • 5 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/ have copies in at least two of the sibling directories ContentComponentDatas, DefaultComponentDatas, Menus, PageComponents, PageDatas, Pages — 1 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/DefaultComponentDatas/Reducer.ts:52
  • 5 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Templates/ have copies in at least two of the sibling directories RNIETemplateComponents, WebIETemplateComponents — 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/index.js:29
  • 5 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/ have copies in at least two of the sibling directories BaseComponent, BaseContentLeafComponent, BasePageLeafComponent, InteractiveComponent — 4 of them are reported below, and 1 is 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js:3 — these 2 files are line-for-line copies of one another — 199 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. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3
  • src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:132 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:151 — the two spans are one implementation copied and then locally edited — 636 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:132
  • src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:35 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:39 — the two spans are one implementation copied and then locally edited — 490 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:35
  • src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RolePermissionManage/RolePermissionManage.jsx:49 — 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50
  • src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:1 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RoleManage/RoleManage.jsx:1 — these 2 files are line-for-line copies of one another — 58 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:1
  • src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/SettingConfig.jsx:8 — the two spans are one implementation copied and then locally edited — 346 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. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/CancelAndReload.jsx:24 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ClipBoard.jsx:18 — the two spans are one implementation copied and then locally edited — 334 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/CancelAndReload.jsx:24
  • src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:54 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RolePermissionManage/RolePermissionManage.jsx:61 — the two spans are one implementation copied and then locally edited — 263 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:54
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PageEditFrame.jsx:26 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PostEditFrame.jsx:23 — the two spans are one implementation copied and then locally edited — 241 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PageEditFrame.jsx:26
  • src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx:32 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:29 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RoleManage/RoleManage.jsx:30 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx:32
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/InputGroup.js:60 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Item.js:167 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/InputGroup.js:60
  • src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4 · src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IELine/Data.ts:4 — 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. — src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4
  • src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETheme/Component.js:9 · src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETwoDimensionalCode/Component.js:10 — the two spans are one implementation copied and then locally edited — 192 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. — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETheme/Component.js:9
  • src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:13 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:112 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:13
  • src/IEManageSystem.Web/ClientApp/src/WebApp/Common/IEBraftEditor/index.js:7 · src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ResourceForm/RichText.jsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/IEBraftEditor/index.js:7
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4 · src/IEManageSystem.Web/ClientApp/src/WebApp/Adapters/RNComponentContainerBoxShow.js:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfigBtnComponent.js:51 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40
  • src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:257 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:332 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:257
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:73 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:102 — 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:73
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:10 · src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:48 — the two spans are one implementation copied and then locally edited — 98 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:10
  • REDACTED:51 · REDACTED:73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:51
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PostEdit/ToolBtns.jsx:32 — the two spans are one implementation copied and then locally edited — 85 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:66 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:89 — 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:66
  • src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEAudio/Component.js:55 · src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEVideo/Component.js:59 — the two spans are one implementation copied and then locally edited — 169 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. — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEAudio/Component.js:55
  • src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx:62 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:94 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RolePermissionManage/RolePermissionManage.jsx:94 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx:62
  • src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:179 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:202 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:223 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:246 · +2 more site(s) not listed — the 6 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:179
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:8 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js:8 — 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. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:8
  • src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IECategoryLabel/Component.js:39 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/Component.jsx:31 — 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. — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IECategoryLabel/Component.js:39
  • src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:41 · src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:79 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:41
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/Login/index.js:40 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/UserInfo/index.js:60 — 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. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/Login/index.js:40
  • src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:19 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEVideo/DataConfig.jsx:39 — 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. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:19

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 Boundaries0.0 / 10Critical✓ 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.

  • src/IEManageSystem.Web/ClientApp/index.js:2 reaches into another package with a relative path (./src/RNApp/RNStart/index) — import the package by name instead. — src/IEManageSystem.Web/ClientApp/index.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:5 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:5
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:7 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:7
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BasicComponentSettingConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BasicComponentSettingConfig.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/index.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/index.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/DeleteConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/DeleteConfig.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/FontComponentSettingConfig/index.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/FontComponentSettingConfig/index.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/PostFieldSettingConfig/index.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/PostFieldSettingConfig/index.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ContainerConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ContainerConfig.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfig.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseMenuComponent/MenuComponentSettingConfig.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseMenuComponent/MenuComponentSettingConfig.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/PageLeafComponentSettingConfig.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/PageLeafComponentSettingConfig.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveComponentConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveComponentConfig.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveContainerConfig.js:5 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveContainerConfig.js:5
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/CmsRedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/CmsRedux.ts:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:17 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:17
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:3
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/IEReduxs/LayoutRedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/IEReduxs/LayoutRedux.ts:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/IEReduxs/PersonalRedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/IEReduxs/PersonalRedux.ts:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/IEReduxs/IERedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/IEReduxs/IERedux.ts:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/Module.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/Module.js:1
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/Module.js:2
  • src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/Module.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/Common/BaseSetting/Module.js:3
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/Components/RegisterTemplateManager.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/Components/RegisterTemplateManager.js:1
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js:11 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js:11
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Module.js:4 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Module.js:4
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Module.js:5 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Module.js:5
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Module.js:2
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Module.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Module.js:3
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:6 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:6
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:1
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:2
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:4 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:4
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:5 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Module.js:5

What to do

  • Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (107 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (4 rows).
R2 · Cyclomatic Complexity9.7 / 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.

  • (anonymous) has cyclomatic complexity 48 and cognitive complexity 47; 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. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
  • getStyle has cyclomatic complexity 37 and cognitive complexity 61; 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. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20
  • exports has cyclomatic complexity 34 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91
  • _initExternalDescribes has cyclomatic complexity 14 and cognitive complexity 25; 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. — REDACTED:45
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Theme/index.js:5
  • getShowTexts has cyclomatic complexity 13 and cognitive complexity 23; 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. — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30
  • setTheme has cyclomatic complexity 13 and cognitive complexity 12; 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. — src/IEManageSystem.Web/ClientApp/src/Common/ice-common/Theme/index.ts:51
  • (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:9
  • onscroll has cyclomatic complexity 11 and cognitive complexity 12; 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. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/Component.jsx:74

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files9.7 / 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.

  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx has 527 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:1
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:1
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js has 414 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:1
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:1

What to do

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

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

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

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:1, src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:1, src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling6.7 / 10Adequate✓ 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.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add `tsc --noEmit` as REDACTED scripts and run them in CI.
R7 · Dead Code9.7 / 10Exemplary✓ 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.

  • 73 file(s) (~3251 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage
  • 8 file(s) (~236 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout
  • 9 file(s) (~152 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson
  • Unreachable from the 18 application, 8 tooling and 17 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 (18 application, 8 tooling, 17 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 (×3) — src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/jest/fileTransform.js, src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/pnpTs.js, src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/jest/cssTransform.js
  • Nothing imports this binding — it is safe to review for removal. (×3) — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ComponentContainer.js:4, src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:24, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/index.js:13
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:142

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 but not declared in any reachable REDACTED — installs work only by hoisting accident. (×25) — src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/CMSManage/Component/ComponentContainers/PageEditComponentContainer/EditFrame.test.js:2, src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/IEEnzyme.js:1, src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/IEEnzyme.js:2, …
  • Declared in src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json but never imported anywhere in that package or its workspace members — while src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Models/ContentPagePermissionCollection.ts DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
  • Declared in src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json but never imported anywhere in that package or its workspace members — while src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.

What to do

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

  • src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts → src/IEManageSystem.Web/ClientApp/src/Common/ice-common/index.js → src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts (one verified cycle inside a mutually-dependent group of 4 files) — src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts:4

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture1.0 / 10Critical✓ 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.

  • `user.Account.Password == password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again. — src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:80
  • MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — src/UtilityAction/Other/Encrypt.cs:12
  • 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 UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)

What to do

  • Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:80`.
  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
  • 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 correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

  • `db` is a `IEManageSystemDbContext`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `Init` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var db = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:63
  • `md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `MD5Utf8` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw. — src/UtilityAction/Other/Encrypt.cs:12

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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 propagation4.0 / 10Weak✓ 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 0/11 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. (×11) — src/IEManageSystem.Web/Controllers/AccountController.cs:62, src/IEManageSystem.Web/Controllers/AccountController.cs:82, src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:36, …

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 unescaped2.7 / 10Weak✓ Tool-verified

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.

  • `setting.code` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/Component.jsx:33
  • `text` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/RichTextEditor/Component.jsx:9

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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 handling4.5 / 10Weak✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — REDACTED:77, src/UtilityAction/Web/WebModelBinding.cs:51
  • `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. — src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:170

What to do

  • Swallowed exception (empty catch)
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 types2.0 / 10Critical✓ 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.

  • 0/10 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

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
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 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 Health44%Weak — gated by R1, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture63%Adequate — gated by D23, R11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity41%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness14%Critical — gated by D12, D13, R4, R8, P1, P3, P8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security10%Critical — gated by D29, D30, C1, C2, S1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling52%Adequate — gated by DM2, DM7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility38%Weak — gated by AC2, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • 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 — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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
Not included — 32 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.

  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: .java:57) at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:39) ... 125 more FAILURE: Build failed with an exception. * What went wrong: Could not initialize class org.…; runtime evidence skipped (launch chosen because src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/android/app/build.gradle applies the Android application plugin and src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/android/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
  • D11 Test Reliability — Test reliability not measured — polyglot suite, one half not re-run
  • D16 Bus Factor — single-maintainer 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 .java, .m, .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
  • 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 .java, .m, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 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 could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the jest suite in src/IEManageSystem.Web/ClientApp/ ran and not one test passed (● Validation Error:), so the coverage would describe the failed run, not the code. 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.
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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
  • R5 Dependency Freshness — uses a yarn 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 — 175 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×78
  • 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
  • + 53 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×27
  • 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
  • + 2 more in this group — see findings.md.
AC2 · Forms & labels · <label> that labels no control · ×21
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:51 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:23 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:39 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:55 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:113 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:171 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:187 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:203 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:222 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:268 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:300 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:324 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:340 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:355 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:371 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:387 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BasePageLeafComponent/PageLeafSettingConfig.jsx:52 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BasePageLeafComponent/PageLeafSettingConfig.jsx:68 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BasePageLeafComponent/PageLeafSettingConfig.jsx:84 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.jsx:177 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.jsx:208 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
R8 · Dependency Hygiene · Unlisted import 'react' · ×7
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/CMSManage/Component/ComponentContainers/PageEditComponentContainer/EditFrame.test.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/ILayoutInstance.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/AntIcons/index.tsx:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'native-base' · ×5
  • Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Models/ContentPagePermissionCollection.ts:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/SearchBar/index.js:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/AntIcons/index.tsx:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC2 · Forms & labels · Link with no accessible name · ×2
  • Link with no accessible name src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserTagNavTools/index.jsx:30 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserTagNavTools/index.jsx:33 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×2
  • Click handler on a non-interactive <div> src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/Component.jsx: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> src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:81 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D12 · Dependency Hygiene · Vulnerable · ×2
  • Vulnerable: AngleSharp — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: Microsoft.AspNetCore.Authentication.JwtBearer — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
D13 · REDACTED Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×2
  • EmptyCatchBlock REDACTED:77 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/UtilityAction/Web/WebModelBinding.cs:51 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D28 · Secrets (history) · High secret · ×2
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'prop-types' · ×2
  • Unlisted import 'prop-types' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'prop-types' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react-router-native' · ×2
  • Unlisted import 'react-router-native' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/index.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'react-router-native' src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC1 · Text alternatives · <img> without a text alternative · ×1
  • <img> without a text alternative src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IETab/Preview.jsx:6 — 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> · ×1
  • Custom control with no accessible name on <div> src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:81 — 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.
AC2 · Forms & labels · <button> with no accessible text · ×1
  • <button> with no accessible text src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.jsx:9 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title src/IEManageSystem.Web/ClientApp/src/WebApp/Adapters/WebView.tsx:13 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC4 · Keyboard semantics · Hover-only interaction on <div> · ×1
  • Hover-only interaction on <div> src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/Component.jsx:136 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×1
  • Click handler on a non-interactive <img> src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:82 — 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 src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:6 — The namespaces IEManageSystem.ApiAuthorization.DomainModel.ApiScopes ↔ IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes ↔ IEManageSystem.CMS.DomainModel ↔ IEManageSystem.CMS.DomainModel.ComponentDatas ↔ IEManageSystem.CMS.DomainModel.Logics ↔ IEManageSystem.CMS.DomainModel.Menus ↔ IEManageSystem.CMS.DomainModel.PageDatas ↔ IEManageSystem.CMS.DomainModel.Pages ↔ IEManageSystem.EntityFrameworkCore ↔ IEManageSystem.Entitys.Authorization.Permissions ↔ IEManageSystem.Entitys.Authorization.Roles ↔ IEManageSystem.Entitys.Authorization.Users ↔ IEManageSystem.Repositorys depend on each other. The lightest dependency in the cycle is IEManageSystem.ApiAuthorization.DomainModel.ApiScopes → IEManageSystem.Repositorys (IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager → IEManageSystem.Repositorys.IEfRepository, 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.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'IEEnzyme' · ×1
  • Unlisted import 'IEEnzyme' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/CMSManage/Component/ComponentContainers/PageEditComponentContainer/EditFrame.test.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'enzyme' · ×1
  • Unlisted import 'enzyme' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/IEEnzyme.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'enzyme-adapter-react-16' · ×1
  • Unlisted import 'enzyme-adapter-react-16' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/IEEnzyme.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react-router' · ×1
  • Unlisted import 'react-router' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/ComponentContainer.js:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'color' · ×1
  • Unlisted import 'color' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'lodash' · ×1
  • Unlisted import 'lodash' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/index.js:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react-native-camera' · ×1
  • Unlisted import 'react-native-camera' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react-native-webview' · ×1
  • Unlisted import 'react-native-webview' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/IEWebView/index.tsx:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'images' · ×1
  • Unlisted import 'images' src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/UserInfo/index.js:7 — 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) src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts:4 — src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts → src/IEManageSystem.Web/ClientApp/src/Common/ice-common/index.js → src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts (one verified cycle inside a mutually-dependent group of 4 files)
S1 · Web-Security Posture · Password hashing without a KDF · ×1
  • Password hashing without a KDF src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:80 — `user.Account.Password == password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again.
Serious — 477 finding(s)
R11 · Import Boundaries · Boundary violation [package · ×40
  • Boundary violation [package:relative-cross-package] src/IEManageSystem.Web/ClientApp/index.js:2 — src/IEManageSystem.Web/ClientApp/index.js:2 reaches into another package with a relative path (./src/RNApp/RNStart/index) — import the package by name instead.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:5 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:5 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:7 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:7 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BasicComponentSettingConfig.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BasicComponentSettingConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/index.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/index.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/DeleteConfig.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/DeleteConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/FontComponentSettingConfig/index.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/FontComponentSettingConfig/index.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/PostFieldSettingConfig/index.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/PostFieldSettingConfig/index.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ContainerConfig.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ContainerConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfig.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseMenuComponent/MenuComponentSettingConfig.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseMenuComponent/MenuComponentSettingConfig.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/PageLeafComponentSettingConfig.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/PageLeafComponentSettingConfig.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveComponentConfig.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveComponentConfig.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveContainerConfig.js:5 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveContainerConfig.js:5 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/CmsRedux.ts:1 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/CmsRedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:17 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:17 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:3 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:3 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/IEReduxs/LayoutRedux.ts:1 — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/IEReduxs/LayoutRedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:1 — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/IEReduxs/PersonalRedux.ts:1 — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/IEReduxs/PersonalRedux.ts:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:1 — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:1 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:2 — src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:2 imports ice-common, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Button.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/BtnLists.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Layout/BodyDiv/Index/IELinePlotDemo.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Item.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Start/scripts/build.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseContainerComponent/ContainerConfigBtnComponent.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ClipBoard.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/CardItem.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageManage/PageManage.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
D12 · Dependency Hygiene · Deprecated · ×37
  • Deprecated: Microsoft.AspNetCore.Diagnostics REDACTED:42 — Microsoft.AspNetCore.Diagnostics 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:43 — Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore 3.0.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc REDACTED:44 — Microsoft.AspNetCore.Mvc 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc REDACTED:28 — Microsoft.AspNetCore.Mvc 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc REDACTED:12 — Microsoft.AspNetCore.Mvc 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Server.IISIntegration REDACTED:45 — Microsoft.AspNetCore.Server.IISIntegration 2.2.1 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Server.Kestrel REDACTED:46 — Microsoft.AspNetCore.Server.Kestrel 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.SpaServices.Extensions REDACTED:38 — Microsoft.AspNetCore.SpaServices.Extensions 3.0.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.StaticFiles REDACTED:47 — Microsoft.AspNetCore.StaticFiles 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.EntityFrameworkCore.SqlServer.Design REDACTED:48 — Microsoft.EntityFrameworkCore.SqlServer.Design 1.1.6 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:49 — Microsoft.Extensions.Options.ConfigurationExtensions 3.0.0 — Other,Legacy
  • Deprecated: Microsoft.VisualStudio.Web.BrowserLink REDACTED:50 — Microsoft.VisualStudio.Web.BrowserLink 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.EnvironmentVariables src/IEManageSystem.Core/IEManageSystem.Core.csproj:15 — Microsoft.Extensions.Configuration.EnvironmentVariables 3.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.Json src/IEManageSystem.Core/IEManageSystem.Core.csproj:16 — Microsoft.Extensions.Configuration.Json 3.0.0 — Other,Legacy
  • Deprecated: Pomelo.EntityFrameworkCore.MySql REDACTED:35 — Pomelo.EntityFrameworkCore.MySql 3.2.0 — Legacy
  • Deprecated: Microsoft.DotNet.InternalAbstractions test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:34 — Microsoft.DotNet.InternalAbstractions 1.0.0 — Other,Legacy
  • Deprecated: xunit test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:23 — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit REDACTED:23 — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/IEManageSystem.CommonInfrastructure.Tests/IEManageSystem.CommonInfrastructure.Tests.csproj:11 — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/IEManageSystem.Application.Tests/IEManageSystem.Application.Tests.csproj:11 — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj:11 — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit.extensibility.execution test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:24 — xunit.extensibility.execution 2.4.1 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it.
  • Deprecated: IdentityModel REDACTED:9 — IdentityModel 3.9.0 — Legacy — the publisher's replacement is `Duende.IdentityModel`; migrate the reference to it.
  • Deprecated: Microsoft.AspNetCore.Authentication REDACTED:10 — Microsoft.AspNetCore.Authentication 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:11 — REDACTED — Other,Legacy
  • + 12 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×35
  • 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
  • + 10 more in this group — see findings.md.
D17 · Explicit Debt · Dead code · ×15
  • Dead code: GetAppConfiguration src/IEManageSystem.Web/Configuration/HostingEnvironmentExtensions.cs:9 — Method GetAppConfiguration — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: VisitPageDataInput src/IEManageSystem.Web/Controllers/CMS/Pages/Dto/VisitPageDataInput.cs:8 — NamedType VisitPageDataInput — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: VisitPageDataOutput src/IEManageSystem.Web/Controllers/CMS/Pages/Dto/VisitPageDataOutput.cs:8 — NamedType VisitPageDataOutput — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ConsentInputModel src/IEManageSystem.Web/Models/ConsentModels/ConsentInputModel.cs:8 — NamedType ConsentInputModel — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ConsentModel src/IEManageSystem.Web/Models/ConsentModels/ConsentModel.cs:8 — NamedType ConsentModel — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ConsentOptions src/IEManageSystem.Web/Models/ConsentModels/ConsentOptions.cs:8 — NamedType ConsentOptions — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: Class1 src/UtilityAction/Class1.cs:5 — NamedType Class1 — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: Regular src/UtilityAction/Other/Regular.cs:11 — NamedType Regular — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ValidateModel src/UtilityAction/ValidateFun/ValidateModel.cs:10 — NamedType ValidateModel — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: VerificationCode src/UtilityAction/ValidateFun/VerificationCode.cs:10 — NamedType VerificationCode — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetMimeType src/UtilityAction/Web/FileContentType.cs:579 — Method GetMimeType — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetImgMimeTypeList src/UtilityAction/Web/FileContentType.cs:606 — Method GetImgMimeTypeList — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: WebModelBinding src/UtilityAction/Web/WebModelBinding.cs:11 — NamedType WebModelBinding — Roslyn's SymbolFinder walked every project the solution loads, including UtilityAction, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: WriteLogicCodeFile src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:20 — NamedType WriteLogicCodeFile — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.CommonInfrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: _commentName src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:22 — Property _commentName — Roslyn's SymbolFinder walked every project the solution loads, including IEManageSystem.CommonInfrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
DM4 · Rich vs anemic model · Anemic entity · ×15
  • Anemic entity: Permission src/IEManageSystem.Core/Entitys/Authorization/Permissions/Permission.cs:9 — `Permission` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Role src/IEManageSystem.Core/Entitys/Authorization/Roles/Role.cs:11 — `Role` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: RolePermission src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:10 — `RolePermission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: UserRole src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:10 — `UserRole` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Account src/IEManageSystem.Core/Entitys/Authorization/Users/Accounts/Account.cs:11 — `Account` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ApiScopePermission src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:12 — `ApiScopePermission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CmsComponent src/IEManageSystem.CMS/DomainModel/CmsComponent.cs:9 — `CmsComponent` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ComponentSingleData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:9 — `ComponentSingleData` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ContentComponentData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:11 — `ContentComponentData` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ContentPagePermission src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:10 — `ContentPagePermission` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ContentPagePermissionCollection src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:12 — `ContentPagePermissionCollection` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Logic src/IEManageSystem.CMS/DomainModel/Logics/Logic.cs:8 — `Logic` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: CompositeMenu src/IEManageSystem.CMS/DomainModel/Menus/CompositeMenu.cs:7 — `CompositeMenu` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Tag src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:9 — `Tag` 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.
  • Anemic entity: SiteSetting src/IEManageSystem.Common/DomainModel/SiteSetting.cs:9 — `SiteSetting` 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.
C2 · Access Controls · No authorization · ×14
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization src/IEManageSystem.Web/Controllers/AccountController.cs:62 — `AccountController.RegisterAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/IEManageSystem.Web/Controllers/AccountController.cs:82 — `AccountController.LoginAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/IEManageSystem.Web/Controllers/CMS/Logics/LogicExecController.cs:24 — `LogicExecController.ExecLogic` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:73 — `PageDataManageController.AddPageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:85 — `PageDataManageController.UpdatePageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:99 — `PageDataManageController.DeletePageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:115 — `PageDataManageController.UpdateComponentData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:137 — `PageDataManageController.ScorePageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:59 — `PageDataQueryController.GetPagesOfUserCanAccessPost` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:108 — `PageDataQueryController.GetPageDatas` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:143 — `PageDataQueryController.GetPageData` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:37 — `InitSiteController.Init` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:43 — `UserController.GetUserScopeAccessAuthorities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×14
  • Awaits without ConfigureAwait(false) — Only 0/13 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:55 — `await _userManager.UserRepository.EnsureCollectionLoadedAsync(user, e => e.UserRoles)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:70 — `await _permissionRepository.GetAllListAsync(e => permissionIds.Contains(e.Id))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:65 — `await SaveChanges()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Users/AdminManager.cs:50 — `await _userManager.CreateUser(userName, password, name, tenantId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Users/RegisterManager.cs:35 — `await _userManager.CreateUser(userName, password, name, tenantId)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:118 — `await SaveChanges()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:45 — `await _UserManager.RegisterAsync(input.UserName, input.Password, input.EmailAddress...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:57 — `await _LoginManager.LoginAsync(input.Username, input.Password, input.TenantId ?? 0)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:62 — `await _adminManager.CreateAdmin(input.UserName, input.Password, input.Name, input.T...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:62 — `await _roleManager.CreateRole(role)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:93 — `await _permissionRepository.GetAllListAsync(e => permissionIds.Contains(e.Id))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Users/UserAppService.cs:50 — `await _userRepository.FirstOrDefaultAsync((int)(_abpSession.UserId ?? 0))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Users/UserAppService.cs:149 — `await _userRepository.FirstOrDefaultAsync((int)(_abpSession.UserId ?? 0))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
D23 · Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) · ×11
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/DeletePageDataService.cs:35 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via DeletePageDataService.DeletePageDataOfCreator — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/UpdateContentComponentDataService.cs:26 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via UpdateContentComponentDataService.UpdateContentComponentData — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/UpdateContentComponentDataService.cs:32 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via UpdateContentComponentDataService.UpdateContentComponentDataOfCreator — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:165 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageManager.AddPage — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:184 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageManager.UpdatePage — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Logics/IActuator.cs:13 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via IActuator.Exec — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs:26 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageDataManager.AddPageData — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs:43 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageDataManager.UpdatePageDataLastUpdater — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs:48 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageDataManager.UpdatePageData — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs:60 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageDataManager.UpdatePageDataOfCreator — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/PageDatas/PageDataManager.cs:76 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageDataManager.DeletePageDataOrCreator — couples the contexts.
X2 · Cancellation propagation · Async method without CancellationToken · ×11
  • Async method without CancellationToken: RegisterAsync src/IEManageSystem.Web/Controllers/AccountController.cs:62 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoginAsync src/IEManageSystem.Web/Controllers/AccountController.cs:82 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoginAsync src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateRole src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:56 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateAdmin src/IEManageSystem.Core/Entitys/Authorization/Users/AdminManager.cs:48 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RegisterAsync src/IEManageSystem.Core/Entitys/Authorization/Users/RegisterManager.cs:33 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateUser src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:95 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Register src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Login src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:55 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateAdmin src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:60 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddRole src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
AC2 · Forms & labels · <Select> field component without a label · ×10
  • <Select> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:35 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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 src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:132 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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 src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IESelect/Component.jsx:12 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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 src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseMenuComponent/MenuSettingConfig.jsx:40 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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 src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BasePageLeafComponent/PageLeafSettingConfig.jsx:35 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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 src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BasePageLeafComponent/PageLeafSettingConfig.jsx:102 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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 src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:139 — 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 src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:531 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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 src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/BtnLists.jsx:39 — 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 src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ResourceForm/FormSelect.jsx:26 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it 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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×10
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Layout/BodyDiv/BodyDiv.css:6 — `.content-container > div > *` moves (`animation: toTop-fade-in 0.5s ease-out 0s 1 normal`) 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 src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:30 — `.listbtn span:nth-child(1)` moves (`animation: span-first-off 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:35 — `.listbtn span:nth-child(2)` moves (`animation: span-second-off 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:40 — `.listbtn span:nth-child(3)` moves (`animation: span-third-off 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:50 — `.listbtn.on span:nth-child(1)` moves (`animation: span-first-on 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:55 — `.listbtn.on span:nth-child(2)` moves (`animation: span-second-on 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:60 — `.listbtn.on span:nth-child(3)` moves (`animation: span-third-on 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.css:26 — `.cms-menu label` moves (`transition: text-indent .15s, height .3s`) 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 src/IEManageSystem.Web/ClientApp/src/WebApp/Account/account.css:37 — `.star` moves (`animation: star-ani 6s infinite ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Account/account.css:54 — `.star:after` moves (`animation: shooting-ani 3s infinite ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D23 · Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) · ×7
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/CheckPermissionService.cs:44 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via CheckPermissionService.IsAllowAccess — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:140 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via ApiScopeManager.Register — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:18 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via ApiScopePermission..ctor — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:31 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via ApiScopePermission.Permission — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs:15 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via ApiScopeNode.IsAllowAccess — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs:36 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via ApiScopeNode.AddPermission — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.ApiAuthorization) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs:46 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.ApiAuthorization's public surface via ApiScopeNode.RemovePermission — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) · ×7
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:15 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via ContentPagePermission.Permission — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:25 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via ContentPagePermissionCollection.IsCanManagePost — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:41 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via ContentPagePermissionCollection.IsCanQueryPost — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:101 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageManager.GetPagesForManagePermission — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:116 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageManager.GetPagesForQueryPermission — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:135 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageManager.IsCanQueryPost — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.CMS) src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:153 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.CMS's public surface via PageManager.IsCanManagePost — couples the contexts.
D3 · God Classes · MethodTooLong · ×7
  • MethodTooLong: BasicSettingConfig.render src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:19 — MethodTooLong — render runs 327 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 227 over it, 3.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UserInfo.render src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:114 — MethodTooLong — render runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PostModal.render src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:103 — MethodTooLong — render 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.
  • MethodTooLong: AccountSecurity.render src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:104 — MethodTooLong — render runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SettingConfig.render src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/SettingConfig.jsx:9 — MethodTooLong — render runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SettingConfig.render src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:14 — MethodTooLong — render runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ComponentContainerBox.getStyle src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20 — MethodTooLong — getStyle runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
IC1 · Incompleteness & stubs · Fake-async · ×7
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:42 — `GetRoles` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:67 — `DeleteRole` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:74 — `UpdateRole` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:98 — `AddPermission` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:114 — `RemovePermission` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/Users/UserAppService.cs:108 — `GetUserInfo` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/IEManageSystem.Application/Services/Users/UserAppService.cs:128 — `SetSafetyProblem` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
D3 · God Classes · FunctionTooLong · ×6
  • FunctionTooLong: Header.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8 — FunctionTooLong — default runs 336 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 236 over it, 3.36× 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: ListItem.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:9 — FunctionTooLong — default runs 334 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 234 over it, 3.34× 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: Button.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Button.js:6 — FunctionTooLong — default runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× 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: Item.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Item.js:8 — FunctionTooLong — default runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: CardItem.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/CardItem.js:8 — FunctionTooLong — default runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/index.js:50 — FunctionTooLong — default runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D23 · Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) · ×4
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:17 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via Actuator..ctor — couples the contexts.
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:19 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via Actuator.Exec — couples the contexts.
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/BaseActuator.cs:32 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via BaseActuator.Exec — couples the contexts.
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:24 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via WriteLogicCodeFile.Exec — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) · ×4
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:17 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via Actuator..ctor — couples the contexts.
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:19 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via Actuator.Exec — couples the contexts.
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/BaseActuator.cs:32 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via BaseActuator.Exec — couples the contexts.
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:24 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.CommonInfrastructure's public surface via WriteLogicCodeFile.Exec — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) · ×4
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:17 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CommonInfrastructure's public surface via Actuator..ctor — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/Actuator.cs:19 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CommonInfrastructure's public surface via Actuator.Exec — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/BaseActuator.cs:32 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CommonInfrastructure's public surface via BaseActuator.Exec — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:24 — User (context IEManageSystem.Core) is exposed in IEManageSystem.CommonInfrastructure's public surface via WriteLogicCodeFile.Exec — couples the contexts.
AC2 · Forms & labels · <TextArea> field component without a label · ×3
  • <TextArea> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEComment/Component.jsx:21 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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.
  • <TextArea> field component without a label src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:153 — 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.
  • <TextArea> field component without a label src/IEManageSystem.Web/ClientApp/src/WebApp/Init/DBConfigure.jsx:37 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in ComponentContainerBox.getStyle at line 20. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2020-07-27..2020-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2020-07-27 18:27:43 +08:00' --until='2020-10-25 18:27:43 +08:00' --full-history --no-merges -- src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91 — src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in exports at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2020-07-27..2020-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2020-07-27 18:27:43 +08:00' --until='2020-10-25 18:27:43 +08:00' --full-history --no-merges -- src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts:76 — src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Actions.createIEThunkAction at line 76. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2020-07-27..2020-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2020-07-27 18:27:43 +08:00' --until='2020-10-25 18:27:43 +08:00' --full-history --no-merges -- src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:81 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:82 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:83 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D23 · Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ComponentDataConfigure.cs:12 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via ComponentDataConfigure.Configure — couples the contexts.
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ComponentDataConfigure.cs:10 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via ComponentDataConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:73 — ContentComponentData (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.ContentComponentDatas — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ContentPagePeimissionCollectionConfigure.cs:12 — ContentPagePermissionCollection (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via ContentPagePeimissionCollectionConfigure.Configure — couples the contexts.
  • Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/ContentPagePeimissionCollectionConfigure.cs:10 — ContentPagePermissionCollection (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via ContentPagePeimissionCollectionConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type ContentPagePermissionCollection (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:67 — ContentPagePermissionCollection (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.ContentPagePermissionCollections — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/MenuBaseConfigure.cs:12 — MenuBase (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via MenuBaseConfigure.Configure — couples the contexts.
  • Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/MenuBaseConfigure.cs:10 — MenuBase (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via MenuBaseConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type MenuBase (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:69 — MenuBase (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.Menus — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) REDACTED:13 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via PageDataConfigure.Configure — couples the contexts.
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) REDACTED:11 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via PageDataConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:71 — PageData (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.PageDatas — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/PermissionConfigure.cs:12 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via PermissionConfigure.Configure — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/PermissionConfigure.cs:10 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via PermissionConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type Permission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:61 — Permission (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.Permissions — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RoleConfigure.cs:13 — Role (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via RoleConfigure.Configure — couples the contexts.
  • Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RoleConfigure.cs:11 — Role (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via RoleConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type Role (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:59 — Role (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.Roles — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) · ×3
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserConfigure.cs:12 — User (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via UserConfigure.Configure — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserConfigure.cs:10 — User (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via UserConfigure.IEntityTypeConfiguration — couples the contexts.
  • Cross-context type User (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:57 — User (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.Users — couples the contexts.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×3
  • Duplicated block (28 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4 · src/IEManageSystem.Web/ClientApp/src/WebApp/Adapters/RNComponentContainerBoxShow.js:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (28 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfigBtnComponent.js:51 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (28 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:257 — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:257 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:332 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
D23 · Boundary Type-Coupling · Cross-context type ApiScopeNode (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) · ×2
  • Cross-context type ApiScopeNode (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/ApiAuthorization/ApiScopeNodeConfigure.cs:12 — ApiScopeNode (context IEManageSystem.ApiAuthorization) is exposed in IEManageSystem.EntityFrameworkCore's public surface via ApiScopeNodeConfigure.Configure — couples the contexts.
  • Cross-context type ApiScopeNode (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/ApiAuthorization/ApiScopeNodeConfigure.cs:10 — ApiScopeNode (context IEManageSystem.ApiAuthorization) is exposed in IEManageSystem.EntityFrameworkCore's public surface via ApiScopeNodeConfigure.IEntityTypeConfiguration — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type CompositeMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×2
  • Cross-context type CompositeMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/CompositeMenuConfigure.cs:12 — CompositeMenu (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via CompositeMenuConfigure.Configure — couples the contexts.
  • Cross-context type CompositeMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/CompositeMenuConfigure.cs:10 — CompositeMenu (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via CompositeMenuConfigure.IEntityTypeConfiguration — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type LeafMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×2
  • Cross-context type LeafMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/LeafMenuConfigure.cs:12 — LeafMenu (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via LeafMenuConfigure.Configure — couples the contexts.
  • Cross-context type LeafMenu (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/CMS/LeafMenuConfigure.cs:10 — LeafMenu (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via LeafMenuConfigure.IEntityTypeConfiguration — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Account (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) · ×2
  • Cross-context type Account (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) REDACTED:12 — Account (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via AccountConfigure.Configure — couples the contexts.
  • Cross-context type Account (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) REDACTED:10 — Account (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via AccountConfigure.IEntityTypeConfiguration — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type RolePermission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) · ×2
  • Cross-context type RolePermission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RolePermissionConfigure.cs:12 — RolePermission (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via RolePermissionConfigure.Configure — couples the contexts.
  • Cross-context type RolePermission (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/RolePermissionConfigure.cs:10 — RolePermission (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via RolePermissionConfigure.IEntityTypeConfiguration — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type UserRole (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) · ×2
  • Cross-context type UserRole (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserRoleConfigure.cs:12 — UserRole (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via UserRoleConfigure.Configure — couples the contexts.
  • Cross-context type UserRole (IEManageSystem.Core → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/Configures/Core/UserRoleConfigure.cs:10 — UserRole (context IEManageSystem.Core) is exposed in IEManageSystem.EntityFrameworkCore's public surface via UserRoleConfigure.IEntityTypeConfiguration — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) src/IEManageSystem.Web/Conventions/IEApiConvention.cs:22 — src/IEManageSystem.Web/Conventions/IEApiConvention.cs:22-32 | src/IEManageSystem.Web/Conventions/IEApiConvention.cs:38-48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:98 — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:98-108 | src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:154-165 — 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 `src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:98` 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 `input` to `GetAdminRolesInput` in one and `GetPermissionsInput` 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.
DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×2
  • One operation mutates 2 aggregates: PageManager.UpdateContentPagePermission src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:228 — `PageManager.UpdateContentPagePermission` saves `Expression`, `ContentPagePermissionCollection` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: MenuManager.UpdateRootMenu src/IEManageSystem.CMS/DomainModel/Menus/MenuManager.cs:119 — `MenuManager.UpdateRootMenu` saves `Expression`, `CompositeMenu` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
R10 · Code Duplication · Duplicated block (42 lines × 2 locations) · ×2
  • Duplicated block (42 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/InputGroup.js:60 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/InputGroup.js:60 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Item.js:167 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
  • Duplicated block (42 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4 — src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4 · src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IELine/Data.ts:4 — 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 (31 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (31 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETheme/Component.js:9 — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETheme/Component.js:9 · src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETwoDimensionalCode/Component.js:10 — the two spans are one implementation copied and then locally edited — 192 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.
  • Duplicated block with local edits (31 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:13 — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:13 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:112 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (22 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (22 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:10 — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:10 · src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:48 — the two spans are one implementation copied and then locally edited — 98 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (22 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PostEdit/ToolBtns.jsx:32 — the two spans are one implementation copied and then locally edited — 85 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 (22 lines × 2 locations) · ×2
  • Duplicated block (22 lines × 2 locations) REDACTED:51 — REDACTED:51 · REDACTED:73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (22 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:66 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:66 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:8 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:8 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js:8 — 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.
  • Duplicated block (19 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IECategoryLabel/Component.js:39 — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IECategoryLabel/Component.js:39 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/Component.jsx:31 — 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 (17 lines × 2 locations) · ×2
  • Duplicated block (17 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/Login/index.js:40 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/Login/index.js:40 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/UserInfo/index.js:60 — 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.
  • Duplicated block (17 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:19 — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:19 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEVideo/DataConfig.jsx:39 — 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.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×2
  • Disposable created and abandoned in the method that made it REDACTED:63 — `db` is a `IEManageSystemDbContext`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `Init` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var db = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/UtilityAction/Other/Encrypt.cs:12 — `md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `MD5Utf8` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2
  • Untrusted text written into markup unescaped src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/Component.jsx:33 — `setting.code` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/RichTextEditor/Component.jsx:9 — `text` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
X3 · Exception handling · Swallowed exception (empty catch) · ×2
  • Swallowed exception (empty catch) REDACTED:77 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/UtilityAction/Web/WebModelBinding.cs:51 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC2 · Forms & labels · <DatePicker> field component without a label · ×1
  • <DatePicker> field component without a label src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ResourceForm/DateTime.jsx:11 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark src/IEManageSystem.Web/ClientApp/public/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×1
  • Link used as a button (placeholder href) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECard/Component.jsx:13 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×1
  • Low contrast colour pair in CSS (3.1:1) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.css:22 — `.picturemanage .custom-file-label::after` sets color: #fff on background-color: #28a745 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×1
  • Low contrast colour pair in CSS (4.4:1) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IERankingList/IERankingList.css:17 — `.IERankingList-item-icon` sets color: #fff on background-color: #db3964 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:7 — `.listbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
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 · Header.default (cyclomatic 48) · ×1
  • Header.default (cyclomatic 48) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8 — Header.default has cyclomatic complexity 48 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 48) · ×1
  • (anonymous) (cyclomatic 48) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8 — (anonymous) has cyclomatic complexity 48 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · exports (cyclomatic 42) · ×1
  • exports (cyclomatic 42) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91 — exports has cyclomatic complexity 42 (threshold 15). Of this number, 34 points are the body's own statements and 8 belong to 10 function items 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 · ComponentContainerBox.getStyle (cyclomatic 37) · ×1
  • ComponentContainerBox.getStyle (cyclomatic 37) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20 — ComponentContainerBox.getStyle has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ResourceList.getShowTexts (cyclomatic 16) · ×1
  • ResourceList.getShowTexts (cyclomatic 16) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30 — ResourceList.getShowTexts has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 3 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.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:65 — 10 consecutive commented-code lines
D2 · Cognitive Complexity · ComponentContainerBox.getStyle (cognitive 61) · ×1
  • ComponentContainerBox.getStyle (cognitive 61) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20 — ComponentContainerBox.getStyle has cognitive complexity 61 (threshold 15). Drivers by points: if/else 46 (58 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Header.default (cognitive 47) · ×1
  • Header.default (cognitive 47) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8 — Header.default has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 35, boolean chains 12. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · (anonymous) (cognitive 47) · ×1
  • (anonymous) (cognitive 47) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8 — (anonymous) has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 35, boolean chains 12. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · exports (cognitive 40) · ×1
  • exports (cognitive 40) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91 — exports has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 26, ternaries 13, if/else 1. Of this number, 32 points are the body's own statements and 8 belong to 10 function items 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 · ResourceList.getShowTexts (cognitive 33) · ×1
  • ResourceList.getShowTexts (cognitive 33) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30 — ResourceList.getShowTexts has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 3 (8 pts) (nesting depth added 15). Of this number, 23 points are the body's own statements and 10 belong to 3 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 · ResourceDescribe._initExternalDescribes (cognitive 25) · ×1
  • ResourceDescribe._initExternalDescribes (cognitive 25) REDACTED:45 — ResourceDescribe._initExternalDescribes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IEApiConvention.Apply (cognitive 17) · ×1
  • IEApiConvention.Apply (cognitive 17) src/IEManageSystem.Web/Conventions/IEApiConvention.cs:16 — IEApiConvention.Apply has cognitive complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D23 · Boundary Type-Coupling · Cross-context type ApiScope (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) · ×1
  • Cross-context type ApiScope (IEManageSystem.ApiAuthorization → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:63 — ApiScope (context IEManageSystem.ApiAuthorization) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.ApiScopes — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type CmsComponent (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×1
  • Cross-context type CmsComponent (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:65 — CmsComponent (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.CmsComponents — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Logic (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) · ×1
  • Cross-context type Logic (IEManageSystem.CMS → IEManageSystem.EntityFrameworkCore) src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore/IEManageSystemDbContext.cs:77 — Logic (context IEManageSystem.CMS) is exposed in IEManageSystem.EntityFrameworkCore's public surface via IEManageSystemDbContext.Logics — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174 — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174-192 | src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:195-217 | src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:220-239 | src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:242-264 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (17–20 lines × 4) · ×1
  • Duplicated block (17–20 lines × 4) src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174 — src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174-190 | src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:195-214 | src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:220-236 | src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:242-261 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:91 — src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:91-107 | src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:121-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) REDACTED:87 — REDACTED:87-106 | REDACTED:177-197 — 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:87` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/IEManageSystem.Application/Dtos/CMS/PageDto.cs:12 — src/IEManageSystem.Application/Dtos/CMS/PageDto.cs:12-26 | src/IEManageSystem.CMS/DomainModel/Pages/Page.cs:24-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/IEManageSystem.Application/Dtos/CMS/SingleComponentDataDto.cs:15 — src/IEManageSystem.Application/Dtos/CMS/SingleComponentDataDto.cs:15-27 | src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:11-23 — 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, `src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:25` calls `ForeignKey` and `src/IEManageSystem.Application/Dtos/CMS/SingleComponentDataDto.cs:28` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:51 — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:51-57 | src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:45-51 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `input` to `GetAdminsInput` in one and `GetRolesInput` 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 (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:218 — src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:218-222 | src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:261-265 — 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.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET netcoreapp3.0 REDACTED:4 — REDACTED declares .NET netcoreapp3.0 as this project's target framework, and .NET Core 3.0, support ended 2020-03-03. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2020-03-03 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: IEManageSystem.Core src/IEManageSystem.Core/IEManageSystem.Core.csproj:1 — IEManageSystem.Core: abstractness 0.09, instability 0.20, distance 0.71 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the jest suite in src/IEManageSystem.Web/ClientApp/ ran and not one test passed (● Validation Error:), so the coverage would describe the failed run, not the code. 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.
DM7 · Repository granularity · Repository contract exposes a live query handle · ×1
  • Repository contract exposes a live query handle: IEfRepository src/IEManageSystem.Core/Repositorys/IEfRepository.cs:11 — `IEfRepository` returns `IQueryable` from `ThenInclude`, `ThenInclude`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked.
IC1 · Incompleteness & stubs · Hollow method · ×1
  • Hollow method — returns a constant without doing the work src/IEManageSystem.Application/Services/Accounts/Dto/RegisterInput.cs:29 — `Validate` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
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.
P8 · Schema migrations · Schema created with EnsureCreated() (no migration path) · ×1
  • Schema created with EnsureCreated() (no migration path) REDACTED:113 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 116 typed · 471 plain JS — the untyped files are src/IEManageSystem.Web/ClientApp/createModulesFile.js, src/IEManageSystem.Web/ClientApp/index.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContext/index.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponent.js, src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js (+465 more).
R10 · Code Duplication · Duplication concentrated across 29 sibling directories (37 clone groups) · ×1
  • Duplication concentrated across 29 sibling directories (37 clone groups) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4 — 37 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/ have copies in at least two of the sibling directories Container, IEAnimation, IEAudio, IEBottomNav, IEButton, IECalendar (+23 more sibling(s) not listed) — 24 of them are reported below, and 13 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 37 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 37 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 37 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 19 sibling directories (25 clone groups) · ×1
  • Duplication concentrated across 19 sibling directories (25 clone groups) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14 — 25 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/ have copies in at least two of the sibling directories Container, IEAnimation, IEAudio, IEBottomNav, IEButton, IECard (+13 more sibling(s) not listed) — 20 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 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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 (13 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (13 clone groups) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4 — 13 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/ have copies in at least two of the sibling directories Common, RNApp, Templates, WebApp — 7 of them are reported below, and 6 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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 (12 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (12 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AuthorizeManage.jsx:12 — 12 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/WebApp/ have copies in at least two of the sibling directories Account, AuthorizeManage, CMSManage, Common, Init, Layout (+2 more sibling(s) not listed) — 3 of them are reported below, and 9 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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 7 sibling directories (11 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (11 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50 — 11 of the duplicated blocks reported below have copies in at least two of the sibling directories AdminManage, AdminPermissionManage, AdminRoleManage, ApiScopePermission, Permission, RoleManage (+1 more sibling(s) not listed) under src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/. That concentration is one structural fact, not 11 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 11 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 10 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (9 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124 — 9 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/ have copies in at least two of the sibling directories Component, Home, LogicManage, MenuListManage, PageEdit, PageManage (+4 more sibling(s) not listed) — 6 of them are reported below, and 3 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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 6 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (5 clone groups) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/DefaultComponentDatas/Reducer.ts:52 — 5 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/ have copies in at least two of the sibling directories ContentComponentDatas, DefaultComponentDatas, Menus, PageComponents, PageDatas, Pages — 1 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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 2 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (5 clone groups) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/index.js:29 — 5 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/Templates/ have copies in at least two of the sibling directories RNIETemplateComponents, WebIETemplateComponents — 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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 (5 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (5 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40 — 5 duplicated blocks under src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/ have copies in at least two of the sibling directories BaseComponent, BaseContentLeafComponent, BasePageLeafComponent, InteractiveComponent — 4 of them are reported below, and 1 is 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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 (199 identical lines × 2 files) · ×1
  • Wholesale file copy (199 identical lines × 2 files) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js:3 — these 2 files are line-for-line copies of one another — 199 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 (99 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (99 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:132 — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:132 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:151 — the two spans are one implementation copied and then locally edited — 636 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 (72 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (72 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:35 — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:35 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:39 — the two spans are one implementation copied and then locally edited — 490 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 (66 lines × 2 locations) · ×1
  • Duplicated block (66 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50 — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RolePermissionManage/RolePermissionManage.jsx:49 — 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 (58 identical lines × 2 files) · ×1
  • Wholesale file copy (58 identical lines × 2 files) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:1 — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:1 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RoleManage/RoleManage.jsx:1 — these 2 files are line-for-line copies of one another — 58 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 (57 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (57 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14 — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14 · src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/SettingConfig.jsx:8 — the two spans are one implementation copied and then locally edited — 346 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 (56 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (56 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/CancelAndReload.jsx:24 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/CancelAndReload.jsx:24 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ClipBoard.jsx:18 — the two spans are one implementation copied and then locally edited — 334 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 (52 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (52 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:54 — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:54 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RolePermissionManage/RolePermissionManage.jsx:61 — the two spans are one implementation copied and then locally edited — 263 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 (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PageEditFrame.jsx:26 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PageEditFrame.jsx:26 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PostEditFrame.jsx:23 — the two spans are one implementation copied and then locally edited — 241 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 (43 lines × 3 locations) · ×1
  • Duplicated block (43 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx:32 — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx:32 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:29 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RoleManage/RoleManage.jsx:30 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/IEBraftEditor/index.js:7 — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/IEBraftEditor/index.js:7 · src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ResourceForm/RichText.jsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:73 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:73 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (21 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEAudio/Component.js:55 — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEAudio/Component.js:55 · src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEVideo/Component.js:59 — the two spans are one implementation copied and then locally edited — 169 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 (21 lines × 3 locations) · ×1
  • Duplicated block (21 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx:62 — src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx:62 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:94 · src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/RolePermissionManage/RolePermissionManage.jsx:94 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 6 locations) · ×1
  • Duplicated block (20 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:179 — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:179 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:202 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:223 · src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:246 · +2 more site(s) not listed — the 6 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 (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:41 — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:41 · src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:79 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 48, cognitive 47) · ×1
  • Complex function (anonymous) (cyclomatic 48, cognitive 47) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8 — (anonymous) has cyclomatic complexity 48 and cognitive complexity 47; 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 getStyle (cyclomatic 37, cognitive 61) · ×1
  • Complex function getStyle (cyclomatic 37, cognitive 61) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20 — getStyle has cyclomatic complexity 37 and cognitive complexity 61; 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 exports (cyclomatic 34, cognitive 32) · ×1
  • Complex function exports (cyclomatic 34, cognitive 32) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91 — exports has cyclomatic complexity 34 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 _initExternalDescribes (cyclomatic 14, cognitive 25) · ×1
  • Complex function _initExternalDescribes (cyclomatic 14, cognitive 25) REDACTED:45 — _initExternalDescribes has cyclomatic complexity 14 and cognitive complexity 25; 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 14, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 13) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Theme/index.js:5 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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 getShowTexts (cyclomatic 13, cognitive 23) · ×1
  • Complex function getShowTexts (cyclomatic 13, cognitive 23) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30 — getShowTexts has cyclomatic complexity 13 and cognitive complexity 23; 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 setTheme (cyclomatic 13, cognitive 12) · ×1
  • Complex function setTheme (cyclomatic 13, cognitive 12) src/IEManageSystem.Web/ClientApp/src/Common/ice-common/Theme/index.ts:51 — setTheme has cyclomatic complexity 13 and cognitive complexity 12; 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 (anonymous) (cyclomatic 12, cognitive 11) · ×1
  • Complex function (anonymous) (cyclomatic 12, cognitive 11) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:9 — (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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 onscroll (cyclomatic 11, cognitive 12) · ×1
  • Complex function onscroll (cyclomatic 11, cognitive 12) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/Component.jsx:74 — onscroll has cyclomatic complexity 11 and cognitive complexity 12; 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 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx · ×1
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx: 527 lines of code src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:1 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx has 527 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 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js · ×1
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js: 441 lines of code src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:1 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js has 441 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 · src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js · ×1
  • src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js: 414 lines of code src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:1 — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js has 414 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 · src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx · ×1
  • src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx: 403 lines of code src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:1 — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~40 LoC) · ×1
  • Dead file (~40 LoC) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/jest/fileTransform.js — no import path from any entry point (18 application, 8 tooling, 17 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 (~35 LoC) · ×1
  • Dead file (~35 LoC) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/pnpTs.js — no import path from any entry point (18 application, 8 tooling, 17 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 (~14 LoC) · ×1
  • Dead file (~14 LoC) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/jest/cssTransform.js — no import path from any entry point (18 application, 8 tooling, 17 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 · Unused dependency 'metro-react-native-babel-preset' · ×1
  • Unused dependency 'metro-react-native-babel-preset' — Declared in src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'native-base' · ×1
  • Unused dependency 'native-base' — Declared in src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json but never imported anywhere in that package or its workspace members — while src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Models/ContentPagePermissionCollection.ts DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency 'react-native-camera' · ×1
  • Unused dependency 'react-native-camera' — Declared in src/IEManageSystem.Web/ClientApp/src/RNApp/RNStart/package.json but never imported anywhere in that package or its workspace members — while src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
S1 · Web-Security Posture · Weak hash algorithm · ×1
  • Weak hash algorithm src/UtilityAction/Other/Encrypt.cs:12 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
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.
X3 · Exception handling · Rethrow loses stack trace (`throw ex;`) · ×1
  • Rethrow loses stack trace (`throw ex;`) src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:170 — `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Minor — 224 finding(s)
D12 · Dependency Hygiene · Deprecated · ×81
  • Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:652 — @babel/plugin-proposal-async-generator-functions 7.10.5 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-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-class-properties REDACTED:661 — @babel/plugin-proposal-class-properties 7.8.3 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: @babel/plugin-proposal-class-properties REDACTED:669 — @babel/plugin-proposal-class-properties 7.10.4 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: @babel/plugin-proposal-dynamic-import REDACTED:686 — @babel/plugin-proposal-dynamic-import 7.10.4 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-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:702 — @babel/plugin-proposal-export-namespace-from 7.10.4 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-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-json-strings REDACTED:710 — @babel/plugin-proposal-json-strings 7.10.4 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-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:718 — @babel/plugin-proposal-logical-assignment-operators 7.11.0 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-logical-assignment-operators instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:726 — @babel/plugin-proposal-nullish-coalescing-operator 7.8.3 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-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:734 — @babel/plugin-proposal-nullish-coalescing-operator 7.10.4 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-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:742 — @babel/plugin-proposal-numeric-separator 7.8.3 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-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:750 — @babel/plugin-proposal-numeric-separator 7.10.4 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-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:758 — @babel/plugin-proposal-object-rest-spread 7.11.0 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-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:767 — @babel/plugin-proposal-optional-catch-binding 7.10.4 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-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:775 — @babel/plugin-proposal-optional-chaining 7.9.0 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-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:783 — @babel/plugin-proposal-optional-chaining 7.11.0 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-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-private-methods REDACTED:792 — @babel/plugin-proposal-private-methods 7.10.4 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-private-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: @babel/plugin-proposal-unicode-property-regex REDACTED:800 — @babel/plugin-proposal-unicode-property-regex 7.10.4 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-unicode-property-regex instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @hapi/address REDACTED:1576 — @hapi/address 2.1.4 is resolved in REDACTED and is marked deprecated by its publisher: "Moved to 'npm install @sideway/address'". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @hapi/bourne REDACTED:1581 — @hapi/bourne 1.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated and is no longer supported or maintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @hapi/hoek REDACTED:1586 — @hapi/hoek 8.5.1 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated and is no longer supported or maintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @hapi/joi REDACTED:1591 — @hapi/joi 15.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Switch to 'npm install joi'". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @hapi/topo REDACTED:1601 — @hapi/topo 3.1.6 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated and is no longer supported or maintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @types/testing-library__dom REDACTED:2231 — @types/testing-library__dom 7.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. testing-library__dom 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: abab REDACTED:2510 — abab 2.0.4 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: airbnb-prop-types REDACTED:2597 — airbnb-prop-types 2.16.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package has been renamed to 'prop-types-tools'". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • + 56 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×40
  • 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 src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.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 src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.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 src/IEManageSystem.CMS/DomainModel/Pages/PageManager.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 src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.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 src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/ApiScopes/ApiScopeManageAppService.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 src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.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 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 src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.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 src/IEManageSystem.CMS/DomainModel/Menus/MenuManager.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 src/IEManageSystem.Application/Services/Users/UserAppService.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 src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.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 src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataQueryAppService.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 src/IEManageSystem.Web/Startup/Startup.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 src/IEManageSystem.EntityFrameworkCore/Configures/CMS/LeafMenuConfigure.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 src/UtilityAction/ValidateFun/VerificationCode.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 src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.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 src/IEManageSystem.Web/Controllers/AccountController.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 src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageManageAppService.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 src/IEManageSystem.Core/Entitys/Authorization/Users/AdminManager.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 src/IEManageSystem.Core/Entitys/Authorization/Permissions/PermissionManager.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 src/IEManageSystem.CMS/DomainModel/Logics/ExecLogicService.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 src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/MenuManageAppService.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.
  • + 15 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×21
  • Outdated: Abp.AspNetCore REDACTED:56 — Abp.AspNetCore 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Web).
  • Outdated: Abp.Castle.Log4Net REDACTED:57 — Abp.Castle.Log4Net 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:43 — Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.SpaServices.Extensions REDACTED:38 — Microsoft.AspNetCore.SpaServices.Extensions 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:31 — Microsoft.EntityFrameworkCore.Tools 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:49 — Microsoft.Extensions.Options.ConfigurationExtensions 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Web).
  • Outdated: Abp src/IEManageSystem.Common/IEManageSystem.Common.csproj:8 — Abp 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Core).
  • Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables src/IEManageSystem.Core/IEManageSystem.Core.csproj:15 — Microsoft.Extensions.Configuration.EnvironmentVariables 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Core).
  • Outdated: Microsoft.Extensions.Configuration.Json src/IEManageSystem.Core/IEManageSystem.Core.csproj:16 — Microsoft.Extensions.Configuration.Json 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Core).
  • Outdated: Abp.AutoMapper REDACTED:21 — Abp.AutoMapper 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Application).
  • Outdated: Abp.EntityFrameworkCore REDACTED:20 — Abp.EntityFrameworkCore 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Application).
  • Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:25 — Microsoft.EntityFrameworkCore.Design 3.1.8 → 10.0.13 available (referenced by IEManageSystem.EntityFrameworkCore).
  • Outdated: Microsoft.EntityFrameworkCore.Sqlite REDACTED:29 — Microsoft.EntityFrameworkCore.Sqlite 3.1.8 → 10.0.13 available (referenced by IEManageSystem.EntityFrameworkCore).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:30 — Microsoft.EntityFrameworkCore.SqlServer 3.1.8 → 10.0.13 available (referenced by IEManageSystem.EntityFrameworkCore).
  • Outdated: Pomelo.EntityFrameworkCore.MySql REDACTED:35 — Pomelo.EntityFrameworkCore.MySql 3.2.0 → 9.0.0 available (referenced by IEManageSystem.EntityFrameworkCore).
  • Outdated: Abp.TestBase test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:30 — Abp.TestBase 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Tests).
  • Outdated: Castle.Windsor.MsDependencyInjection test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:32 — Castle.Windsor.MsDependencyInjection 3.3.1 → 6.0.0 available (referenced by IEManageSystem.Tests).
  • Outdated: Microsoft.EntityFrameworkCore.InMemory test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:33 — Microsoft.EntityFrameworkCore.InMemory 3.0.0 → 10.0.13 available (referenced by IEManageSystem.Tests).
  • Outdated: Abp.AspNetCore.TestBase REDACTED:29 — Abp.AspNetCore.TestBase 5.0.0 → 10.5.1 available (referenced by IEManageSystem.Web.Tests).
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:11 — REDACTED → 10.0.13 available (referenced by IEManageSystem.JwtAuthentication).
  • Outdated: coverlet.collector test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj:16 — coverlet.collector 1.0.1 → 10.1.0 available (referenced by IEManageSystem.CommonInfrastructure.Tests).
DM5 · Encapsulated state · Mutable entity · ×20
  • Mutable entity: Permission src/IEManageSystem.Core/Entitys/Authorization/Permissions/Permission.cs:9 — `Permission` exposes publicly writable state (DisplayName, Describe).
  • Mutable entity: Role src/IEManageSystem.Core/Entitys/Authorization/Roles/Role.cs:11 — `Role` exposes publicly writable state (DisplayName, Describe, RolePermissions).
  • Mutable entity: RolePermission src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:10 — `RolePermission` exposes publicly writable state (RoleId, PermissionId, Permission).
  • Mutable entity: User src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:16 — `User` exposes publicly writable state (EmailAddress, Name, Phone, PersonSignature, RealName, IDNumber, and 5 more).
  • Mutable entity: UserRole src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:10 — `UserRole` exposes publicly writable state (Role).
  • Mutable entity: Account src/IEManageSystem.Core/Entitys/Authorization/Users/Accounts/Account.cs:11 — `Account` exposes publicly writable state (Password, SafetyProblem).
  • Mutable entity: ApiScope src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScope.cs:13 — `ApiScope` exposes publicly writable state (ApiManageScope, ApiQueryScope).
  • Mutable entity: ApiScopePermission src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:12 — `ApiScopePermission` exposes publicly writable state (ApiScopeId, PermissionId, Permission).
  • Mutable entity: ApiScopeNode src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs:11 — `ApiScopeNode` exposes publicly writable state (ApiScopePermissions).
  • Mutable entity: CmsComponent src/IEManageSystem.CMS/DomainModel/CmsComponent.cs:9 — `CmsComponent` exposes publicly writable state (Name).
  • Mutable entity: ComponentSingleData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:9 — `ComponentSingleData` exposes publicly writable state (Name, SortIndex, Field1, Field2, Field3, Field4, and 3 more).
  • Mutable entity: ContentComponentData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:11 — `ContentComponentData` exposes publicly writable state (Sign, SingleDatas, PageData, PageDataId).
  • Mutable entity: ContentPagePermission src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:10 — `ContentPagePermission` exposes publicly writable state (PermissionId, Permission, ContentPagePermissionCollectionId, ContentPagePermissionCollection, IsManage).
  • Mutable entity: ContentPagePermissionCollection src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:12 — `ContentPagePermissionCollection` exposes publicly writable state (IsEnableQueryPermission, ContentPagePermissions, PageName).
  • Mutable entity: Logic src/IEManageSystem.CMS/DomainModel/Logics/Logic.cs:8 — `Logic` exposes publicly writable state (Name, Code).
  • Mutable entity: CompositeMenu src/IEManageSystem.CMS/DomainModel/Menus/CompositeMenu.cs:7 — `CompositeMenu` exposes publicly writable state (Menus).
  • Mutable entity: MenuBase src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:11 — `MenuBase` exposes publicly writable state (Name, DisplayName, Icon, CompositeMenuId, RootMenuId, RootMenu, and 2 more).
  • Mutable entity: PageData src/IEManageSystem.CMS/DomainModel/PageDatas/PageData.cs:18 — `PageData` exposes publicly writable state (Name, Title, Describe, Content, Images, Field1, and 8 more).
  • Mutable entity: Tag src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:9 — `Tag` exposes publicly writable state (Name, DisplayName, PageData, PageDataId).
  • Mutable entity: SiteSetting src/IEManageSystem.Common/DomainModel/SiteSetting.cs:9 — `SiteSetting` exposes publicly writable state (Key, Value, DisplayName, Group).
DM2 · Strongly-typed ids · Primitive id on a domain type · ×15
  • Primitive id on a domain type: RolePermission.RoleId src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:13 — `RolePermission.RoleId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: RolePermission.PermissionId src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:15 — `RolePermission.PermissionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: User.TenantId src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:87 — `User.TenantId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: UserRole.UserId src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:25 — `UserRole.UserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: UserRole.RoleId src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:27 — `UserRole.RoleId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: ApiScopePermission.ApiScopeId src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:27 — `ApiScopePermission.ApiScopeId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: ApiScopePermission.PermissionId src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:29 — `ApiScopePermission.PermissionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: ComponentSingleData.ComponentDataId src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:25 — `ComponentSingleData.ComponentDataId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: ContentComponentData.PageDataId src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:24 — `ContentComponentData.PageDataId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: ContentPagePermission.PermissionId src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:12 — `ContentPagePermission.PermissionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: ContentPagePermission.ContentPagePermissionCollectionId src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:17 — `ContentPagePermission.ContentPagePermissionCollectionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: MenuBase.CompositeMenuId src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:28 — `MenuBase.CompositeMenuId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: MenuBase.RootMenuId src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:30 — `MenuBase.RootMenuId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: Tag.PageDataId src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:18 — `Tag.PageDataId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: SiteSetting.Key src/IEManageSystem.Common/DomainModel/SiteSetting.cs:11 — `SiteSetting.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.
X10 · Duplicated predicate · Duplicated predicate · ×11
  • Duplicated predicate src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:44 — `!AutoSaveChanges || _unitOfWorkManager.Current == null` appears character-identically in 2 files — src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs, src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.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 REDACTED:147 — `e.Name == input.PageDataName && e.PageName == input.PageName` appears character-identically in 2 files — src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs, 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 src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/RootComponentContainerBox/index.js:37 — `data.imageList.length > 0 && data.imageList[0]` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/RootComponentContainerBox/index.js, src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEPostList/IComponent.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js:95 — `ownProps.match.params.pageName || "Home"` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Home/PageContainer.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:18 — `platform === PLATFORM.IOS && (deviceHeight === 812 || deviceWidth === 812 || deviceHeight === 896 || deviceWidth === 896)` appears character-identically in 3 files — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js, src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js, src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Footer.js:105 — `platform === PLATFORM.IOS && platformStyle !== PLATFORM.MATERIAL` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Footer.js, src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:135 — `setting.hiddenPageing == false && this.footer()` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEPostList/Component.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Home/PageContainer.jsx:103 — `stateProps.isExistPage && stateProps.isExistPageData` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Home/PageContainer.jsx, src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PostEdit/index.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEButton/IComponent.js:38 — `this.props.interactivText || setting.text` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEButton/IComponent.js, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/Component.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:105 — `this.state.headSculpture === null || this.state.headSculpture === "" || this.state.headSculpture == undefined` appears character-identically in 2 files — src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx, src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:51 — `string.IsNullOrEmpty(input.SearchKey) || e.Name.Contains(input.SearchKey)` appears character-identically in 2 files — src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs, src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.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.
D30 · Dependency Vulnerabilities · Low CVE · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Commented-out code · ×3
  • Commented-out code src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/IMenuManageAppService.cs:13 — 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 src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/IMenuManageAppService.cs:15 — 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 src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:56 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
R7 · Dead Code · Unused export 'default' · ×2
  • Unused export 'default' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:24 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/index.js:13 — Nothing imports this binding — it is safe to review for removal.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 193 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.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 15 project(s) overshoot their size bounds, lowering Project Cohesion to 8.7/10. The most over is `IEManageSystem.Application` (3967 LoC, 191 public types across 32 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 41 of 41 significant files have no living knowledge — the codebase as a whole is dormant, not 41 separate risks. Counted over 41 of the 336 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 src/UtilityAction/Web/FileContentType.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: 3 authored method(s) exceed the IL budget src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataQueryAppService.cs:53 — 3 of 614 first-party methods compile to oversized IL bodies (> 250 instructions); worst: IEManageSystem.Services.ManageHome.CMS.Pages.PageDataQueryAppService.GetPageDatas @ src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataQueryAppService.cs:53, 439 IL instructions; that pulled this dimension to 9.9/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.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 269/269 types (100%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — 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 release approval gate · ×1
  • No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
PF2 · Allocation hygiene · No allocation-aware APIs detected · ×1
  • No allocation-aware APIs detected — No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.
R7 · Dead Code · Unused export 'ContainerSettingName' · ×1
  • Unused export 'ContainerSettingName' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ComponentContainer.js:4 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused module-local declaration 'locale' · ×1
  • Unused module-local declaration 'locale' src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:142 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
S1 · Web-Security Posture · No security response headers detected · ×1
  • 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.)
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • 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.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 0/11 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 · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/10 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 17 finding(s)
D12 · Dependency Hygiene · Outdated · ×15
  • Outdated: Castle.Core — Castle.Core 4.4.0 → 5.2.1 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.Diagnostics — Microsoft.AspNetCore.Diagnostics 2.2.0 → 2.3.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.Mvc — Microsoft.AspNetCore.Mvc 2.2.0 → 2.3.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.Server.IISIntegration — Microsoft.AspNetCore.Server.IISIntegration 2.2.1 → 2.3.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.Server.Kestrel — Microsoft.AspNetCore.Server.Kestrel 2.2.0 → 2.3.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.AspNetCore.StaticFiles — Microsoft.AspNetCore.StaticFiles 2.2.0 → 2.3.13 available (referenced by IEManageSystem.Web).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 16.2.0 → 18.11.0 available (referenced by IEManageSystem.Tests).
  • Outdated: NSubstitute — NSubstitute 4.2.0 → 6.2.0 available (referenced by IEManageSystem.Tests).
  • Outdated: Shouldly — Shouldly 3.0.2 → 4.3.0 available (referenced by IEManageSystem.Tests).
  • Outdated: xunit — xunit 2.4.1 → 2.9.3 available (referenced by IEManageSystem.Tests).
  • Outdated: xunit.extensibility.execution — xunit.extensibility.execution 2.4.1 → 2.9.3 available (referenced by IEManageSystem.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.4.1 → 4.0.1 available (referenced by IEManageSystem.Tests).
  • Outdated: AngleSharp — REDACTED → 1.8.5 available (referenced by IEManageSystem.Web.Tests).
  • Outdated: Microsoft.AspNetCore.Authentication — Microsoft.AspNetCore.Authentication 2.2.0 → 2.3.13 available (referenced by IEManageSystem.JwtAuthentication).
  • Outdated: Microsoft.CodeAnalysis.CSharp — Microsoft.CodeAnalysis.CSharp 3.3.1 → 5.9.0 available (referenced by IEManageSystem.CommonInfrastructure).
D10 · Test Quality · Mock framework · ×1
  • Mock framework: NSubstitute — IEManageSystem.Tests references NSubstitute.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: IEManageSystem.Common src/IEManageSystem.Common/IEManageSystem.Common.csproj:1 — IEManageSystem.Common: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

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-25c839c36b4c43398ee18490d5aed51d/history.json --exit-code 0 --source .1artifacts/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-25c839c36b4c43398ee18490d5aed51d/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 .25artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list IEManageSystem.sln package --vulnerable --include-transitive --format json152artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.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 01a16080-807e-73f6-b224-21c85673b470 · 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 — 19 field(s) across 4 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.

Email — 8 field(s)
  • UserDto.EmailAddress src/IEManageSystem.Application/Dtos/Core/Users/UserDto.cs:19
  • RegisterInput.EmailAddress src/IEManageSystem.Application/Services/Accounts/Dto/RegisterInput.cs:21
  • CreateAdminInput.EmailAddress src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/Dto/CreateAdminInput.cs:30
  • UpdateAdminInput.EmailAddress src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/Dto/UpdateAdminInput.cs:21
  • SetUserInfoInput.EmailAddress src/IEManageSystem.Application/Services/Users/Dto/SetUserInfoInput.cs:14
  • IdentityUser.EmailAddress src/IEManageSystem.Core/Entitys/Authorization/Identitys/IdentityUser.cs:16
  • User.EmailAddress src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:33
  • UserClaimInfo.EmailAddress src/IEManageSystem.JwtAuthentication/Model/UserClaimInfo.cs:20
Phone — 7 field(s)
  • UserDto.Phone src/IEManageSystem.Application/Dtos/Core/Users/UserDto.cs:29
  • CreateAdminInput.Phone src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/Dto/CreateAdminInput.cs:42
  • UpdateAdminInput.Phone src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/Dto/UpdateAdminInput.cs:33
  • SetUserInfoInput.Phone src/IEManageSystem.Application/Services/Users/Dto/SetUserInfoInput.cs:26
  • IdentityUser.Phone src/IEManageSystem.Core/Entitys/Authorization/Identitys/IdentityUser.cs:23
  • User.Phone src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:45
  • UserClaimInfo.Phone src/IEManageSystem.JwtAuthentication/Model/UserClaimInfo.cs:24
Date of birth — 3 field(s)
  • UserDto.BirthDate src/IEManageSystem.Application/Dtos/Core/Users/UserDto.cs:64
  • SetUserInfoInput.BirthDate src/IEManageSystem.Application/Services/Users/Dto/SetUserInfoInput.cs:61
  • User.BirthDate src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:80
Name — 1 field(s)
  • RegisterInput.Surname src/IEManageSystem.Application/Services/Accounts/Dto/RegisterInput.cs:14

Issues: 175 · Warnings: 477 · Recommendations: 224 · Info: 17 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 22:06 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