kawser2133/clean-structured-project

This system is an ASP.NET Core application built on Clean Architecture principles, designed to manage product data through a structured layering of Core, Infrastructure, and UI components. It provides full CRUD capabilities for products, supported by Entity Framework Core for database persistence and AutoMapper for object mapping. The architecture is complemented by a comprehensive unit test suite and utilizes .NET 7 with standard dependency injection and caching strategies.

The application now includes the initial Entity Framework Core migration and model snapshot for the \ApplicationDbContext\, establishing the database schema for \Products\ and ASP.NET Identity tables (\Users\, \Roles\, etc.). Additionally, a \BaseRepository\ is introduced with support for generic existence checks and pagination, and a \ProductRepository\ is added to handle product-specific data access.

Project.Infrastructure · high confidence

The repository has been initialized with a complete ASP.NET Core project template following Clean Architecture principles. This includes the solution file (Clean.Project.sln) defining the Core, Infrastructure, and UI layers, along with a comprehensive .gitignore for Visual Studio and .NET builds, an MIT License, and a detailed README.md explaining the architecture, features, and usage instructions.

(repo-wide) · high confidence

The Project.UI layer is introduced with a complete set of controllers, views, and configuration files to support product management. The ProductController implements CRUD operations (Create, Edit, Delete, Details) and a paginated index view, backed by in-memory caching for product details. The Home controller provides a dashboard view. The application registers service, repository, and AutoMapper mappings, and configures a custom request/response logging middleware. The UI includes a sidebar layout, CSS styling, and JavaScript for sidebar toggling.

Project.UI · high confidence

Added foundational classes and interfaces to support product operations: a generic pagination view model, a base entity class, and a Product entity with validation attributes. Introduced a NotFoundException for error handling, along with generic mapper and repository interfaces that define standard CRUD and pagination operations. The ProductService implements these interfaces, using AutoMapper for object mapping and manual mapping for updates, enabling retrieval, creation, update, and deletion of products with support for paginated results.

Project.Core · high confidence

Added new unit tests for the Product domain, including tests for the ProductService, ProductRepository, and ProductController. The test suite covers the CreateProductAsync flow, repository AddAsync operations, and the controller's Index action, ensuring that the product management features function correctly across the application layers.

Project.UnitTest · high confidence

The project has been initialized with a .NET 7 target framework across all four projects (Core, Infrastructure, UI, and UnitTest). This includes adding NuGet packages for Entity Framework Core 7.0.8, AutoMapper 12.0.1, and various testing and code-generation tools, establishing the foundational dependencies for the application.

(dependencies) · high confidence

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

• CAI 36 → 35 (-1.4)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 69 → 69 (+0.0)
• Architecture 86 → 86 (+0.0)
• Maturity 48 → 48 (+0.0)
• Readiness 36 → 36 (+0.0)
• Security 22 → 19 (-3.1)
• Accessibility 66 → 66 (+0.0)

• Duplicated block (19 lines × 2) (Project.UI/Controllers/ProductController.cs)
• Medium CVE: Azure.Identity 1.6.0
• Medium CVE: Azure.Identity 1.6.0
• No exposed public API
• single-maintainer — knowledge-concentration (bus factor) risk

• Documentation: no usage examples (README.md)
• Duplicated block (30 lines × 2) (Project.UI/Controllers/ProductController.cs)
• End-of-life runtime: .NET net7.0
• The method name 'IsExists' in the repository layer uses non-standard plural phrasing for a boolean existence check.
• The method name 'IsExists' uses non-standard plural phrasing for a boolean existence check. Standard convention is singular 'Exists' (e.g., 'Does the product exist?').
• The method name 'IsExistsForUpdate' combines the non-standard 'IsExists' with a specific use-case suffix. While the suffix is descriptive, the base verb form is inconsistent with standard C# conventions for existence checks.
• The method name 'IsExistsForUpdate' in the repository layer mirrors the service layer inconsistency. It should align with the corrected service naming.
• redundant comment (Project.Infrastructure/Data/ApplicationDbContextConfigurations.cs)

• Unchanged — 1 HTTP endpoints

• Unchanged — 2 containers · 0 contexts · 0 edges

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

kawser2133/clean-structured-project 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.