Skip to content
CAI
Software that uses CAICheck a score

nitin27may/clean-architecture-docker-dotnet-angular

40.4

Weak · 9 November 2026

8.5k

lines of production code

TypeScript

with C#

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a full-stack application starter kit built on .NET 10, Angular 22, and PostgreSQL, designed to demonstrate a production-ready Clean Architecture with Role-Based Access Control. It provides a complete implementation for managing contacts, users, roles, and permissions, featuring granular API authorization and comprehensive activity logging. The platform includes an administrative dashboard for system configuration and monitoring, alongside a user-facing interface for profile management and contact operations.

How it got here

2021 — Initial release and core feature implementation

7 changes.

This period marks the initial release of a full-stack Clean Architecture starter kit, establishing the foundational project structure with Angular 22, .NET 10, and PostgreSQL. The work focused on scaffolding the application with essential DevOps tooling, Docker configurations, and role-based access control mechanisms. Subsequent efforts implemented core user-facing features, including contact management, user profile editing, and a landing page, while upgrading the underlying technology stack to their latest major versions.

2022–2025 — Admin panel and RBAC implementation

11 changes.

This period focused on establishing the core infrastructure and security framework, including a .NET Aspire development environment, Nginx load balancing, and a granular role-based access control system with activity logging. It simultaneously delivered a comprehensive admin dashboard for managing users, roles, permissions, operations, and pages, alongside the initial domain model and API endpoints for contact management.

Features

Admin activity log monitoring interface

Administrators can now view and monitor user activities through a new Activity Logs page in the admin area. This feature provides a paginated table displaying username, email, activity description, endpoint, and timestamp for each event. Users can filter logs by username or email using the dedicated filter form, perform quick client-side searches across all columns, and sort the data by any column header. The interface includes loading, empty, and error states to ensure a smooth experience while retrieving log data.

frontend/src/app/feature/admin/activity-log · high confidence

Admin dashboard with role-based access control and activity logging

The admin feature now provides a structured dashboard with a navigation sidebar linking to Pages, Operations, Permissions, Role Permissions, User Roles, and Users. Access to these sections is enforced via a PermissionGuard that checks specific read permissions (e.g., 'Users', 'ActivityLog', 'Pages') before rendering the corresponding components. The module also introduces an Activity Log view, secured by its own permission check, allowing administrators to monitor system activities.

frontend/src/app/feature/admin · high confidence

Frontend scaffolding with Angular 21, Material 3, and Tailwind 4

The frontend project has been initialized with a modern enterprise stack: Angular 21, Angular Material 19+, and Tailwind CSS 4. This includes a new Dockerfile (Node 22 builder, Nginx server), Nginx configuration for SPA routing, and proxy settings for the Aspire 13 backend. Core UI components have been added, including a confirm dialog, empty state, page header, and skeleton loaders, alongside a comprehensive validation library (error-tailor) and permission directives/guards to support role-based access control.

frontend · high confidence

Initial database schema, seed data, and API request collection for Contacts management

This change introduces the foundational database structure and initial data for the application, including tables for Users, Roles, Permissions, Pages, Operations, Contacts, and Activity Logs, along with a seed script that populates default admin, reader, and editor roles and users. It also adds a Bruno API collection (\api-collection\) containing pre-configured HTTP requests for testing the Contacts, Users, Roles, Permissions, Pages, and Operations endpoints, providing a ready-to-use client-side interface for developers to interact with the new backend capabilities.

(repo-wide) · high confidence

Initial domain model and contact person management logic

This change introduces the core domain entities for the Contact module, including ContactPerson, User, Role, Permission, and their associated mapping tables (UserRole, RolePermission, PageOperationMapping). It also adds the application-layer use cases for creating and updating contact persons, complete with validation rules for fields like email, mobile, and date of birth. This establishes the foundational data structures and business logic for managing contact records within the system.

Contact.Domain, backend/Contact.Application/UseCases/ContactPerson · high confidence

Initial release of the Clean Architecture full-stack starter kit

