Skip to content
CAI
Software that uses CAICheck a score

Njabulo240/QuickStart

31.0

Weak · 8 November 2026

5.3k

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 web application built on ASP.NET Core and Angular, designed to manage accounts, customers, users, and roles. It provides a secure, authenticated frontend interface for user interaction and a robust backend API with comprehensive audit logging and exception handling. The architecture separates concerns into distinct layers including contracts, entities, repositories, and services, supported by a SQL database with migrations.

Features

Initial QuickStart API implementation with full CRUD, authentication, and audit logging

The QuickStart area introduces a complete ASP.NET Core Web API scaffold, including controllers for Accounts, Customers, Users, Roles, and Audit Logs, alongside a custom middleware for automatic audit logging. The change adds a comprehensive exception handling pipeline that maps internal exceptions to specific HTTP status codes and error responses, configures JWT-based authentication with ASP.NET Identity, and sets up a logging infrastructure. It also includes a fallback controller to serve the frontend application and establishes the database context and migrations for the initial schema.

QuickStart · high confidence

Introduces Angular-based QuickStartUI with authentication and layout components

The QuickStartUI area is introduced as a new Angular application, providing the frontend for the Matech platform. This includes a full application shell with routing, a responsive sidebar layout, and a header with user profile and logout functionality. Authentication features are added, including login, forgot password, and password change/reset forms, all protected by an AuthGuard. The UI also features error handling interceptors, a loading spinner, and various UI components like a sidebar navigation and a user profile dropdown.

QuickStartUI · high confidence

Dependencies

Added .NET 8.0 QuickStart project structure and Angular UI dependencies

Introduced a new QuickStart solution structure for .NET 8.0, including project files for Contracts, Entities, LoggerService, Repository, Service, and the main QuickStart web application, alongside a QuickStartUI folder containing an Angular 17.3 frontend with Material, ApexCharts, and SignalR dependencies.

(dependencies) · medium 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 30 → 31 (+0.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 60 → 60 (+0.0)
  • Architecture 92 → 92 (+0.0)
  • Maturity 40 → 46 (+6.2)
  • Readiness 16 → 16 (+0.0)
  • Security 35 → 36 (+1.0)
  • Accessibility 40 → 39 (-0.8)
  • Performance 100 → 100 (+0.0)

Resolved (27)

  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)
  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)
  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)
  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)
  • IAccountService has inconsistent parameter signatures compared to other services. It requires 'customerId' for all operations, while ICustomerService only requires 'customerId' for Get/Update/Delete but not Create. This inconsistency in required parameters for similar CRUD operations across services is confusing.
  • IAccountService methods include 'ForCustomer' in their names, implying a nested resource pattern, whereas ICustomerService methods do not include 'ForCustomer' (e.g., CreateCustomerAsync vs CreateAccountForCustomerAsync). This creates an inconsistent API surface for similar hierarchical relationships.
  • IAccountService uses 'trackChanges' as a boolean parameter for all methods, while ICustomerService also uses 'trackChanges' but IRoleService and IUserService do not. This inconsistency in tracking changes across services suggests a lack of unified data access strategy.
  • Inconsistent casing convention for entity properties. Most properties in the Customer entity (Country, Address, LastName) use PascalCase, but 'status' uses camelCase. This breaks the naming convention for the domain model.
  • Inconsistent naming conventions for retrieval operations. Some services use 'GetAll' for collections (ICustomerService, IUserService, IRoleService) while others use 'Get' (IAccountService). Additionally, singular retrieval uses 'Get' vs 'GetById'. There is also a typo in IAccountService.GetAccountsAync.
  • Inconsistent naming for creation and modification operations. 'Create' is used for IAccountService and ICustomerService, but 'Edit' is used for IRoleService. 'Update' is used for IUserService and ICustomerService. 'CreateAccountForCustomerAsync' implies a specific context not present in 'CreateCustomerAsync'.
  • Inconsistent spelling of the suffix 'Async' in method names. 'GetAccountsAync' uses a typo ('Aync') while other similar async methods ('GetAuditLogsAsync', 'GetAccountsAsync') correctly use 'Async'.
  • Low XML-doc coverage: Contracts (QuickStart/Contracts/Contracts.csproj)
  • Low XML-doc coverage: EmailService (QuickStart/EmailService/EmailService.csproj)
  • Low XML-doc coverage: Entities (QuickStart/Entities/Entities.csproj)
  • Low XML-doc coverage: LoggerService (QuickStart/LoggerService/LoggerService.csproj)
  • Low XML-doc coverage: QuickStart (QuickStart/QuickStart/QuickStart.csproj)
  • Low XML-doc coverage: QuickStart.Presentation (QuickStart/QuickStart.Presentation/QuickStart.Presentation.csproj)
  • Low XML-doc coverage: Repository (QuickStart/Repository/Repository.csproj)
  • Low XML-doc coverage: Service (QuickStart/Service/Service.csproj)
  • Low XML-doc coverage: Service.Contracts (QuickStart/Service.Contracts/Service.Contracts.csproj)
  • …and 7 more

New (3)

  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)
  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)
  • High CVE: [GHSA redacted] (QuickStartUI/package-lock.json)

API surface

  • Unchanged — 28 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

Njabulo240/QuickStart 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 67a729d06c7da5f87d98459df6ae7d4976ccd0af — 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.