IceEmblem/IEManageSystem

This release establishes the foundational architecture for the IE Manage System, introducing a layered structure with core, application, and data access modules. It delivers initial implementations for user and role-based authorization, API scope management, and a flexible CMS engine featuring dynamic logic execution and in-memory caching. The update also includes multi-database support via Entity Framework Core, comprehensive unit test coverage for new services, and a migration to .NET Core 3.0 and ABP 5.0.

The application now includes new backend services for account management and authorization management. Users can register and log in via the new AccountAppService. Administrators can manage admin accounts (create, update, delete, and assign roles/permissions) through the AdminManageAppService. Additionally, new services allow for the management of API scopes and permissions, enabling administrators to configure access controls and permissions for API resources.

src/IEManageSystem.Application/Services · high confidence

Introduced new attributes to manage API domain authorization. The ApiAuthorizationAttribute enables API domain authorization checks on controllers or AppServices, while the ApiAuthorizationQueryAttribute distinguishes query methods (requiring API query access) from management methods (requiring API management access).

src/IEManageSystem.Application/Attributes · high confidence

Introduced new domain services for managing API scopes and checking user permissions. The ApiScopeManager handles registration and caching of API scopes, while the CheckPermissionService evaluates whether a user has the necessary manage or query permissions to access specific API scopes. This adds the core logic for API-level authorization and scope management within the system.

src/IEManageSystem.ApiAuthorization · high confidence

Introduced new domain entities to support the system's authorization model. This includes the Permission entity, which defines access rights and includes built-in super, admin, and user permissions. The Role entity manages role definitions and their associated permissions, while the UserRole and RolePermission association classes link users to roles and roles to permissions. Additionally, the User and Account entities were added to handle user profiles, authentication credentials, and security questions. These changes establish the foundational data structures for user and role management.

IEManageSystem.Core · high confidence

Introduced new domain classes to support API scope management and permissions. This includes the \ApiScope\ entity with \ApiManageScope\ and \ApiQueryScope\ sub-nodes, along with the \ApiScopePermission\ mapping class. These models enable the system to define and manage granular permissions for API scopes, supporting both management and query access control.

IEManageSystem.ApiAuthorization · high confidence

A new in-memory cache implementation, IEMemoryCache, has been introduced in the CommonInfrastructure.Core module. This class extends the standard MemoryCache to provide a configurable caching mechanism, supporting the system's performance optimization efforts.

src/IEManageSystem.CommonInfrastructure/Core · high confidence

Added configuration and utility files for the web client, including Babel and React Native build configurations, a module loader script, and standard web assets (manifest, robots.txt, index.html).

src/IEManageSystem.Web · high confidence

The Android application's main entry point (MainApplication.java) has been added, establishing the React Native host configuration and integrating key native modules including the WebView, Video, Vector Icons, File System, and Camera packages. Additionally, Flipper debugging support is initialized during app startup, enabling developers to inspect network requests and state in debug builds.

. · high confidence

The repository was initialized with the core solution file (IEManageSystem.sln) defining the project structure, including the Web, Core, Application, and Entity Framework Core layers, alongside standard configuration files like .gitattributes, .gitignore, and a MIT LICENSE.

(repo-wide) · high confidence

The application layer introduces new Data Transfer Objects (DTOs) to expose domain entities for the API and user management. This includes ApiScopeDto for API scopes, PermissionDto and RoleDto for core authorization, and a suite of user-related DTOs (UserDto, AccountDto, SafetyProblemDto) that map to the underlying Entity Framework Core models. These additions enable the application to serialize and transmit user, role, and permission data to clients.

(repo-wide) · medium confidence

The EF Core configuration layer now includes entity type configurations and seed data for the CMS menu system (CompositeMenu, LeafMenu, and MenuBase), page data, and core authorization models (Account, User, Role, and Permission). This establishes the default application state, including a SuperAdmin user and role, and pre-configures the main and app-side navigation menus.

src/IEManageSystem.EntityFrameworkCore/Configures · high confidence

Added a new ApiScopeProvider class that registers API scopes for user information, administrator, role, and permission management, as well as CMS features like menu, page, picture, and logic management, along with site settings. This establishes the foundational structure for API authorization and content management capabilities within the system.

src/IEManageSystem.Application/ApiScopeProviders · high confidence

Added a new set of Data Transfer Objects (DTOs) in the CMS module to support content management features. The changes introduce DTOs for page data (PageDataDto, PageDto), menu structures (MenuDto), component data (ComponentDataDto, SingleComponentDataDto), and associated entities like tags (TagDto), pictures (PictureDto), and permissions (ContentPagePeimissionCollectionDto, ContentPagePermissionDto). These DTOs map to domain models and enable the backend to handle page content, menu navigation, and component-based page building.

src/IEManageSystem.Application/Dtos/CMS · high confidence

Added domain models and managers for managing CMS content, including page and component data handling, menu management with caching, and a logic execution service for dynamic actions. The change introduces new classes such as ComponentDataManager, PageDataManager, MenuManager, and ExecLogicService, enabling structured content management, permission-based access control, and extensible logic execution.

src/IEManageSystem.CMS · high confidence

Added new domain models to support content management: PageData with scoring, click tracking, and tag associations; a hierarchical menu structure with CompositeMenu, LeafMenu, and MenuBase; component data models (ContentComponentData, ComponentSingleData) for flexible content storage; and ContentPagePermission/ContentPagePermissionCollection to manage page-level access and query permissions for articles.