The repository is initialized with a production-ready full-stack application featuring an Angular 22 frontend, a .NET 10 backend API, and PostgreSQL 17. The project introduces a Clean Architecture structure with Role-Based Access Control (RBAC), utilizing .NET Aspire 13.4 for local development orchestration. It includes comprehensive DevOps tooling with Docker Compose configurations (including pre-built images from GHCR), NGINX load balancing, and GitHub Actions CI workflows. Additionally, the repo establishes project governance with a permissive license policy (replacing AutoMapper with Mapperly), contributing guidelines, and security reporting procedures.

(repo-wide) · high confidence

Introduce .NET Aspire application host and service defaults

The aspire location now includes a new AppHost configuration that orchestrates the local development environment by provisioning a PostgreSQL database with pgAdmin, a .NET Contact API, and an Angular frontend, while wiring them together with service discovery and health checks. Additionally, a ServiceDefaults library has been added to provide standardized OpenTelemetry instrumentation, resilience handlers, and health check endpoints for the services.

aspire · high confidence

Introduce Nginx-based load balancer for frontend and API routing

Added a new Nginx load balancer configuration that routes traffic to the Angular frontend on port 8080 and the API backend on port 8000. The setup includes specific proxy headers for SPA handling and caching control for the frontend, while also exposing the Swagger documentation under the /swagger/ path.

loadbalancer · high confidence

Introduce granular, role-based API authorization and activity logging

The backend now enforces fine-grained access control on all API endpoints (Contacts, Users, Roles, Pages, Operations) using a custom permission system. Controllers are secured with an AuthorizePermission attribute that validates specific page-operation policies (e.g., Contacts.Create) against the user's assigned roles. A new middleware pipeline captures detailed activity logs for every authorized request, recording the user, action, and endpoint. This replaces the previous generic authorization model with a structured, auditable permission framework.

backend · high confidence

New Operations and Pages management interfaces in the admin area

Administrators can now manage system operations and application pages directly through the frontend. This change introduces dedicated UI components and services for both areas: the Operations interface allows users to create, edit, and delete operations by name and description, while the Pages interface enables management of application pages by name and URL. Both interfaces provide a unified experience with inline forms, data tables for listing existing items, and real-time validation feedback.

frontend/src/app/feature/admin/operations, frontend/src/app/feature/admin/pages · high confidence

New Role Management interface in Admin panel

Administrators can now create, edit, and delete system roles via a new dedicated page. This change introduces the \RolesComponent\ and \RoleService\ in the admin roles feature area, providing a UI to manage role names and descriptions, with a table listing existing roles and a form for adding or updating them.

frontend/src/app/feature/admin/roles · high confidence

New User Management interface in the Admin area

The admin users feature now includes a dedicated UI for managing system users. Administrators can view a list of users with their first name, last name, username, email, and mobile number, and perform create, edit, and delete operations. The interface provides a form for adding or editing user details with validation, a data table for listing existing users, and confirmation dialogs for deletions, backed by the core UserService.

frontend/src/app/feature/admin/users · high confidence

New User Roles Management interface in Admin panel

Administrators can now assign and manage roles for system users via a new dedicated page. This change introduces a standalone Angular component featuring a form to select a user and assign multiple roles, alongside a details section that displays the user's current role assignments. The implementation includes a new service to handle the API calls for fetching and updating user roles, along with the necessary UI components for loading states and validation feedback.

frontend/src/app/feature/admin/user-roles · high confidence

New contact list view with role-based access and pagination

The contact list page now displays contacts in a sortable, filterable, and paginated table. Access to view, edit, and delete contacts is controlled by role-based permissions (Create, Read, Update, Delete) via the \*hasPermission directive. The interface includes a search bar to filter by name, email, or phone, and allows users to sort by name, email, phone, or city. Users can navigate through pages of results and perform actions like viewing details, editing, or deleting specific contacts, with appropriate feedback provided via notifications.

frontend/src/app/feature/contact/contact-list · high confidence

New home page with technology showcase and feature highlights

The user home page now displays a dedicated landing section that highlights the application's technology stack (including Angular 21, .NET 10, and PostgreSQL) and key features like contact management, secure authentication, and dark mode support. Users can now directly access the GitHub repository, view a demo video, or read documentation from this page, with the UI styled using Material Design components and TailwindCSS.

frontend/src/app/feature/user/home · high confidence

