# Changelog

## Score

- CAI 45 → 48 (+2.5)
- Rubric changed (rubric-2026.08.18 → rubric-2026.08.19) — scores are not directly comparable.

## Lenses

- Code Health 81 → 81 (+0.0)
- Architecture 83 → 83 (+0.0)
- Maturity 51 → 51 (+0.0)
- Readiness 33 → 38 (+5.2)
- Security 48 → 48 (+0.0)

## Resolved (6)

- Inconsistent naming for cryptographic helpers: 'RSACryption' uses 'Cryption' (misspelling of Cryptography) while others use 'Helper' or 'Utils'.
- Inconsistent naming for utility classes: 'TypeParse' vs 'Utils'. While not strictly the same concept, the namespace 'Utitlies' (misspelled) contains both, suggesting a general utility namespace where 'TypeParse' is an outlier in naming convention compared to 'Utils'.
- Inconsistent spelling of 'Extensions' as 'Extenstions' in the class name 'EntityBaseExtenstions'.
- Inconsistent spelling of 'Receive' as 'Recevice' in the class name 'UdpSyncListenReceviceService'.
- Leaked secret: high-entropy-secret (Lfz.Core/Utitlies/Utils.cs)
- Typo in namespace name: 'Utitlies' is likely a misspelling of 'Utilities'. This typo is present in both the namespace and the classes within it.

## New (5)

- Inconsistency in naming cryptographic helpers. Some use 'Helper' (TripleDESHelper), some use 'Utils' (CRCUtils), and some use specific class names (RSACryption). While not a direct contradiction, the lack of a consistent suffix (e.g., all ending in 'Helper' or 'Utils') is a minor inconsistency. However, the most glaring issue is the typo 'Utitlies' in the namespace.
- Inconsistency in the naming of base entity classes. 'EntityBase' is used in 'Lfz.Data.EntityBase' and 'Lfz.Data.Nh.Entities.EntityBase<T>', but 'CloneEntityBase' and 'EntityBaseExtenstions' (typo: Extenstions) suggest a different naming pattern or a typo. Specifically, 'EntityBaseExtenstions' has a typo 'Extenstions' instead of 'Extensions'.
- Inconsistency in the naming of network service classes. Some use 'Listen' (e.g., TcpListenServiceBase, UdpListenServiceBase), while others use 'Client' (TcpClientService, TcpClientAsyncService) or 'Sync/Async' distinctions. More importantly, 'UdpSyncListenReceviceService' contains a typo 'Recevice' instead of 'Receive'.
- The namespace 'Lfz.Utitlies' contains multiple classes and methods. The spelling 'Utitlies' appears to be a typo for 'Utilities'. This typo is consistently applied across the namespace and its members, but the namespace name itself is misspelled compared to standard English and potentially other namespaces in the codebase (e.g., if there were a 'Lfz.Utilities' namespace, it would be an inconsistency, but here the typo is pervasive). However, looking at the list, we see 'Lfz.Utitlies' used repeatedly. Is there a 'Lfz.Utilities'? No. But wait, we see 'Lfz.Utitlies.Utils' and 'Lfz.Utitlies.TypeParse'. The typo 'Utitlies' is consistent within that namespace. However, we also see 'Lfz.Utitlies.Utils.GetDisplayName' and 'Lfz.Utitlies.Utils.MapPath'. The typo is consistent. Let's look for other typos or inconsistencies.
- The namespace 'Lfz.Utitlies' is misspelled (should be 'Utilities'). This affects all members within it.

## Architecture

- Unchanged — 1 containers · 1 contexts · 0 edges