Skip to content
CAI
Software that uses CAICheck a score

kawser2133/clean-structured-project

35.8

Weak · 8 November 2026

767

lines of production code

C#

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

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.

Features

Initial database schema and repository layer for product management

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

Initial release of Clean Structured Project template

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

Initial release of the Product management UI

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

Introduce core abstractions and services for product management

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

Test coverage

Added unit tests for Product service, repository, and controller

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

Dependencies

Initial project structure and dependencies for .NET 7

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 cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.

Score

  • CAI 34 → 36 (+1.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 69 → 69 (+0.0)
  • Architecture 86 → 86 (+0.0)
  • Maturity 45 → 50 (+5.7)
  • Readiness 36 → 40 (+3.8)
  • Security 19 → 21 (+2.0)
  • Accessibility 57 → 46 (-10.6)
  • Performance 100 → 100 (+0.0)

Resolved (8)

  • Documentation: no usage examples (README.md)
  • End-of-life runtime: .NET net7.0 (Project.UnitTest/Project.UnitTest.csproj)
  • The method 'IsExistsForUpdate' is used to check for existence with specific criteria. While consistent across the service and repository layers, the name is verbose and grammatically awkward ('Is Exists'). Furthermore, comparing 'IsExists' (generic) and 'IsExistsForUpdate' (specific) shows a naming pattern where the generic check is 'IsExists' and the specific is 'IsExistsForUpdate'. This is internally consistent but stylistically poor. More critically, there is a potential confusion with 'IsExists<Tvalue>' in the repository which takes different parameters. However, the primary inconsistency is the use of 'IsExists' vs standard 'Exists'.
  • The method name 'IsExists' is grammatically incorrect and non-standard for a predicate returning a boolean. The standard C# convention is 'Exists' or 'ExistsAsync'. While 'IsExists' appears in both the interface and implementation, it represents a deviation from the common 'Exists' pattern used in most .NET libraries (e.g., List.Exists, String.IsNullOrEmpty). However, since it is consistent between interface and implementation, it is a style issue rather than an inconsistency between symbols. A more significant inconsistency is found in the naming of the update-check variant.
  • Vulnerable: AutoMapper
  • XML-doc coverage: Project.Core (Project.Core/Project.Core.csproj)
  • XML-doc coverage: Project.Infrastructure (Project.Infrastructure/Project.Infrastructure.csproj)
  • XML-doc coverage: Project.UI (Project.UI/Project.UI.csproj)

New (9)

  • End-of-life runtime: .NET net7.0 (Project.Core/Project.Core.csproj)
  • End-of-life runtime: .NET net7.0 (Project.Infrastructure/Project.Infrastructure.csproj)
  • End-of-life runtime: .NET net7.0 (Project.UI/Project.UI.csproj)
  • End-of-life runtime: .NET net7.0 (Project.UnitTest/Project.UnitTest.csproj)
  • Medium: security finding (details withheld)
  • Medium: security finding (details withheld)
  • Medium: security finding (details withheld)
  • Medium: security finding (details withheld)
  • redundant comment (Project.Core/Services/ProductService.cs)

API surface

  • Unchanged — 1 HTTP endpoints

Architecture

  • Unchanged — 2 containers · 0 contexts · 0 edges

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

Survey your own repository

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.

About this page

  • The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit e88d985f135030d979c55a23b8f60f05b003f9b9 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.