Executive summary
carlossalasamper/react-native-clean-architecture is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because the project has no automated tests. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 13, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 20 points. Adding automated tests would lift Production Readiness itself, also worth about 20. Raising Production Readiness to 70 would lift the score to about 62.
Thirty-five known security holes in the packages the code depends on can be used by attackers. One password or key in the code and one in the code's history are open to anyone who can read the repository, and the project has no automated tests, so a change can break it without warning. Replacing each exposed password or key, adding automated tests and updating the vulnerable packages would close these risks. The piece of business logic tied to the database or web code needs separating from the database and web code.
The product code is 875 lines, too few for a meaningful rebuild estimate.
If Production Readiness rose from 13 to 70, the lowest score rated Strong, the score would rise from 40 to about 62.
New since the last survey: 6 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 7 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com.carlossalasamper.reactnativecleanarchitecture | 2 src.AppModule | 3 src.core.CoreModule | 4 src.core.application.UseCase | 5 src.core.domain.entities.Env | 6 src.core.domain.enums.Locale | 7 src.core.domain.specifications.IHttpClient | 8 src.core.infrastructure.models.PayloadDto | 9 src.core.infrastructure.models.ResponseDto | 10 src.core.presentation | 11 src.core.presentation.hooks | 12 src.core.presentation.i18n | 13 src.core.presentation.navigation | 14 src.core.presentation.navigation.types | 15 src.core.presentation.screens | 16 src.core.presentation.types.PaginationState | 17 src.core.presentation.utils | 18 src.post.PostModule | 19 src.post.application.types.GetPostsPayload | 20 src.post.application.types.GetPostsResponse | 21 src.post.domain.entities.PostEntity | 22 src.post.domain.specifications.IPostRepository | 23 src.post.presentation.screens | 24 src.post.presentation.types.FindPostStoreState | 25 src.post.presentation.types.GetPostsStoreState | 26 src.core.infrastructure.implementations.HttpClient | 27 src.core.presentation.types.ListState | 28 src.post.application.useCases.FindPostUseCase | 29 src.post.application.useCases.GetPostsUseCase | 30 src.post.infrastructure.implementations.PostRepository | 31 src.post.infrastructure.models.GetPostsQuery | 32 src.post.infrastructure.models.PostDto | 33 src.post.presentation.components.PostItem | 34 src.post.presentation.components | 35 src.post.presentation.stores.FindPostStore.FindPostStore | 36 src.post.presentation.stores.GetPostsStore.GetPostsStore | 37 src.post.presentation.stores.FindPostStore | 38 src.post.presentation.stores.GetPostsStore |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.carlossalasamper.reactnativecleanarchitecture | ||||||||||||||||||||||||||||||||||||||
| 2 src.AppModule | ||||||||||||||||||||||||||||||||||||||
| 3 src.core.CoreModule | ||||||||||||||||||||||||||||||||||||||
| 4 src.core.application.UseCase | ||||||||||||||||||||||||||||||||||||||
| 5 src.core.domain.entities.Env | ||||||||||||||||||||||||||||||||||||||
| 6 src.core.domain.enums.Locale | ||||||||||||||||||||||||||||||||||||||
| 7 src.core.domain.specifications.IHttpClient | ||||||||||||||||||||||||||||||||||||||
| 8 src.core.infrastructure.models.PayloadDto | ||||||||||||||||||||||||||||||||||||||
| 9 src.core.infrastructure.models.ResponseDto | ||||||||||||||||||||||||||||||||||||||
| 10 src.core.presentation | ||||||||||||||||||||||||||||||||||||||
| 11 src.core.presentation.hooks | ||||||||||||||||||||||||||||||||||||||
| 12 src.core.presentation.i18n | ||||||||||||||||||||||||||||||||||||||
| 13 src.core.presentation.navigation | ||||||||||||||||||||||||||||||||||||||
| 14 src.core.presentation.navigation.types | ||||||||||||||||||||||||||||||||||||||
| 15 src.core.presentation.screens | ||||||||||||||||||||||||||||||||||||||
| 16 src.core.presentation.types.PaginationState | ||||||||||||||||||||||||||||||||||||||
| 17 src.core.presentation.utils | ||||||||||||||||||||||||||||||||||||||
| 18 src.post.PostModule | ||||||||||||||||||||||||||||||||||||||
| 19 src.post.application.types.GetPostsPayload | ||||||||||||||||||||||||||||||||||||||
| 20 src.post.application.types.GetPostsResponse | ||||||||||||||||||||||||||||||||||||||
| 21 src.post.domain.entities.PostEntity | ||||||||||||||||||||||||||||||||||||||
| 22 src.post.domain.specifications.IPostRepository | ||||||||||||||||||||||||||||||||||||||
| 23 src.post.presentation.screens | ||||||||||||||||||||||||||||||||||||||
| 24 src.post.presentation.types.FindPostStoreState | ||||||||||||||||||||||||||||||||||||||
| 25 src.post.presentation.types.GetPostsStoreState | ||||||||||||||||||||||||||||||||||||||
| 26 src.core.infrastructure.implementations.HttpClient | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 src.core.presentation.types.ListState | 1 | |||||||||||||||||||||||||||||||||||||
| 28 src.post.application.useCases.FindPostUseCase | 1 | |||||||||||||||||||||||||||||||||||||
| 29 src.post.application.useCases.GetPostsUseCase | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 src.post.infrastructure.implementations.PostRepository | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 src.post.infrastructure.models.GetPostsQuery | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 src.post.infrastructure.models.PostDto | 1 | |||||||||||||||||||||||||||||||||||||
| 33 src.post.presentation.components.PostItem | 1 | |||||||||||||||||||||||||||||||||||||
| 34 src.post.presentation.components | 1 | |||||||||||||||||||||||||||||||||||||
| 35 src.post.presentation.stores.FindPostStore.FindPostStore | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 src.post.presentation.stores.GetPostsStore.GetPostsStore | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 src.post.presentation.stores.FindPostStore | 1 | |||||||||||||||||||||||||||||||||||||
| 38 src.post.presentation.stores.GetPostsStore | 1 |
26→5 src.core.infrastructure.implementations.HttpClient uses src.core.domain.entities.Env✕
- Connections
- 1 pair of types, where a type in src.core.infrastructure.implementations.HttpClient uses a type in src.core.domain.entities.Env.
- The types involved
src.core.infrastructure.implementations.HttpClient.HttpClient→src.core.domain.entities.Env.Env
- Direction
- src.core.infrastructure.implementations.HttpClient uses src.core.domain.entities.Env, so a change to src.core.domain.entities.Env can break src.core.infrastructure.implementations.HttpClient, while a change to src.core.infrastructure.implementations.HttpClient can't break src.core.domain.entities.Env.
- Position
- Below the diagonal: src.core.infrastructure.implementations.HttpClient uses a module listed above it, which is the healthy direction.
26→7 src.core.infrastructure.implementations.HttpClient uses src.core.domain.specifications.IHttpClient✕
- Connections
- 1 pair of types, where a type in src.core.infrastructure.implementations.HttpClient uses a type in src.core.domain.specifications.IHttpClient.
- The types involved
src.core.infrastructure.implementations.HttpClient.HttpClient→src.core.domain.specifications.IHttpClient.IHttpClient
- Direction
- src.core.infrastructure.implementations.HttpClient uses src.core.domain.specifications.IHttpClient, so a change to src.core.domain.specifications.IHttpClient can break src.core.infrastructure.implementations.HttpClient, while a change to src.core.infrastructure.implementations.HttpClient can't break src.core.domain.specifications.IHttpClient.
- Position
- Below the diagonal: src.core.infrastructure.implementations.HttpClient uses a module listed above it, which is the healthy direction.
27→16 src.core.presentation.types.ListState uses src.core.presentation.types.PaginationState✕
- Connections
- 1 pair of types, where a type in src.core.presentation.types.ListState uses a type in src.core.presentation.types.PaginationState.
- The types involved
src.core.presentation.types.ListState.ListState→src.core.presentation.types.PaginationState.PaginationState
- Direction
- src.core.presentation.types.ListState uses src.core.presentation.types.PaginationState, so a change to src.core.presentation.types.PaginationState can break src.core.presentation.types.ListState, while a change to src.core.presentation.types.ListState can't break src.core.presentation.types.PaginationState.
- Position
- Below the diagonal: src.core.presentation.types.ListState uses a module listed above it, which is the healthy direction.
28→22 src.post.application.useCases.FindPostUseCase uses src.post.domain.specifications.IPostRepository✕
- Connections
- 1 pair of types, where a type in src.post.application.useCases.FindPostUseCase uses a type in src.post.domain.specifications.IPostRepository.
- The types involved
src.post.application.useCases.FindPostUseCase.FindPostUseCase→src.post.domain.specifications.IPostRepository.IPostRepository
- Direction
- src.post.application.useCases.FindPostUseCase uses src.post.domain.specifications.IPostRepository, so a change to src.post.domain.specifications.IPostRepository can break src.post.application.useCases.FindPostUseCase, while a change to src.post.application.useCases.FindPostUseCase can't break src.post.domain.specifications.IPostRepository.
- Position
- Below the diagonal: src.post.application.useCases.FindPostUseCase uses a module listed above it, which is the healthy direction.
29→4 src.post.application.useCases.GetPostsUseCase uses src.core.application.UseCase✕
- Connections
- 1 pair of types, where a type in src.post.application.useCases.GetPostsUseCase uses a type in src.core.application.UseCase.
- The types involved
src.post.application.useCases.GetPostsUseCase.GetPostsUseCase→src.core.application.UseCase.UseCase
- Direction
- src.post.application.useCases.GetPostsUseCase uses src.core.application.UseCase, so a change to src.core.application.UseCase can break src.post.application.useCases.GetPostsUseCase, while a change to src.post.application.useCases.GetPostsUseCase can't break src.core.application.UseCase.
- Position
- Below the diagonal: src.post.application.useCases.GetPostsUseCase uses a module listed above it, which is the healthy direction.
29→19 src.post.application.useCases.GetPostsUseCase uses src.post.application.types.GetPostsPayload✕
- Connections
- 1 pair of types, where a type in src.post.application.useCases.GetPostsUseCase uses a type in src.post.application.types.GetPostsPayload.
- The types involved
src.post.application.useCases.GetPostsUseCase.GetPostsUseCase→src.post.application.types.GetPostsPayload.GetPostsPayload
- Direction
- src.post.application.useCases.GetPostsUseCase uses src.post.application.types.GetPostsPayload, so a change to src.post.application.types.GetPostsPayload can break src.post.application.useCases.GetPostsUseCase, while a change to src.post.application.useCases.GetPostsUseCase can't break src.post.application.types.GetPostsPayload.
- Position
- Below the diagonal: src.post.application.useCases.GetPostsUseCase uses a module listed above it, which is the healthy direction.
29→22 src.post.application.useCases.GetPostsUseCase uses src.post.domain.specifications.IPostRepository✕
- Connections
- 1 pair of types, where a type in src.post.application.useCases.GetPostsUseCase uses a type in src.post.domain.specifications.IPostRepository.
- The types involved
src.post.application.useCases.GetPostsUseCase.GetPostsUseCase→src.post.domain.specifications.IPostRepository.IPostRepository
- Direction
- src.post.application.useCases.GetPostsUseCase uses src.post.domain.specifications.IPostRepository, so a change to src.post.domain.specifications.IPostRepository can break src.post.application.useCases.GetPostsUseCase, while a change to src.post.application.useCases.GetPostsUseCase can't break src.post.domain.specifications.IPostRepository.
- Position
- Below the diagonal: src.post.application.useCases.GetPostsUseCase uses a module listed above it, which is the healthy direction.
30→7 src.post.infrastructure.implementations.PostRepository uses src.core.domain.specifications.IHttpClient✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.implementations.PostRepository uses a type in src.core.domain.specifications.IHttpClient.
- The types involved
src.post.infrastructure.implementations.PostRepository.PostRepository→src.core.domain.specifications.IHttpClient.IHttpClient
- Direction
- src.post.infrastructure.implementations.PostRepository uses src.core.domain.specifications.IHttpClient, so a change to src.core.domain.specifications.IHttpClient can break src.post.infrastructure.implementations.PostRepository, while a change to src.post.infrastructure.implementations.PostRepository can't break src.core.domain.specifications.IHttpClient.
- Position
- Below the diagonal: src.post.infrastructure.implementations.PostRepository uses a module listed above it, which is the healthy direction.
30→19 src.post.infrastructure.implementations.PostRepository uses src.post.application.types.GetPostsPayload✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.implementations.PostRepository uses a type in src.post.application.types.GetPostsPayload.
- The types involved
src.post.infrastructure.implementations.PostRepository.PostRepository→src.post.application.types.GetPostsPayload.GetPostsPayload
- Direction
- src.post.infrastructure.implementations.PostRepository uses src.post.application.types.GetPostsPayload, so a change to src.post.application.types.GetPostsPayload can break src.post.infrastructure.implementations.PostRepository, while a change to src.post.infrastructure.implementations.PostRepository can't break src.post.application.types.GetPostsPayload.
- Position
- Below the diagonal: src.post.infrastructure.implementations.PostRepository uses a module listed above it, which is the healthy direction.
30→20 src.post.infrastructure.implementations.PostRepository uses src.post.application.types.GetPostsResponse✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.implementations.PostRepository uses a type in src.post.application.types.GetPostsResponse.
- The types involved
src.post.infrastructure.implementations.PostRepository.PostRepository→src.post.application.types.GetPostsResponse.GetPostsResponse
- Direction
- src.post.infrastructure.implementations.PostRepository uses src.post.application.types.GetPostsResponse, so a change to src.post.application.types.GetPostsResponse can break src.post.infrastructure.implementations.PostRepository, while a change to src.post.infrastructure.implementations.PostRepository can't break src.post.application.types.GetPostsResponse.
- Position
- Below the diagonal: src.post.infrastructure.implementations.PostRepository uses a module listed above it, which is the healthy direction.
30→22 src.post.infrastructure.implementations.PostRepository uses src.post.domain.specifications.IPostRepository✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.implementations.PostRepository uses a type in src.post.domain.specifications.IPostRepository.
- The types involved
src.post.infrastructure.implementations.PostRepository.PostRepository→src.post.domain.specifications.IPostRepository.IPostRepository
- Direction
- src.post.infrastructure.implementations.PostRepository uses src.post.domain.specifications.IPostRepository, so a change to src.post.domain.specifications.IPostRepository can break src.post.infrastructure.implementations.PostRepository, while a change to src.post.infrastructure.implementations.PostRepository can't break src.post.domain.specifications.IPostRepository.
- Position
- Below the diagonal: src.post.infrastructure.implementations.PostRepository uses a module listed above it, which is the healthy direction.
31→8 src.post.infrastructure.models.GetPostsQuery uses src.core.infrastructure.models.PayloadDto✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.models.GetPostsQuery uses a type in src.core.infrastructure.models.PayloadDto.
- The types involved
src.post.infrastructure.models.GetPostsQuery.GetPostsQuery→src.core.infrastructure.models.PayloadDto.PayloadDto
- Direction
- src.post.infrastructure.models.GetPostsQuery uses src.core.infrastructure.models.PayloadDto, so a change to src.core.infrastructure.models.PayloadDto can break src.post.infrastructure.models.GetPostsQuery, while a change to src.post.infrastructure.models.GetPostsQuery can't break src.core.infrastructure.models.PayloadDto.
- Position
- Below the diagonal: src.post.infrastructure.models.GetPostsQuery uses a module listed above it, which is the healthy direction.
31→19 src.post.infrastructure.models.GetPostsQuery uses src.post.application.types.GetPostsPayload✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.models.GetPostsQuery uses a type in src.post.application.types.GetPostsPayload.
- The types involved
src.post.infrastructure.models.GetPostsQuery.GetPostsQuery→src.post.application.types.GetPostsPayload.GetPostsPayload
- Direction
- src.post.infrastructure.models.GetPostsQuery uses src.post.application.types.GetPostsPayload, so a change to src.post.application.types.GetPostsPayload can break src.post.infrastructure.models.GetPostsQuery, while a change to src.post.infrastructure.models.GetPostsQuery can't break src.post.application.types.GetPostsPayload.
- Position
- Below the diagonal: src.post.infrastructure.models.GetPostsQuery uses a module listed above it, which is the healthy direction.
32→9 src.post.infrastructure.models.PostDto uses src.core.infrastructure.models.ResponseDto✕
- Connections
- 1 pair of types, where a type in src.post.infrastructure.models.PostDto uses a type in src.core.infrastructure.models.ResponseDto.
- The types involved
src.post.infrastructure.models.PostDto.PostDto→src.core.infrastructure.models.ResponseDto.ResponseDto
- Direction
- src.post.infrastructure.models.PostDto uses src.core.infrastructure.models.ResponseDto, so a change to src.core.infrastructure.models.ResponseDto can break src.post.infrastructure.models.PostDto, while a change to src.post.infrastructure.models.PostDto can't break src.core.infrastructure.models.ResponseDto.
- Position
- Below the diagonal: src.post.infrastructure.models.PostDto uses a module listed above it, which is the healthy direction.
33→21 src.post.presentation.components.PostItem uses src.post.domain.entities.PostEntity✕
- Connections
- 1 pair of types, where a type in src.post.presentation.components.PostItem uses a type in src.post.domain.entities.PostEntity.
- The types involved
src.post.presentation.components.PostItem.PostItemProps→src.post.domain.entities.PostEntity.PostEntity
- Direction
- src.post.presentation.components.PostItem uses src.post.domain.entities.PostEntity, so a change to src.post.domain.entities.PostEntity can break src.post.presentation.components.PostItem, while a change to src.post.presentation.components.PostItem can't break src.post.domain.entities.PostEntity.
- Position
- Below the diagonal: src.post.presentation.components.PostItem uses a module listed above it, which is the healthy direction.
34→33 src.post.presentation.components uses src.post.presentation.components.PostItem✕
- Connections
- 1 pair of types, where a type in src.post.presentation.components uses a type in src.post.presentation.components.PostItem.
- The types involved
src.post.presentation.components.PostItem→src.post.presentation.components.PostItem.PostItemProps
- Direction
- src.post.presentation.components uses src.post.presentation.components.PostItem, so a change to src.post.presentation.components.PostItem can break src.post.presentation.components, while a change to src.post.presentation.components can't break src.post.presentation.components.PostItem.
- Position
- Below the diagonal: src.post.presentation.components uses a module listed above it, which is the healthy direction.
35→24 src.post.presentation.stores.FindPostStore.FindPostStore uses src.post.presentation.types.FindPostStoreState✕
- Connections
- 1 pair of types, where a type in src.post.presentation.stores.FindPostStore.FindPostStore uses a type in src.post.presentation.types.FindPostStoreState.
- The types involved
src.post.presentation.stores.FindPostStore.FindPostStore.FindPostStore→src.post.presentation.types.FindPostStoreState.FindPostStoreState
- Direction
- src.post.presentation.stores.FindPostStore.FindPostStore uses src.post.presentation.types.FindPostStoreState, so a change to src.post.presentation.types.FindPostStoreState can break src.post.presentation.stores.FindPostStore.FindPostStore, while a change to src.post.presentation.stores.FindPostStore.FindPostStore can't break src.post.presentation.types.FindPostStoreState.
- Position
- Below the diagonal: src.post.presentation.stores.FindPostStore.FindPostStore uses a module listed above it, which is the healthy direction.
35→28 src.post.presentation.stores.FindPostStore.FindPostStore uses src.post.application.useCases.FindPostUseCase✕
- Connections
- 1 pair of types, where a type in src.post.presentation.stores.FindPostStore.FindPostStore uses a type in src.post.application.useCases.FindPostUseCase.
- The types involved
src.post.presentation.stores.FindPostStore.FindPostStore.FindPostStore→src.post.application.useCases.FindPostUseCase.FindPostUseCase
- Direction
- src.post.presentation.stores.FindPostStore.FindPostStore uses src.post.application.useCases.FindPostUseCase, so a change to src.post.application.useCases.FindPostUseCase can break src.post.presentation.stores.FindPostStore.FindPostStore, while a change to src.post.presentation.stores.FindPostStore.FindPostStore can't break src.post.application.useCases.FindPostUseCase.
- Position
- Below the diagonal: src.post.presentation.stores.FindPostStore.FindPostStore uses a module listed above it, which is the healthy direction.
36→25 src.post.presentation.stores.GetPostsStore.GetPostsStore uses src.post.presentation.types.GetPostsStoreState✕
- Connections
- 1 pair of types, where a type in src.post.presentation.stores.GetPostsStore.GetPostsStore uses a type in src.post.presentation.types.GetPostsStoreState.
- The types involved
src.post.presentation.stores.GetPostsStore.GetPostsStore.GetPostsStore→src.post.presentation.types.GetPostsStoreState.GetPostsStoreState
- Direction
- src.post.presentation.stores.GetPostsStore.GetPostsStore uses src.post.presentation.types.GetPostsStoreState, so a change to src.post.presentation.types.GetPostsStoreState can break src.post.presentation.stores.GetPostsStore.GetPostsStore, while a change to src.post.presentation.stores.GetPostsStore.GetPostsStore can't break src.post.presentation.types.GetPostsStoreState.
- Position
- Below the diagonal: src.post.presentation.stores.GetPostsStore.GetPostsStore uses a module listed above it, which is the healthy direction.
36→29 src.post.presentation.stores.GetPostsStore.GetPostsStore uses src.post.application.useCases.GetPostsUseCase✕
- Connections
- 1 pair of types, where a type in src.post.presentation.stores.GetPostsStore.GetPostsStore uses a type in src.post.application.useCases.GetPostsUseCase.
- The types involved
src.post.presentation.stores.GetPostsStore.GetPostsStore.GetPostsStore→src.post.application.useCases.GetPostsUseCase.GetPostsUseCase
- Direction
- src.post.presentation.stores.GetPostsStore.GetPostsStore uses src.post.application.useCases.GetPostsUseCase, so a change to src.post.application.useCases.GetPostsUseCase can break src.post.presentation.stores.GetPostsStore.GetPostsStore, while a change to src.post.presentation.stores.GetPostsStore.GetPostsStore can't break src.post.application.useCases.GetPostsUseCase.
- Position
- Below the diagonal: src.post.presentation.stores.GetPostsStore.GetPostsStore uses a module listed above it, which is the healthy direction.
37→35 src.post.presentation.stores.FindPostStore uses src.post.presentation.stores.FindPostStore.FindPostStore✕
- Connections
- 1 pair of types, where a type in src.post.presentation.stores.FindPostStore uses a type in src.post.presentation.stores.FindPostStore.FindPostStore.
- The types involved
src.post.presentation.stores.FindPostStore.useFindPostStore→src.post.presentation.stores.FindPostStore.FindPostStore.FindPostStore
- Direction
- src.post.presentation.stores.FindPostStore uses src.post.presentation.stores.FindPostStore.FindPostStore, so a change to src.post.presentation.stores.FindPostStore.FindPostStore can break src.post.presentation.stores.FindPostStore, while a change to src.post.presentation.stores.FindPostStore can't break src.post.presentation.stores.FindPostStore.FindPostStore.
- Position
- Below the diagonal: src.post.presentation.stores.FindPostStore uses a module listed above it, which is the healthy direction.
38→36 src.post.presentation.stores.GetPostsStore uses src.post.presentation.stores.GetPostsStore.GetPostsStore✕
- Connections
- 1 pair of types, where a type in src.post.presentation.stores.GetPostsStore uses a type in src.post.presentation.stores.GetPostsStore.GetPostsStore.
- The types involved
src.post.presentation.stores.GetPostsStore.useGetPostsStore→src.post.presentation.stores.GetPostsStore.GetPostsStore.GetPostsStore
- Direction
- src.post.presentation.stores.GetPostsStore uses src.post.presentation.stores.GetPostsStore.GetPostsStore, so a change to src.post.presentation.stores.GetPostsStore.GetPostsStore can break src.post.presentation.stores.GetPostsStore, while a change to src.post.presentation.stores.GetPostsStore can't break src.post.presentation.stores.GetPostsStore.GetPostsStore.
- Position
- Below the diagonal: src.post.presentation.stores.GetPostsStore uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 48 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +20.2 pts | Low | Secret Scanning |
| Resolve the 1 No tests found finding(s) in Test Distribution. | +20.2 pts | Low | Test Distribution |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +20.2 pts | High | Code Coverage |
| Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository). | +6.3 pts | Medium | Domain ↔ infrastructure boundary |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +3.7 pts | Medium | CI/CD gates |
| Add tests that import the unreached modules (directly or through their public entry). | +3.7 pts | Medium | Test Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.3 pts | Low | ADR Quality |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +1.8 pts | Medium | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| src/core/infrastructure/implementations/HttpClient.ts | 7.3 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 67 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 67 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 61 of 73 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 3 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 10 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 10 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits to judge knowledge freshness (10 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 10 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server exited, and its output does not match a cause we recognise. (rule: unrecognised-exit). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "at getDefaultConfig (<repo>/node_modules/@expo/metro-config/src/ExpoMetroConfig.ts:371:21) / at Object.<anonymous> (<repo>/metro.config.js:4:18) / at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) / at Function._load (node:internal/modules/cjs/loader:1123:12) / at TracingChannel.traceSync (node:diagnostics_channel:322:14) / at wrapModuleLoad (node:internal/modules/cjs/loader:217:24) / at Module.require (node:internal/modules/cjs/loader:1335:12)" No runtime evidence was gathered.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
3 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 2 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 875 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with HttpClient.ts (2). — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (2 contexts). Contexts: core, post.
D26 · Project Cohesion
0 of 2 build units (Gradle, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
48 finding(s): 4 critical, 31 high, 9 medium, 4 low.
What to do
- Resolve the 31 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (31). — One of this dimension's main actionable groups (31 issue-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 23 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM6 · Domain ↔ infrastructure boundary
- `src/core/domain/specifications/IHttpClient.ts` (domain layer) depends on `axios` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — src/core/domain/specifications/IHttpClient.ts:1
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
What to do
- Keep implementation types off the public surface (Kotlin: `internal`) — even for a small library, every public type is a stability contract.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:18
What to do
- Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- src/post/presentation/components/PostItem.tsx:18 · src/post/presentation/screens/PostScreen.tsx:24 — the two spans are one implementation copied and then locally edited — 103 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/post/presentation/components/PostItem.tsx:18
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- 0% of 37 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 1 application, 6 tooling and 0 test entry point(s) detected in this repo. Gate removals on `yarn run check-ts` — an undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 6 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/post/infrastructure/models/GetPostsQuery.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/infrastructure/models/PayloadDto.ts
- no import path from any entry point (1 application, 6 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — src/post/infrastructure/models/GetPostsQuery.ts, src/core/domain/enums/Locale.ts
- Nothing imports this binding — it is safe to review for removal. — src/core/presentation/navigation/types/index.tsx:23
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — app.config.ts:1
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/post/presentation/stores/FindPostStore/FindPostStore.ts:31
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~6.3 `!` null assertions per 1k TypeScript source lines — 6 assertion(s) across the 951 source line(s) of the 48 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/post/infrastructure/models/PostDto.ts (4), src/post/infrastructure/models/GetPostsQuery.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Adequate — gated by X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Adequate | Acceptable, with room to improve. |
| Maturity | 70% | Strong | Solid. |
| Readiness | 13% | Critical — gated by D8, D9, R4, R8, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 97% | Exemplary | Solid. |
| Domain Modelling | 50% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- AXR1 Runtime accessibility (rendered) — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 3 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 3 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 706 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 30 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 4 claim(s) of kinds M4 does not check were not checked (command argument 4); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JavaScript/TypeScript, JVM source (2 module(s), 50 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 40 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No automated tests
- Domain depends on infrastructure: IHttpClient src/core/domain/specifications/IHttpClient.ts:1
- Unlisted import '@expo/config-types' app.config.ts:1
Serious — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/core/infrastructure/implementations/HttpClient.ts:16
- TodoComment src/core/infrastructure/implementations/HttpClient.ts:24
- WCAG 2.5.5 reproducibly failed on a screen of the running app
- No CI pipeline
- Duplicated block with local edits (20 matched lines × 2 locations) src/post/presentation/components/PostItem.tsx:18
- Test Coverage
- Dead file (~19 LoC) src/core/infrastructure/models/PayloadDto.ts
- Dead file (~18 LoC) src/post/infrastructure/models/GetPostsQuery.ts
- Dead file (~6 LoC) src/core/domain/enums/Locale.ts
- Unused dependency '@expo/prebuild-config'
- Unused dependency 'expo-dev-client'
- Unused dependency 'expo-splash-screen'
- Swallowed exception (empty catch) src/post/presentation/stores/FindPostStore/FindPostStore.ts:31
Minor — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- No tests found
- No ADRs
- No SAST
- No dependency-update automation package.json:18
- Unused export 'RootScreenNavigationProp' src/core/presentation/navigation/types/index.tsx:23
- Null assertions (`!`) reduce the strict null checking score
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c8ec918939334aa48157bfcdfd163b71/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c8ec918939334aa48157bfcdfd163b71/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 48 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |