rafaelfgx/Architecture

This system appears to be a codebase undergoing significant behavioral modifications across a large number of files, alongside routine dependency maintenance. The history indicates a major refactor or feature shift affecting the entire repository, rather than a specific, narrowly defined service. Without further context, it is difficult to determine the specific domain or purpose beyond these broad structural changes.

A change to existing behaviour in (repo-wide) — 1 commit, 126 files.

(repo-wide) · medium confidence · unverified

A dependency / build maintenance change in (dependencies) — 1 commit, 7 files.

(dependencies) · medium confidence · unverified

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

• CAI 33 → 36 (+3.2)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 77 → 79 (+1.8)
• Architecture 93 → 94 (+1.1)
• Maturity 54 → 56 (+2.3)
• Readiness 14 → 15 (+0.7)
• Security 49 → 45 (-3.3)
• Accessibility 40 → 58 (+18.2)

• Dependency hygiene not measured — no packages were read
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium IaC: CKV2_GHA_1 (.github/workflows/build.yaml)
• No exposed public API
• Scanner failed to run — not a clean result
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• single-commit history — no usable git history window to measure hotspots
• single-maintainer — knowledge-concentration (bus factor) risk

• High IaC: WD-COMPOSE-0002 (docker-compose.yaml)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Inconsistent casing for domain property names in parameters. The domain types (User, Auth) define properties with PascalCase names (Name, Email, Status, Login, Password, Salt, Roles). However, the parameter string Name in UserRepository.ListModelAsync uses PascalCase, which is consistent. However, looking at AuthRepository.GetByLoginAsync, the parameter is string (unnamed in signature but conceptually login). More critically, compare Parameter: string Name in UserRepository.ListModelAsync with Property: public Architecture.Domain.User.Name. While both are 'Name', the parameter casing matches the property. Let's look for a clearer mismatch. Ah, Parameter: string Name vs Property: public Architecture.Domain.User.Name. This is consistent. Let's look at Parameter: string Login vs Property: public Architecture.Domain.Auth.Login. Consistent. Let's look at Parameter: string Password vs Property: public Architecture.Domain.Auth.Password. Consistent. Let's look at Parameter: string Email vs Property: public Architecture.Domain.User.Email. Consistent. Let's look at Parameter: string role vs Property: public Architecture.Domain.Auth.Roles. Here is a mismatch: the property is Roles (plural, PascalCase), but the parameter in AuthConfiguration.Configure is role (singular, camelCase). Similarly, Parameter: string name in ExampleConfiguration.Configure vs Property: public Architecture.Domain.User.Name (if it were related) or Parameter: string Name in UserRepository. Actually, ExampleConfiguration configures Example, not User. Example doesn't have a Name property listed. User has Name. Auth has Roles. The parameter role in AuthConfiguration is singular, while the domain property is Roles (plural). This suggests a semantic drift or inconsistency in how the collection is referred to in configuration vs domain model.
• Inconsistent casing for the 'Id' parameter across different methods. UserController.Get and UserController.Delete use long id (camelCase), while GridUserRequest and GridExampleRequest types likely have an Id property (PascalCase) based on standard C# conventions for DTOs, but the parameters passed into handlers/controllers vary. Specifically, Parameter: long Id appears in GridUserRequest (likely a property or parameter in a request object context) and Parameter: long id appears in UserController.Get. While id is standard for local variables/parameters and Id for properties, the inconsistency arises if these parameters are meant to map directly to a property named Id. More clearly, Parameter: string Login in AuthConfiguration vs Property: public Architecture.Domain.Auth.Login. This is consistent. However, Parameter: string name in ExampleConfiguration vs Parameter: string Name in UserRepository. The casing differs (camelCase vs PascalCase) for the same concept 'Name'.
• Medium IaC: CKV_DOCKER_2 (dockerfile)
• Medium IaC: WD-DOCKER-0003 (dockerfile)
• Medium IaC: WD-DOCKER-0003 (dockerfile)
• Medium IaC: WD-DOCKER-0003 (dockerfile)
• Medium IaC: WD-DOCKER-0004 (dockerfile)
• No dependency advisory monitoring
• Scanner failed to run — not a clean result
• Scanner failed to run — not a clean result
• Shell project: Architecture.Model (source/Model/Architecture.Model.csproj)
• Workflow token permissions not restricted

• 1 commits — 1 feature/other, 0 fixes

• source/Web — 1 commit

• change: .

• 1 added · 1 removed (a removed endpoint is potentially breaking)

• POST /api/auth

• POST /api/auths

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

rafaelfgx/Architecture 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.