IEManageSystem.CMS · high confidence

The application layer now provides a standardized base class, IEManageSystemAppServiceBase, which configures the system's localization source for all derived application services. Additionally, the IEManageSystemApplicationModule registers the application's components by depending on the core, CMS, API authorization, and AutoMapper modules, establishing the foundation for the application's service architecture.

src/IEManageSystem.Application · high confidence

A new runtime compilation mechanism has been added to the CMS infrastructure, allowing business logic to be defined as C\# code strings and executed dynamically. This is implemented through a new \ActuatorFactory\ that compiles user-provided code into a temporary assembly, which is then loaded and invoked via reflection. The system now supports registering and executing these 'actuators' to handle CMS page and component data, providing a more flexible way to manage content logic without recompiling the main application.

src/IEManageSystem.CommonInfrastructure/CMS · high confidence

Adds new repository classes to the data access layer, including a base repository (EfRepositoryBase) and a generic implementation (EfRepository) that provides query tracking controls (NoTracking/Tracking) and support for complex LINQ includes. A specific repository (PageDataRepository) is also added for CMS page data, enabling the application to manage page content through this new data access pattern.

src/IEManageSystem.EntityFrameworkCore/Repositorys · medium confidence

The system now includes a new authorization and user management layer within the core module. This introduces a \LoginManager\ for handling authentication and retrieving user roles and permissions, alongside \UserManager\, \AdminManager\, and \RegisterManager\ for user lifecycle operations. Role and permission management is handled by \RoleManager\ and \PermissionManager\, which also implement caching for permission data. Additionally, the application is configured with multi-language support for English, Turkish, and Simplified Chinese, and a configuration helper is added to manage application settings.

src/IEManageSystem.Core · high confidence

Introduced new domain and data transfer objects for site settings. The \SiteSetting\ entity in the \IEManageSystem.Common.DomainModel\ namespace now includes properties for \Key\, \Value\, \DisplayName\, and \Group\. A corresponding \SiteSettingDto\ has been added to the \IEManageSystem.Application/Dtos/Common\ directory, mapping to the domain model via AutoMapper.

IEManageSystem.Common, src/IEManageSystem.Application/Dtos/Common · high confidence

The Entity Framework Core layer now supports SQL Server, MySQL, and SQLite. The \DbContextOptionsConfigurer\ was added to dynamically configure the database provider based on a \dbType\ parameter, and the \IEManageSystemDbContext\ was created with the corresponding \DbSet\ properties and model configurations. This change enables the application to connect to different database systems, with the specific provider selected at runtime via the \ConnectionType\ configuration.

src/IEManageSystem.EntityFrameworkCore/EntityFrameworkCore · high confidence

Added test data builders for core domain entities; Added test infrastructure for IEManageSystem; Added tests for CMS page and page data management services; Added tests for the CMS ActuatorFactory; Added unit tests for CheckPermissionService; Added unit tests for logic registration and execution services; Added unit tests for menu management services; Added web integration test infrastructure.

The project has been upgraded to target .NET Core 3.0, requiring a compatible runtime environment. The Abp framework has been updated to version 5.0.0, which brings in corresponding updates to related packages such as Abp.EntityFrameworkCore, Abp.AutoMapper, and Abp.AspNetCore. Additionally, the solution structure has been reorganized into distinct layers including Core, Application, CMS, Common, and Web, each with their own project files and dependencies. The frontend client application has also been updated with new dependencies for React Native, Ant Design, and various UI components.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 24 → 24 (-0.2)
• Rubric changed (rubric-2026.08.18 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 44 → 44 (-0.4)
• Architecture 85 → 64 (-20.9)
• Maturity 43 → 43 (-0.1)
• Readiness 13 → 14 (+0.7)
• Security 19 → 21 (+2.0)
• Accessibility 41 → 39 (-1.5)
• Performance 60 → 60 (+0.0)

• Boundary-crossing change coupling: ExecLogicService.cs ↔ ActuatorFactory.cs (src/IEManageSystem.CMS/DomainModel/Logics/ExecLogicService.cs)
• Boundary-crossing change coupling: PageManageAppService.cs ↔ PageDataManager.cs (src/IEManageSystem.Application/Services/ManageHome/CMS/Pages/PageManageAppService.cs)
• Bounded contexts not declared
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• …and 50 more

• (anonymous) (cognitive 47) (src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js)
• (anonymous) (cyclomatic 48) (src/IEManageSystem.Web/ClientApp/src/RNApp/RNCommon/Theme/NativeBaseTheme/components/Header.js)
• CommentedOutCode (src/IEManageSystem.CommonInfrastructure/CMS/ActuatorFactory.cs)
• ComponentContainerBox.getStyle (cognitive 61) (src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js)
• ComponentContainerBox.getStyle (cyclomatic 37) (src/IEManageSystem.Web/ClientApp/src/Common/BaseCMSManage/ComponentContainerBoxs/index.js)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• Critical CVE: [GHSA redacted] (src/IEManageSystem.Web/ClientApp/yarn.lock)
• …and 157 more

• Unchanged — 13 HTTP endpoints

• Containers 0 added · 0 removed · contexts 1 added · 1 removed · edges 0 added · 0 removed

• app

• .

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

IceEmblem/IEManageSystem was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.