# Changelog

> **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 36 → 36 (-0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 72 → 72 (+0.0)
- Architecture 76 → 76 (+0.0)
- Maturity 50 → 50 (+0.0)
- Readiness 25 → 24 (-0.5)
- Security 40 → 41 (+0.7)
- Domain Modelling 50 → 50 (+0.0)
- Accessibility 46 → 46 (+0.2)
- Performance 100 → 100 (+0.0)

## Resolved (12)

- High CVE: [GHSA redacted] (web/package-lock.json)
- High CVE: [GHSA redacted] (web/package-lock.json)
- High CVE: [GHSA redacted] (web/package-lock.json)
- High CVE: [GHSA redacted] (web/package-lock.json)
- Inconsistent namespace structure for user-chat relationship commands. Commands related to modifying the relationship between a user and a chat (adding, removing, updating permissions) are placed in `MessagingPlatform.Application.CQRS.UserChats.Commands.*`, whereas commands related to the Chat entity itself (create, delete, update) are in `MessagingPlatform.Application.CQRS.Chats.Commands.*`. While this distinguishes between 'Chat' and 'UserChat' entities, it creates a parallel structure where `UserChats` is treated as a separate aggregate root namespace rather than a sub-resource of `Chats` or `Users`. This is a minor structural inconsistency in how the CQRS namespaces are organized for related entities.
- Inconsistent naming for the user authentication/account management service. The command handler for adding a user injects a dependency named `_accountService` (referring to `IAccountService`/`AccountService`), while the sign-in command and the service itself use the term 'Account'. However, in the `UserService` and `IUserService` interfaces, the same logical domain concept (managing user identity, passwords, and profile) is referred to as 'User' (`UserService`, `IUserService`, `UserRepository`). This creates a split between 'Account' and 'User' terminology for what appears to be the same core identity management domain, potentially causing confusion about whether 'Account' and 'User' are distinct entities or synonyms.
- Medium CVE: [GHSA redacted] (web/package-lock.json)
- XML-doc coverage: MessagingPlatform.Api (backend/src/MessagingPlatform.Api/MessagingPlatform.Api.csproj)
- XML-doc coverage: MessagingPlatform.Application (backend/src/MessagingPlatform.Application/MessagingPlatform.Application.csproj)
- XML-doc coverage: MessagingPlatform.Domain (backend/src/MessagingPlatform.Domain/MessagingPlatform.Domain.csproj)
- XML-doc coverage: MessagingPlatform.Infrastructure (backend/src/MessagingPlatform.Infrastructure/MessagingPlatform.Infrastructure.csproj)
- redundant comment (backend/src/MessagingPlatform.Application/Common/Models/UserDTOs/UpdateUserDto.cs)

## New (8)

- High CVE: [GHSA redacted] (web/package-lock.json)
- High CVE: [GHSA redacted] (web/package-lock.json)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Outdated (npm): encoding
- `DeleteMessage` returns an awaitable but lacks the `Async` suffix its 21 peers carry (backend/src/MessagingPlatform.Domain/Interfaces/IMessageRepository.cs)
- `GetById` returns an awaitable but lacks the `Async` suffix its 21 peers carry (backend/src/MessagingPlatform.Domain/Interfaces/IMessageRepository.cs)

## API surface

- Unchanged — 24 HTTP endpoints

## Architecture

- Unchanged — 2 containers · 1 contexts · 0 edges