New standalone contact creation and editing form

The contact form has been replaced with a new standalone Angular component that provides a unified interface for both creating new contacts and editing existing ones. The form collects first name, last name, email, mobile number, date of birth, city, and postal code, utilizing Angular Material components for input fields and a date picker. It includes client-side validation for required fields and email format, handles submission loading states with a spinner, and displays success or error notifications upon completion. The component also features a reset function and navigation back to the contacts list.

frontend/src/app/feature/contact/contact-form · high confidence

New user profile management interface with tabbed editing and password change

A new standalone Profile component has been introduced for the user profile feature, providing a tabbed interface for managing account details. Users can now edit their first name, last name, email, and phone number through a form with validation, while their role is displayed as a read-only label. A separate tab allows users to change their password by entering their current password and a new password, with client-side validation ensuring fields are not empty and passwords match. The component uses Angular Material for UI elements and handles updates via the UserService, refreshing the local state and notifying the user of success or failure.

frontend/src/app/feature/user/profile · high confidence

Dependencies

Upgrade to .NET 10, Angular 22, and .NET Aspire 13.4.6

The project has upgraded its core technology stack to newer major versions. The backend now targets .NET 10.0 and utilizes .NET Aspire 13.4.6 for orchestration, including updated Service Defaults with .NET 10-compatible OpenTelemetry and resilience packages. The frontend has been upgraded to Angular 22.1.3 and Tailwind CSS 4.1.1. Additionally, the backend replaced AutoMapper with Mapperly for object mapping.

(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

Score

  • CAI 48 → 40 (-7.8)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 70 → 70 (+0.0)
  • Architecture 85 → 86 (+1.6)
  • Maturity 56 → 72 (+16.0)
  • Readiness 35 → 35 (+0.0)
  • Security 56 → 56 (-0.0)
  • Domain Modelling 33 (new)
  • Accessibility 57 → 46 (-10.2)
  • Performance 100 → 100 (+0.0)

Resolved (2)

  • High CVE: [GHSA redacted] (frontend/package-lock.json)
  • The concept of retrieving role permission mappings is named differently in the interface (GetRolePermissionMappingsAsync) and the service implementation (GetRolePermissionMappingByRoleIdAsync). The interface uses plural 'Mappings' and a generic name, while the service uses singular 'Mapping' and specifies 'ByRoleId'. This inconsistency in number and specificity can be confusing.

New (38)

  • High CVE: [GHSA redacted] (frontend/package-lock.json)
  • High CVE: [GHSA redacted] (frontend/package-lock.json)
  • High CVE: [GHSA redacted] (frontend/package-lock.json)
  • Medium CVE: [GHSA redacted] (frontend/package-lock.json)
  • Outdated (npm): @tailwindcss/node
  • Outdated (npm): @tailwindcss/oxide
  • Outdated (npm): @tailwindcss/oxide-android-arm64
  • Outdated (npm): @tailwindcss/oxide-darwin-arm64
  • Outdated (npm): @tailwindcss/oxide-darwin-x64
  • Outdated (npm): @tailwindcss/oxide-freebsd-x64
  • Outdated (npm): @tailwindcss/oxide-linux-arm-gnueabihf
  • Outdated (npm): @tailwindcss/oxide-linux-arm64-gnu
  • Outdated (npm): @tailwindcss/oxide-linux-arm64-musl
  • Outdated (npm): @tailwindcss/oxide-linux-x64-gnu
  • Outdated (npm): @tailwindcss/oxide-linux-x64-musl
  • Outdated (npm): @tailwindcss/oxide-wasm32-wasi
  • Outdated (npm): @tailwindcss/oxide-win32-arm64-msvc
  • Outdated (npm): @tailwindcss/oxide-win32-x64-msvc
  • Outdated (npm): @tailwindcss/postcss
  • Outdated (npm): encodeurl
  • …and 18 more

API surface

  • Unchanged — 32 HTTP endpoints

Architecture

  • Unchanged — 3 containers · 1 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

nitin27may/clean-architecture-docker-dotnet-angular 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 9 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 443946b32b23bac487ce8b5a8467ea78ae09c85c — 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-b921b700395b.