Executive summary
IceEmblem/IEManageSystem is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no encryption of stored data, no key vault and no enforced HTTPS and no access checks on the code's endpoints or handlers. It scores 21 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 10, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 7 points. Encrypting the sensitive stored data and keeping its keys in a vault would lift Security and Compliance itself, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 30.
108 known security holes in the packages the code depends on can be used by attackers. Three passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Updating the vulnerable packages and replacing each exposed password or key would close both risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the place where passwords are scrambled with a fast general-purpose hash. The 25 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 38,381 lines, about €37,000 to rebuild.
If Security and Compliance rose from 10 to 70, the lowest score rated Strong, the score would rise from 21 to about 30.
New since the last survey: 69 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.ApiAuthorization/IEManageSystem.ApiAuthorization.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.CMS/IEManageSystem.CMS.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.Common/IEManageSystem.Common.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.CommonInfrastructure/IEManageSystem.CommonInfrastructure.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.Core/IEManageSystem.Core.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 src/UtilityAction/UtilityAction.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.Application.Tests/IEManageSystem.Application.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.CommonInfrastructure.Tests/IEManageSystem.CommonInfrastructure.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.Tests/IEManageSystem.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 REDACTED
- Stateful singletons · Process-global static state: WebConfiguration src/IEManageSystem.Web/Configuration/WebConfiguration.cs
- Rich vs anemic model · Anemic entity: ApiScope src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScope.cs
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAudio/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECard/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/SettingConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx
- Forms & labels · <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx
- Page structure · Text directly inside a table row src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx
- Page structure · Text directly inside a table row src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx
Fixed since the last survey: 814 findings
- God Classes · MethodTooLong: SettingConfig.render src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/SettingConfig.jsx
- God Classes · MethodTooLong: SettingConfig.render src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx
- Dependency Hygiene · Vulnerable: AngleSharp
- Dependency Hygiene · Vulnerable: Microsoft.AspNetCore.Authentication.JwtBearer
- 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
- Boundary Type-Coupling · Cross-context type ContentComponentData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs
- Boundary Type-Coupling · Cross-context type PageData (IEManageSystem.CMS → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs
- Boundary Type-Coupling · Cross-context type User (IEManageSystem.Core → IEManageSystem.CommonInfrastructure) src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js REDACTED
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ToolLibrary/IETool.ts
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: 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
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.0 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
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 problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 21. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 38,381 lines of product code |
| Comment lines | The estimate prices 37,691 lines. Comment lines count towards the size of 38,381 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 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.Menus | 15 IEManageSystem.Entitys.Authorization.Roles | 16 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig | 17 IEManageSystem.Entitys.Authorization.Users | 18 IEManageSystem.CMS.DomainModel.PageDatas | 19 IEManageSystem.CMS.DomainModel.Pages | 20 IEManageSystem.CMS.DomainModel.ComponentDatas | 21 IEManageSystem.CMS.DomainModel | 22 IEManageSystem.CMS.DomainModel.Logics | 23 IEManageSystem.Configures.CMS | 24 IEManageSystem.CommonInfrastructure.CMS | 25 IEManageSystem.EntityFrameworkCore | 26 IEManageSystem.Repositorys | 27 IEManageSystem.Entitys.Authorization.Permissions | 28 IEManageSystem.Services.ManageHome.CMS.Menus | 29 IEManageSystem.Services.ManageHome.CMS.Pages | 30 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes | 31 IEManageSystem.Configures.Core | 32 IEManageSystem.Entitys.Authorization.LoginManagers | 33 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins | 34 IEManageSystem.Services.ManageHome.AuthorizeManage.Roles | 35 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes | 36 IEManageSystem.Services.Accounts | 37 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes | 38 IEManageSystem.Web.Controllers | 39 IEManageSystem.Web.Controllers.CMS.Logics | 40 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.Menus | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 IEManageSystem.Entitys.Authorization.Roles | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 IEManageSystem.Entitys.Authorization.Users | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 IEManageSystem.CMS.DomainModel.PageDatas | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 IEManageSystem.CMS.DomainModel.Pages | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 20 IEManageSystem.CMS.DomainModel.ComponentDatas | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 IEManageSystem.CMS.DomainModel | 2 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 22 IEManageSystem.CMS.DomainModel.Logics | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 23 IEManageSystem.Configures.CMS | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 IEManageSystem.CommonInfrastructure.CMS | 3 | 3 | 3 | 3 | 4 | |||||||||||||||||||||||||||||||||||
| 25 IEManageSystem.EntityFrameworkCore | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 26 IEManageSystem.Repositorys | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 IEManageSystem.Entitys.Authorization.Permissions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 IEManageSystem.Services.ManageHome.CMS.Menus | 2 | 2 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 29 IEManageSystem.Services.ManageHome.CMS.Pages | 4 | 2 | 2 | 4 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 30 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 IEManageSystem.Configures.Core | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 IEManageSystem.Entitys.Authorization.LoginManagers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 IEManageSystem.Services.ManageHome.AuthorizeManage.Roles | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 IEManageSystem.Services.Accounts | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 IEManageSystem.Web.Controllers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 IEManageSystem.Web.Controllers.CMS.Logics | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 IEManageSystem.Web.Controllers.CMS.Pages | 2 | 1 | 2 | 3 | 2 | 2 |
14→5 IEManageSystem.CMS.DomainModel.Menus uses IEManageSystem.Web✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.Menus uses a type in IEManageSystem.Web.
- The types involved
IEManageSystem.CMS.DomainModel.Menus.MenuManager→IEManageSystem.Web.IIEMemoryCache
- Direction
- IEManageSystem.CMS.DomainModel.Menus uses IEManageSystem.Web, so a change to IEManageSystem.Web can break IEManageSystem.CMS.DomainModel.Menus, while a change to IEManageSystem.CMS.DomainModel.Menus can't break IEManageSystem.Web.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Menus uses a module listed above it, which is the healthy direction.
14→26 IEManageSystem.CMS.DomainModel.Menus uses IEManageSystem.Repositorys part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.Menus uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.CMS.DomainModel.Menus.MenuManager→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.CMS.DomainModel.Menus uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.CMS.DomainModel.Menus, while a change to IEManageSystem.CMS.DomainModel.Menus can't break IEManageSystem.Repositorys.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→27 IEManageSystem.Entitys.Authorization.Roles uses IEManageSystem.Entitys.Authorization.Permissions part of a loop✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.Entitys.Authorization.Roles uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Entitys.Authorization.Roles.Role→IEManageSystem.Entitys.Authorization.Permissions.PermissionIEManageSystem.Entitys.Authorization.Roles.RoleManager→IEManageSystem.Entitys.Authorization.Permissions.PermissionIEManageSystem.Entitys.Authorization.Roles.RolePermission→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.Entitys.Authorization.Roles uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Entitys.Authorization.Roles, while a change to IEManageSystem.Entitys.Authorization.Roles can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→8 src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig uses src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig✕
- Connections
- 1 pair of types, where a type in src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig uses a type in src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig.
- The types involved
src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig.BaseComponentSettingConfig→src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig.IEditConfig
- Direction
- src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig uses src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig, so a change to src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig can break src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig, while a change to src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig can't break src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.IEditConfig.
- Position
- Below the diagonal: src.IEManageSystem_Web.ClientApp.src.Common.BaseCMSManage.Components.BaseComponents.BaseComponent.BaseComponentSettingConfig uses a module listed above it, which is the healthy direction.
17→15 IEManageSystem.Entitys.Authorization.Users uses IEManageSystem.Entitys.Authorization.Roles✕
- Connections
- 6 pairs of types, where a type in IEManageSystem.Entitys.Authorization.Users uses a type in IEManageSystem.Entitys.Authorization.Roles.
- The types involved
IEManageSystem.Entitys.Authorization.Users.AdminManager→IEManageSystem.Entitys.Authorization.Roles.RoleIEManageSystem.Entitys.Authorization.Users.AdminManager→IEManageSystem.Entitys.Authorization.Roles.RoleManagerIEManageSystem.Entitys.Authorization.Users.User→IEManageSystem.Entitys.Authorization.Roles.RoleIEManageSystem.Entitys.Authorization.Users.UserManager→IEManageSystem.Entitys.Authorization.Roles.RoleIEManageSystem.Entitys.Authorization.Users.UserManager→IEManageSystem.Entitys.Authorization.Roles.RoleManagerIEManageSystem.Entitys.Authorization.Users.UserRole→IEManageSystem.Entitys.Authorization.Roles.Role
- Direction
- IEManageSystem.Entitys.Authorization.Users uses IEManageSystem.Entitys.Authorization.Roles, so a change to IEManageSystem.Entitys.Authorization.Roles can break IEManageSystem.Entitys.Authorization.Users, while a change to IEManageSystem.Entitys.Authorization.Users can't break IEManageSystem.Entitys.Authorization.Roles.
- Position
- Below the diagonal: IEManageSystem.Entitys.Authorization.Users uses a module listed above it, which is the healthy direction.
17→26 IEManageSystem.Entitys.Authorization.Users uses IEManageSystem.Repositorys part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Entitys.Authorization.Users uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.Entitys.Authorization.Users.UserManager→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.Entitys.Authorization.Users uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.Entitys.Authorization.Users, while a change to IEManageSystem.Entitys.Authorization.Users can't break IEManageSystem.Repositorys.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→17 IEManageSystem.CMS.DomainModel.PageDatas uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.PageDatas uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.CMS.DomainModel.PageDatas.PageDataManager→IEManageSystem.Entitys.Authorization.Users.User
- Direction
- IEManageSystem.CMS.DomainModel.PageDatas uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.CMS.DomainModel.PageDatas, while a change to IEManageSystem.CMS.DomainModel.PageDatas can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.PageDatas uses a module listed above it, which is the healthy direction.
18→21 IEManageSystem.CMS.DomainModel.PageDatas uses IEManageSystem.CMS.DomainModel part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.PageDatas uses a type in IEManageSystem.CMS.DomainModel.
- The types involved
IEManageSystem.CMS.DomainModel.PageDatas.PageData→IEManageSystem.CMS.DomainModel.EntityEdit
- Direction
- IEManageSystem.CMS.DomainModel.PageDatas uses IEManageSystem.CMS.DomainModel, so a change to IEManageSystem.CMS.DomainModel can break IEManageSystem.CMS.DomainModel.PageDatas, while a change to IEManageSystem.CMS.DomainModel.PageDatas can't break IEManageSystem.CMS.DomainModel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→26 IEManageSystem.CMS.DomainModel.PageDatas uses IEManageSystem.Repositorys part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.PageDatas uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.CMS.DomainModel.PageDatas.PageDataManager→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.CMS.DomainModel.PageDatas uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.CMS.DomainModel.PageDatas, while a change to IEManageSystem.CMS.DomainModel.PageDatas can't break IEManageSystem.Repositorys.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→5 IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.Web✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.Pages uses a type in IEManageSystem.Web.
- The types involved
IEManageSystem.CMS.DomainModel.Pages.PageManager→IEManageSystem.Web.IIEMemoryCache
- Direction
- IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.Web, so a change to IEManageSystem.Web can break IEManageSystem.CMS.DomainModel.Pages, while a change to IEManageSystem.CMS.DomainModel.Pages can't break IEManageSystem.Web.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Pages uses a module listed above it, which is the healthy direction.
19→17 IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.Pages uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.CMS.DomainModel.Pages.PageManager→IEManageSystem.Entitys.Authorization.Users.User
- Direction
- IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.CMS.DomainModel.Pages, while a change to IEManageSystem.CMS.DomainModel.Pages can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Pages uses a module listed above it, which is the healthy direction.
19→21 IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.CMS.DomainModel part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.Pages uses a type in IEManageSystem.CMS.DomainModel.
- The types involved
IEManageSystem.CMS.DomainModel.Pages.Page→IEManageSystem.CMS.DomainModel.EntityEdit
- Direction
- IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.CMS.DomainModel, so a change to IEManageSystem.CMS.DomainModel can break IEManageSystem.CMS.DomainModel.Pages, while a change to IEManageSystem.CMS.DomainModel.Pages can't break IEManageSystem.CMS.DomainModel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→27 IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.Entitys.Authorization.Permissions part of a loop✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.CMS.DomainModel.Pages uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.CMS.DomainModel.Pages.ContentPagePermission→IEManageSystem.Entitys.Authorization.Permissions.PermissionIEManageSystem.CMS.DomainModel.Pages.ContentPagePermissionCollection→IEManageSystem.Entitys.Authorization.Permissions.PermissionIEManageSystem.CMS.DomainModel.Pages.PageManager→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.CMS.DomainModel.Pages uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.CMS.DomainModel.Pages, while a change to IEManageSystem.CMS.DomainModel.Pages can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→5 IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.Web✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.ComponentDatas uses a type in IEManageSystem.Web.
- The types involved
IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManager→IEManageSystem.Web.IIEMemoryCache
- Direction
- IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.Web, so a change to IEManageSystem.Web can break IEManageSystem.CMS.DomainModel.ComponentDatas, while a change to IEManageSystem.CMS.DomainModel.ComponentDatas can't break IEManageSystem.Web.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.ComponentDatas uses a module listed above it, which is the healthy direction.
20→18 IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.CMS.DomainModel.ComponentDatas uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManager→IEManageSystem.CMS.DomainModel.PageDatas.PageDataIEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData→IEManageSystem.CMS.DomainModel.PageDatas.PageData
- Direction
- IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.CMS.DomainModel.ComponentDatas, while a change to IEManageSystem.CMS.DomainModel.ComponentDatas can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.ComponentDatas uses a module listed above it, which is the healthy direction.
20→21 IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.CMS.DomainModel part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.ComponentDatas uses a type in IEManageSystem.CMS.DomainModel.
- The types involved
IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentSingleData→IEManageSystem.CMS.DomainModel.ISingleData
- Direction
- IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.CMS.DomainModel, so a change to IEManageSystem.CMS.DomainModel can break IEManageSystem.CMS.DomainModel.ComponentDatas, while a change to IEManageSystem.CMS.DomainModel.ComponentDatas can't break IEManageSystem.CMS.DomainModel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→26 IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.Repositorys part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel.ComponentDatas uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManager→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.CMS.DomainModel.ComponentDatas uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.CMS.DomainModel.ComponentDatas, while a change to IEManageSystem.CMS.DomainModel.ComponentDatas can't break IEManageSystem.Repositorys.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→17 IEManageSystem.CMS.DomainModel uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.CMS.DomainModel uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.CMS.DomainModel.DeletePageDataService→IEManageSystem.Entitys.Authorization.Users.UserIEManageSystem.CMS.DomainModel.UpdateContentComponentDataService→IEManageSystem.Entitys.Authorization.Users.User
- Direction
- IEManageSystem.CMS.DomainModel uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.CMS.DomainModel, while a change to IEManageSystem.CMS.DomainModel can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel uses a module listed above it, which is the healthy direction.
21→18 IEManageSystem.CMS.DomainModel uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 4 pairs of types, where a type in IEManageSystem.CMS.DomainModel uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.CMS.DomainModel.DeletePageDataService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataIEManageSystem.CMS.DomainModel.DeletePageDataService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataManagerIEManageSystem.CMS.DomainModel.UpdateContentComponentDataService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataIEManageSystem.CMS.DomainModel.UpdateContentComponentDataService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataManager
- Direction
- IEManageSystem.CMS.DomainModel uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.CMS.DomainModel, while a change to IEManageSystem.CMS.DomainModel can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel uses a module listed above it, which is the healthy direction.
21→19 IEManageSystem.CMS.DomainModel uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 1 pair of types, where a type in IEManageSystem.CMS.DomainModel uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.CMS.DomainModel.DeletePageService→IEManageSystem.CMS.DomainModel.Pages.PageManager
- Direction
- IEManageSystem.CMS.DomainModel uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.CMS.DomainModel, while a change to IEManageSystem.CMS.DomainModel can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel uses a module listed above it, which is the healthy direction.
21→20 IEManageSystem.CMS.DomainModel uses IEManageSystem.CMS.DomainModel.ComponentDatas✕
- Connections
- 4 pairs of types, where a type in IEManageSystem.CMS.DomainModel uses a type in IEManageSystem.CMS.DomainModel.ComponentDatas.
- The types involved
IEManageSystem.CMS.DomainModel.DeletePageDataService→IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManagerIEManageSystem.CMS.DomainModel.DeletePageService→IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManagerIEManageSystem.CMS.DomainModel.UpdateContentComponentDataService→IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManagerIEManageSystem.CMS.DomainModel.UpdateContentComponentDataService→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData
- Direction
- IEManageSystem.CMS.DomainModel uses IEManageSystem.CMS.DomainModel.ComponentDatas, so a change to IEManageSystem.CMS.DomainModel.ComponentDatas can break IEManageSystem.CMS.DomainModel, while a change to IEManageSystem.CMS.DomainModel can't break IEManageSystem.CMS.DomainModel.ComponentDatas.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel uses a module listed above it, which is the healthy direction.
22→17 IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.CMS.DomainModel.Logics uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.CMS.DomainModel.Logics.ExecLogicService→IEManageSystem.Entitys.Authorization.Users.UserManagerIEManageSystem.CMS.DomainModel.Logics.IActuator→IEManageSystem.Entitys.Authorization.Users.User
- Direction
- IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.CMS.DomainModel.Logics, while a change to IEManageSystem.CMS.DomainModel.Logics can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Logics uses a module listed above it, which is the healthy direction.
22→18 IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.CMS.DomainModel.Logics uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.CMS.DomainModel.Logics.ExecLogicService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataManagerIEManageSystem.CMS.DomainModel.Logics.IActuator→IEManageSystem.CMS.DomainModel.PageDatas.PageData
- Direction
- IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.CMS.DomainModel.Logics, while a change to IEManageSystem.CMS.DomainModel.Logics can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Logics uses a module listed above it, which is the healthy direction.
22→19 IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.CMS.DomainModel.Logics uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.CMS.DomainModel.Logics.ExecLogicService→IEManageSystem.CMS.DomainModel.Pages.PageManagerIEManageSystem.CMS.DomainModel.Logics.IActuator→IEManageSystem.CMS.DomainModel.Pages.Page
- Direction
- IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.CMS.DomainModel.Logics, while a change to IEManageSystem.CMS.DomainModel.Logics can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Logics uses a module listed above it, which is the healthy direction.
22→20 IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.CMS.DomainModel.ComponentDatas✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.CMS.DomainModel.Logics uses a type in IEManageSystem.CMS.DomainModel.ComponentDatas.
- The types involved
IEManageSystem.CMS.DomainModel.Logics.ExecLogicService→IEManageSystem.CMS.DomainModel.ComponentDatas.ComponentDataManagerIEManageSystem.CMS.DomainModel.Logics.IActuator→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData
- Direction
- IEManageSystem.CMS.DomainModel.Logics uses IEManageSystem.CMS.DomainModel.ComponentDatas, so a change to IEManageSystem.CMS.DomainModel.ComponentDatas can break IEManageSystem.CMS.DomainModel.Logics, while a change to IEManageSystem.CMS.DomainModel.Logics can't break IEManageSystem.CMS.DomainModel.ComponentDatas.
- Position
- Below the diagonal: IEManageSystem.CMS.DomainModel.Logics uses a module listed above it, which is the healthy direction.
23→14 IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.Menus✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.Configures.CMS uses a type in IEManageSystem.CMS.DomainModel.Menus.
- The types involved
IEManageSystem.Configures.CMS.CompositeMenuConfigure→IEManageSystem.CMS.DomainModel.Menus.CompositeMenuIEManageSystem.Configures.CMS.LeafMenuConfigure→IEManageSystem.CMS.DomainModel.Menus.LeafMenuIEManageSystem.Configures.CMS.MenuBaseConfigure→IEManageSystem.CMS.DomainModel.Menus.MenuBase
- Direction
- IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.Menus, so a change to IEManageSystem.CMS.DomainModel.Menus can break IEManageSystem.Configures.CMS, while a change to IEManageSystem.Configures.CMS can't break IEManageSystem.CMS.DomainModel.Menus.
- Position
- Below the diagonal: IEManageSystem.Configures.CMS uses a module listed above it, which is the healthy direction.
23→18 IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Configures.CMS uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.Configures.CMS.PageDataConfigure→IEManageSystem.CMS.DomainModel.PageDatas.PageData
- Direction
- IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.Configures.CMS, while a change to IEManageSystem.Configures.CMS can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.Configures.CMS uses a module listed above it, which is the healthy direction.
23→19 IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Configures.CMS uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.Configures.CMS.ContentPagePeimissionCollectionConfigure→IEManageSystem.CMS.DomainModel.Pages.ContentPagePermissionCollection
- Direction
- IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.Configures.CMS, while a change to IEManageSystem.Configures.CMS can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.Configures.CMS uses a module listed above it, which is the healthy direction.
23→20 IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.ComponentDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Configures.CMS uses a type in IEManageSystem.CMS.DomainModel.ComponentDatas.
- The types involved
IEManageSystem.Configures.CMS.ComponentDataConfigure→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData
- Direction
- IEManageSystem.Configures.CMS uses IEManageSystem.CMS.DomainModel.ComponentDatas, so a change to IEManageSystem.CMS.DomainModel.ComponentDatas can break IEManageSystem.Configures.CMS, while a change to IEManageSystem.Configures.CMS can't break IEManageSystem.CMS.DomainModel.ComponentDatas.
- Position
- Below the diagonal: IEManageSystem.Configures.CMS uses a module listed above it, which is the healthy direction.
24→17 IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.CommonInfrastructure.CMS uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.CommonInfrastructure.CMS.Actuator→IEManageSystem.Entitys.Authorization.Users.UserIEManageSystem.CommonInfrastructure.CMS.BaseActuator→IEManageSystem.Entitys.Authorization.Users.UserIEManageSystem.CommonInfrastructure.CMS.WriteLogicCodeFile→IEManageSystem.Entitys.Authorization.Users.User
- Direction
- IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.CommonInfrastructure.CMS, while a change to IEManageSystem.CommonInfrastructure.CMS can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.CommonInfrastructure.CMS uses a module listed above it, which is the healthy direction.
24→18 IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.CommonInfrastructure.CMS uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.CommonInfrastructure.CMS.Actuator→IEManageSystem.CMS.DomainModel.PageDatas.PageDataIEManageSystem.CommonInfrastructure.CMS.BaseActuator→IEManageSystem.CMS.DomainModel.PageDatas.PageDataIEManageSystem.CommonInfrastructure.CMS.WriteLogicCodeFile→IEManageSystem.CMS.DomainModel.PageDatas.PageData
- Direction
- IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.CommonInfrastructure.CMS, while a change to IEManageSystem.CommonInfrastructure.CMS can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.CommonInfrastructure.CMS uses a module listed above it, which is the healthy direction.
24→19 IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.CommonInfrastructure.CMS uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.CommonInfrastructure.CMS.Actuator→IEManageSystem.CMS.DomainModel.Pages.PageIEManageSystem.CommonInfrastructure.CMS.BaseActuator→IEManageSystem.CMS.DomainModel.Pages.PageIEManageSystem.CommonInfrastructure.CMS.WriteLogicCodeFile→IEManageSystem.CMS.DomainModel.Pages.Page
- Direction
- IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.CommonInfrastructure.CMS, while a change to IEManageSystem.CommonInfrastructure.CMS can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.CommonInfrastructure.CMS uses a module listed above it, which is the healthy direction.
24→20 IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.ComponentDatas✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.CommonInfrastructure.CMS uses a type in IEManageSystem.CMS.DomainModel.ComponentDatas.
- The types involved
IEManageSystem.CommonInfrastructure.CMS.Actuator→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentDataIEManageSystem.CommonInfrastructure.CMS.BaseActuator→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentDataIEManageSystem.CommonInfrastructure.CMS.WriteLogicCodeFile→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData
- Direction
- IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.ComponentDatas, so a change to IEManageSystem.CMS.DomainModel.ComponentDatas can break IEManageSystem.CommonInfrastructure.CMS, while a change to IEManageSystem.CommonInfrastructure.CMS can't break IEManageSystem.CMS.DomainModel.ComponentDatas.
- Position
- Below the diagonal: IEManageSystem.CommonInfrastructure.CMS uses a module listed above it, which is the healthy direction.
24→22 IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.Logics✕
- Connections
- 4 pairs of types, where a type in IEManageSystem.CommonInfrastructure.CMS uses a type in IEManageSystem.CMS.DomainModel.Logics.
- The types involved
IEManageSystem.CommonInfrastructure.CMS.Actuator→IEManageSystem.CMS.DomainModel.Logics.IActuatorIEManageSystem.CommonInfrastructure.CMS.ActuatorFactory→IEManageSystem.CMS.DomainModel.Logics.IActuatorIEManageSystem.CommonInfrastructure.CMS.ActuatorFactory→IEManageSystem.CMS.DomainModel.Logics.IActuatorFactoryIEManageSystem.CommonInfrastructure.CMS.BaseActuator→IEManageSystem.CMS.DomainModel.Logics.IActuator
- Direction
- IEManageSystem.CommonInfrastructure.CMS uses IEManageSystem.CMS.DomainModel.Logics, so a change to IEManageSystem.CMS.DomainModel.Logics can break IEManageSystem.CommonInfrastructure.CMS, while a change to IEManageSystem.CommonInfrastructure.CMS can't break IEManageSystem.CMS.DomainModel.Logics.
- Position
- Below the diagonal: IEManageSystem.CommonInfrastructure.CMS uses a module listed above it, which is the healthy direction.
25→14 IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.Menus✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.CMS.DomainModel.Menus.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.CMS.DomainModel.Menus.MenuBase
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.Menus, so a change to IEManageSystem.CMS.DomainModel.Menus can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.CMS.DomainModel.Menus.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→15 IEManageSystem.EntityFrameworkCore uses IEManageSystem.Entitys.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.Entitys.Authorization.Roles.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.Entitys.Authorization.Roles.Role
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.Entitys.Authorization.Roles, so a change to IEManageSystem.Entitys.Authorization.Roles can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.Entitys.Authorization.Roles.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→17 IEManageSystem.EntityFrameworkCore uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.Entitys.Authorization.Users.User
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→18 IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.CMS.DomainModel.PageDatas.PageData
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→19 IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.CMS.DomainModel.Pages.ContentPagePermissionCollection
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→20 IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.ComponentDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.CMS.DomainModel.ComponentDatas.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.ComponentDatas, so a change to IEManageSystem.CMS.DomainModel.ComponentDatas can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.CMS.DomainModel.ComponentDatas.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→21 IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.CMS.DomainModel.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.CMS.DomainModel.CmsComponent
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel, so a change to IEManageSystem.CMS.DomainModel can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.CMS.DomainModel.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→22 IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.Logics✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.CMS.DomainModel.Logics.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.CMS.DomainModel.Logics.Logic
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.CMS.DomainModel.Logics, so a change to IEManageSystem.CMS.DomainModel.Logics can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.CMS.DomainModel.Logics.
- Position
- Below the diagonal: IEManageSystem.EntityFrameworkCore uses a module listed above it, which is the healthy direction.
25→27 IEManageSystem.EntityFrameworkCore uses IEManageSystem.Entitys.Authorization.Permissions part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→35 IEManageSystem.EntityFrameworkCore uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.EntityFrameworkCore uses a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.
- The types involved
IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext→IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScope
- Direction
- IEManageSystem.EntityFrameworkCore uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, so a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can break IEManageSystem.EntityFrameworkCore, while a change to IEManageSystem.EntityFrameworkCore can't break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→25 IEManageSystem.Repositorys uses IEManageSystem.EntityFrameworkCore✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Repositorys uses a type in IEManageSystem.EntityFrameworkCore.
- The types involved
IEManageSystem.Repositorys.EfRepository→IEManageSystem.EntityFrameworkCore.IEManageSystemDbContextIEManageSystem.Repositorys.EfRepositoryBase→IEManageSystem.EntityFrameworkCore.IEManageSystemDbContext
- Direction
- IEManageSystem.Repositorys uses IEManageSystem.EntityFrameworkCore, so a change to IEManageSystem.EntityFrameworkCore can break IEManageSystem.Repositorys, while a change to IEManageSystem.Repositorys can't break IEManageSystem.EntityFrameworkCore.
- Position
- Below the diagonal: IEManageSystem.Repositorys uses a module listed above it, which is the healthy direction.
27→5 IEManageSystem.Entitys.Authorization.Permissions uses IEManageSystem.Web✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Entitys.Authorization.Permissions uses a type in IEManageSystem.Web.
- The types involved
IEManageSystem.Entitys.Authorization.Permissions.PermissionManager→IEManageSystem.Web.IIEMemoryCache
- Direction
- IEManageSystem.Entitys.Authorization.Permissions uses IEManageSystem.Web, so a change to IEManageSystem.Web can break IEManageSystem.Entitys.Authorization.Permissions, while a change to IEManageSystem.Entitys.Authorization.Permissions can't break IEManageSystem.Web.
- Position
- Below the diagonal: IEManageSystem.Entitys.Authorization.Permissions uses a module listed above it, which is the healthy direction.
27→26 IEManageSystem.Entitys.Authorization.Permissions uses IEManageSystem.Repositorys✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Entitys.Authorization.Permissions uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.Entitys.Authorization.Permissions.PermissionManager→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.Entitys.Authorization.Permissions uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.Entitys.Authorization.Permissions, while a change to IEManageSystem.Entitys.Authorization.Permissions can't break IEManageSystem.Repositorys.
- Position
- Below the diagonal: IEManageSystem.Entitys.Authorization.Permissions uses a module listed above it, which is the healthy direction.
28→1 IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Menus uses a type in IEManageSystem.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Menus.MenuAppService→IEManageSystem.IEManageSystemAppServiceBaseIEManageSystem.Services.ManageHome.CMS.Menus.MenuManageAppService→IEManageSystem.IEManageSystemAppServiceBase
- Direction
- IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem, so a change to IEManageSystem can break IEManageSystem.Services.ManageHome.CMS.Menus, while a change to IEManageSystem.Services.ManageHome.CMS.Menus can't break IEManageSystem.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Menus uses a module listed above it, which is the healthy direction.
28→2 IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.Dtos.CMS✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Menus uses a type in IEManageSystem.Dtos.CMS.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Menus.MenuAppService→IEManageSystem.Dtos.CMS.MenuDtoIEManageSystem.Services.ManageHome.CMS.Menus.MenuManageAppService→IEManageSystem.Dtos.CMS.MenuDto
- Direction
- IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.Dtos.CMS, so a change to IEManageSystem.Dtos.CMS can break IEManageSystem.Services.ManageHome.CMS.Menus, while a change to IEManageSystem.Services.ManageHome.CMS.Menus can't break IEManageSystem.Dtos.CMS.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Menus uses a module listed above it, which is the healthy direction.
28→14 IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.CMS.DomainModel.Menus✕
- Connections
- 4 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Menus uses a type in IEManageSystem.CMS.DomainModel.Menus.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Menus.MenuAppService→IEManageSystem.CMS.DomainModel.Menus.MenuBaseIEManageSystem.Services.ManageHome.CMS.Menus.MenuAppService→IEManageSystem.CMS.DomainModel.Menus.MenuManagerIEManageSystem.Services.ManageHome.CMS.Menus.MenuManageAppService→IEManageSystem.CMS.DomainModel.Menus.MenuBaseIEManageSystem.Services.ManageHome.CMS.Menus.MenuManageAppService→IEManageSystem.CMS.DomainModel.Menus.MenuManager
- Direction
- IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.CMS.DomainModel.Menus, so a change to IEManageSystem.CMS.DomainModel.Menus can break IEManageSystem.Services.ManageHome.CMS.Menus, while a change to IEManageSystem.Services.ManageHome.CMS.Menus can't break IEManageSystem.CMS.DomainModel.Menus.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Menus uses a module listed above it, which is the healthy direction.
28→18 IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.CMS.Menus uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Menus.MenuManageAppService→IEManageSystem.CMS.DomainModel.PageDatas.PageData
- Direction
- IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.Services.ManageHome.CMS.Menus, while a change to IEManageSystem.Services.ManageHome.CMS.Menus can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Menus uses a module listed above it, which is the healthy direction.
28→26 IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.Repositorys✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Menus uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Menus.MenuAppService→IEManageSystem.Repositorys.IEfRepositoryIEManageSystem.Services.ManageHome.CMS.Menus.MenuManageAppService→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.Services.ManageHome.CMS.Menus uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.Services.ManageHome.CMS.Menus, while a change to IEManageSystem.Services.ManageHome.CMS.Menus can't break IEManageSystem.Repositorys.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Menus uses a module listed above it, which is the healthy direction.
29→1 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem✕
- Connections
- 4 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataManageAppService→IEManageSystem.IEManageSystemAppServiceBaseIEManageSystem.Services.ManageHome.CMS.Pages.PageDataQueryAppService→IEManageSystem.IEManageSystemAppServiceBaseIEManageSystem.Services.ManageHome.CMS.Pages.PageManageAppService→IEManageSystem.IEManageSystemAppServiceBaseIEManageSystem.Services.ManageHome.CMS.Pages.PageQueryAppService→IEManageSystem.IEManageSystemAppServiceBase
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem, so a change to IEManageSystem can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
29→17 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataManageAppService→IEManageSystem.Entitys.Authorization.Users.UserManagerIEManageSystem.Services.ManageHome.CMS.Pages.PageManageAppService→IEManageSystem.Entitys.Authorization.Users.UserManager
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
29→18 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataManageAppService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataManagerIEManageSystem.Services.ManageHome.CMS.Pages.PageDataQueryAppService→IEManageSystem.CMS.DomainModel.PageDatas.PageDataManager
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
29→19 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 4 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataManageAppService→IEManageSystem.CMS.DomainModel.Pages.PageManagerIEManageSystem.Services.ManageHome.CMS.Pages.PageManageAppService→IEManageSystem.CMS.DomainModel.Pages.PageManagerIEManageSystem.Services.ManageHome.CMS.Pages.PageQueryAppService→IEManageSystem.CMS.DomainModel.Pages.ContentPagePermissionCollectionIEManageSystem.Services.ManageHome.CMS.Pages.PageQueryAppService→IEManageSystem.CMS.DomainModel.Pages.PageManager
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
29→20 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel.ComponentDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.CMS.DomainModel.ComponentDatas.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataQueryAppService→IEManageSystem.CMS.DomainModel.ComponentDatas.ContentComponentData
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel.ComponentDatas, so a change to IEManageSystem.CMS.DomainModel.ComponentDatas can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.CMS.DomainModel.ComponentDatas.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
29→21 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.CMS.DomainModel.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataManageAppService→IEManageSystem.CMS.DomainModel.DeletePageDataServiceIEManageSystem.Services.ManageHome.CMS.Pages.PageDataManageAppService→IEManageSystem.CMS.DomainModel.UpdateContentComponentDataServiceIEManageSystem.Services.ManageHome.CMS.Pages.PageManageAppService→IEManageSystem.CMS.DomainModel.DeletePageService
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.CMS.DomainModel, so a change to IEManageSystem.CMS.DomainModel can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.CMS.DomainModel.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
29→26 IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.Repositorys✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.CMS.Pages uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.Services.ManageHome.CMS.Pages.PageDataQueryAppService→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.Services.ManageHome.CMS.Pages uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.Services.ManageHome.CMS.Pages, while a change to IEManageSystem.Services.ManageHome.CMS.Pages can't break IEManageSystem.Repositorys.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.CMS.Pages uses a module listed above it, which is the healthy direction.
30→27 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes.ApiScopeNode→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes, while a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses a module listed above it, which is the healthy direction.
30→35 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes part of a loop✕
- Connections
- 1 pair of types, where a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.
- The types involved
IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes.ApiScopeNode→IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopePermission
- Direction
- IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, so a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes, while a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes can't break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→15 IEManageSystem.Configures.Core uses IEManageSystem.Entitys.Authorization.Roles✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Configures.Core uses a type in IEManageSystem.Entitys.Authorization.Roles.
- The types involved
IEManageSystem.Configures.Core.RoleConfigure→IEManageSystem.Entitys.Authorization.Roles.RoleIEManageSystem.Configures.Core.RolePermissionConfigure→IEManageSystem.Entitys.Authorization.Roles.RolePermission
- Direction
- IEManageSystem.Configures.Core uses IEManageSystem.Entitys.Authorization.Roles, so a change to IEManageSystem.Entitys.Authorization.Roles can break IEManageSystem.Configures.Core, while a change to IEManageSystem.Configures.Core can't break IEManageSystem.Entitys.Authorization.Roles.
- Position
- Below the diagonal: IEManageSystem.Configures.Core uses a module listed above it, which is the healthy direction.
31→17 IEManageSystem.Configures.Core uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Configures.Core uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.Configures.Core.UserConfigure→IEManageSystem.Entitys.Authorization.Users.UserIEManageSystem.Configures.Core.UserRoleConfigure→IEManageSystem.Entitys.Authorization.Users.UserRole
- Direction
- IEManageSystem.Configures.Core uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.Configures.Core, while a change to IEManageSystem.Configures.Core can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.Configures.Core uses a module listed above it, which is the healthy direction.
31→27 IEManageSystem.Configures.Core uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Configures.Core uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Configures.Core.PermissionConfigure→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.Configures.Core uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Configures.Core, while a change to IEManageSystem.Configures.Core can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.Configures.Core uses a module listed above it, which is the healthy direction.
32→15 IEManageSystem.Entitys.Authorization.LoginManagers uses IEManageSystem.Entitys.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Entitys.Authorization.LoginManagers uses a type in IEManageSystem.Entitys.Authorization.Roles.
- The types involved
IEManageSystem.Entitys.Authorization.LoginManagers.LoginManager→IEManageSystem.Entitys.Authorization.Roles.Role
- Direction
- IEManageSystem.Entitys.Authorization.LoginManagers uses IEManageSystem.Entitys.Authorization.Roles, so a change to IEManageSystem.Entitys.Authorization.Roles can break IEManageSystem.Entitys.Authorization.LoginManagers, while a change to IEManageSystem.Entitys.Authorization.LoginManagers can't break IEManageSystem.Entitys.Authorization.Roles.
- Position
- Below the diagonal: IEManageSystem.Entitys.Authorization.LoginManagers uses a module listed above it, which is the healthy direction.
32→17 IEManageSystem.Entitys.Authorization.LoginManagers uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Entitys.Authorization.LoginManagers uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.Entitys.Authorization.LoginManagers.LoginManager→IEManageSystem.Entitys.Authorization.Users.UserManager
- Direction
- IEManageSystem.Entitys.Authorization.LoginManagers uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.Entitys.Authorization.LoginManagers, while a change to IEManageSystem.Entitys.Authorization.LoginManagers can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.Entitys.Authorization.LoginManagers uses a module listed above it, which is the healthy direction.
32→27 IEManageSystem.Entitys.Authorization.LoginManagers uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Entitys.Authorization.LoginManagers uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Entitys.Authorization.LoginManagers.LoginManager→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.Entitys.Authorization.LoginManagers uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Entitys.Authorization.LoginManagers, while a change to IEManageSystem.Entitys.Authorization.LoginManagers can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.Entitys.Authorization.LoginManagers uses a module listed above it, which is the healthy direction.
33→1 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a type in IEManageSystem.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Admins.AdminManageAppService→IEManageSystem.IEManageSystemAppServiceBase
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem, so a change to IEManageSystem can break IEManageSystem.Services.ManageHome.AuthorizeManage.Admins, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Admins can't break IEManageSystem.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a module listed above it, which is the healthy direction.
33→15 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem.Entitys.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a type in IEManageSystem.Entitys.Authorization.Roles.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Admins.AdminManageAppService→IEManageSystem.Entitys.Authorization.Roles.RoleManager
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem.Entitys.Authorization.Roles, so a change to IEManageSystem.Entitys.Authorization.Roles can break IEManageSystem.Services.ManageHome.AuthorizeManage.Admins, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Admins can't break IEManageSystem.Entitys.Authorization.Roles.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a module listed above it, which is the healthy direction.
33→17 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Admins.AdminManageAppService→IEManageSystem.Entitys.Authorization.Users.AdminManager
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.Services.ManageHome.AuthorizeManage.Admins, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Admins can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a module listed above it, which is the healthy direction.
33→27 IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Admins.AdminManageAppService→IEManageSystem.Entitys.Authorization.Permissions.PermissionManager
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Services.ManageHome.AuthorizeManage.Admins, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Admins can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Admins uses a module listed above it, which is the healthy direction.
34→1 IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses IEManageSystem✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses a type in IEManageSystem.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Roles.RoleManageAppService→IEManageSystem.IEManageSystemAppServiceBase
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses IEManageSystem, so a change to IEManageSystem can break IEManageSystem.Services.ManageHome.AuthorizeManage.Roles, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Roles can't break IEManageSystem.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses a module listed above it, which is the healthy direction.
34→15 IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses IEManageSystem.Entitys.Authorization.Roles✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses a type in IEManageSystem.Entitys.Authorization.Roles.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Roles.RoleManageAppService→IEManageSystem.Entitys.Authorization.Roles.RoleManager
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses IEManageSystem.Entitys.Authorization.Roles, so a change to IEManageSystem.Entitys.Authorization.Roles can break IEManageSystem.Services.ManageHome.AuthorizeManage.Roles, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Roles can't break IEManageSystem.Entitys.Authorization.Roles.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses a module listed above it, which is the healthy direction.
34→27 IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.Roles.RoleManageAppService→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Services.ManageHome.AuthorizeManage.Roles, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.Roles can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.Roles uses a module listed above it, which is the healthy direction.
35→5 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.Web✕
- Connections
- 1 pair of types, where a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a type in IEManageSystem.Web.
- The types involved
IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager→IEManageSystem.Web.IIEMemoryCache
- Direction
- IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.Web, so a change to IEManageSystem.Web can break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, while a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can't break IEManageSystem.Web.
- Position
- Below the diagonal: IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a module listed above it, which is the healthy direction.
35→26 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.Repositorys✕
- Connections
- 1 pair of types, where a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a type in IEManageSystem.Repositorys.
- The types involved
IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager→IEManageSystem.Repositorys.IEfRepository
- Direction
- IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.Repositorys, so a change to IEManageSystem.Repositorys can break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, while a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can't break IEManageSystem.Repositorys.
- Position
- Below the diagonal: IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a module listed above it, which is the healthy direction.
35→27 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager→IEManageSystem.Entitys.Authorization.Permissions.PermissionIEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager→IEManageSystem.Entitys.Authorization.Permissions.PermissionManagerIEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopePermission→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, while a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a module listed above it, which is the healthy direction.
35→30 IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes.
- The types involved
IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScope→IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes.ApiScopeNodeIEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopePermission→IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes.ApiScopeNode
- Direction
- IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes, so a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes can break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, while a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can't break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.AuthorizationNodes.
- Position
- Below the diagonal: IEManageSystem.ApiAuthorization.DomainModel.ApiScopes uses a module listed above it, which is the healthy direction.
36→1 IEManageSystem.Services.Accounts uses IEManageSystem✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.Accounts uses a type in IEManageSystem.
- The types involved
IEManageSystem.Services.Accounts.AccountAppService→IEManageSystem.IEManageSystemAppServiceBase
- Direction
- IEManageSystem.Services.Accounts uses IEManageSystem, so a change to IEManageSystem can break IEManageSystem.Services.Accounts, while a change to IEManageSystem.Services.Accounts can't break IEManageSystem.
- Position
- Below the diagonal: IEManageSystem.Services.Accounts uses a module listed above it, which is the healthy direction.
36→17 IEManageSystem.Services.Accounts uses IEManageSystem.Entitys.Authorization.Users✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.Accounts uses a type in IEManageSystem.Entitys.Authorization.Users.
- The types involved
IEManageSystem.Services.Accounts.AccountAppService→IEManageSystem.Entitys.Authorization.Users.RegisterManager
- Direction
- IEManageSystem.Services.Accounts uses IEManageSystem.Entitys.Authorization.Users, so a change to IEManageSystem.Entitys.Authorization.Users can break IEManageSystem.Services.Accounts, while a change to IEManageSystem.Services.Accounts can't break IEManageSystem.Entitys.Authorization.Users.
- Position
- Below the diagonal: IEManageSystem.Services.Accounts uses a module listed above it, which is the healthy direction.
36→32 IEManageSystem.Services.Accounts uses IEManageSystem.Entitys.Authorization.LoginManagers✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.Accounts uses a type in IEManageSystem.Entitys.Authorization.LoginManagers.
- The types involved
IEManageSystem.Services.Accounts.AccountAppService→IEManageSystem.Entitys.Authorization.LoginManagers.LoginManager
- Direction
- IEManageSystem.Services.Accounts uses IEManageSystem.Entitys.Authorization.LoginManagers, so a change to IEManageSystem.Entitys.Authorization.LoginManagers can break IEManageSystem.Services.Accounts, while a change to IEManageSystem.Services.Accounts can't break IEManageSystem.Entitys.Authorization.LoginManagers.
- Position
- Below the diagonal: IEManageSystem.Services.Accounts uses a module listed above it, which is the healthy direction.
37→1 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses IEManageSystem✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses a type in IEManageSystem.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes.ApiScopeManageAppService→IEManageSystem.IEManageSystemAppServiceBase
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses IEManageSystem, so a change to IEManageSystem can break IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes can't break IEManageSystem.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses a module listed above it, which is the healthy direction.
37→27 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes.ApiScopeManageAppService→IEManageSystem.Entitys.Authorization.Permissions.Permission
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses a module listed above it, which is the healthy direction.
37→35 IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses a type in IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.
- The types involved
IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes.ApiScopeManageAppService→IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.ApiScopeManager
- Direction
- IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses IEManageSystem.ApiAuthorization.DomainModel.ApiScopes, so a change to IEManageSystem.ApiAuthorization.DomainModel.ApiScopes can break IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes, while a change to IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes can't break IEManageSystem.ApiAuthorization.DomainModel.ApiScopes.
- Position
- Below the diagonal: IEManageSystem.Services.ManageHome.AuthorizeManage.ApiScopes uses a module listed above it, which is the healthy direction.
38→4 IEManageSystem.Web.Controllers uses IEManageSystem.JwtAuthentication✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Web.Controllers uses a type in IEManageSystem.JwtAuthentication.
- The types involved
IEManageSystem.Web.Controllers.AccountController→IEManageSystem.JwtAuthentication.JwtTokenHandler
- Direction
- IEManageSystem.Web.Controllers uses IEManageSystem.JwtAuthentication, so a change to IEManageSystem.JwtAuthentication can break IEManageSystem.Web.Controllers, while a change to IEManageSystem.Web.Controllers can't break IEManageSystem.JwtAuthentication.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers uses a module listed above it, which is the healthy direction.
38→36 IEManageSystem.Web.Controllers uses IEManageSystem.Services.Accounts✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Web.Controllers uses a type in IEManageSystem.Services.Accounts.
- The types involved
IEManageSystem.Web.Controllers.AccountController→IEManageSystem.Services.Accounts.AccountAppService
- Direction
- IEManageSystem.Web.Controllers uses IEManageSystem.Services.Accounts, so a change to IEManageSystem.Services.Accounts can break IEManageSystem.Web.Controllers, while a change to IEManageSystem.Web.Controllers can't break IEManageSystem.Services.Accounts.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers uses a module listed above it, which is the healthy direction.
39→4 IEManageSystem.Web.Controllers.CMS.Logics uses IEManageSystem.JwtAuthentication✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Web.Controllers.CMS.Logics uses a type in IEManageSystem.JwtAuthentication.
- The types involved
IEManageSystem.Web.Controllers.CMS.Logics.LogicExecController→IEManageSystem.JwtAuthentication.ClaimManager
- Direction
- IEManageSystem.Web.Controllers.CMS.Logics uses IEManageSystem.JwtAuthentication, so a change to IEManageSystem.JwtAuthentication can break IEManageSystem.Web.Controllers.CMS.Logics, while a change to IEManageSystem.Web.Controllers.CMS.Logics can't break IEManageSystem.JwtAuthentication.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Logics uses a module listed above it, which is the healthy direction.
39→38 IEManageSystem.Web.Controllers.CMS.Logics uses IEManageSystem.Web.Controllers✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Web.Controllers.CMS.Logics uses a type in IEManageSystem.Web.Controllers.
- The types involved
IEManageSystem.Web.Controllers.CMS.Logics.LogicExecController→IEManageSystem.Web.Controllers.IEManageSystemControllerBase
- Direction
- IEManageSystem.Web.Controllers.CMS.Logics uses IEManageSystem.Web.Controllers, so a change to IEManageSystem.Web.Controllers can break IEManageSystem.Web.Controllers.CMS.Logics, while a change to IEManageSystem.Web.Controllers.CMS.Logics can't break IEManageSystem.Web.Controllers.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Logics uses a module listed above it, which is the healthy direction.
40→4 IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.JwtAuthentication✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Web.Controllers.CMS.Pages uses a type in IEManageSystem.JwtAuthentication.
- The types involved
IEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.JwtAuthentication.ClaimManagerIEManageSystem.Web.Controllers.CMS.Pages.PageDataQueryController→IEManageSystem.JwtAuthentication.ClaimManager
- Direction
- IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.JwtAuthentication, so a change to IEManageSystem.JwtAuthentication can break IEManageSystem.Web.Controllers.CMS.Pages, while a change to IEManageSystem.Web.Controllers.CMS.Pages can't break IEManageSystem.JwtAuthentication.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Pages uses a module listed above it, which is the healthy direction.
40→18 IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.CMS.DomainModel.PageDatas✕
- Connections
- 1 pair of types, where a type in IEManageSystem.Web.Controllers.CMS.Pages uses a type in IEManageSystem.CMS.DomainModel.PageDatas.
- The types involved
IEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.CMS.DomainModel.PageDatas.PageDataManager
- Direction
- IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.CMS.DomainModel.PageDatas, so a change to IEManageSystem.CMS.DomainModel.PageDatas can break IEManageSystem.Web.Controllers.CMS.Pages, while a change to IEManageSystem.Web.Controllers.CMS.Pages can't break IEManageSystem.CMS.DomainModel.PageDatas.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Pages uses a module listed above it, which is the healthy direction.
40→19 IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.CMS.DomainModel.Pages✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Web.Controllers.CMS.Pages uses a type in IEManageSystem.CMS.DomainModel.Pages.
- The types involved
IEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.CMS.DomainModel.Pages.PageManagerIEManageSystem.Web.Controllers.CMS.Pages.PageDataQueryController→IEManageSystem.CMS.DomainModel.Pages.PageManager
- Direction
- IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.CMS.DomainModel.Pages, so a change to IEManageSystem.CMS.DomainModel.Pages can break IEManageSystem.Web.Controllers.CMS.Pages, while a change to IEManageSystem.Web.Controllers.CMS.Pages can't break IEManageSystem.CMS.DomainModel.Pages.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Pages uses a module listed above it, which is the healthy direction.
40→27 IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.Entitys.Authorization.Permissions✕
- Connections
- 3 pairs of types, where a type in IEManageSystem.Web.Controllers.CMS.Pages uses a type in IEManageSystem.Entitys.Authorization.Permissions.
- The types involved
IEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.Entitys.Authorization.Permissions.PermissionIEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.Entitys.Authorization.Permissions.PermissionManagerIEManageSystem.Web.Controllers.CMS.Pages.PageDataQueryController→IEManageSystem.Entitys.Authorization.Permissions.PermissionManager
- Direction
- IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.Entitys.Authorization.Permissions, so a change to IEManageSystem.Entitys.Authorization.Permissions can break IEManageSystem.Web.Controllers.CMS.Pages, while a change to IEManageSystem.Web.Controllers.CMS.Pages can't break IEManageSystem.Entitys.Authorization.Permissions.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Pages uses a module listed above it, which is the healthy direction.
40→29 IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.Services.ManageHome.CMS.Pages✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Web.Controllers.CMS.Pages uses a type in IEManageSystem.Services.ManageHome.CMS.Pages.
- The types involved
IEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.Services.ManageHome.CMS.Pages.IPageDataManageAppServiceIEManageSystem.Web.Controllers.CMS.Pages.PageDataQueryController→IEManageSystem.Services.ManageHome.CMS.Pages.IPageDataQueryAppService
- Direction
- IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.Services.ManageHome.CMS.Pages, so a change to IEManageSystem.Services.ManageHome.CMS.Pages can break IEManageSystem.Web.Controllers.CMS.Pages, while a change to IEManageSystem.Web.Controllers.CMS.Pages can't break IEManageSystem.Services.ManageHome.CMS.Pages.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Pages uses a module listed above it, which is the healthy direction.
40→38 IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.Web.Controllers✕
- Connections
- 2 pairs of types, where a type in IEManageSystem.Web.Controllers.CMS.Pages uses a type in IEManageSystem.Web.Controllers.
- The types involved
IEManageSystem.Web.Controllers.CMS.Pages.PageDataManageController→IEManageSystem.Web.Controllers.IEManageSystemControllerBaseIEManageSystem.Web.Controllers.CMS.Pages.PageDataQueryController→IEManageSystem.Web.Controllers.IEManageSystemControllerBase
- Direction
- IEManageSystem.Web.Controllers.CMS.Pages uses IEManageSystem.Web.Controllers, so a change to IEManageSystem.Web.Controllers can break IEManageSystem.Web.Controllers.CMS.Pages, while a change to IEManageSystem.Web.Controllers.CMS.Pages can't break IEManageSystem.Web.Controllers.
- Position
- Below the diagonal: IEManageSystem.Web.Controllers.CMS.Pages uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 153 | High / Critical |
| A05:2025 — Injection | 23 | Medium |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED; 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.); Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. | +6.7 pts | Low | REDACTED Scanning |
| 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.7 pts | Medium | Data Protection |
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +5.7 pts | Medium | Access Controls |
| Resolve the 83 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (83). | +5.5 pts | Medium | Dependency Hygiene |
| 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`. | +5.0 pts | Medium | Web-Security Posture |
| Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED. | +2.4 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +1.8 pts | Low | Secrets (history) |
| Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +1.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.1 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.2 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| src/IEManageSystem.Core/IEManageSystem.Core.csproj | 4.0 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp3.0 |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| test/IEManageSystem.Tests/IEManageSystem.Tests.csproj | 4.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp3.0 |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.5 | Mixed | Explicit Debt: EmptyCatchBlock |
| src/UtilityAction/Web/WebModelBinding.cs | 5.8 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj | 5.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp3.0 |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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
This survey 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. All 102 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 102 dimensions across the health lenses
- 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, 808 of 849 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 — We 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 — We 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 — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We 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 — We measured this, but not all of it. What we 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-en.json`, `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem-tr.json`, `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem-zh-CHS.json`, `src/IEManageSystem.Core/Localization/SourceFiles/IEManageSystem.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.
- AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 103 further occurrence(s) are not listed individually; the score already reflects all 143.
- AXB2 Runtime readiness — not measured this run — We 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. `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We 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: xrdchh5u0ydg80p8d/cp_initcf39471ad2848fb82befe662c0627ed4). > Could not open cp_init generic class cache for initialization script '/tmp/codehealth-gradle/init.d/codehealth-pkg-cache.gradle' (/tmp/cod…; 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 — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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. 69 further occurrence(s) are not listed individually; the score already reflects all 109.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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 is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Header.default at 48.
What to do
- 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.
- 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.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was ComponentContainerBox.getStyle at 61.
What to do
- 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.
- 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.
D3 · God Classes
11 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- 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).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with BasicSettingConfig.jsx, UserInfo.jsx, PageData.jsx. — One of this dimension's main actionable groups (5 warning-level).
- 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.
D4 · Code Duplication
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.
What to do
- 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).
- 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).
- 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).
- 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.
D5 · Coupling
15 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- 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).
- 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.
D6 · Cohesion (LCOM4)
0 of 37 classes have LCOM4 above 3.
D9 · Test Distribution
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.
D10 · Test Quality
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.
D12 · Dependency Hygiene
36 outdated, 2 vulnerable, 19 deprecated packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
What to do
- Resolve the 83 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (83). — One of this dimension's main actionable groups (83 recommendation-level).
- 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).
- Resolve the 21 Outdated finding(s) in Dependency Hygiene — start with REDACTED (5), REDACTED (5), IEManageSystem.Tests.csproj (3). — One of this dimension's main actionable groups (21 recommendation-level).
- 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.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- 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).
- 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.
D14 · License Compliance
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.
D15 · Churn × Complexity Hotspots
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)
What to do
- 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).
D17 · Explicit Debt
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).
What to do
- 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).
- 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).
- 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).
- 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.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 1 document(s) read across 35 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
73 domain type(s) cross context boundaries across 9 contexts; they are measured and withheld (not published, not scored). Contexts: IEManageSystem, IEManageSystem.ApiAuthorization, IEManageSystem.CMS, IEManageSystem.Common, IEManageSystem.CommonInfrastructure, IEManageSystem.Core, IEManageSystem.EntityFrameworkCore, IEManageSystem.JwtAuthentication, UtilityAction.
D24 · Comment Value
15 of 119 judged comments only repeat the code they sit on (12.6 %). 577 comment(s) in another language or script were not judged.
What to do
- Resolve the 15 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (15). — One of this dimension's main actionable groups (15 recommendation-level).
D26 · Project Cohesion
1 of 15 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
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.
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 0 high, 23 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.
What to do
- 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).
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- 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).
D30 · Dependency Vulnerabilities
153 finding(s): 28 critical, 80 high, 35 medium, 10 low.
What to do
- Resolve the 78 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (69), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (78 issue-level).
- 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).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
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.
What to do
- 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).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- 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).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
3 of 614 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
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.
What to do
- Resolve the 15 End-of-life runtime finding(s) in Platform End-of-Life — start with IEManageSystem.ApiAuthorization.csproj, REDACTED, IEManageSystem.CMS.csproj. — One of this dimension's main actionable groups (15 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- 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 & labels
- 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. (×29) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAudio/DataConfig.jsx:12, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:14, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:24, …
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — 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. (×8) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:34, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:19, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:29, …
- 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. — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:51
- This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). 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. (×2) — src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:35, src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:132
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 structure
- 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
- A <tr> may hold only <td>/<th> cells. Text or a value written between the cells is moved out of the table by the browser, so it is read detached from its row. Wrap it in a <td>. (×2) — src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:124, src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:155
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 semantics
- 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 correctness
AC6 · Visual & motion safety
- `.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 enforcement
- 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. — REDACTED:33
What to do
- Accessibility linting is already configured — assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `WebConfiguration` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Issuer, Audience, SymmetricKey; e.g. `Issuer` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/IEManageSystem.Web/Configuration/WebConfiguration.cs:9
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- 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 direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
C1 · Data Protection
- 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 Controls
- 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 boundaries
DM10 · One transaction, one aggregate
- `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 state
DM2 · Strongly-typed ids
- `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 model
- `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
- `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
- `ApiScope` 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.ApiAuthorization/DomainModel/ApiScopes/ApiScope.cs:13
- `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
- `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 state
- `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 granularity
- `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 decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `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)
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 10 of 10 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- 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 structure
M4 · Documentation accuracy
P1 · CI/CD gates
- 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 & versioning
- 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 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- 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.
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:20
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 & Rollback
- 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 Hygiene
- 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 migrations
- `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 discipline
- 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).
PF3 · Async & latency hygiene
- 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 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).
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 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 Boundaries
- 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 (2 rows).
R2 · Cyclomatic Complexity
- (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 Files
- 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 Coverage
- 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 · Tooling
- 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 Code
- 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 Hygiene
- 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 REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in REDACTED 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 REDACTED 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 Imports
- 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 Posture
- `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 correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `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 state
X2 · Cancellation propagation
- Only 0/3 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. (×3) — src/IEManageSystem.Web/Controllers/AccountController.cs:82, src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:36, src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:55
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `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 knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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 rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- 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
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 44% | Weak — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 50% | Adequate — gated by R11, AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 47% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 15% | Critical — gated by D13, R4, R8, P1, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 10% | Critical — gated by D29, C1, C2, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 53% | Adequate — gated by DM2, DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 35% | Weak — gated by AC2, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- 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
- 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 — 33 check(s) not relevant to this codebase
- 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: xrdchh5u0ydg80p8d/cp_initcf39471ad2848fb82befe662c0627ed4). > Could not open cp_init generic class cache for initialization script '/tmp/codehealth-gradle/init.d/codehealth-pkg-cache.gradle' (/tmp/cod…; 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, TypeScript surface was not measured.
- 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
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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)
Critical — 150 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/CMSManage/Component/ComponentContainers/PageEditComponentContainer/EditFrame.test.js:1
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:1
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/ILayoutInstance.js:1
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:1
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/AntIcons/index.tsx:1
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx:1
- Unlisted import 'react' src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:1
- Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Models/ContentPagePermissionCollection.ts:1
- Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/SearchBar/index.js:3
- Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/AntIcons/index.tsx:2
- Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx:4
- Unlisted import 'native-base' src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:4
- Click handler on a non-interactive <div> src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/Component.jsx:17
- Click handler on a non-interactive <div> src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:81
- REDACTED
- REDACTED
- EmptyCatchBlock REDACTED:77
- EmptyCatchBlock src/UtilityAction/Web/WebModelBinding.cs:51
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'prop-types' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:2
- Unlisted import 'prop-types' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js:2
- Unlisted import 'react-router-native' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/index.js:2
- Unlisted import 'react-router-native' src/IEManageSystem.Web/ClientApp/src/RNApp/RNLayout/Layout.js:3
- <img> without a text alternative src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IETab/Preview.jsx:6
- <label> that labels no control src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:51
- <iframe> without a title src/IEManageSystem.Web/ClientApp/src/WebApp/Adapters/WebView.tsx:13
- Hover-only interaction on <div> src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/Component.jsx:136
- Click handler on a non-interactive <img> src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/PictureBox.jsx:82
- Namespace dependency cycle src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:6
- REDACTED
- REDACTED
- Unlisted import 'IEEnzyme' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/CMSManage/Component/ComponentContainers/PageEditComponentContainer/EditFrame.test.js:2
- Unlisted import 'enzyme' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/IEEnzyme.js:1
- Unlisted import 'enzyme-adapter-react-16' src/IEManageSystem.Web/ClientApp/src/WebApp/__tests/IEEnzyme.js:2
- Unlisted import 'react-router' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/ComponentContainer.js:3
- Unlisted import 'color' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3
- Unlisted import 'lodash' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/index.js:4
- Unlisted import 'react-native-camera' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/Camera/index.tsx:3
- Unlisted import 'react-native-webview' src/IEManageSystem.Web/ClientApp/src/RNApp/RNInfrastructure/IEWebView/index.tsx:2
- Unlisted import 'images' src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/UserInfo/index.js:7
- Import cycle (2 files) src/IEManageSystem.Web/ClientApp/src/Common/ice-common/IEStore.ts:4
- Password hashing without a KDF src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:80
Serious — 433 finding(s)
- Boundary violation [package:relative-cross-package] src/IEManageSystem.Web/ClientApp/index.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:5
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:7
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BaseComponentSettingConfig.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/BasicComponentSettingConfig.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/CommonStyleSettingConfig/index.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/DeleteConfig.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/FontComponentSettingConfig/index.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseComponent/PostFieldSettingConfig/index.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ContainerConfig.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContentLeafComponent/ComponentDataConfig.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseMenuComponent/MenuComponentSettingConfig.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BasePageLeafComponent/PageLeafComponentSettingConfig.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveComponentConfig.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/InteractiveContainerConfig.js:5
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/CmsRedux.ts:1
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:17
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Module.js:3
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/IEReduxs/LayoutRedux.ts:1
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:1
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BaseLayout/Module.js:2
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/IEReduxs/PersonalRedux.ts:1
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:1
- Boundary violation [package:app-undeclared-workspace-dep] src/IEManageSystem.Web/ClientApp/src/Common/BasePerson/Module.js:2
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Button.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/platform.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/PageComponents/Reducer.ts:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/BtnLists.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Layout/BodyDiv/Index/IELinePlotDemo.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/index.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Item.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/Start/scripts/build.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseContainerComponent/ContainerConfigBtnComponent.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ClipBoard.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/CardItem.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageManage/PageManage.jsx:1
- No test reaches this file src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/index.jsx:1
- Deprecated: Microsoft.AspNetCore.Diagnostics REDACTED:42
- Deprecated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:43
- Deprecated: Microsoft.AspNetCore.Mvc REDACTED:44
- Deprecated: Microsoft.AspNetCore.Mvc REDACTED:28
- Deprecated: Microsoft.AspNetCore.Mvc REDACTED:12
- Deprecated: Microsoft.AspNetCore.Server.IISIntegration REDACTED:45
- Deprecated: Microsoft.AspNetCore.Server.Kestrel REDACTED:46
- Deprecated: Microsoft.AspNetCore.SpaServices.Extensions REDACTED:38
- Deprecated: Microsoft.AspNetCore.StaticFiles REDACTED:47
- Deprecated: Microsoft.EntityFrameworkCore.SqlServer.Design REDACTED:48
- Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:49
- Deprecated: Microsoft.VisualStudio.Web.BrowserLink REDACTED:50
- Deprecated: Microsoft.Extensions.Configuration.EnvironmentVariables src/IEManageSystem.Core/IEManageSystem.Core.csproj:15
- Deprecated: Microsoft.Extensions.Configuration.Json src/IEManageSystem.Core/IEManageSystem.Core.csproj:16
- Deprecated: Pomelo.EntityFrameworkCore.MySql REDACTED:35
- Deprecated: Microsoft.DotNet.InternalAbstractions test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:34
- Deprecated: xunit test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:23
- Deprecated: xunit REDACTED:23
- Deprecated: xunit test/IEManageSystem.CommonInfrastructure.Tests/IEManageSystem.CommonInfrastructure.Tests.csproj:11
- Deprecated: xunit test/IEManageSystem.Application.Tests/IEManageSystem.Application.Tests.csproj:11
- Deprecated: xunit test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj:11
- Deprecated: xunit.extensibility.execution test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:24
- Deprecated: IdentityModel REDACTED:9
- Deprecated: Microsoft.AspNetCore.Authentication REDACTED:10
- Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:11
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAudio/DataConfig.jsx:12
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:14
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:24
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:34
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/SettingConfig.jsx:62
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:19
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:29
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:39
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:55
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:114
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEButton/SettingConfig.jsx:124
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECard/DataConfig.jsx:24
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:29
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:53
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/SettingConfig.jsx:11
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/SettingConfig.jsx:45
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/SettingConfig.jsx:23
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECategoryLabel/SettingConfig.jsx:33
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:18
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:37
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/SettingConfig.jsx:12
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/SettingConfig.jsx:23
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx:19
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx:32
- <Input> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEInfoGroup/DataConfig.jsx:45
- 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
- Dead code: GetAppConfiguration src/IEManageSystem.Web/Configuration/HostingEnvironmentExtensions.cs:9
- Dead code: VisitPageDataInput src/IEManageSystem.Web/Controllers/CMS/Pages/Dto/VisitPageDataInput.cs:8
- Dead code: VisitPageDataOutput src/IEManageSystem.Web/Controllers/CMS/Pages/Dto/VisitPageDataOutput.cs:8
- Dead code: ConsentInputModel src/IEManageSystem.Web/Models/ConsentModels/ConsentInputModel.cs:8
- Dead code: ConsentModel src/IEManageSystem.Web/Models/ConsentModels/ConsentModel.cs:8
- Dead code: ConsentOptions src/IEManageSystem.Web/Models/ConsentModels/ConsentOptions.cs:8
- Dead code: Class1 src/UtilityAction/Class1.cs:5
- Dead code: Regular src/UtilityAction/Other/Regular.cs:11
- Dead code: ValidateModel src/UtilityAction/ValidateFun/ValidateModel.cs:10
- Dead code: VerificationCode src/UtilityAction/ValidateFun/VerificationCode.cs:10
- Dead code: GetMimeType src/UtilityAction/Web/FileContentType.cs:579
- Dead code: GetImgMimeTypeList src/UtilityAction/Web/FileContentType.cs:606
- Dead code: WebModelBinding src/UtilityAction/Web/WebModelBinding.cs:11
- Dead code: WriteLogicCodeFile src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:20
- Dead code: _commentName src/IEManageSystem.CommonInfrastructure/CMS/WriteLogicCodeFile.cs:22
- End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.ApiAuthorization/IEManageSystem.ApiAuthorization.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 REDACTED:4
- End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.CMS/IEManageSystem.CMS.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.Common/IEManageSystem.Common.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.CommonInfrastructure/IEManageSystem.CommonInfrastructure.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 src/IEManageSystem.Core/IEManageSystem.Core.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 REDACTED:4
- End-of-life runtime: .NET netcoreapp3.0 REDACTED:4
- End-of-life runtime: .NET netcoreapp3.0 REDACTED:4
- End-of-life runtime: .NET netcoreapp3.0 src/UtilityAction/UtilityAction.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.Application.Tests/IEManageSystem.Application.Tests.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.CommonInfrastructure.Tests/IEManageSystem.CommonInfrastructure.Tests.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:4
- End-of-life runtime: .NET netcoreapp3.0 REDACTED:4
- No authorization
- No authorization src/IEManageSystem.Web/Controllers/AccountController.cs:62
- No authorization src/IEManageSystem.Web/Controllers/AccountController.cs:82
- No authorization src/IEManageSystem.Web/Controllers/CMS/Logics/LogicExecController.cs:24
- No authorization REDACTED:73
- No authorization REDACTED:85
- No authorization REDACTED:99
- No authorization REDACTED:115
- No authorization REDACTED:137
- No authorization REDACTED:59
- No authorization REDACTED:108
- No authorization REDACTED:143
- No authorization REDACTED:37
- No authorization REDACTED:43
- Anemic entity: Permission src/IEManageSystem.Core/Entitys/Authorization/Permissions/Permission.cs:9
- Anemic entity: RolePermission src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:10
- Anemic entity: UserRole src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:10
- Anemic entity: Account src/IEManageSystem.Core/Entitys/Authorization/Users/Accounts/Account.cs:11
- Anemic entity: ApiScope src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScope.cs:13
- Anemic entity: ApiScopePermission src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:12
- Anemic entity: CmsComponent src/IEManageSystem.CMS/DomainModel/CmsComponent.cs:9
- Anemic entity: ComponentSingleData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:9
- Anemic entity: ContentPagePermission src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:10
- Anemic entity: ContentPagePermissionCollection src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:12
- Anemic entity: Logic src/IEManageSystem.CMS/DomainModel/Logics/Logic.cs:8
- Anemic entity: CompositeMenu src/IEManageSystem.CMS/DomainModel/Menus/CompositeMenu.cs:7
- Anemic entity: Tag src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:9
- Anemic entity: SiteSetting src/IEManageSystem.Common/DomainModel/SiteSetting.cs:9
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:55
- Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:70
- Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:65
- Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Users/AdminManager.cs:50
- Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Users/RegisterManager.cs:35
- Awaits without ConfigureAwait(false) src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:118
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:45
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:57
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:62
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:62
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:93
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Users/UserAppService.cs:50
- Awaits without ConfigureAwait(false) src/IEManageSystem.Application/Services/Users/UserAppService.cs:149
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Layout/BodyDiv/BodyDiv.css:6
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:30
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:35
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:40
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:50
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:55
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:60
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Menu/Menu.css:26
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Account/account.css:37
- Animation without a prefers-reduced-motion guard src/IEManageSystem.Web/ClientApp/src/WebApp/Account/account.css:54
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:42
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:67
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:74
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:98
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:114
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/Users/UserAppService.cs:108
- Fake-async — async method never awaits src/IEManageSystem.Application/Services/Users/UserAppService.cs:128
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: Header.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
- FunctionTooLong: ListItem.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:9
- FunctionTooLong: Button.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Button.js:6
- FunctionTooLong: Item.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Item.js:8
- FunctionTooLong: CardItem.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/CardItem.js:8
- FunctionTooLong: index.default src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/index.js:50
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: BasicSettingConfig.render src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:19
- MethodTooLong: UserInfo.render src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/UserInfo/UserInfo.jsx:114
- MethodTooLong: PostModal.render src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageData/PageData.jsx:103
- MethodTooLong: AccountSecurity.render src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:104
- MethodTooLong: ComponentContainerBox.getStyle src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20
- Hotspot: src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20
- Hotspot: src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91
- Hotspot: src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts src/IEManageSystem.Web/ClientApp/src/Common/Core/IEReduxs/Actions.ts:77
- TodoComment src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:81
- TodoComment src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:82
- TodoComment src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:83
- Duplicated block (28 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4
- Duplicated block (28 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40
- Duplicated block (28 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:257
- Async method without CancellationToken: LoginAsync src/IEManageSystem.Web/Controllers/AccountController.cs:82
- Async method without CancellationToken: LoginAsync src/IEManageSystem.Core/Entitys/Authorization/LoginManagers/LoginManager.cs:36
- Async method without CancellationToken: Login src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:55
- <Select> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:35
- <Select> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:132
- Text directly inside a table row src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:124
- Text directly inside a table row src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:155
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) src/IEManageSystem.Web/Conventions/IEApiConvention.cs:22
- Duplicated block (11 lines × 2) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:98
- One operation mutates 2 aggregates: PageManager.UpdateContentPagePermission src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:228
- One operation mutates 2 aggregates: MenuManager.UpdateRootMenu src/IEManageSystem.CMS/DomainModel/Menus/MenuManager.cs:119
- Duplicated block (42 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/InputGroup.js:60
- Duplicated block (42 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4
- Duplicated block with local edits (31 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IETheme/Component.js:9
- Duplicated block with local edits (31 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IELine/DataConfig.jsx:13
- Duplicated block with local edits (22 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/InteractiveComponent/ContainerComponentContainer.js:10
- Duplicated block with local edits (22 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124
- Duplicated block (22 lines × 2 locations) REDACTED:51
- Duplicated block (22 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/Hotkey.jsx:66
- Duplicated block (19 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/material.js:8
- Duplicated block (19 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IECategoryLabel/Component.js:39
- Duplicated block (17 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/RNApp/RNPerson/Login/index.js:40
- Duplicated block (17 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEImg/DataConfig.jsx:19
- Disposable created and abandoned in the method that made it REDACTED:63
- Disposable created and abandoned in the method that made it src/UtilityAction/Other/Encrypt.cs:12
- Untrusted text written into markup unescaped src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEBottomNav/Component.jsx:33
- Untrusted text written into markup unescaped src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/RichTextEditor/Component.jsx:9
- Swallowed exception (empty catch) REDACTED:77
- Swallowed exception (empty catch) src/UtilityAction/Web/WebModelBinding.cs:51
- <TextArea> field component without a label src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEComment/Component.jsx:21
- Page without a main landmark src/IEManageSystem.Web/ClientApp/public/index.html:2
- Link used as a button (placeholder href) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECard/Component.jsx:13
- Low contrast colour pair in CSS (3.1:1) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.css:22
- Low contrast colour pair in CSS (4.4:1) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IERankingList/IERankingList.css:17
- Focus outline removed in CSS without a :focus replacement src/IEManageSystem.Web/ClientApp/src/WebApp/Common/ListBtn/index.css:7
- Process-global static state: WebConfiguration src/IEManageSystem.Web/Configuration/WebConfiguration.cs:9
- No data-protection/encryption
- 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
- CommentedOutCode src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:65
- 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
- ResourceDescribe._initExternalDescribes (cognitive 25) REDACTED:45
- IEApiConvention.Apply (cognitive 17) src/IEManageSystem.Web/Conventions/IEApiConvention.cs:16
- REDACTED
- 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
- Duplicated block (15 lines × 2) src/IEManageSystem.Application/Dtos/CMS/PageDto.cs:12
- Duplicated block (13 lines × 2) src/IEManageSystem.Application/Dtos/CMS/SingleComponentDataDto.cs:15
- Duplicated block (7 lines × 2) src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:51
- Duplicated block (5 lines × 2) src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:218
- Off the main sequence: IEManageSystem.Core src/IEManageSystem.Core/IEManageSystem.Core.csproj:1
- Coverage not measured — .NET and JavaScript/TypeScript suite
- Repository contract exposes a live query handle: IEfRepository src/IEManageSystem.Core/Repositorys/IEfRepository.cs:11
- Hollow method — returns a constant without doing the work src/IEManageSystem.Application/Services/Accounts/Dto/RegisterInput.cs:29
- No CI pipeline
- Schema created with EnsureCreated() (no migration path) REDACTED:113
- Type Safety
- Duplication concentrated across 29 sibling directories (37 clone groups) src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IECarousel/Data.ts:4
- Duplication concentrated across 19 sibling directories (25 clone groups) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14
- Duplication concentrated across 4 sibling directories (13 clone groups) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Component/ComponentContainerBoxs/ComponentContainerBoxShow.js:4
- Duplication concentrated across 8 sibling directories (12 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AuthorizeManage.jsx:12
- Duplication concentrated across 7 sibling directories (11 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50
- Duplication concentrated across 10 sibling directories (9 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/ComponentContainer/ToolBtns.jsx:124
- Duplication concentrated across 6 sibling directories (5 clone groups) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/IEReduxs/DefaultComponentDatas/Reducer.ts:52
- Duplication concentrated across 2 sibling directories (5 clone groups) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/index.js:29
- Duplication concentrated across 4 sibling directories (5 clone groups) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/ComponentSettingConfigBtnComponent.js:40
- Wholesale file copy (199 identical lines × 2 files) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:3
- Duplicated block with local edits (99 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:132
- Duplicated block with local edits (72 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:35
- Duplicated block (66 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/ApiScopePermission/ApiScopePermission.jsx:50
- Wholesale file copy (58 identical lines × 2 files) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/Permission/Permission.jsx:1
- Duplicated block with local edits (57 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IECarousel/DataConfig.jsx:14
- Duplicated block with local edits (56 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PageEdit/CancelAndReload.jsx:24
- Duplicated block with local edits (52 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminRoleManage/AdminRoleManage.jsx:54
- Duplicated block with local edits (44 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/ComponentContainerBoxs/PageEditFrame.jsx:26
- Duplicated block (43 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminManage/AdminManage.jsx:32
- Duplicated block (29 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/IEBraftEditor/index.js:7
- Duplicated block (27 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/PictureManage/index.jsx:73
- Duplicated block with local edits (21 matched lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEAudio/Component.js:55
- Duplicated block (21 lines × 3 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/AuthorizeManage/AdminPermissionManage/AdminPermissionManage.jsx:62
- Duplicated block (20 lines × 6 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:179
- Duplicated block (18 lines × 2 locations) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:41
- Complex function (anonymous) (cyclomatic 48, cognitive 47) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js:8
- Complex function getStyle (cyclomatic 37, cognitive 61) src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js:20
- Complex function exports (cyclomatic 34, cognitive 32) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/webpack.config.js:91
- Complex function _initExternalDescribes (cyclomatic 14, cognitive 25) REDACTED:45
- Complex function (anonymous) (cyclomatic 14, cognitive 13) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Theme/index.js:5
- Complex function getShowTexts (cyclomatic 13, cognitive 23) src/IEManageSystem.Web/ClientApp/src/WebApp/Common/Resource/ResourceList.jsx:30
- Complex function setTheme (cyclomatic 13, cognitive 12) src/IEManageSystem.Web/ClientApp/src/Common/ice-common/Theme/index.ts:51
- Complex function (anonymous) (cyclomatic 12, cognitive 11) src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/ListItem.js:9
- Complex function onscroll (cyclomatic 11, cognitive 12) src/IEManageSystem.Web/ClientApp/src/Templates/WebIETemplateComponents/IEAnimation/Component.jsx:74
- 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/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/Header.js: 414 lines of code 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: 403 lines of code src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/BaseComponent/BasicSettingConfig.jsx:1
- No typecheck script
- Dead file (~40 LoC) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/jest/fileTransform.js
- Dead file (~35 LoC) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/pnpTs.js
- Dead file (~14 LoC) src/IEManageSystem.Web/ClientApp/src/WebApp/Start/config/jest/cssTransform.js
- Unused dependency 'metro-react-native-babel-preset'
- Unused dependency 'native-base'
- Unused dependency 'react-native-camera'
- Weak hash algorithm src/UtilityAction/Other/Encrypt.cs:12
- NuGet dependencies are not locked
- Rethrow loses stack trace (`throw ex;`) src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:170
Minor — 242 finding(s)
- Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:652
- Deprecated: @babel/plugin-proposal-class-properties REDACTED:661
- Deprecated: @babel/plugin-proposal-class-properties REDACTED:669
- Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:686
- Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:702
- Deprecated: @babel/plugin-proposal-json-strings REDACTED:710
- Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:718
- Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:726
- Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:734
- Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:742
- Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:750
- Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:758
- Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:767
- Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:775
- Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:783
- Deprecated: @babel/plugin-proposal-private-methods REDACTED:792
- Deprecated: @babel/plugin-proposal-unicode-property-regex REDACTED:800
- Deprecated: @hapi/address REDACTED:1576
- Deprecated: @hapi/bourne REDACTED:1581
- Deprecated: @hapi/hoek REDACTED:1586
- Deprecated: @hapi/joi REDACTED:1591
- Deprecated: @hapi/topo REDACTED:1601
- Deprecated: @types/testing-library__dom REDACTED:2231
- Deprecated: abab REDACTED:2510
- Deprecated: airbnb-prop-types REDACTED:2597
- Orphaned file REDACTED:1
- Orphaned file src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataManageAppService.cs:1
- Orphaned file src/IEManageSystem.CMS/DomainModel/Pages/PageManager.cs:1
- Orphaned file src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/ApiScopes/ApiScopeManageAppService.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file src/IEManageSystem.Core/Entitys/Authorization/Users/UserManager.cs:1
- Orphaned file src/IEManageSystem.CMS/DomainModel/Menus/MenuManager.cs:1
- Orphaned file src/IEManageSystem.Application/Services/Users/UserAppService.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Roles/RoleManageAppService.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataQueryAppService.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/IEManageSystem.Web/Startup/Startup.cs:1
- Orphaned file src/IEManageSystem.EntityFrameworkCore/Configures/CMS/LeafMenuConfigure.cs:1
- Orphaned file src/UtilityAction/ValidateFun/VerificationCode.cs:1
- Orphaned file src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:1
- Orphaned file src/IEManageSystem.Web/Controllers/AccountController.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageManageAppService.cs:1
- Orphaned file src/IEManageSystem.Core/Entitys/Authorization/Users/AdminManager.cs:1
- Orphaned file src/IEManageSystem.Core/Entitys/Authorization/Permissions/PermissionManager.cs:1
- Orphaned file src/IEManageSystem.CMS/DomainModel/Logics/ExecLogicService.cs:1
- Orphaned file src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/MenuManageAppService.cs:1
- Outdated: Abp.AspNetCore REDACTED:56
- Outdated: Abp.Castle.Log4Net REDACTED:57
- Outdated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:43
- Outdated: Microsoft.AspNetCore.SpaServices.Extensions REDACTED:38
- Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:31
- Outdated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:49
- Outdated: Abp src/IEManageSystem.Common/IEManageSystem.Common.csproj:8
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables src/IEManageSystem.Core/IEManageSystem.Core.csproj:15
- Outdated: Microsoft.Extensions.Configuration.Json src/IEManageSystem.Core/IEManageSystem.Core.csproj:16
- Outdated: Abp.AutoMapper REDACTED:21
- Outdated: Abp.EntityFrameworkCore REDACTED:20
- Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:25
- Outdated: Microsoft.EntityFrameworkCore.Sqlite REDACTED:29
- Outdated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:30
- Outdated: Pomelo.EntityFrameworkCore.MySql REDACTED:35
- Outdated: Abp.TestBase test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:30
- Outdated: Castle.Windsor.MsDependencyInjection test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:32
- Outdated: Microsoft.EntityFrameworkCore.InMemory test/IEManageSystem.Tests/IEManageSystem.Tests.csproj:33
- Outdated: Abp.AspNetCore.TestBase REDACTED:29
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:11
- Outdated: coverlet.collector test/IEManageSystem.ApiAuthorization.Tests/IEManageSystem.ApiAuthorization.Tests.csproj:16
- Mutable entity: Permission src/IEManageSystem.Core/Entitys/Authorization/Permissions/Permission.cs:9
- Mutable entity: Role src/IEManageSystem.Core/Entitys/Authorization/Roles/Role.cs:11
- Mutable entity: RolePermission src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:10
- Mutable entity: User src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:16
- Mutable entity: UserRole src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:10
- Mutable entity: Account src/IEManageSystem.Core/Entitys/Authorization/Users/Accounts/Account.cs:11
- Mutable entity: ApiScope src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScope.cs:13
- Mutable entity: ApiScopePermission src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:12
- Mutable entity: ApiScopeNode src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/AuthorizationNodes/ApiScopeNode.cs:11
- Mutable entity: CmsComponent src/IEManageSystem.CMS/DomainModel/CmsComponent.cs:9
- Mutable entity: ComponentSingleData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:9
- Mutable entity: ContentComponentData src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:11
- Mutable entity: ContentPagePermission src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:10
- Mutable entity: ContentPagePermissionCollection src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:12
- Mutable entity: Logic src/IEManageSystem.CMS/DomainModel/Logics/Logic.cs:8
- Mutable entity: CompositeMenu src/IEManageSystem.CMS/DomainModel/Menus/CompositeMenu.cs:7
- Mutable entity: MenuBase src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:11
- Mutable entity: PageData src/IEManageSystem.CMS/DomainModel/PageDatas/PageData.cs:18
- Mutable entity: Tag src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:9
- Mutable entity: SiteSetting src/IEManageSystem.Common/DomainModel/SiteSetting.cs:9
- redundant comment src/IEManageSystem.Application/Properties/AssemblyInfo.cs:5
- redundant comment src/IEManageSystem.Application/Properties/AssemblyInfo.cs:13
- redundant comment src/IEManageSystem.Application/Properties/AssemblyInfo.cs:18
- redundant comment src/IEManageSystem.Core/Properties/AssemblyInfo.cs:5
- redundant comment src/IEManageSystem.Core/Properties/AssemblyInfo.cs:13
- redundant comment src/IEManageSystem.Core/Properties/AssemblyInfo.cs:18
- redundant comment src/IEManageSystem.EntityFrameworkCore/Properties/AssemblyInfo.cs:5
- redundant comment src/IEManageSystem.EntityFrameworkCore/Properties/AssemblyInfo.cs:13
- redundant comment src/IEManageSystem.EntityFrameworkCore/Properties/AssemblyInfo.cs:18
- redundant comment test/IEManageSystem.Tests/Properties/AssemblyInfo.cs:5
- redundant comment test/IEManageSystem.Tests/Properties/AssemblyInfo.cs:13
- redundant comment test/IEManageSystem.Tests/Properties/AssemblyInfo.cs:18
- redundant comment test/IEManageSystem.Web.Tests/Properties/AssemblyInfo.cs:5
- redundant comment test/IEManageSystem.Web.Tests/Properties/AssemblyInfo.cs:13
- redundant comment test/IEManageSystem.Web.Tests/Properties/AssemblyInfo.cs:18
- Primitive id on a domain type: RolePermission.RoleId src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:13
- Primitive id on a domain type: RolePermission.PermissionId src/IEManageSystem.Core/Entitys/Authorization/Roles/RolePermission.cs:15
- Primitive id on a domain type: User.TenantId src/IEManageSystem.Core/Entitys/Authorization/Users/User.cs:87
- Primitive id on a domain type: UserRole.UserId src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:25
- Primitive id on a domain type: UserRole.RoleId src/IEManageSystem.Core/Entitys/Authorization/Users/UserRole.cs:27
- Primitive id on a domain type: ApiScopePermission.ApiScopeId src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:27
- Primitive id on a domain type: ApiScopePermission.PermissionId src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopePermission.cs:29
- Primitive id on a domain type: ComponentSingleData.ComponentDataId src/IEManageSystem.CMS/DomainModel/ComponentDatas/ComponentSingleData.cs:25
- Primitive id on a domain type: ContentComponentData.PageDataId src/IEManageSystem.CMS/DomainModel/ComponentDatas/ContentComponentData.cs:24
- Primitive id on a domain type: ContentPagePermission.PermissionId src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:12
- Primitive id on a domain type: ContentPagePermission.ContentPagePermissionCollectionId src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermission.cs:17
- Primitive id on a domain type: MenuBase.CompositeMenuId src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:28
- Primitive id on a domain type: MenuBase.RootMenuId src/IEManageSystem.CMS/DomainModel/Menus/MenuBase.cs:30
- Primitive id on a domain type: Tag.PageDataId src/IEManageSystem.CMS/DomainModel/PageDatas/Tag.cs:18
- Primitive id on a domain type: SiteSetting.Key src/IEManageSystem.Common/DomainModel/SiteSetting.cs:11
- Duplicated predicate src/IEManageSystem.Core/Entitys/Authorization/Roles/RoleManager.cs:44
- Duplicated predicate REDACTED:147
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/RootComponentContainerBox/index.js:37
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/RNApp/RNCMS/Home/PageContainer.js:95
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:18
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Footer.js:105
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:135
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Home/PageContainer.jsx:103
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/Templates/IETemplateComponents/IEButton/IComponent.js:38
- Duplicated predicate src/IEManageSystem.Web/ClientApp/src/WebApp/Personal/AccountSecurity/AccountSecurity.jsx:105
- Duplicated predicate src/IEManageSystem.Application/Services/ManageHome/AuthorizeManage/Admins/AdminManageAppService.cs:51
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Commented-out code src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/IMenuManageAppService.cs:13
- Commented-out code src/IEManageSystem.Application/Services/ManageHome/CMS/Menus/IMenuManageAppService.cs:15
- Commented-out code src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs:56
- Unused export 'default' src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/variables/commonColor.js:24
- Unused export 'default' src/IEManageSystem.Web/ClientApp/src/WebApp/CMSManage/Component/Components/BaseComponents/index.js:13
- Accessibility enforcement below the top rung REDACTED:33
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- Projects may be oversized for their cohesion REDACTED:1
- REDACTED
- Dormant codebase
- Most significant orphaned file src/UtilityAction/Web/FileContentType.cs:1
- IL efficiency: 3 authored method(s) exceed the IL budget src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageDataQueryAppService.cs:53
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No SAST
- No dependency-update automation REDACTED:20
- No release approval gate
- No changelog
- No performance benchmarks
- Unused export 'ContainerSettingName' src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/Components/BaseComponents/BaseContainerComponent/ComponentContainer.js:4
- Unused module-local declaration 'locale' src/IEManageSystem.Web/ClientApp/src/Templates/RNIETemplateComponents/IEPostList/Component.js:142
- No security response headers detected
- No app-layer HTTPS enforcement detected
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
Minor — 24 finding(s)
- Outdated: Castle.Core
- Outdated: Microsoft.AspNetCore.Diagnostics
- Outdated: Microsoft.AspNetCore.Mvc
- Outdated: Microsoft.AspNetCore.Server.IISIntegration
- Outdated: Microsoft.AspNetCore.Server.Kestrel
- Outdated: Microsoft.AspNetCore.StaticFiles
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NSubstitute
- Outdated: Shouldly
- Outdated: xunit
- Outdated: xunit.extensibility.execution
- Outdated: xunit.runner.visualstudio
- Outdated: AngleSharp
- Outdated: Microsoft.AspNetCore.Authentication
- Outdated: Microsoft.CodeAnalysis.CSharp
- doc comments repeat the names src/IEManageSystem.ApiAuthorization/DomainModel/ApiScopes/ApiScopeManager.cs:89
- doc comments repeat the names src/IEManageSystem.Application/Services/Accounts/AccountAppService.cs:37
- doc comments repeat the names src/IEManageSystem.CMS/DomainModel/ContentPagePermissionCollections/ContentPagePermissionCollection.cs:23
- doc comments repeat the names src/IEManageSystem.Core/Entitys/Authorization/Users/RegisterManager.cs:27
- doc comments repeat the names src/IEManageSystem.JwtAuthentication/Authorizations/IEAuthorizationRequirement.cs:10
- doc comments repeat the names src/IEManageSystem.Web/Controllers/AccountController.cs:59
- doc comments repeat the names src/UtilityAction/ValidateFun/ValidateModel.cs:12
- Mock framework: NSubstitute
- Off the main sequence: IEManageSystem.Common src/IEManageSystem.Common/IEManageSystem.Common.csproj:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-466e994e165648cfab71cc549bc8444d/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-466e994e165648cfab71cc549bc8444d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list IEManageSystem.sln package --vulnerable --include-transitive --format json | 153 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | 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 Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
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