hiiammalte/foodtruacker
44.0
Weak · 8 November 2026
3.1k
lines of production code
C#
primary language
7
measurements over time
What this system is
This is a .NET 9-based event-sourcing application that manages user accounts and tour pricing through a domain-driven architecture. It provides role-based access control for administrators and customers, handling account creation, verification, and credential updates via MediatR commands. The system persists state using MySQL, MongoDB, and EventStoreDB, with acceptance tests ensuring domain event integrity.
Features
Added user account management commands and projections
The application now supports creating, verifying, and updating admin and customer accounts, including changing email addresses and passwords. This includes new MediatR commands for account creation, email/password updates, and verification, alongside event handlers and projections that synchronize account changes to read models and trigger email verification workflows.
foodtruacker.Application · high confidence
Initial project scaffolding and configuration
The repository was initialized with a complete project structure, including a solution file defining multiple .NET class libraries (API, Application, Domain, etc.), a Docker Compose configuration for local development with MySQL, MongoDB, and EventStoreDB, and a .gitignore/.dockerignore setup. This establishes the foundational build and runtime environment for the application.
(repo-wide) · high confidence
Introduce role-based authorization and user account management endpoints
The API now enforces role-based access control using JWT Bearer tokens. The AdministrationController is restricted to the 'Admin' role, while the CustomersController requires 'Admin' or 'Customer' roles. The AuthenticationController handles public login and email verification, routing verified users to either admin or customer flows. New DTOs (CreateAdminAccountDTO, CreateCustomerAccountDTO, etc.) support account creation and updates. The Startup class registers JWT authentication, MySQL Identity storage, and MediatR for command/query handling, enabling the new account management features.
foodtruacker.Framework · high confidence
Introduced domain models and event-sourcing infrastructure for user account and tour pricing management
Added new domain aggregates for managing user accounts and tour pricing, including \Admin\ and \Customer\ aggregates in the \UserAccountManagement\ bounded context, and a \TourStopPricingModel\ aggregate in the \TourPricingManagement\ context. These aggregates support creating accounts, verifying them, and changing email addresses or passwords, all driven by domain events. The change also introduces the underlying event-sourcing infrastructure in \SharedKernel\, including the \AggregateRoot\ base class, \DomainEvent\ and \IDomainEvent\ interfaces, and value object abstractions (\ValueObject\, \IValueObject\) to support the new domain logic.
foodtruacker.Domain, foodtruacker.SharedKernel · high confidence
Test coverage
Added acceptance tests for user account management
Added acceptance tests for user account management, including registration, verification, and password/email changes for both customers and admins. The tests verify that the correct domain events are published for each scenario.
foodtruacker.AcceptanceTests · high confidence
Dependencies
Upgrade to .NET 9 and update NuGet packages
The project has been upgraded to the .NET 9 runtime, with all .csproj files now targeting net9.0. Additionally, key dependencies have been updated to their latest versions, including the EventStore client libraries (v23.3.7), Grpc.Net.Client (v2.67.0), and various Microsoft.Extensions packages (v9.0.0).
(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
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 43 → 44 (+0.7)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 55 → 55 (+0.1)
- Architecture 89 → 63 (-26.1)
- Maturity 63 → 66 (+3.4)
- Readiness 25 → 25 (+0.0)
- Security 57 → 58 (+0.9)
- Domain Modelling 81 → 81 (+0.0)
- Event-Driven 100 → 100 (+0.0)
- Event Sourcing 55 → 72 (+17.0)
- Performance 100 → 100 (+0.0)
Resolved (14)
- End-of-life runtime: .NET net9.0 (foodtruacker.SharedKernel/foodtruacker.SharedKernel.csproj)
- Inconsistent naming for user name components: 'Firstname' and 'Lastname' are used in some DTOs and test fields, while 'Last' is used in the ValueObject. Additionally, 'PlainPassword' is used in tests while 'Password' is used in DTOs, and 'CurrentPassword'/'NewPassword' are used in other contexts. While 'Firstname'/'Lastname' vs 'First'/'Last' is a common variation, the mix of 'Firstname' (DTO/Test) and 'Last' (ValueObject) for the same semantic concept (surname) is inconsistent. Furthermore, 'PlainPassword' in tests vs 'Password' in DTOs creates confusion about whether the field contains the raw input or a hash, especially since the ValueObject is 'HashedPassword'.
- XML-doc coverage: foodtruacker.API (foodtruacker.Framework/API/foodtruacker.API.csproj)
- XML-doc coverage: foodtruacker.Application (foodtruacker.Application/foodtruacker.Application.csproj)
- XML-doc coverage: foodtruacker.Authentication (foodtruacker.Framework/Authentication/foodtruacker.Authentication.csproj)
- XML-doc coverage: foodtruacker.Domain (foodtruacker.Domain/foodtruacker.Domain.csproj)
- XML-doc coverage: foodtruacker.EmailService (foodtruacker.Framework/EmailService/foodtruacker.EmailService.csproj)
- XML-doc coverage: foodtruacker.EventSourcingRepository (foodtruacker.Framework/EventsourcingRepository/foodtruacker.EventSourcingRepository.csproj)
- XML-doc coverage: foodtruacker.QueryRepository (foodtruacker.Framework/QueryRepository/foodtruacker.QueryRepository.csproj)
- XML-doc coverage: foodtruacker.SharedKernel (foodtruacker.SharedKernel/foodtruacker.SharedKernel.csproj)
- redundant comment (foodtruacker.Framework/API/Extensions/IdentityMySqlServiceExtensions.cs)
- redundant comment (foodtruacker.Framework/API/Extensions/IdentityMySqlServiceExtensions.cs)
- redundant comment (foodtruacker.Framework/API/Extensions/IdentityMySqlServiceExtensions.cs)
- redundant comment (foodtruacker.Framework/API/Startup.cs)
New (2)
- Medium CVE: MySqlConnector 2.3.5 (foodtruacker.AcceptanceTests/foodtruacker.AcceptanceTests.csproj)
- Medium: security finding (details withheld)
API surface
- Unchanged — 3 HTTP endpoints
Architecture
- Unchanged — 2 containers · 3 contexts · 2 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
hiiammalte/foodtruacker 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 380819a38775f36e70c4483ae28988832d51bbbd — 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.