Executive summary
capcom6/android-sms-gateway falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 48 out of 100 and is rated Weak, and all 29 of its critical findings are security problems in the build pipeline.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 7 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 59.
Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and one pipeline step puts outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks.
The product code is 21,228 lines, about €25,000 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 48 to about 59.
New since the last survey: 43 findings
- Cyclomatic Complexity · PduParser.parseHeaders (cyclomatic 159) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- Cyclomatic Complexity · PduParser.parseContentTypeParams (cyclomatic 28) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- Cyclomatic Complexity · SSEManager.connect (cyclomatic 16) app/src/main/java/me/capcom/smsgateway/helpers/SSEManager.kt
- Cognitive Complexity · PduParser.parseHeaders (cognitive 263) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- Cognitive Complexity · PduParser.parseContentTypeParams (cognitive 60) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- Cognitive Complexity · PduParser.parseContentType (cognitive 18) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- Cognitive Complexity · SSEManager.connect (cognitive 16) app/src/main/java/me/capcom/smsgateway/helpers/SSEManager.kt
- God Classes · MethodTooLong: PduParser.parseHeaders app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- God Classes · ClassTooLong: PduParser app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- God Classes · FileTooLong: aosp/PduParser.java app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- Code Duplication · Edited copy of a member (42 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Code Duplication · Edited copy of a member (24 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Code Duplication · Edited copy of a member (30 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java
- Code Duplication · Edited copy of a member (16 corresponding lines) app/src/main/java/me/capcom/smsgateway/ui/settings/CloudServerSettingsFragment.kt
- Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) app/src/main/java/me/capcom/smsgateway/ui/SettingsFragment.kt
- Code Duplication · Edited copy of a member (22 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java
- Code Duplication · Edited copy of a member (15 corresponding lines) app/src/main/java/me/capcom/smsgateway/ui/HolderFragment.kt
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/incoming/IncomingMessagesSettings.kt
- Code Duplication · Edited copy of a member (27 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java
- Code Duplication · Edited copy of a member (14 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/device/DeviceSettings.kt
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadWorker.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsReceiver.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt
- Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) app/src/main/java/me/capcom/smsgateway/helpers/SubscriptionsHelper.kt
- Code Duplication · Duplicated block (18–20 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Code Duplication · Duplicated block (15 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/incoming/vm/IncomingMessagesListViewModel.kt
- Code Duplication · Duplicated block (7 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MessagesReceiver.kt
- Code Duplication · Duplicated block (16 lines × 4) app/src/main/java/me/capcom/smsgateway/modules/device/workers/KeyRotationWorker.kt
- Code Duplication · Duplicated block (9 lines × 3) app/src/main/java/me/capcom/smsgateway/modules/gateway/services/SSEForegroundService.kt
- Code Duplication · Duplicated block (10 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/messages/workers/SendMessagesWorker.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Change Coupling · Change coupling: GatewayService.kt ↔ RegistrationWorker.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/GatewayService.kt
- Change Coupling · Change coupling: RegistrationWorker.kt ↔ HomeFragment.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/workers/RegistrationWorker.kt
- Supply-chain Provenance & Signing · REDACTED
- Exception handling · Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
Fixed since the last survey: 11 findings
- Cognitive Complexity · MMSParser.parseEncodedString (cognitive 16) app/src/main/java/me/capcom/smsgateway/modules/receiver/parsers/MMSParser.kt
- Code Duplication · Duplicated block (18–20 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Code Duplication · Duplicated block (7 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/incoming/vm/IncomingMessagesListViewModel.kt
- Code Duplication · Duplicated block (7 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MessagesReceiver.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt
- Churn × Complexity Hotspots · Hotspot: app/src/main/java/me/capcom/smsgateway/modules/localserver/domain/messages/PostMessageRequest.kt app/src/main/java/me/capcom/smsgateway/modules/localserver/domain/messages/PostMessageRequest.kt
- Change Coupling · Change coupling: WebService.kt ↔ EventsReceiver.kt app/src/main/java/me/capcom/smsgateway/modules/localserver/WebService.kt
- Change Coupling · Change coupling: PullMessagesWorker.kt ↔ MessagesService.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/workers/PullMessagesWorker.kt
- Exception handling · Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/receiver/parsers/MMSParser.kt
Rebuild cost: about €25,000 · Estimate
| Cost to rebuild | €8,500 to €42,000, for 141 to 447 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,228 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 modules.events | 2 modules.health.domain | 3 modules.incoming.db | 4 modules.logs.db | 5 modules.notifications | 6 modules.receiver.data | 7 domain | 8 modules.connection | 9 modules.logs | 10 domain.MessageContent | 11 modules.device | 12 modules.localserver.domain | 13 modules.webhooks.domain | 14 data.entities | 15 helpers | 16 modules.gateway.GatewayApi | 17 modules.mms | 18 modules.webhooks.db | 19 data.dao | 20 modules.incoming | 21 modules.messages.data | 22 ui.adapters | 23 modules.localserver.auth | 24 modules.localserver.domain.messages | 25 modules.messages | 26 modules.gateway | 27 modules.health | 28 modules.messages.vm | 29 modules.localserver | 30 modules.webhooks | 31 modules.settings | 32 modules.webhooks.workers | 33 ui.settings | 34 modules.encryption | 35 modules.receiver | 36 modules.gateway.inbox | 37 modules.localserver.routes | 38 modules.orchestrator | 39 data | 40 ui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 modules.events | ||||||||||||||||||||||||||||||||||||||||
| 2 modules.health.domain | ||||||||||||||||||||||||||||||||||||||||
| 3 modules.incoming.db | ||||||||||||||||||||||||||||||||||||||||
| 4 modules.logs.db | ||||||||||||||||||||||||||||||||||||||||
| 5 modules.notifications | ||||||||||||||||||||||||||||||||||||||||
| 6 modules.receiver.data | ||||||||||||||||||||||||||||||||||||||||
| 7 domain | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 modules.connection | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 modules.logs | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 10 domain.MessageContent | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 modules.device | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 12 modules.localserver.domain | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 modules.webhooks.domain | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 data.entities | 7 | 3 | ||||||||||||||||||||||||||||||||||||||
| 15 helpers | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 modules.gateway.GatewayApi | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 modules.mms | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 modules.webhooks.db | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 data.dao | 2 | 8 | ||||||||||||||||||||||||||||||||||||||
| 20 modules.incoming | 2 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 21 modules.messages.data | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 ui.adapters | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 modules.localserver.auth | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 modules.localserver.domain.messages | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 modules.messages | 1 | 1 | 5 | 1 | 4 | 1 | 3 | 6 | 3 | 1 | ||||||||||||||||||||||||||||||
| 26 modules.gateway | 3 | 1 | 1 | 1 | 20 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 27 modules.health | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 modules.messages.vm | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 modules.localserver | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 modules.webhooks | 2 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||
| 31 modules.settings | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 32 modules.webhooks.workers | 3 | 2 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 33 ui.settings | 1 | 3 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 34 modules.encryption | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 modules.receiver | 2 | 1 | 1 | 1 | 4 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||
| 36 modules.gateway.inbox | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 modules.localserver.routes | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 38 modules.orchestrator | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 39 data | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 40 ui | 1 | 1 | 1 | 1 | 4 | 2 | 2 | 2 | 1 |
7→2 domain uses modules.health.domain✕
- Connections
- 3 pairs of types, where a type in domain uses a type in modules.health.domain.
- The types involved
me.capcom.smsgateway.domain.HealthResponse→me.capcom.smsgateway.modules.health.domain.CheckResultme.capcom.smsgateway.domain.HealthResponse→me.capcom.smsgateway.modules.health.domain.HealthResultme.capcom.smsgateway.domain.HealthResponse→me.capcom.smsgateway.modules.health.domain.Status
- Direction
- domain uses modules.health.domain, so a change to modules.health.domain can break domain, while a change to domain can't break modules.health.domain.
- Position
- Below the diagonal: domain uses a module listed above it, which is the healthy direction.
8→2 modules.connection uses modules.health.domain✕
- Connections
- 1 pair of types, where a type in modules.connection uses a type in modules.health.domain.
- The types involved
me.capcom.smsgateway.modules.connection.ConnectionService→me.capcom.smsgateway.modules.health.domain.CheckResult
- Direction
- modules.connection uses modules.health.domain, so a change to modules.health.domain can break modules.connection, while a change to modules.connection can't break modules.health.domain.
- Position
- Below the diagonal: modules.connection uses a module listed above it, which is the healthy direction.
9→4 modules.logs uses modules.logs.db✕
- Connections
- 2 pairs of types, where a type in modules.logs uses a type in modules.logs.db.
- The types involved
me.capcom.smsgateway.modules.logs.LogsService→me.capcom.smsgateway.modules.logs.db.LogEntriesDaome.capcom.smsgateway.modules.logs.LogsService→me.capcom.smsgateway.modules.logs.db.LogEntry
- Direction
- modules.logs uses modules.logs.db, so a change to modules.logs.db can break modules.logs, while a change to modules.logs can't break modules.logs.db.
- Position
- Below the diagonal: modules.logs uses a module listed above it, which is the healthy direction.
9→31 modules.logs uses modules.settings part of a loop✕
- Connections
- 3 pairs of types, where a type in modules.logs uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.logs.LogsSettings→me.capcom.smsgateway.modules.settings.Exporterme.capcom.smsgateway.modules.logs.LogsSettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.logs.LogsSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.logs uses modules.settings, so a change to modules.settings can break modules.logs, while a change to modules.logs can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→7 domain.MessageContent uses domain✕
- Connections
- 3 pairs of types, where a type in domain.MessageContent uses a type in domain.
- The types involved
me.capcom.smsgateway.domain.MessageContent.Data→me.capcom.smsgateway.domain.MessageContentme.capcom.smsgateway.domain.MessageContent.Mms→me.capcom.smsgateway.domain.MessageContentme.capcom.smsgateway.domain.MessageContent.Text→me.capcom.smsgateway.domain.MessageContent
- Direction
- domain.MessageContent uses domain, so a change to domain can break domain.MessageContent, while a change to domain.MessageContent can't break domain.
- Position
- Below the diagonal: domain.MessageContent uses a module listed above it, which is the healthy direction.
11→1 modules.device uses modules.events✕
- Connections
- 1 pair of types, where a type in modules.device uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.device.DeviceService→me.capcom.smsgateway.modules.events.EventBus
- Direction
- modules.device uses modules.events, so a change to modules.events can break modules.device, while a change to modules.device can't break modules.events.
- Position
- Below the diagonal: modules.device uses a module listed above it, which is the healthy direction.
11→9 modules.device uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.device uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.device.DeviceService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.device uses modules.logs, so a change to modules.logs can break modules.device, while a change to modules.device can't break modules.logs.
- Position
- Below the diagonal: modules.device uses a module listed above it, which is the healthy direction.
11→31 modules.device uses modules.settings part of a loop✕
- Connections
- 2 pairs of types, where a type in modules.device uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.device.DeviceSettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.device.DeviceSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.device uses modules.settings, so a change to modules.settings can break modules.device, while a change to modules.device can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 modules.localserver.domain uses modules.incoming.db✕
- Connections
- 1 pair of types, where a type in modules.localserver.domain uses a type in modules.incoming.db.
- The types involved
me.capcom.smsgateway.modules.localserver.domain.InboxRefreshRequest→me.capcom.smsgateway.modules.incoming.db.IncomingMessageType
- Direction
- modules.localserver.domain uses modules.incoming.db, so a change to modules.incoming.db can break modules.localserver.domain, while a change to modules.localserver.domain can't break modules.incoming.db.
- Position
- Below the diagonal: modules.localserver.domain uses a module listed above it, which is the healthy direction.
12→7 modules.localserver.domain uses domain✕
- Connections
- 1 pair of types, where a type in modules.localserver.domain uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.localserver.domain.InboxRefreshRequest→me.capcom.smsgateway.domain.WebhookDelivery
- Direction
- modules.localserver.domain uses domain, so a change to domain can break modules.localserver.domain, while a change to modules.localserver.domain can't break domain.
- Position
- Below the diagonal: modules.localserver.domain uses a module listed above it, which is the healthy direction.
13→7 modules.webhooks.domain uses domain✕
- Connections
- 1 pair of types, where a type in modules.webhooks.domain uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.webhooks.domain.WebHookDTO→me.capcom.smsgateway.domain.EntitySource
- Direction
- modules.webhooks.domain uses domain, so a change to domain can break modules.webhooks.domain, while a change to modules.webhooks.domain can't break domain.
- Position
- Below the diagonal: modules.webhooks.domain uses a module listed above it, which is the healthy direction.
14→7 data.entities uses domain✕
- Connections
- 7 pairs of types, where a type in data.entities uses a type in domain.
- The types involved
me.capcom.smsgateway.data.entities.Message→me.capcom.smsgateway.domain.EntitySourceme.capcom.smsgateway.data.entities.Message→me.capcom.smsgateway.domain.MessageContentme.capcom.smsgateway.data.entities.Message→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.data.entities.MessageRecipient→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.data.entities.MessageState→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.data.entities.MessageWithRecipients→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.data.entities.RecipientState→me.capcom.smsgateway.domain.ProcessingState
- Direction
- data.entities uses domain, so a change to domain can break data.entities, while a change to data.entities can't break domain.
- Position
- Below the diagonal: data.entities uses a module listed above it, which is the healthy direction.
14→10 data.entities uses domain.MessageContent✕
- Connections
- 3 pairs of types, where a type in data.entities uses a type in domain.MessageContent.
- The types involved
me.capcom.smsgateway.data.entities.Message→me.capcom.smsgateway.domain.MessageContent.Datame.capcom.smsgateway.data.entities.Message→me.capcom.smsgateway.domain.MessageContent.Mmsme.capcom.smsgateway.data.entities.Message→me.capcom.smsgateway.domain.MessageContent.Text
- Direction
- data.entities uses domain.MessageContent, so a change to domain.MessageContent can break data.entities, while a change to data.entities can't break domain.MessageContent.
- Position
- Below the diagonal: data.entities uses a module listed above it, which is the healthy direction.
15→12 helpers uses modules.localserver.domain✕
- Connections
- 1 pair of types, where a type in helpers uses a type in modules.localserver.domain.
- The types involved
me.capcom.smsgateway.helpers.SubscriptionsHelper→me.capcom.smsgateway.modules.localserver.domain.SimCard
- Direction
- helpers uses modules.localserver.domain, so a change to modules.localserver.domain can break helpers, while a change to helpers can't break modules.localserver.domain.
- Position
- Below the diagonal: helpers uses a module listed above it, which is the healthy direction.
16→7 modules.gateway.GatewayApi uses domain✕
- Connections
- 2 pairs of types, where a type in modules.gateway.GatewayApi uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayApi.MessagePatchRequest→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.modules.gateway.GatewayApi.RecipientState→me.capcom.smsgateway.domain.ProcessingState
- Direction
- modules.gateway.GatewayApi uses domain, so a change to domain can break modules.gateway.GatewayApi, while a change to modules.gateway.GatewayApi can't break domain.
- Position
- Below the diagonal: modules.gateway.GatewayApi uses a module listed above it, which is the healthy direction.
16→13 modules.gateway.GatewayApi uses modules.webhooks.domain✕
- Connections
- 1 pair of types, where a type in modules.gateway.GatewayApi uses a type in modules.webhooks.domain.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayApi.WebHook→me.capcom.smsgateway.modules.webhooks.domain.WebHookEvent
- Direction
- modules.gateway.GatewayApi uses modules.webhooks.domain, so a change to modules.webhooks.domain can break modules.gateway.GatewayApi, while a change to modules.gateway.GatewayApi can't break modules.webhooks.domain.
- Position
- Below the diagonal: modules.gateway.GatewayApi uses a module listed above it, which is the healthy direction.
17→9 modules.mms uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.mms uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.mms.MmsAttachmentStorage→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.mms uses modules.logs, so a change to modules.logs can break modules.mms, while a change to modules.mms can't break modules.logs.
- Position
- Below the diagonal: modules.mms uses a module listed above it, which is the healthy direction.
17→10 modules.mms uses domain.MessageContent✕
- Connections
- 1 pair of types, where a type in modules.mms uses a type in domain.MessageContent.
- The types involved
me.capcom.smsgateway.modules.mms.MmsSender→me.capcom.smsgateway.domain.MessageContent.Mms
- Direction
- modules.mms uses domain.MessageContent, so a change to domain.MessageContent can break modules.mms, while a change to modules.mms can't break domain.MessageContent.
- Position
- Below the diagonal: modules.mms uses a module listed above it, which is the healthy direction.
18→7 modules.webhooks.db uses domain✕
- Connections
- 2 pairs of types, where a type in modules.webhooks.db uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.webhooks.db.WebHook→me.capcom.smsgateway.domain.EntitySourceme.capcom.smsgateway.modules.webhooks.db.WebHooksDao→me.capcom.smsgateway.domain.EntitySource
- Direction
- modules.webhooks.db uses domain, so a change to domain can break modules.webhooks.db, while a change to modules.webhooks.db can't break domain.
- Position
- Below the diagonal: modules.webhooks.db uses a module listed above it, which is the healthy direction.
18→13 modules.webhooks.db uses modules.webhooks.domain✕
- Connections
- 2 pairs of types, where a type in modules.webhooks.db uses a type in modules.webhooks.domain.
- The types involved
me.capcom.smsgateway.modules.webhooks.db.WebHook→me.capcom.smsgateway.modules.webhooks.domain.WebHookEventme.capcom.smsgateway.modules.webhooks.db.WebHooksDao→me.capcom.smsgateway.modules.webhooks.domain.WebHookEvent
- Direction
- modules.webhooks.db uses modules.webhooks.domain, so a change to modules.webhooks.domain can break modules.webhooks.db, while a change to modules.webhooks.db can't break modules.webhooks.domain.
- Position
- Below the diagonal: modules.webhooks.db uses a module listed above it, which is the healthy direction.
18→30 modules.webhooks.db uses modules.webhooks part of a loop✕
- Connections
- 1 pair of types, where a type in modules.webhooks.db uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.modules.webhooks.db.WebhookQueueRepository→me.capcom.smsgateway.modules.webhooks.WebhookPayloadStorage
- Direction
- modules.webhooks.db uses modules.webhooks, so a change to modules.webhooks can break modules.webhooks.db, while a change to modules.webhooks.db can't break modules.webhooks.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→7 data.dao uses domain✕
- Connections
- 2 pairs of types, where a type in data.dao uses a type in domain.
- The types involved
me.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.domain.EntitySourceme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.domain.ProcessingState
- Direction
- data.dao uses domain, so a change to domain can break data.dao, while a change to data.dao can't break domain.
- Position
- Below the diagonal: data.dao uses a module listed above it, which is the healthy direction.
19→14 data.dao uses data.entities✕
- Connections
- 8 pairs of types, where a type in data.dao uses a type in data.entities.
- The types involved
me.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.Messageme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.MessageRecipientme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.MessageStateme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.MessageWithRecipientsme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.MessagesStatsme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.MessagesTotalsme.capcom.smsgateway.data.dao.MessagesDao→me.capcom.smsgateway.data.entities.RecipientStateme.capcom.smsgateway.data.dao.TokensDao→me.capcom.smsgateway.data.entities.Token
- Direction
- data.dao uses data.entities, so a change to data.entities can break data.dao, while a change to data.dao can't break data.entities.
- Position
- Below the diagonal: data.dao uses a module listed above it, which is the healthy direction.
20→3 modules.incoming uses modules.incoming.db✕
- Connections
- 2 pairs of types, where a type in modules.incoming uses a type in modules.incoming.db.
- The types involved
me.capcom.smsgateway.modules.incoming.IncomingMessagesService→me.capcom.smsgateway.modules.incoming.db.IncomingMessageme.capcom.smsgateway.modules.incoming.IncomingMessagesService→me.capcom.smsgateway.modules.incoming.db.IncomingMessageType
- Direction
- modules.incoming uses modules.incoming.db, so a change to modules.incoming.db can break modules.incoming, while a change to modules.incoming can't break modules.incoming.db.
- Position
- Below the diagonal: modules.incoming uses a module listed above it, which is the healthy direction.
20→6 modules.incoming uses modules.receiver.data✕
- Connections
- 1 pair of types, where a type in modules.incoming uses a type in modules.receiver.data.
- The types involved
me.capcom.smsgateway.modules.incoming.IncomingMessagesService→me.capcom.smsgateway.modules.receiver.data.InboxMessage
- Direction
- modules.incoming uses modules.receiver.data, so a change to modules.receiver.data can break modules.incoming, while a change to modules.incoming can't break modules.receiver.data.
- Position
- Below the diagonal: modules.incoming uses a module listed above it, which is the healthy direction.
20→9 modules.incoming uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.incoming uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.incoming.IncomingMessagesService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.incoming uses modules.logs, so a change to modules.logs can break modules.incoming, while a change to modules.incoming can't break modules.logs.
- Position
- Below the diagonal: modules.incoming uses a module listed above it, which is the healthy direction.
20→17 modules.incoming uses modules.mms✕
- Connections
- 1 pair of types, where a type in modules.incoming uses a type in modules.mms.
- The types involved
me.capcom.smsgateway.modules.incoming.IncomingMessagesService→me.capcom.smsgateway.modules.mms.MmsAttachmentStorage
- Direction
- modules.incoming uses modules.mms, so a change to modules.mms can break modules.incoming, while a change to modules.incoming can't break modules.mms.
- Position
- Below the diagonal: modules.incoming uses a module listed above it, which is the healthy direction.
20→31 modules.incoming uses modules.settings part of a loop✕
- Connections
- 3 pairs of types, where a type in modules.incoming uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.incoming.IncomingMessagesSettings→me.capcom.smsgateway.modules.settings.Exporterme.capcom.smsgateway.modules.incoming.IncomingMessagesSettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.incoming.IncomingMessagesSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.incoming uses modules.settings, so a change to modules.settings can break modules.incoming, while a change to modules.incoming can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→7 modules.messages.data uses domain✕
- Connections
- 4 pairs of types, where a type in modules.messages.data uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.messages.data.Message→me.capcom.smsgateway.domain.MessageContentme.capcom.smsgateway.modules.messages.data.SendRequest→me.capcom.smsgateway.domain.EntitySourceme.capcom.smsgateway.modules.messages.data.StoredSendRequest→me.capcom.smsgateway.domain.EntitySourceme.capcom.smsgateway.modules.messages.data.StoredSendRequest→me.capcom.smsgateway.domain.ProcessingState
- Direction
- modules.messages.data uses domain, so a change to domain can break modules.messages.data, while a change to modules.messages.data can't break domain.
- Position
- Below the diagonal: modules.messages.data uses a module listed above it, which is the healthy direction.
21→14 modules.messages.data uses data.entities✕
- Connections
- 1 pair of types, where a type in modules.messages.data uses a type in data.entities.
- The types involved
me.capcom.smsgateway.modules.messages.data.StoredSendRequest→me.capcom.smsgateway.data.entities.MessageRecipient
- Direction
- modules.messages.data uses data.entities, so a change to data.entities can break modules.messages.data, while a change to modules.messages.data can't break data.entities.
- Position
- Below the diagonal: modules.messages.data uses a module listed above it, which is the healthy direction.
22→14 ui.adapters uses data.entities✕
- Connections
- 1 pair of types, where a type in ui.adapters uses a type in data.entities.
- The types involved
me.capcom.smsgateway.ui.adapters.MessagesAdapter→me.capcom.smsgateway.data.entities.Message
- Direction
- ui.adapters uses data.entities, so a change to data.entities can break ui.adapters, while a change to ui.adapters can't break data.entities.
- Position
- Below the diagonal: ui.adapters uses a module listed above it, which is the healthy direction.
22→18 ui.adapters uses modules.webhooks.db✕
- Connections
- 1 pair of types, where a type in ui.adapters uses a type in modules.webhooks.db.
- The types involved
me.capcom.smsgateway.ui.adapters.WebhookQueueAdapter→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueEntity
- Direction
- ui.adapters uses modules.webhooks.db, so a change to modules.webhooks.db can break ui.adapters, while a change to ui.adapters can't break modules.webhooks.db.
- Position
- Below the diagonal: ui.adapters uses a module listed above it, which is the healthy direction.
23→9 modules.localserver.auth uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.localserver.auth uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.localserver.auth.JwtService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.localserver.auth uses modules.logs, so a change to modules.logs can break modules.localserver.auth, while a change to modules.localserver.auth can't break modules.logs.
- Position
- Below the diagonal: modules.localserver.auth uses a module listed above it, which is the healthy direction.
23→19 modules.localserver.auth uses data.dao✕
- Connections
- 1 pair of types, where a type in modules.localserver.auth uses a type in data.dao.
- The types involved
me.capcom.smsgateway.modules.localserver.auth.JwtService→me.capcom.smsgateway.data.dao.TokensDao
- Direction
- modules.localserver.auth uses data.dao, so a change to data.dao can break modules.localserver.auth, while a change to modules.localserver.auth can't break data.dao.
- Position
- Below the diagonal: modules.localserver.auth uses a module listed above it, which is the healthy direction.
23→29 modules.localserver.auth uses modules.localserver part of a loop✕
- Connections
- 1 pair of types, where a type in modules.localserver.auth uses a type in modules.localserver.
- The types involved
me.capcom.smsgateway.modules.localserver.auth.JwtService→me.capcom.smsgateway.modules.localserver.LocalServerSettings
- Direction
- modules.localserver.auth uses modules.localserver, so a change to modules.localserver can break modules.localserver.auth, while a change to modules.localserver.auth can't break modules.localserver.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→7 modules.localserver.domain.messages uses domain✕
- Connections
- 1 pair of types, where a type in modules.localserver.domain.messages uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.localserver.domain.messages.Message→me.capcom.smsgateway.domain.ProcessingState
- Direction
- modules.localserver.domain.messages uses domain, so a change to domain can break modules.localserver.domain.messages, while a change to modules.localserver.domain.messages can't break domain.
- Position
- Below the diagonal: modules.localserver.domain.messages uses a module listed above it, which is the healthy direction.
24→21 modules.localserver.domain.messages uses modules.messages.data✕
- Connections
- 1 pair of types, where a type in modules.localserver.domain.messages uses a type in modules.messages.data.
- The types involved
me.capcom.smsgateway.modules.localserver.domain.messages.MessageSort→me.capcom.smsgateway.modules.messages.data.MessageSort
- Direction
- modules.localserver.domain.messages uses modules.messages.data, so a change to modules.messages.data can break modules.localserver.domain.messages, while a change to modules.localserver.domain.messages can't break modules.messages.data.
- Position
- Below the diagonal: modules.localserver.domain.messages uses a module listed above it, which is the healthy direction.
25→1 modules.messages uses modules.events✕
- Connections
- 1 pair of types, where a type in modules.messages uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.messages.MessageStateService→me.capcom.smsgateway.modules.events.EventBus
- Direction
- modules.messages uses modules.events, so a change to modules.events can break modules.messages, while a change to modules.messages can't break modules.events.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→2 modules.messages uses modules.health.domain✕
- Connections
- 1 pair of types, where a type in modules.messages uses a type in modules.health.domain.
- The types involved
me.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.health.domain.CheckResult
- Direction
- modules.messages uses modules.health.domain, so a change to modules.health.domain can break modules.messages, while a change to modules.messages can't break modules.health.domain.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→7 modules.messages uses domain✕
- Connections
- 5 pairs of types, where a type in modules.messages uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.messages.MessageStateService→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.modules.messages.MessageStateTransitions→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.modules.messages.MessagesRepository→me.capcom.smsgateway.domain.ProcessingStateme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.domain.EntitySourceme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.domain.ProcessingState
- Direction
- modules.messages uses domain, so a change to domain can break modules.messages, while a change to modules.messages can't break domain.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→9 modules.messages uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.messages uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.messages uses modules.logs, so a change to modules.logs can break modules.messages, while a change to modules.messages can't break modules.logs.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→14 modules.messages uses data.entities✕
- Connections
- 4 pairs of types, where a type in modules.messages uses a type in data.entities.
- The types involved
me.capcom.smsgateway.modules.messages.MessageStateService→me.capcom.smsgateway.data.entities.MessageWithRecipientsme.capcom.smsgateway.modules.messages.MessagesRepository→me.capcom.smsgateway.data.entities.MessageWithRecipientsme.capcom.smsgateway.modules.messages.MessagesRepository→me.capcom.smsgateway.data.entities.MessagesTotalsme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.data.entities.MessageWithRecipients
- Direction
- modules.messages uses data.entities, so a change to data.entities can break modules.messages, while a change to modules.messages can't break data.entities.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→17 modules.messages uses modules.mms✕
- Connections
- 1 pair of types, where a type in modules.messages uses a type in modules.mms.
- The types involved
me.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.mms.MmsSender
- Direction
- modules.messages uses modules.mms, so a change to modules.mms can break modules.messages, while a change to modules.messages can't break modules.mms.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→19 modules.messages uses data.dao✕
- Connections
- 3 pairs of types, where a type in modules.messages uses a type in data.dao.
- The types involved
me.capcom.smsgateway.modules.messages.MessageStateService→me.capcom.smsgateway.data.dao.MessagesDaome.capcom.smsgateway.modules.messages.MessagesRepository→me.capcom.smsgateway.data.dao.MessagesDaome.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.data.dao.MessagesDao
- Direction
- modules.messages uses data.dao, so a change to data.dao can break modules.messages, while a change to modules.messages can't break data.dao.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→21 modules.messages uses modules.messages.data✕
- Connections
- 6 pairs of types, where a type in modules.messages uses a type in modules.messages.data.
- The types involved
me.capcom.smsgateway.modules.messages.MessagesRepository→me.capcom.smsgateway.modules.messages.data.SendRequestme.capcom.smsgateway.modules.messages.MessagesRepository→me.capcom.smsgateway.modules.messages.data.StoredSendRequestme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.messages.data.MessageSortme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.messages.data.SendParamsme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.messages.data.SendRequestme.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.messages.data.StoredSendRequest
- Direction
- modules.messages uses modules.messages.data, so a change to modules.messages.data can break modules.messages, while a change to modules.messages can't break modules.messages.data.
- Position
- Below the diagonal: modules.messages uses a module listed above it, which is the healthy direction.
25→31 modules.messages uses modules.settings part of a loop✕
- Connections
- 3 pairs of types, where a type in modules.messages uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.messages.MessagesSettings→me.capcom.smsgateway.modules.settings.Exporterme.capcom.smsgateway.modules.messages.MessagesSettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.messages.MessagesSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.messages uses modules.settings, so a change to modules.settings can break modules.messages, while a change to modules.messages can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→34 modules.messages uses modules.encryption part of a loop✕
- Connections
- 1 pair of types, where a type in modules.messages uses a type in modules.encryption.
- The types involved
me.capcom.smsgateway.modules.messages.MessagesService→me.capcom.smsgateway.modules.encryption.EncryptionService
- Direction
- modules.messages uses modules.encryption, so a change to modules.encryption can break modules.messages, while a change to modules.messages can't break modules.encryption.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→1 modules.gateway uses modules.events✕
- Connections
- 3 pairs of types, where a type in modules.gateway uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.gateway.EventsReceiver→me.capcom.smsgateway.modules.events.EventBusme.capcom.smsgateway.modules.gateway.EventsReceiver→me.capcom.smsgateway.modules.events.EventsReceiverme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.events.EventBus
- Direction
- modules.gateway uses modules.events, so a change to modules.events can break modules.gateway, while a change to modules.gateway can't break modules.events.
- Position
- Below the diagonal: modules.gateway uses a module listed above it, which is the healthy direction.
26→6 modules.gateway uses modules.receiver.data✕
- Connections
- 1 pair of types, where a type in modules.gateway uses a type in modules.receiver.data.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.receiver.data.InboxMessage
- Direction
- modules.gateway uses modules.receiver.data, so a change to modules.receiver.data can break modules.gateway, while a change to modules.gateway can't break modules.receiver.data.
- Position
- Below the diagonal: modules.gateway uses a module listed above it, which is the healthy direction.
26→9 modules.gateway uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.gateway uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.gateway uses modules.logs, so a change to modules.logs can break modules.gateway, while a change to modules.gateway can't break modules.logs.
- Position
- Below the diagonal: modules.gateway uses a module listed above it, which is the healthy direction.
26→11 modules.gateway uses modules.device✕
- Connections
- 1 pair of types, where a type in modules.gateway uses a type in modules.device.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.device.DeviceService
- Direction
- modules.gateway uses modules.device, so a change to modules.device can break modules.gateway, while a change to modules.gateway can't break modules.device.
- Position
- Below the diagonal: modules.gateway uses a module listed above it, which is the healthy direction.
26→16 modules.gateway uses modules.gateway.GatewayApi✕
- Connections
- 20 pairs of types, where a type in modules.gateway uses a type in modules.gateway.GatewayApi.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.DeviceGetResponseme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.DevicePatchRequestme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.DeviceRegisterRequestme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.DeviceRegisterResponseme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.GetUserCodeResponseme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.InboxMessageme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.Messageme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.MessagePatchRequestme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.PasswordChangeRequestme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.ProcessingOrderme.capcom.smsgateway.modules.gateway.GatewayApi→me.capcom.smsgateway.modules.gateway.GatewayApi.WebHookme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.GatewayApi.GetUserCodeResponseme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.GatewayApi.InboxMessageme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.GatewayApi.Messageme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.GatewayApi.MessagePatchRequestme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.GatewayApi.SimCardme.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.GatewayApi.WebHookme.capcom.smsgateway.modules.gateway.GatewayServiceKt→me.capcom.smsgateway.modules.gateway.GatewayApi.Messageme.capcom.smsgateway.modules.gateway.GatewayServiceKt→me.capcom.smsgateway.modules.gateway.GatewayApi.MessagePatchRequestme.capcom.smsgateway.modules.gateway.GatewaySettings→me.capcom.smsgateway.modules.gateway.GatewayApi.DeviceRegisterResponse
- Direction
- modules.gateway uses modules.gateway.GatewayApi, so a change to modules.gateway.GatewayApi can break modules.gateway, while a change to modules.gateway can't break modules.gateway.GatewayApi.
- Position
- Below the diagonal: modules.gateway uses a module listed above it, which is the healthy direction.
26→25 modules.gateway uses modules.messages✕
- Connections
- 1 pair of types, where a type in modules.gateway uses a type in modules.messages.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.messages.MessagesService
- Direction
- modules.gateway uses modules.messages, so a change to modules.messages can break modules.gateway, while a change to modules.gateway can't break modules.messages.
- Position
- Below the diagonal: modules.gateway uses a module listed above it, which is the healthy direction.
26→31 modules.gateway uses modules.settings part of a loop✕
- Connections
- 3 pairs of types, where a type in modules.gateway uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewaySettings→me.capcom.smsgateway.modules.settings.Exporterme.capcom.smsgateway.modules.gateway.GatewaySettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.gateway.GatewaySettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.gateway uses modules.settings, so a change to modules.settings can break modules.gateway, while a change to modules.gateway can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→36 modules.gateway uses modules.gateway.inbox part of a loop✕
- Connections
- 1 pair of types, where a type in modules.gateway uses a type in modules.gateway.inbox.
- The types involved
me.capcom.smsgateway.modules.gateway.GatewayService→me.capcom.smsgateway.modules.gateway.inbox.InboxUploadService
- Direction
- modules.gateway uses modules.gateway.inbox, so a change to modules.gateway.inbox can break modules.gateway, while a change to modules.gateway can't break modules.gateway.inbox.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→2 modules.health uses modules.health.domain✕
- Connections
- 1 pair of types, where a type in modules.health uses a type in modules.health.domain.
- The types involved
me.capcom.smsgateway.modules.health.HealthService→me.capcom.smsgateway.modules.health.domain.HealthResult
- Direction
- modules.health uses modules.health.domain, so a change to modules.health.domain can break modules.health, while a change to modules.health can't break modules.health.domain.
- Position
- Below the diagonal: modules.health uses a module listed above it, which is the healthy direction.
27→8 modules.health uses modules.connection✕
- Connections
- 1 pair of types, where a type in modules.health uses a type in modules.connection.
- The types involved
me.capcom.smsgateway.modules.health.HealthService→me.capcom.smsgateway.modules.connection.ConnectionService
- Direction
- modules.health uses modules.connection, so a change to modules.connection can break modules.health, while a change to modules.health can't break modules.connection.
- Position
- Below the diagonal: modules.health uses a module listed above it, which is the healthy direction.
27→25 modules.health uses modules.messages✕
- Connections
- 1 pair of types, where a type in modules.health uses a type in modules.messages.
- The types involved
me.capcom.smsgateway.modules.health.HealthService→me.capcom.smsgateway.modules.messages.MessagesService
- Direction
- modules.health uses modules.messages, so a change to modules.messages can break modules.health, while a change to modules.health can't break modules.messages.
- Position
- Below the diagonal: modules.health uses a module listed above it, which is the healthy direction.
28→7 modules.messages.vm uses domain✕
- Connections
- 1 pair of types, where a type in modules.messages.vm uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.messages.vm.MessagesListViewModel→me.capcom.smsgateway.domain.ProcessingState
- Direction
- modules.messages.vm uses domain, so a change to domain can break modules.messages.vm, while a change to modules.messages.vm can't break domain.
- Position
- Below the diagonal: modules.messages.vm uses a module listed above it, which is the healthy direction.
28→14 modules.messages.vm uses data.entities✕
- Connections
- 2 pairs of types, where a type in modules.messages.vm uses a type in data.entities.
- The types involved
me.capcom.smsgateway.modules.messages.vm.MessagesListViewModel→me.capcom.smsgateway.data.entities.Messageme.capcom.smsgateway.modules.messages.vm.MessagesListViewModel→me.capcom.smsgateway.data.entities.MessagesTotals
- Direction
- modules.messages.vm uses data.entities, so a change to data.entities can break modules.messages.vm, while a change to modules.messages.vm can't break data.entities.
- Position
- Below the diagonal: modules.messages.vm uses a module listed above it, which is the healthy direction.
28→21 modules.messages.vm uses modules.messages.data✕
- Connections
- 1 pair of types, where a type in modules.messages.vm uses a type in modules.messages.data.
- The types involved
me.capcom.smsgateway.modules.messages.vm.MessageDetailsViewModel→me.capcom.smsgateway.modules.messages.data.StoredSendRequest
- Direction
- modules.messages.vm uses modules.messages.data, so a change to modules.messages.data can break modules.messages.vm, while a change to modules.messages.vm can't break modules.messages.data.
- Position
- Below the diagonal: modules.messages.vm uses a module listed above it, which is the healthy direction.
28→25 modules.messages.vm uses modules.messages✕
- Connections
- 2 pairs of types, where a type in modules.messages.vm uses a type in modules.messages.
- The types involved
me.capcom.smsgateway.modules.messages.vm.MessageDetailsViewModel→me.capcom.smsgateway.modules.messages.MessagesRepositoryme.capcom.smsgateway.modules.messages.vm.MessagesListViewModel→me.capcom.smsgateway.modules.messages.MessagesRepository
- Direction
- modules.messages.vm uses modules.messages, so a change to modules.messages can break modules.messages.vm, while a change to modules.messages.vm can't break modules.messages.
- Position
- Below the diagonal: modules.messages.vm uses a module listed above it, which is the healthy direction.
29→1 modules.localserver uses modules.events✕
- Connections
- 1 pair of types, where a type in modules.localserver uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.localserver.LocalServerService→me.capcom.smsgateway.modules.events.EventBus
- Direction
- modules.localserver uses modules.events, so a change to modules.events can break modules.localserver, while a change to modules.localserver can't break modules.events.
- Position
- Below the diagonal: modules.localserver uses a module listed above it, which is the healthy direction.
29→5 modules.localserver uses modules.notifications✕
- Connections
- 1 pair of types, where a type in modules.localserver uses a type in modules.notifications.
- The types involved
me.capcom.smsgateway.modules.localserver.WebService→me.capcom.smsgateway.modules.notifications.NotificationsService
- Direction
- modules.localserver uses modules.notifications, so a change to modules.notifications can break modules.localserver, while a change to modules.localserver can't break modules.notifications.
- Position
- Below the diagonal: modules.localserver uses a module listed above it, which is the healthy direction.
29→23 modules.localserver uses modules.localserver.auth✕
- Connections
- 1 pair of types, where a type in modules.localserver uses a type in modules.localserver.auth.
- The types involved
me.capcom.smsgateway.modules.localserver.WebService→me.capcom.smsgateway.modules.localserver.auth.JwtService
- Direction
- modules.localserver uses modules.localserver.auth, so a change to modules.localserver.auth can break modules.localserver, while a change to modules.localserver can't break modules.localserver.auth.
- Position
- Below the diagonal: modules.localserver uses a module listed above it, which is the healthy direction.
29→27 modules.localserver uses modules.health✕
- Connections
- 1 pair of types, where a type in modules.localserver uses a type in modules.health.
- The types involved
me.capcom.smsgateway.modules.localserver.WebService→me.capcom.smsgateway.modules.health.HealthService
- Direction
- modules.localserver uses modules.health, so a change to modules.health can break modules.localserver, while a change to modules.localserver can't break modules.health.
- Position
- Below the diagonal: modules.localserver uses a module listed above it, which is the healthy direction.
29→31 modules.localserver uses modules.settings part of a loop✕
- Connections
- 1 pair of types, where a type in modules.localserver uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.localserver.LocalServerSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.localserver uses modules.settings, so a change to modules.settings can break modules.localserver, while a change to modules.localserver can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 modules.webhooks uses modules.events✕
- Connections
- 2 pairs of types, where a type in modules.webhooks uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.webhooks.EventsReceiver→me.capcom.smsgateway.modules.events.EventBusme.capcom.smsgateway.modules.webhooks.EventsReceiver→me.capcom.smsgateway.modules.events.EventsReceiver
- Direction
- modules.webhooks uses modules.events, so a change to modules.events can break modules.webhooks, while a change to modules.webhooks can't break modules.events.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→5 modules.webhooks uses modules.notifications✕
- Connections
- 1 pair of types, where a type in modules.webhooks uses a type in modules.notifications.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.notifications.NotificationsService
- Direction
- modules.webhooks uses modules.notifications, so a change to modules.notifications can break modules.webhooks, while a change to modules.webhooks can't break modules.notifications.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→7 modules.webhooks uses domain✕
- Connections
- 1 pair of types, where a type in modules.webhooks uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.domain.EntitySource
- Direction
- modules.webhooks uses domain, so a change to domain can break modules.webhooks, while a change to modules.webhooks can't break domain.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→9 modules.webhooks uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.webhooks uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.webhooks uses modules.logs, so a change to modules.logs can break modules.webhooks, while a change to modules.webhooks can't break modules.logs.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→13 modules.webhooks uses modules.webhooks.domain✕
- Connections
- 2 pairs of types, where a type in modules.webhooks uses a type in modules.webhooks.domain.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.webhooks.domain.WebHookDTOme.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.webhooks.domain.WebHookEvent
- Direction
- modules.webhooks uses modules.webhooks.domain, so a change to modules.webhooks.domain can break modules.webhooks, while a change to modules.webhooks can't break modules.webhooks.domain.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→18 modules.webhooks uses modules.webhooks.db✕
- Connections
- 1 pair of types, where a type in modules.webhooks uses a type in modules.webhooks.db.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.webhooks.db.WebHooksDao
- Direction
- modules.webhooks uses modules.webhooks.db, so a change to modules.webhooks.db can break modules.webhooks, while a change to modules.webhooks can't break modules.webhooks.db.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→26 modules.webhooks uses modules.gateway✕
- Connections
- 1 pair of types, where a type in modules.webhooks uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.gateway.GatewaySettings
- Direction
- modules.webhooks uses modules.gateway, so a change to modules.gateway can break modules.webhooks, while a change to modules.webhooks can't break modules.gateway.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→29 modules.webhooks uses modules.localserver✕
- Connections
- 1 pair of types, where a type in modules.webhooks uses a type in modules.localserver.
- The types involved
me.capcom.smsgateway.modules.webhooks.WebHooksService→me.capcom.smsgateway.modules.localserver.LocalServerSettings
- Direction
- modules.webhooks uses modules.localserver, so a change to modules.localserver can break modules.webhooks, while a change to modules.webhooks can't break modules.localserver.
- Position
- Below the diagonal: modules.webhooks uses a module listed above it, which is the healthy direction.
30→31 modules.webhooks uses modules.settings part of a loop✕
- Connections
- 4 pairs of types, where a type in modules.webhooks uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.webhooks.TemporaryStorage→me.capcom.smsgateway.modules.settings.KeyValueStorageme.capcom.smsgateway.modules.webhooks.WebhooksSettings→me.capcom.smsgateway.modules.settings.Exporterme.capcom.smsgateway.modules.webhooks.WebhooksSettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.webhooks.WebhooksSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.webhooks uses modules.settings, so a change to modules.settings can break modules.webhooks, while a change to modules.webhooks can't break modules.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→5 modules.settings uses modules.notifications✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.notifications.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.notifications.NotificationsService
- Direction
- modules.settings uses modules.notifications, so a change to modules.notifications can break modules.settings, while a change to modules.settings can't break modules.notifications.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→9 modules.settings uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.logs.LogsSettings
- Direction
- modules.settings uses modules.logs, so a change to modules.logs can break modules.settings, while a change to modules.settings can't break modules.logs.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→11 modules.settings uses modules.device✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.device.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.device.DeviceSettings
- Direction
- modules.settings uses modules.device, so a change to modules.device can break modules.settings, while a change to modules.settings can't break modules.device.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→20 modules.settings uses modules.incoming✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.incoming.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.incoming.IncomingMessagesSettings
- Direction
- modules.settings uses modules.incoming, so a change to modules.incoming can break modules.settings, while a change to modules.settings can't break modules.incoming.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→25 modules.settings uses modules.messages✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.messages.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.messages.MessagesSettings
- Direction
- modules.settings uses modules.messages, so a change to modules.messages can break modules.settings, while a change to modules.settings can't break modules.messages.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→26 modules.settings uses modules.gateway✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.gateway.GatewaySettings
- Direction
- modules.settings uses modules.gateway, so a change to modules.gateway can break modules.settings, while a change to modules.settings can't break modules.gateway.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→30 modules.settings uses modules.webhooks✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.webhooks.WebhooksSettings
- Direction
- modules.settings uses modules.webhooks, so a change to modules.webhooks can break modules.settings, while a change to modules.settings can't break modules.webhooks.
- Position
- Below the diagonal: modules.settings uses a module listed above it, which is the healthy direction.
31→34 modules.settings uses modules.encryption part of a loop✕
- Connections
- 1 pair of types, where a type in modules.settings uses a type in modules.encryption.
- The types involved
me.capcom.smsgateway.modules.settings.SettingsService→me.capcom.smsgateway.modules.encryption.EncryptionSettings
- Direction
- modules.settings uses modules.encryption, so a change to modules.encryption can break modules.settings, while a change to modules.settings can't break modules.encryption.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→5 modules.webhooks.workers uses modules.notifications✕
- Connections
- 3 pairs of types, where a type in modules.webhooks.workers uses a type in modules.notifications.
- The types involved
me.capcom.smsgateway.modules.webhooks.workers.ReviewWebhooksWorker→me.capcom.smsgateway.modules.notifications.NotificationsServiceme.capcom.smsgateway.modules.webhooks.workers.SendWebhookWorker→me.capcom.smsgateway.modules.notifications.NotificationsServiceme.capcom.smsgateway.modules.webhooks.workers.WebhookQueueProcessorWorker→me.capcom.smsgateway.modules.notifications.NotificationsService
- Direction
- modules.webhooks.workers uses modules.notifications, so a change to modules.notifications can break modules.webhooks.workers, while a change to modules.webhooks.workers can't break modules.notifications.
- Position
- Below the diagonal: modules.webhooks.workers uses a module listed above it, which is the healthy direction.
32→9 modules.webhooks.workers uses modules.logs✕
- Connections
- 2 pairs of types, where a type in modules.webhooks.workers uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.webhooks.workers.SendWebhookWorker→me.capcom.smsgateway.modules.logs.LogsServiceme.capcom.smsgateway.modules.webhooks.workers.WebhookQueueProcessorWorker→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.webhooks.workers uses modules.logs, so a change to modules.logs can break modules.webhooks.workers, while a change to modules.webhooks.workers can't break modules.logs.
- Position
- Below the diagonal: modules.webhooks.workers uses a module listed above it, which is the healthy direction.
32→18 modules.webhooks.workers uses modules.webhooks.db✕
- Connections
- 2 pairs of types, where a type in modules.webhooks.workers uses a type in modules.webhooks.db.
- The types involved
me.capcom.smsgateway.modules.webhooks.workers.WebhookQueueProcessorWorker→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueEntityme.capcom.smsgateway.modules.webhooks.workers.WebhookQueueProcessorWorker→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueRepository
- Direction
- modules.webhooks.workers uses modules.webhooks.db, so a change to modules.webhooks.db can break modules.webhooks.workers, while a change to modules.webhooks.workers can't break modules.webhooks.db.
- Position
- Below the diagonal: modules.webhooks.workers uses a module listed above it, which is the healthy direction.
32→30 modules.webhooks.workers uses modules.webhooks✕
- Connections
- 5 pairs of types, where a type in modules.webhooks.workers uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.modules.webhooks.workers.ReviewWebhooksWorker→me.capcom.smsgateway.modules.webhooks.WebHooksServiceme.capcom.smsgateway.modules.webhooks.workers.SendWebhookWorker→me.capcom.smsgateway.modules.webhooks.TemporaryStorageme.capcom.smsgateway.modules.webhooks.workers.SendWebhookWorker→me.capcom.smsgateway.modules.webhooks.WebhooksSettingsme.capcom.smsgateway.modules.webhooks.workers.WebhookQueueProcessorWorker→me.capcom.smsgateway.modules.webhooks.WebhookPayloadStorageme.capcom.smsgateway.modules.webhooks.workers.WebhookQueueProcessorWorker→me.capcom.smsgateway.modules.webhooks.WebhooksSettings
- Direction
- modules.webhooks.workers uses modules.webhooks, so a change to modules.webhooks can break modules.webhooks.workers, while a change to modules.webhooks.workers can't break modules.webhooks.
- Position
- Below the diagonal: modules.webhooks.workers uses a module listed above it, which is the healthy direction.
33→11 ui.settings uses modules.device✕
- Connections
- 1 pair of types, where a type in ui.settings uses a type in modules.device.
- The types involved
me.capcom.smsgateway.ui.settings.DeviceSettingsFragment→me.capcom.smsgateway.modules.device.DeviceService
- Direction
- ui.settings uses modules.device, so a change to modules.device can break ui.settings, while a change to ui.settings can't break modules.device.
- Position
- Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
33→18 ui.settings uses modules.webhooks.db✕
- Connections
- 3 pairs of types, where a type in ui.settings uses a type in modules.webhooks.db.
- The types involved
me.capcom.smsgateway.ui.settings.WebhookQueueDetailFragment→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueDaome.capcom.smsgateway.ui.settings.WebhookQueueDetailFragment→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueEntityme.capcom.smsgateway.ui.settings.WebhookQueueListFragment→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueEntity
- Direction
- ui.settings uses modules.webhooks.db, so a change to modules.webhooks.db can break ui.settings, while a change to ui.settings can't break modules.webhooks.db.
- Position
- Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
33→22 ui.settings uses ui.adapters✕
- Connections
- 2 pairs of types, where a type in ui.settings uses a type in ui.adapters.
- The types involved
me.capcom.smsgateway.ui.settings.WebhookQueueListFragment→me.capcom.smsgateway.ui.adapters.WebhookQueueAdapterme.capcom.smsgateway.ui.settings.WebhooksListFragment→me.capcom.smsgateway.ui.adapters.WebhookAdapter
- Direction
- ui.settings uses ui.adapters, so a change to ui.adapters can break ui.settings, while a change to ui.settings can't break ui.adapters.
- Position
- Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
33→26 ui.settings uses modules.gateway✕
- Connections
- 2 pairs of types, where a type in ui.settings uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.ui.settings.CloudServerSettingsFragment→me.capcom.smsgateway.modules.gateway.GatewayServiceme.capcom.smsgateway.ui.settings.CloudServerSettingsFragment→me.capcom.smsgateway.modules.gateway.GatewaySettings
- Direction
- ui.settings uses modules.gateway, so a change to modules.gateway can break ui.settings, while a change to ui.settings can't break modules.gateway.
- Position
- Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
33→30 ui.settings uses modules.webhooks✕
- Connections
- 2 pairs of types, where a type in ui.settings uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.ui.settings.WebhookQueueDetailFragment→me.capcom.smsgateway.modules.webhooks.WebhookPayloadStorageme.capcom.smsgateway.ui.settings.WebhooksListFragment→me.capcom.smsgateway.modules.webhooks.WebHooksService
- Direction
- ui.settings uses modules.webhooks, so a change to modules.webhooks can break ui.settings, while a change to ui.settings can't break modules.webhooks.
- Position
- Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
34→31 modules.encryption uses modules.settings✕
- Connections
- 2 pairs of types, where a type in modules.encryption uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.encryption.EncryptionSettings→me.capcom.smsgateway.modules.settings.Importerme.capcom.smsgateway.modules.encryption.EncryptionSettings→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.encryption uses modules.settings, so a change to modules.settings can break modules.encryption, while a change to modules.encryption can't break modules.settings.
- Position
- Below the diagonal: modules.encryption uses a module listed above it, which is the healthy direction.
35→1 modules.receiver uses modules.events✕
- Connections
- 2 pairs of types, where a type in modules.receiver uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.receiver.EventsReceiver→me.capcom.smsgateway.modules.events.EventBusme.capcom.smsgateway.modules.receiver.EventsReceiver→me.capcom.smsgateway.modules.events.EventsReceiver
- Direction
- modules.receiver uses modules.events, so a change to modules.events can break modules.receiver, while a change to modules.receiver can't break modules.events.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→3 modules.receiver uses modules.incoming.db✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in modules.incoming.db.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.incoming.db.IncomingMessageType
- Direction
- modules.receiver uses modules.incoming.db, so a change to modules.incoming.db can break modules.receiver, while a change to modules.receiver can't break modules.incoming.db.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→6 modules.receiver uses modules.receiver.data✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in modules.receiver.data.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.receiver.data.InboxMessage
- Direction
- modules.receiver uses modules.receiver.data, so a change to modules.receiver.data can break modules.receiver, while a change to modules.receiver can't break modules.receiver.data.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→7 modules.receiver uses domain✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in domain.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.domain.WebhookDelivery
- Direction
- modules.receiver uses domain, so a change to domain can break modules.receiver, while a change to modules.receiver can't break domain.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→9 modules.receiver uses modules.logs✕
- Connections
- 4 pairs of types, where a type in modules.receiver uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.receiver.MmsContentObserver→me.capcom.smsgateway.modules.logs.LogsServiceme.capcom.smsgateway.modules.receiver.MmsReceiver→me.capcom.smsgateway.modules.logs.LogsServiceme.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.logs.LogsServiceme.capcom.smsgateway.modules.receiver.SmsContentObserver→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.receiver uses modules.logs, so a change to modules.logs can break modules.receiver, while a change to modules.receiver can't break modules.logs.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→13 modules.receiver uses modules.webhooks.domain✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in modules.webhooks.domain.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.webhooks.domain.WebHookEvent
- Direction
- modules.receiver uses modules.webhooks.domain, so a change to modules.webhooks.domain can break modules.receiver, while a change to modules.receiver can't break modules.webhooks.domain.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→20 modules.receiver uses modules.incoming✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in modules.incoming.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.incoming.IncomingMessagesService
- Direction
- modules.receiver uses modules.incoming, so a change to modules.incoming can break modules.receiver, while a change to modules.receiver can't break modules.incoming.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→26 modules.receiver uses modules.gateway✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.gateway.GatewayService
- Direction
- modules.receiver uses modules.gateway, so a change to modules.gateway can break modules.receiver, while a change to modules.receiver can't break modules.gateway.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→30 modules.receiver uses modules.webhooks✕
- Connections
- 1 pair of types, where a type in modules.receiver uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverService→me.capcom.smsgateway.modules.webhooks.WebHooksService
- Direction
- modules.receiver uses modules.webhooks, so a change to modules.webhooks can break modules.receiver, while a change to modules.receiver can't break modules.webhooks.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
35→31 modules.receiver uses modules.settings✕
- Connections
- 2 pairs of types, where a type in modules.receiver uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.receiver.ReceiverSettings→me.capcom.smsgateway.modules.settings.KeyValueStorageme.capcom.smsgateway.modules.receiver.StateStorage→me.capcom.smsgateway.modules.settings.KeyValueStorage
- Direction
- modules.receiver uses modules.settings, so a change to modules.settings can break modules.receiver, while a change to modules.receiver can't break modules.settings.
- Position
- Below the diagonal: modules.receiver uses a module listed above it, which is the healthy direction.
36→5 modules.gateway.inbox uses modules.notifications✕
- Connections
- 1 pair of types, where a type in modules.gateway.inbox uses a type in modules.notifications.
- The types involved
me.capcom.smsgateway.modules.gateway.inbox.InboxUploadWorker→me.capcom.smsgateway.modules.notifications.NotificationsService
- Direction
- modules.gateway.inbox uses modules.notifications, so a change to modules.notifications can break modules.gateway.inbox, while a change to modules.gateway.inbox can't break modules.notifications.
- Position
- Below the diagonal: modules.gateway.inbox uses a module listed above it, which is the healthy direction.
36→6 modules.gateway.inbox uses modules.receiver.data✕
- Connections
- 1 pair of types, where a type in modules.gateway.inbox uses a type in modules.receiver.data.
- The types involved
me.capcom.smsgateway.modules.gateway.inbox.InboxUploadService→me.capcom.smsgateway.modules.receiver.data.InboxMessage
- Direction
- modules.gateway.inbox uses modules.receiver.data, so a change to modules.receiver.data can break modules.gateway.inbox, while a change to modules.gateway.inbox can't break modules.receiver.data.
- Position
- Below the diagonal: modules.gateway.inbox uses a module listed above it, which is the healthy direction.
36→9 modules.gateway.inbox uses modules.logs✕
- Connections
- 2 pairs of types, where a type in modules.gateway.inbox uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.gateway.inbox.InboxUploadService→me.capcom.smsgateway.modules.logs.LogsServiceme.capcom.smsgateway.modules.gateway.inbox.InboxUploadWorker→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.gateway.inbox uses modules.logs, so a change to modules.logs can break modules.gateway.inbox, while a change to modules.gateway.inbox can't break modules.logs.
- Position
- Below the diagonal: modules.gateway.inbox uses a module listed above it, which is the healthy direction.
36→16 modules.gateway.inbox uses modules.gateway.GatewayApi✕
- Connections
- 1 pair of types, where a type in modules.gateway.inbox uses a type in modules.gateway.GatewayApi.
- The types involved
me.capcom.smsgateway.modules.gateway.inbox.InboxUploadWorker→me.capcom.smsgateway.modules.gateway.GatewayApi.InboxMessage
- Direction
- modules.gateway.inbox uses modules.gateway.GatewayApi, so a change to modules.gateway.GatewayApi can break modules.gateway.inbox, while a change to modules.gateway.inbox can't break modules.gateway.GatewayApi.
- Position
- Below the diagonal: modules.gateway.inbox uses a module listed above it, which is the healthy direction.
36→26 modules.gateway.inbox uses modules.gateway✕
- Connections
- 1 pair of types, where a type in modules.gateway.inbox uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.modules.gateway.inbox.InboxUploadWorker→me.capcom.smsgateway.modules.gateway.GatewayService
- Direction
- modules.gateway.inbox uses modules.gateway, so a change to modules.gateway can break modules.gateway.inbox, while a change to modules.gateway.inbox can't break modules.gateway.
- Position
- Below the diagonal: modules.gateway.inbox uses a module listed above it, which is the healthy direction.
36→34 modules.gateway.inbox uses modules.encryption✕
- Connections
- 1 pair of types, where a type in modules.gateway.inbox uses a type in modules.encryption.
- The types involved
me.capcom.smsgateway.modules.gateway.inbox.InboxUploadService→me.capcom.smsgateway.modules.encryption.EncryptionService
- Direction
- modules.gateway.inbox uses modules.encryption, so a change to modules.encryption can break modules.gateway.inbox, while a change to modules.gateway.inbox can't break modules.encryption.
- Position
- Below the diagonal: modules.gateway.inbox uses a module listed above it, which is the healthy direction.
37→9 modules.localserver.routes uses modules.logs✕
- Connections
- 2 pairs of types, where a type in modules.localserver.routes uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.AuthRoutes→me.capcom.smsgateway.modules.logs.LogsServiceme.capcom.smsgateway.modules.localserver.routes.LogsRoutes→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.localserver.routes uses modules.logs, so a change to modules.logs can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.logs.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→11 modules.localserver.routes uses modules.device✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.device.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.DeviceRoutes→me.capcom.smsgateway.modules.device.DeviceService
- Direction
- modules.localserver.routes uses modules.device, so a change to modules.device can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.device.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→17 modules.localserver.routes uses modules.mms✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.mms.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.InboxRoutes→me.capcom.smsgateway.modules.mms.MmsAttachmentStorage
- Direction
- modules.localserver.routes uses modules.mms, so a change to modules.mms can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.mms.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→20 modules.localserver.routes uses modules.incoming✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.incoming.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.InboxRoutes→me.capcom.smsgateway.modules.incoming.IncomingMessagesService
- Direction
- modules.localserver.routes uses modules.incoming, so a change to modules.incoming can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.incoming.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→23 modules.localserver.routes uses modules.localserver.auth✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.localserver.auth.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.AuthRoutes→me.capcom.smsgateway.modules.localserver.auth.JwtService
- Direction
- modules.localserver.routes uses modules.localserver.auth, so a change to modules.localserver.auth can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.localserver.auth.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→24 modules.localserver.routes uses modules.localserver.domain.messages✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.localserver.domain.messages.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.MessagesRoutesKt→me.capcom.smsgateway.modules.localserver.domain.messages.Message
- Direction
- modules.localserver.routes uses modules.localserver.domain.messages, so a change to modules.localserver.domain.messages can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.localserver.domain.messages.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→25 modules.localserver.routes uses modules.messages✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.messages.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.MessagesRoutes→me.capcom.smsgateway.modules.messages.MessagesService
- Direction
- modules.localserver.routes uses modules.messages, so a change to modules.messages can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.messages.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→29 modules.localserver.routes uses modules.localserver✕
- Connections
- 4 pairs of types, where a type in modules.localserver.routes uses a type in modules.localserver.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.DeviceRoutes→me.capcom.smsgateway.modules.localserver.LocalServerSettingsme.capcom.smsgateway.modules.localserver.routes.InboxRoutes→me.capcom.smsgateway.modules.localserver.LocalServerSettingsme.capcom.smsgateway.modules.localserver.routes.MessagesRoutes→me.capcom.smsgateway.modules.localserver.LocalServerSettingsme.capcom.smsgateway.modules.localserver.routes.WebhooksRoutes→me.capcom.smsgateway.modules.localserver.LocalServerSettings
- Direction
- modules.localserver.routes uses modules.localserver, so a change to modules.localserver can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.localserver.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→30 modules.localserver.routes uses modules.webhooks✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.WebhooksRoutes→me.capcom.smsgateway.modules.webhooks.WebHooksService
- Direction
- modules.localserver.routes uses modules.webhooks, so a change to modules.webhooks can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.webhooks.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→31 modules.localserver.routes uses modules.settings✕
- Connections
- 1 pair of types, where a type in modules.localserver.routes uses a type in modules.settings.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.SettingsRoutes→me.capcom.smsgateway.modules.settings.SettingsService
- Direction
- modules.localserver.routes uses modules.settings, so a change to modules.settings can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.settings.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
37→35 modules.localserver.routes uses modules.receiver✕
- Connections
- 2 pairs of types, where a type in modules.localserver.routes uses a type in modules.receiver.
- The types involved
me.capcom.smsgateway.modules.localserver.routes.InboxRoutes→me.capcom.smsgateway.modules.receiver.ReceiverServiceme.capcom.smsgateway.modules.localserver.routes.MessagesRoutes→me.capcom.smsgateway.modules.receiver.ReceiverService
- Direction
- modules.localserver.routes uses modules.receiver, so a change to modules.receiver can break modules.localserver.routes, while a change to modules.localserver.routes can't break modules.receiver.
- Position
- Below the diagonal: modules.localserver.routes uses a module listed above it, which is the healthy direction.
38→1 modules.orchestrator uses modules.events✕
- Connections
- 2 pairs of types, where a type in modules.orchestrator uses a type in modules.events.
- The types involved
me.capcom.smsgateway.modules.orchestrator.EventsRouter→me.capcom.smsgateway.modules.events.EventBusme.capcom.smsgateway.modules.orchestrator.EventsRouter→me.capcom.smsgateway.modules.events.ExternalEvent
- Direction
- modules.orchestrator uses modules.events, so a change to modules.events can break modules.orchestrator, while a change to modules.orchestrator can't break modules.events.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→9 modules.orchestrator uses modules.logs✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.logs.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.logs.LogsService
- Direction
- modules.orchestrator uses modules.logs, so a change to modules.logs can break modules.orchestrator, while a change to modules.orchestrator can't break modules.logs.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→11 modules.orchestrator uses modules.device✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.device.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.device.DeviceService
- Direction
- modules.orchestrator uses modules.device, so a change to modules.device can break modules.orchestrator, while a change to modules.orchestrator can't break modules.device.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→15 modules.orchestrator uses helpers✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in helpers.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.helpers.SettingsHelper
- Direction
- modules.orchestrator uses helpers, so a change to helpers can break modules.orchestrator, while a change to modules.orchestrator can't break helpers.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→20 modules.orchestrator uses modules.incoming✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.incoming.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.incoming.IncomingMessagesService
- Direction
- modules.orchestrator uses modules.incoming, so a change to modules.incoming can break modules.orchestrator, while a change to modules.orchestrator can't break modules.incoming.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→25 modules.orchestrator uses modules.messages✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.messages.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.messages.MessagesService
- Direction
- modules.orchestrator uses modules.messages, so a change to modules.messages can break modules.orchestrator, while a change to modules.orchestrator can't break modules.messages.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→26 modules.orchestrator uses modules.gateway✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.gateway.GatewayService
- Direction
- modules.orchestrator uses modules.gateway, so a change to modules.gateway can break modules.orchestrator, while a change to modules.orchestrator can't break modules.gateway.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→29 modules.orchestrator uses modules.localserver✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.localserver.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.localserver.LocalServerService
- Direction
- modules.orchestrator uses modules.localserver, so a change to modules.localserver can break modules.orchestrator, while a change to modules.orchestrator can't break modules.localserver.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→30 modules.orchestrator uses modules.webhooks✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.webhooks.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.webhooks.WebHooksService
- Direction
- modules.orchestrator uses modules.webhooks, so a change to modules.webhooks can break modules.orchestrator, while a change to modules.orchestrator can't break modules.webhooks.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
38→35 modules.orchestrator uses modules.receiver✕
- Connections
- 1 pair of types, where a type in modules.orchestrator uses a type in modules.receiver.
- The types involved
me.capcom.smsgateway.modules.orchestrator.OrchestratorService→me.capcom.smsgateway.modules.receiver.ReceiverService
- Direction
- modules.orchestrator uses modules.receiver, so a change to modules.receiver can break modules.orchestrator, while a change to modules.orchestrator can't break modules.receiver.
- Position
- Below the diagonal: modules.orchestrator uses a module listed above it, which is the healthy direction.
39→3 data uses modules.incoming.db✕
- Connections
- 1 pair of types, where a type in data uses a type in modules.incoming.db.
- The types involved
me.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.modules.incoming.db.IncomingMessagesDao
- Direction
- data uses modules.incoming.db, so a change to modules.incoming.db can break data, while a change to data can't break modules.incoming.db.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
39→4 data uses modules.logs.db✕
- Connections
- 1 pair of types, where a type in data uses a type in modules.logs.db.
- The types involved
me.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.modules.logs.db.LogEntriesDao
- Direction
- data uses modules.logs.db, so a change to modules.logs.db can break data, while a change to data can't break modules.logs.db.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
39→18 data uses modules.webhooks.db✕
- Connections
- 2 pairs of types, where a type in data uses a type in modules.webhooks.db.
- The types involved
me.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.modules.webhooks.db.WebHooksDaome.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.modules.webhooks.db.WebhookQueueDao
- Direction
- data uses modules.webhooks.db, so a change to modules.webhooks.db can break data, while a change to data can't break modules.webhooks.db.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
39→19 data uses data.dao✕
- Connections
- 2 pairs of types, where a type in data uses a type in data.dao.
- The types involved
me.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.data.dao.MessagesDaome.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.data.dao.TokensDao
- Direction
- data uses data.dao, so a change to data.dao can break data, while a change to data can't break data.dao.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
39→36 data uses modules.gateway.inbox✕
- Connections
- 1 pair of types, where a type in data uses a type in modules.gateway.inbox.
- The types involved
me.capcom.smsgateway.data.AppDatabase→me.capcom.smsgateway.modules.gateway.inbox.InboxUploadDao
- Direction
- data uses modules.gateway.inbox, so a change to modules.gateway.inbox can break data, while a change to data can't break modules.gateway.inbox.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
40→1 ui uses modules.events✕
- Connections
- 1 pair of types, where a type in ui uses a type in modules.events.
- The types involved
me.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.events.EventBus
- Direction
- ui uses modules.events, so a change to modules.events can break ui, while a change to ui can't break modules.events.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→8 ui uses modules.connection✕
- Connections
- 1 pair of types, where a type in ui uses a type in modules.connection.
- The types involved
me.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.connection.ConnectionService
- Direction
- ui uses modules.connection, so a change to modules.connection can break ui, while a change to ui can't break modules.connection.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→14 ui uses data.entities✕
- Connections
- 1 pair of types, where a type in ui uses a type in data.entities.
- The types involved
me.capcom.smsgateway.ui.MessagesListFragment→me.capcom.smsgateway.data.entities.Message
- Direction
- ui uses data.entities, so a change to data.entities can break ui, while a change to ui can't break data.entities.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→15 ui uses helpers✕
- Connections
- 1 pair of types, where a type in ui uses a type in helpers.
- The types involved
me.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.helpers.SettingsHelper
- Direction
- ui uses helpers, so a change to helpers can break ui, while a change to ui can't break helpers.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→22 ui uses ui.adapters✕
- Connections
- 4 pairs of types, where a type in ui uses a type in ui.adapters.
- The types involved
me.capcom.smsgateway.ui.IncomingMessagesListFragment→me.capcom.smsgateway.ui.adapters.IncomingMessagesAdapterme.capcom.smsgateway.ui.LogsListFragment→me.capcom.smsgateway.ui.adapters.LogItemsAdapterme.capcom.smsgateway.ui.MessageDetailsFragment→me.capcom.smsgateway.ui.adapters.MessageRecipientsAdapterme.capcom.smsgateway.ui.MessagesListFragment→me.capcom.smsgateway.ui.adapters.MessagesAdapter
- Direction
- ui uses ui.adapters, so a change to ui.adapters can break ui, while a change to ui can't break ui.adapters.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→26 ui uses modules.gateway✕
- Connections
- 2 pairs of types, where a type in ui uses a type in modules.gateway.
- The types involved
me.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.gateway.GatewayServiceme.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.gateway.GatewaySettings
- Direction
- ui uses modules.gateway, so a change to modules.gateway can break ui, while a change to ui can't break modules.gateway.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→28 ui uses modules.messages.vm✕
- Connections
- 2 pairs of types, where a type in ui uses a type in modules.messages.vm.
- The types involved
me.capcom.smsgateway.ui.MessageDetailsFragment→me.capcom.smsgateway.modules.messages.vm.MessageDetailsViewModelme.capcom.smsgateway.ui.MessagesListFragment→me.capcom.smsgateway.modules.messages.vm.MessagesListViewModel
- Direction
- ui uses modules.messages.vm, so a change to modules.messages.vm can break ui, while a change to ui can't break modules.messages.vm.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→29 ui uses modules.localserver✕
- Connections
- 2 pairs of types, where a type in ui uses a type in modules.localserver.
- The types involved
me.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.localserver.LocalServerServiceme.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.localserver.LocalServerSettings
- Direction
- ui uses modules.localserver, so a change to modules.localserver can break ui, while a change to ui can't break modules.localserver.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
40→38 ui uses modules.orchestrator✕
- Connections
- 1 pair of types, where a type in ui uses a type in modules.orchestrator.
- The types involved
me.capcom.smsgateway.ui.HomeFragment→me.capcom.smsgateway.modules.orchestrator.OrchestratorService
- Direction
- ui uses modules.orchestrator, so a change to modules.orchestrator can break ui, while a change to ui can't break modules.orchestrator.
- Position
- Below the diagonal: ui 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 |
|---|---|---|
| A05:2025 — Injection | 32 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Adopt pino (or winston) and log at meaningful points in the services you run; Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +6.8 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +3.3 pts | Low | ADR Quality |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +5.5 pts | Medium | Observability |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +3.6 pts | Medium | Outbound HTTP resilience |
| 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. | +2.9 pts | Medium | Architecture documentation |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +1.5 pts | Medium | Constructible invalid state |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +1.5 pts | Medium | Strongly-typed ids |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java | 7.0 | Mixed | Cyclomatic Complexity: PduParser.parseHeaders (cyclomatic 159) |
| app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java | 7.0 | Mixed | Cyclomatic Complexity: PduComposer.appendHeader (cyclomatic 37) |
| app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java | 7.1 | Mixed | Cyclomatic Complexity: PduHeaders.setOctet (cyclomatic 66) |
| app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt | 7.1 | Mixed | Code Duplication: Edited copy of a member (42 corresponding lines) |
| app/src/main/java/me/capcom/smsgateway/ui/IncomingMessagesListFragment.kt | 7.2 | Mixed | Cyclomatic Complexity: IncomingMessagesListFragment.onViewCreated (cyclomatic 25) |
| app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt | 7.2 | Mixed | Cyclomatic Complexity: InboxRoutes.inboxRoutes (cyclomatic 22) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/EncodedStringValue.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt | 7.4 | Mixed | Cyclomatic Complexity: MessagesRoutes.messagesRoutes (cyclomatic 20) |
| app/src/main/java/me/capcom/smsgateway/ui/MessagesListFragment.kt | 7.8 | Mixed | Cyclomatic Complexity: MessagesListFragment.onViewCreated (cyclomatic 33) |
| app/src/main/java/me/capcom/smsgateway/modules/gateway/EventsReceiver.kt | 7.8 | Mixed | Cyclomatic Complexity: EventsReceiver.collect (cyclomatic 28) |
| app/src/main/java/me/capcom/smsgateway/ui/settings/WebhookQueueListFragment.kt | 7.8 | Mixed | Cyclomatic Complexity: WebhookQueueListFragment.onViewCreated (cyclomatic 28) |
| app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesSettings.kt | 7.8 | Mixed | Cyclomatic Complexity: MessagesSettings.import (cyclomatic 23) |
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 52 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 — 52 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, 157 of 287 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
- D8 Code Coverage — 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. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — 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. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- 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-maintainer repository — bus factor is not applicable (3 contributor(s) across 435 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 2 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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: 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — 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. `app` (21228 LoC, 565 module-visible types across 74 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 464 sampled here came from .kt files. This repository's .java source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D32 Data Compliance (PII/GDPR) — 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. `app/src/main/assets/api/swagger-ui-standalone-preset.js`, `app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadEntity.kt`, `app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — 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. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — 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. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: it. Searched Location: app/src/debug/google-services.json app/src/google-services.jso…; runtime evidence skipped (launch chosen because app/build.gradle applies the Android application plugin and gradlew builds it).
- 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.
- DM8 Value-object opportunities — 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. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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. The frontend declares that it computes whether a construction is produced or passed, yet 280 of 380 constructions arrived without the answer. Arm two skipped them; it did not clear them.
- GD1 Unfinished & placeholder code — 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. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — 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. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- X1 Async correctness — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X12 Unreachable branch — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
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.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- 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.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PduParser.parseHeaders at 159. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being MessagesService.resultToErrorMessage at 59 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with PduParser.parseHeaders (cyclomatic 159), PduHeaders.setOctet (cyclomatic 66). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.4 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was PduParser.parseHeaders at 263.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with PduParser.parseHeaders (cognitive 263). — Refactoring it lifts Cognitive Complexity from 5.8 to about 6.6/10.
D3 · God Classes
14 god class(es) detected.
What to do
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with PduComposer.java (2), PduParser.java, MessagesRoutes.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 ClassTooLong finding(s) in God Classes — start with PduParser.java, PduComposer.java, MessagesService.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with PduParser.java, PduComposer.java, MessagesService.kt. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
12 duplicated block group(s) detected. A further 14 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with MmsContentObserver.kt (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copies of one member (3 members, 16+ corresponding lines) finding(s) in Code Duplication — start with IncomingMessagesSettings.kt, InboxUploadWorker.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with IncomingMessagesListFragment.kt, MessagesReceiver.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
2 production modules (Gradle), 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 1 of the 2 (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 68 classes have LCOM4 above 3.
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 236 artifact(s) resolved, 132 of them gradable against Maven Central, and 123 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 21 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 12 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt (7×16=112); app/src/main/java/me/capcom/smsgateway/modules/gateway/EventsReceiver.kt (3×28=84); app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt (4×20=80)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with MessagesService.kt, EventsReceiver.kt, MessagesRoutes.kt. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
4 deducted task-comment markers across 21228 LoC (0.0/KLoC) → score 10.0. 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 3 TodoComment finding(s) in Explicit Debt — start with EncodedStringValue.java (2), MessagesService.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with SendReq.java. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 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 — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
55 % of calls cross a namespace and 22 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .kt source only — this repository's .java was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
32 finding(s): 0 critical, 29 high, 3 medium, 0 low. 21 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `app/src/main/assets/api/swagger-ui-standalone-preset.js`, `gradlew` (line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 21 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (21 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 90 of the 266 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: GatewayService.kt↔RegistrationWorker.kt 83%; PostMessageRequest.kt↔MessagesService.kt 80%; GatewayService.kt↔PostMessageRequest.kt 80%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with GatewayService.kt, AppDatabase.kt, RegistrationWorker.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with PostMessageRequest.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 37 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
AX3 · Project dependency cycles
AX4 · Dependency direction
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Message`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Message` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/data/entities/Message.kt:55
- `MessageRecipient`'s public constructor takes `messageId`, `phoneNumber`, `error` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MessageRecipient` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/data/entities/MessageRecipient.kt:12
- `MessageState`'s public constructor takes `messageId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MessageState` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/data/entities/MessageState.kt:17
- `RecipientState`'s public constructor takes `messageId`, `phoneNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `RecipientState` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/data/entities/RecipientState.kt:17
- `Token`'s public constructor takes `id`, `tokenUse`, `parentJti` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Token` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/data/entities/Token.kt:16
- `DeviceKey`'s public constructor takes `publicKeyBase64` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `DeviceKey` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/modules/device/db/DeviceKey.kt:15
- `InboxUploadEntity`'s public constructor takes `messageId`, `type`, `senderEncrypted`, `recipientEncrypted`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `InboxUploadEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadEntity.kt:14
- `IncomingMessage`'s public constructor takes `id`, `sender`, `recipient`, `contentPreview` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `IncomingMessage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/modules/incoming/db/IncomingMessage.kt:21
- `LogEntry`'s public constructor takes `module`, `message` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `LogEntry` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/modules/logs/db/LogEntry.kt:9
- `WebHook`'s public constructor takes `id`, `url` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WebHook` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/modules/webhooks/db/WebHook.kt:9
- `WebhookQueueEntity`'s public constructor takes `id`, `url`, `payload`, `lastError` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WebhookQueueEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/me/capcom/smsgateway/modules/webhooks/db/WebhookQueueEntity.kt:20
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `MessageRecipient.messageId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — app/src/main/java/me/capcom/smsgateway/data/entities/MessageRecipient.kt:13
- `MessageState.messageId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — app/src/main/java/me/capcom/smsgateway/data/entities/MessageState.kt:18
- `RecipientState.messageId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — app/src/main/java/me/capcom/smsgateway/data/entities/RecipientState.kt:18
- `IncomingMessage.subscriptionId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — app/src/main/java/me/capcom/smsgateway/modules/incoming/db/IncomingMessage.kt:27
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `Message` is an aggregate/entity with 18 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/data/entities/Message.kt:26
- `MessageRecipient` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/data/entities/MessageRecipient.kt:12
- `MessageState` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/data/entities/MessageState.kt:17
- `RecipientState` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/data/entities/RecipientState.kt:17
- `Token` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/data/entities/Token.kt:16
- `DeviceKey` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/modules/device/db/DeviceKey.kt:15
- `IncomingMessage` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/modules/incoming/db/IncomingMessage.kt:21
- `WebHook` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/me/capcom/smsgateway/modules/webhooks/db/WebHook.kt:9
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
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.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- No logging call was found in the 264 JavaScript/TypeScript, JVM production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 8 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. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — 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.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `HttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app/src/main/java/me/capcom/smsgateway/modules/gateway/GatewayApi.kt:36
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X2 · Cancellation propagation
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (e: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/me/capcom/smsgateway/services/PushService.kt:101
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:139, app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:150, app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:163, …
- 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. (×2) — app/src/main/java/me/capcom/smsgateway/modules/ping/services/PingForegroundService.kt:62, app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadWorker.kt:74
- `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:1081
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:896
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/me/capcom/smsgateway/helpers/DateTimeParser.kt:28
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by P2, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 53% | Adequate — gated by DM2, DM4, DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model 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. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no public interfaces
- 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.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: it. Searched Location: app/src/debug/google-services.json app/src/google-services.jso…; runtime evidence skipped (launch chosen because app/build.gradle applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- 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 — ~3060 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D16 Bus Factor — single-maintainer 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 does not read html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model 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. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 14 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 12); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- 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.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 29 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
Serious — 122 finding(s)
- Constructible in an invalid state: Message app/src/main/java/me/capcom/smsgateway/data/entities/Message.kt:55
- Constructible in an invalid state: MessageRecipient app/src/main/java/me/capcom/smsgateway/data/entities/MessageRecipient.kt:12
- Constructible in an invalid state: MessageState app/src/main/java/me/capcom/smsgateway/data/entities/MessageState.kt:17
- Constructible in an invalid state: RecipientState app/src/main/java/me/capcom/smsgateway/data/entities/RecipientState.kt:17
- Constructible in an invalid state: Token app/src/main/java/me/capcom/smsgateway/data/entities/Token.kt:16
- Constructible in an invalid state: DeviceKey app/src/main/java/me/capcom/smsgateway/modules/device/db/DeviceKey.kt:15
- Constructible in an invalid state: InboxUploadEntity app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadEntity.kt:14
- Constructible in an invalid state: IncomingMessage app/src/main/java/me/capcom/smsgateway/modules/incoming/db/IncomingMessage.kt:21
- Constructible in an invalid state: LogEntry app/src/main/java/me/capcom/smsgateway/modules/logs/db/LogEntry.kt:9
- Constructible in an invalid state: WebHook app/src/main/java/me/capcom/smsgateway/modules/webhooks/db/WebHook.kt:9
- Constructible in an invalid state: WebhookQueueEntity app/src/main/java/me/capcom/smsgateway/modules/webhooks/db/WebhookQueueEntity.kt:20
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/services/PushService.kt:101
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:139
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:150
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:163
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:224
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/receiver/events/MessagesExportRequestedEvent.kt:41
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:1081
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:896
- Swallowed exception (caught, then discarded) app/src/main/java/me/capcom/smsgateway/helpers/DateTimeParser.kt:28
- Anemic entity: Message app/src/main/java/me/capcom/smsgateway/data/entities/Message.kt:26
- Anemic entity: MessageRecipient app/src/main/java/me/capcom/smsgateway/data/entities/MessageRecipient.kt:12
- Anemic entity: MessageState app/src/main/java/me/capcom/smsgateway/data/entities/MessageState.kt:17
- Anemic entity: RecipientState app/src/main/java/me/capcom/smsgateway/data/entities/RecipientState.kt:17
- Anemic entity: Token app/src/main/java/me/capcom/smsgateway/data/entities/Token.kt:16
- Anemic entity: DeviceKey app/src/main/java/me/capcom/smsgateway/modules/device/db/DeviceKey.kt:15
- Anemic entity: IncomingMessage app/src/main/java/me/capcom/smsgateway/modules/incoming/db/IncomingMessage.kt:21
- Anemic entity: WebHook app/src/main/java/me/capcom/smsgateway/modules/webhooks/db/WebHook.kt:9
- MethodTooLong: PduParser.parseHeaders app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:109
- MethodTooLong: MessagesRoutes.messagesRoutes app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt:54
- MethodTooLong: InboxRoutes.inboxRoutes app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt:39
- MethodTooLong: PduComposer.appendHeader app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:544
- MethodTooLong: PduComposer.makeMessageBody app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:919
- MethodTooLong: HomeFragment.onViewCreated app/src/main/java/me/capcom/smsgateway/ui/HomeFragment.kt:158
- MethodTooLong: PduHeaders.setOctet app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java:358
- ClassTooLong: PduParser app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:30
- ClassTooLong: PduComposer app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:31
- ClassTooLong: MessagesService app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt:46
- ClassTooLong: PduHeaders app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java:25
- Change coupling: GatewayService.kt ↔ RegistrationWorker.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/GatewayService.kt:1
- Change coupling: AppDatabase.kt ↔ MessagesService.kt app/src/main/java/me/capcom/smsgateway/data/AppDatabase.kt:1
- Change coupling: RegistrationWorker.kt ↔ HomeFragment.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/workers/RegistrationWorker.kt:1
- Change coupling: PullMessagesWorker.kt ↔ PushService.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/workers/PullMessagesWorker.kt:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt:174
- Hotspot: app/src/main/java/me/capcom/smsgateway/modules/gateway/EventsReceiver.kt app/src/main/java/me/capcom/smsgateway/modules/gateway/EventsReceiver.kt:31
- Hotspot: app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt:54
- TodoComment app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/EncodedStringValue.java:53
- TodoComment app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/EncodedStringValue.java:154
- TodoComment app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt:49
- FileTooLong: aosp/PduParser.java app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java
- FileTooLong: aosp/PduComposer.java app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java
- FileTooLong: messages/MessagesService.kt app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt
- Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt:45
- Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt:119
- Duplicated block (12 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt:84
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 16+ corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/incoming/IncomingMessagesSettings.kt:20
- Edited copies of one member (3 members, 16+ corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadWorker.kt:45
- Duplicated block (7 lines × 2) app/src/main/java/me/capcom/smsgateway/ui/IncomingMessagesListFragment.kt:86
- Duplicated block (7 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/receiver/MessagesReceiver.kt:116
- Swallowed exception (empty catch) app/src/main/java/me/capcom/smsgateway/modules/ping/services/PingForegroundService.kt:62
- Swallowed exception (empty catch) app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadWorker.kt:74
- PduParser.parseHeaders (cyclomatic 159) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:109
- PduHeaders.setOctet (cyclomatic 66) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java:358
- PduComposer.appendHeader (cyclomatic 37) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:544
- MessagesListFragment.onViewCreated (cyclomatic 33) app/src/main/java/me/capcom/smsgateway/ui/MessagesListFragment.kt:37
- EventsReceiver.collect (cyclomatic 28) app/src/main/java/me/capcom/smsgateway/modules/gateway/EventsReceiver.kt:31
- WebhookQueueListFragment.onViewCreated (cyclomatic 28) app/src/main/java/me/capcom/smsgateway/ui/settings/WebhookQueueListFragment.kt:39
- PduComposer.makeMessageBody (cyclomatic 28) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:919
- PduParser.parseContentTypeParams (cyclomatic 28) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:1233
- IncomingMessagesListFragment.onViewCreated (cyclomatic 25) app/src/main/java/me/capcom/smsgateway/ui/IncomingMessagesListFragment.kt:34
- MessagesSettings.import (cyclomatic 23) app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesSettings.kt:188
- InboxRoutes.inboxRoutes (cyclomatic 22) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt:39
- MessagesRoutes.messagesRoutes (cyclomatic 20) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt:54
- SSEManager.connect (cyclomatic 16) app/src/main/java/me/capcom/smsgateway/helpers/SSEManager.kt:53
- MessagesService.processStateIntent (cyclomatic 16) app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt:174
- FixmeComment app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/SendReq.java:31
- PduParser.parseHeaders (cognitive 263) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:109
- PduComposer.makeMessageBody (cognitive 61) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:919
- PduParser.parseContentTypeParams (cognitive 60) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:1233
- PduHeaders.setOctet (cognitive 56) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java:358
- WebhookQueueListFragment.onViewCreated (cognitive 41) app/src/main/java/me/capcom/smsgateway/ui/settings/WebhookQueueListFragment.kt:39
- PduComposer.appendHeader (cognitive 36) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:544
- MessagesListFragment.onViewCreated (cognitive 35) app/src/main/java/me/capcom/smsgateway/ui/MessagesListFragment.kt:37
- MessagesService.processStateIntent (cognitive 30) app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt:174
- EventsReceiver.collect (cognitive 28) app/src/main/java/me/capcom/smsgateway/modules/gateway/EventsReceiver.kt:31
- IncomingMessagesListFragment.onViewCreated (cognitive 27) app/src/main/java/me/capcom/smsgateway/ui/IncomingMessagesListFragment.kt:34
- InboxRoutes.inboxRoutes (cognitive 24) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt:39
- MessagesSettings.import (cognitive 22) app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesSettings.kt:188
- PduParser.parseContentType (cognitive 18) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduParser.java:1422
- MessagesRoutes.messagesRoutes (cognitive 17) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/MessagesRoutes.kt:54
- SSEManager.connect (cognitive 16) app/src/main/java/me/capcom/smsgateway/helpers/SSEManager.kt:53
- REDACTED
- Change-coupling hub: PostMessageRequest.kt → AppDatabase.kt, GatewayService.kt, WebService.kt, MessagesService.kt app/src/main/java/me/capcom/smsgateway/modules/localserver/domain/messages/PostMessageRequest.kt
- REDACTED
- REDACTED
- Edited copy of a member (42 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt:25
- Edited copy of a member (24 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentObserver.kt:75
- Edited copy of a member (30 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduComposer.java:716
- Edited copy of a member (16 corresponding lines) app/src/main/java/me/capcom/smsgateway/ui/settings/CloudServerSettingsFragment.kt:233
- Edited copies of one member (3 members, 19+ corresponding lines) app/src/main/java/me/capcom/smsgateway/ui/SettingsFragment.kt:50
- Edited copy of a member (22 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java:618
- Edited copy of a member (15 corresponding lines) app/src/main/java/me/capcom/smsgateway/ui/HolderFragment.kt:73
- Edited copy of a member (27 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/mms/pdu/aosp/PduHeaders.java:515
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/device/DeviceSettings.kt:33
- Edited copy of a member (11 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsReceiver.kt:133
- Edited copy of a member (10 corresponding lines) app/src/main/java/me/capcom/smsgateway/modules/receiver/MmsContentReader.kt:157
- Edited copies of one member (4 members, 13+ corresponding lines) app/src/main/java/me/capcom/smsgateway/helpers/SubscriptionsHelper.kt:22
- Duplicated block (21 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/gateway/workers/SettingsUpdateWorker.kt:44
- Duplicated block (18–20 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt:108
- Duplicated block (9 lines × 2) app/src/main/java/me/capcom/smsgateway/ui/IncomingMessagesListFragment.kt:38
- Duplicated block (15 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/incoming/vm/IncomingMessagesListViewModel.kt:38
- Duplicated block (16 lines × 4) app/src/main/java/me/capcom/smsgateway/modules/device/workers/KeyRotationWorker.kt:43
- Duplicated block (9 lines × 3) app/src/main/java/me/capcom/smsgateway/modules/gateway/services/SSEForegroundService.kt:150
- Duplicated block (10 lines × 2) app/src/main/java/me/capcom/smsgateway/modules/messages/workers/SendMessagesWorker.kt:66
- No structured logging
- Outbound HTTP without resilience app/src/main/java/me/capcom/smsgateway/modules/gateway/GatewayApi.kt:36
Minor — 13 finding(s)
- Primitive id on a domain type: MessageRecipient.messageId app/src/main/java/me/capcom/smsgateway/data/entities/MessageRecipient.kt:13
- Primitive id on a domain type: MessageState.messageId app/src/main/java/me/capcom/smsgateway/data/entities/MessageState.kt:18
- Primitive id on a domain type: RecipientState.messageId app/src/main/java/me/capcom/smsgateway/data/entities/RecipientState.kt:18
- Primitive id on a domain type: IncomingMessage.subscriptionId app/src/main/java/me/capcom/smsgateway/modules/incoming/db/IncomingMessage.kt:27
- Duplicated predicate app/src/main/java/me/capcom/smsgateway/modules/incoming/vm/IncomingMessagesListViewModel.kt:40
- Duplicated predicate app/src/main/java/me/capcom/smsgateway/modules/localserver/routes/InboxRoutes.kt:109
- No ADRs found app/build.gradle:2
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
Minor — 123 finding(s)
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): com.google.auto:auto-common
- Outdated (compile): com.google.auto.value:auto-value-annotations
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-metadata-jvm
- Outdated (compile): com.google.devtools.ksp:symbol-processing-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.squareup:kotlinpoet
- Outdated (compile): org.jetbrains.kotlin:kotlin-reflect
- Outdated (compile): org.xerial:sqlite-jdbc
- Outdated (compile): commons-codec:commons-codec
- Outdated (compile): junit:junit
- Outdated (compile): org.hamcrest:hamcrest-core
- Outdated (compile): com.squareup:javawriter
- Outdated (compile): org.hamcrest:hamcrest-library
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-android
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
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-90a57d3ff5ce439e84dbf9e2c122d5aa/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-90a57d3ff5ce439e84dbf9e2c122d5aa/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 . | 32 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| 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. semgrep could not parse 3 file(s) — `app/src/main/assets/api/swagger-ui-standalone-preset.js`, `app/src/main/java/me/capcom/smsgateway/modules/gateway/inbox/InboxUploadEntity.kt`, `app/src/main/java/me/capcom/smsgateway/modules/messages/MessagesService.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |