Executive summary
chartmann1590/LiveTranscribe-Android falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 64.8 out of 100 and is rated Adequate, and all 40 of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 56.0, is the weakest lens and counts most in the score. The best first step is adopting a logging library, worth about 6.9 points. Adding automated security scanning comes next, worth about 6.1 points. Raising Production Readiness to 70 would lift the score to about 70.7.
Thirty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and four secrets can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 11,847 lines, about €16,000 to rebuild.
If Production Readiness rose from 56.0 to 70, the lowest score rated Strong, the score would rise from 64.8 to about 70.7.
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,200 to €26,000, for 87 to 276 hours of work, about 0.1 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.9 at a score of 65. 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 | Small: 11,847 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 cloudflare-worker-feedback.src | 2 com.charles.livecaptionn.compatibility | 3 com.charles.livecaptionn.data.feedback | 4 com.charles.livecaptionn.service.CaptionForegroundService | 5 com.charles.livecaptionn.settings | 6 com.charles.livecaptionn.speech.VoskModelCatalog | 7 com.charles.livecaptionn.speech.VoskStreamingSession | 8 cloudflare-worker-feedback | 9 com.charles.livecaptionn.compatibility.CompatibilityTier | 10 com.charles.livecaptionn.data | 11 com.charles.livecaptionn.settings.AudioSource | 12 com.charles.livecaptionn.settings.Language | 13 com.charles.livecaptionn.settings.SttBackend | 14 com.charles.livecaptionn.settings.TranslationBackend | 15 com.charles.livecaptionn.speech | 16 com.charles.livecaptionn.ui.feedback | 17 com.charles.livecaptionn.ui.feedback.FeedbackViewModel | 18 com.charles.livecaptionn.ui.l10n.UiLocalizationRepository | 19 com.charles.livecaptionn.billing | 20 com.charles.livecaptionn.speech.ModelQuality | 21 com.charles.livecaptionn.speech.RecognitionStatus | 22 com.charles.livecaptionn.speech.VoskSource | 23 com.charles.livecaptionn.translation | 24 com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage | 25 com.charles.livecaptionn.ads | 26 com.charles.livecaptionn.billing.Entitlement | 27 com.charles.livecaptionn.billing.ManageAction | 28 com.charles.livecaptionn.billing.PremiumProduct | 29 com.charles.livecaptionn.billing.PremiumState | 30 com.charles.livecaptionn.billing.PurchaseFlowResult | 31 com.charles.livecaptionn.ui.l10n | 32 com.charles.livecaptionn.ui.premium | 33 com.charles.livecaptionn.ui.premium.PremiumViewModel | 34 com.charles.livecaptionn.overlay | 35 com.charles.livecaptionn.ui.l10n.UiStrings | 36 com.charles.livecaptionn.update | 37 com.charles.livecaptionn.service | 38 com.charles.livecaptionn.di | 39 com.charles.livecaptionn | 40 com.charles.livecaptionn.ui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cloudflare-worker-feedback.src | ||||||||||||||||||||||||||||||||||||||||
| 2 com.charles.livecaptionn.compatibility | ||||||||||||||||||||||||||||||||||||||||
| 3 com.charles.livecaptionn.data.feedback | ||||||||||||||||||||||||||||||||||||||||
| 4 com.charles.livecaptionn.service.CaptionForegroundService | ||||||||||||||||||||||||||||||||||||||||
| 5 com.charles.livecaptionn.settings | ||||||||||||||||||||||||||||||||||||||||
| 6 com.charles.livecaptionn.speech.VoskModelCatalog | ||||||||||||||||||||||||||||||||||||||||
| 7 com.charles.livecaptionn.speech.VoskStreamingSession | ||||||||||||||||||||||||||||||||||||||||
| 8 cloudflare-worker-feedback | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 com.charles.livecaptionn.compatibility.CompatibilityTier | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 com.charles.livecaptionn.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 com.charles.livecaptionn.settings.AudioSource | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 com.charles.livecaptionn.settings.Language | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 com.charles.livecaptionn.settings.SttBackend | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 com.charles.livecaptionn.settings.TranslationBackend | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 com.charles.livecaptionn.speech | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 com.charles.livecaptionn.ui.feedback | 7 | |||||||||||||||||||||||||||||||||||||||
| 17 com.charles.livecaptionn.ui.feedback.FeedbackViewModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 com.charles.livecaptionn.ui.l10n.UiLocalizationRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 com.charles.livecaptionn.billing | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 com.charles.livecaptionn.speech.ModelQuality | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 com.charles.livecaptionn.speech.RecognitionStatus | 5 | |||||||||||||||||||||||||||||||||||||||
| 22 com.charles.livecaptionn.speech.VoskSource | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 com.charles.livecaptionn.translation | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 24 com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 com.charles.livecaptionn.ads | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 com.charles.livecaptionn.billing.Entitlement | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 com.charles.livecaptionn.billing.ManageAction | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 com.charles.livecaptionn.billing.PremiumProduct | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 com.charles.livecaptionn.billing.PremiumState | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 com.charles.livecaptionn.billing.PurchaseFlowResult | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 com.charles.livecaptionn.ui.l10n | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 com.charles.livecaptionn.ui.premium | 4 | |||||||||||||||||||||||||||||||||||||||
| 33 com.charles.livecaptionn.ui.premium.PremiumViewModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 com.charles.livecaptionn.overlay | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 com.charles.livecaptionn.ui.l10n.UiStrings | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 com.charles.livecaptionn.update | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 com.charles.livecaptionn.service | 1 | 2 | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 38 com.charles.livecaptionn.di | 1 | 6 | 2 | 2 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 39 com.charles.livecaptionn | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 com.charles.livecaptionn.ui | 5 | 8 | 6 | 4 | 2 | 1 | 3 | 1 | 2 |
8→1 cloudflare-worker-feedback uses cloudflare-worker-feedback.src✕
- Connections
- 1 pair of types, where a type in cloudflare-worker-feedback uses a type in cloudflare-worker-feedback.src.
- The types involved
cloudflare-worker-feedback.index→cloudflare-worker-feedback.src.Env
- Direction
- cloudflare-worker-feedback uses cloudflare-worker-feedback.src, so a change to cloudflare-worker-feedback.src can break cloudflare-worker-feedback, while a change to cloudflare-worker-feedback can't break cloudflare-worker-feedback.src.
- Position
- Below the diagonal: cloudflare-worker-feedback uses a module listed above it, which is the healthy direction.
9→2 com.charles.livecaptionn.compatibility.CompatibilityTier uses com.charles.livecaptionn.compatibility✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.compatibility.CompatibilityTier uses a type in com.charles.livecaptionn.compatibility.
- The types involved
com.charles.livecaptionn.compatibility.CompatibilityTier.BORDERLINE→com.charles.livecaptionn.compatibility.CompatibilityTiercom.charles.livecaptionn.compatibility.CompatibilityTier.PASSED→com.charles.livecaptionn.compatibility.CompatibilityTiercom.charles.livecaptionn.compatibility.CompatibilityTier.UNSUPPORTED→com.charles.livecaptionn.compatibility.CompatibilityTier
- Direction
- com.charles.livecaptionn.compatibility.CompatibilityTier uses com.charles.livecaptionn.compatibility, so a change to com.charles.livecaptionn.compatibility can break com.charles.livecaptionn.compatibility.CompatibilityTier, while a change to com.charles.livecaptionn.compatibility.CompatibilityTier can't break com.charles.livecaptionn.compatibility.
- Position
- Below the diagonal: com.charles.livecaptionn.compatibility.CompatibilityTier uses a module listed above it, which is the healthy direction.
10→5 com.charles.livecaptionn.data uses com.charles.livecaptionn.settings✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.data uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.data.SettingsDataStore→com.charles.livecaptionn.settings.CaptionSettingscom.charles.livecaptionn.data.SettingsRepository→com.charles.livecaptionn.settings.CaptionSettings
- Direction
- com.charles.livecaptionn.data uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.data, while a change to com.charles.livecaptionn.data can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.data uses a module listed above it, which is the healthy direction.
10→19 com.charles.livecaptionn.data uses com.charles.livecaptionn.billing part of a loop✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.data uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.data.PremiumLocalStore→com.charles.livecaptionn.billing.PremiumState
- Direction
- com.charles.livecaptionn.data uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.data, while a change to com.charles.livecaptionn.data can't break com.charles.livecaptionn.billing.
- 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.
11→5 com.charles.livecaptionn.settings.AudioSource uses com.charles.livecaptionn.settings✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.settings.AudioSource uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.settings.AudioSource.Companion→com.charles.livecaptionn.settings.AudioSourcecom.charles.livecaptionn.settings.AudioSource.MIC→com.charles.livecaptionn.settings.AudioSourcecom.charles.livecaptionn.settings.AudioSource.SYSTEM→com.charles.livecaptionn.settings.AudioSource
- Direction
- com.charles.livecaptionn.settings.AudioSource uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.settings.AudioSource, while a change to com.charles.livecaptionn.settings.AudioSource can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.settings.AudioSource uses a module listed above it, which is the healthy direction.
12→5 com.charles.livecaptionn.settings.Language uses com.charles.livecaptionn.settings✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.settings.Language uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.settings.Language.Companion→com.charles.livecaptionn.settings.Language
- Direction
- com.charles.livecaptionn.settings.Language uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.settings.Language, while a change to com.charles.livecaptionn.settings.Language can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.settings.Language uses a module listed above it, which is the healthy direction.
13→5 com.charles.livecaptionn.settings.SttBackend uses com.charles.livecaptionn.settings✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.settings.SttBackend uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.settings.SttBackend.Companion→com.charles.livecaptionn.settings.SttBackendcom.charles.livecaptionn.settings.SttBackend.LOCAL_VOSK→com.charles.livecaptionn.settings.SttBackendcom.charles.livecaptionn.settings.SttBackend.REMOTE_WHISPER→com.charles.livecaptionn.settings.SttBackend
- Direction
- com.charles.livecaptionn.settings.SttBackend uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.settings.SttBackend, while a change to com.charles.livecaptionn.settings.SttBackend can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.settings.SttBackend uses a module listed above it, which is the healthy direction.
14→5 com.charles.livecaptionn.settings.TranslationBackend uses com.charles.livecaptionn.settings✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.settings.TranslationBackend uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.settings.TranslationBackend.Companion→com.charles.livecaptionn.settings.TranslationBackendcom.charles.livecaptionn.settings.TranslationBackend.LIBRE_TRANSLATE→com.charles.livecaptionn.settings.TranslationBackendcom.charles.livecaptionn.settings.TranslationBackend.ML_KIT→com.charles.livecaptionn.settings.TranslationBackend
- Direction
- com.charles.livecaptionn.settings.TranslationBackend uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.settings.TranslationBackend, while a change to com.charles.livecaptionn.settings.TranslationBackend can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.settings.TranslationBackend uses a module listed above it, which is the healthy direction.
15→5 com.charles.livecaptionn.speech uses com.charles.livecaptionn.settings✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.speech uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.speech.StreamingSttEngine→com.charles.livecaptionn.settings.AudioSourcecom.charles.livecaptionn.speech.SystemAudioEngine→com.charles.livecaptionn.settings.SttBackend
- Direction
- com.charles.livecaptionn.speech uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.speech, while a change to com.charles.livecaptionn.speech can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.speech uses a module listed above it, which is the healthy direction.
15→6 com.charles.livecaptionn.speech uses com.charles.livecaptionn.speech.VoskModelCatalog✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.speech uses a type in com.charles.livecaptionn.speech.VoskModelCatalog.
- The types involved
com.charles.livecaptionn.speech.VoskModelCatalog→com.charles.livecaptionn.speech.VoskModelCatalog.BundledModel
- Direction
- com.charles.livecaptionn.speech uses com.charles.livecaptionn.speech.VoskModelCatalog, so a change to com.charles.livecaptionn.speech.VoskModelCatalog can break com.charles.livecaptionn.speech, while a change to com.charles.livecaptionn.speech can't break com.charles.livecaptionn.speech.VoskModelCatalog.
- Position
- Below the diagonal: com.charles.livecaptionn.speech uses a module listed above it, which is the healthy direction.
15→7 com.charles.livecaptionn.speech uses com.charles.livecaptionn.speech.VoskStreamingSession✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.speech uses a type in com.charles.livecaptionn.speech.VoskStreamingSession.
- The types involved
com.charles.livecaptionn.speech.VoskStreamingSession→com.charles.livecaptionn.speech.VoskStreamingSession.FeedResult
- Direction
- com.charles.livecaptionn.speech uses com.charles.livecaptionn.speech.VoskStreamingSession, so a change to com.charles.livecaptionn.speech.VoskStreamingSession can break com.charles.livecaptionn.speech, while a change to com.charles.livecaptionn.speech can't break com.charles.livecaptionn.speech.VoskStreamingSession.
- Position
- Below the diagonal: com.charles.livecaptionn.speech uses a module listed above it, which is the healthy direction.
16→3 com.charles.livecaptionn.ui.feedback uses com.charles.livecaptionn.data.feedback✕
- Connections
- 7 pairs of types, where a type in com.charles.livecaptionn.ui.feedback uses a type in com.charles.livecaptionn.data.feedback.
- The types involved
com.charles.livecaptionn.ui.feedback.FeedbackScreensKt→com.charles.livecaptionn.data.feedback.BugReportcom.charles.livecaptionn.ui.feedback.FeedbackScreensKt→com.charles.livecaptionn.data.feedback.GithubCommentcom.charles.livecaptionn.ui.feedback.FeedbackUiState→com.charles.livecaptionn.data.feedback.BugReportcom.charles.livecaptionn.ui.feedback.FeedbackUiState→com.charles.livecaptionn.data.feedback.GithubCommentcom.charles.livecaptionn.ui.feedback.FeedbackUiState→com.charles.livecaptionn.data.feedback.GithubIssuecom.charles.livecaptionn.ui.feedback.FeedbackViewModel→com.charles.livecaptionn.data.feedback.BugReportcom.charles.livecaptionn.ui.feedback.FeedbackViewModel→com.charles.livecaptionn.data.feedback.BugReportRepo
- Direction
- com.charles.livecaptionn.ui.feedback uses com.charles.livecaptionn.data.feedback, so a change to com.charles.livecaptionn.data.feedback can break com.charles.livecaptionn.ui.feedback, while a change to com.charles.livecaptionn.ui.feedback can't break com.charles.livecaptionn.data.feedback.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.feedback uses a module listed above it, which is the healthy direction.
17→3 com.charles.livecaptionn.ui.feedback.FeedbackViewModel uses com.charles.livecaptionn.data.feedback✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.feedback.FeedbackViewModel uses a type in com.charles.livecaptionn.data.feedback.
- The types involved
com.charles.livecaptionn.ui.feedback.FeedbackViewModel.Factory→com.charles.livecaptionn.data.feedback.BugReportRepo
- Direction
- com.charles.livecaptionn.ui.feedback.FeedbackViewModel uses com.charles.livecaptionn.data.feedback, so a change to com.charles.livecaptionn.data.feedback can break com.charles.livecaptionn.ui.feedback.FeedbackViewModel, while a change to com.charles.livecaptionn.ui.feedback.FeedbackViewModel can't break com.charles.livecaptionn.data.feedback.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.feedback.FeedbackViewModel uses a module listed above it, which is the healthy direction.
18→31 com.charles.livecaptionn.ui.l10n.UiLocalizationRepository uses com.charles.livecaptionn.ui.l10n part of a loop✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.l10n.UiLocalizationRepository uses a type in com.charles.livecaptionn.ui.l10n.
- The types involved
com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.State→com.charles.livecaptionn.ui.l10n.UiStrings
- Direction
- com.charles.livecaptionn.ui.l10n.UiLocalizationRepository uses com.charles.livecaptionn.ui.l10n, so a change to com.charles.livecaptionn.ui.l10n can break com.charles.livecaptionn.ui.l10n.UiLocalizationRepository, while a change to com.charles.livecaptionn.ui.l10n.UiLocalizationRepository can't break com.charles.livecaptionn.ui.l10n.
- 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→10 com.charles.livecaptionn.billing uses com.charles.livecaptionn.data✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.billing uses a type in com.charles.livecaptionn.data.
- The types involved
com.charles.livecaptionn.billing.PlayBillingRepository→com.charles.livecaptionn.data.PremiumLocalStorecom.charles.livecaptionn.billing.StripeBillingRepository→com.charles.livecaptionn.data.PremiumLocalStore
- Direction
- com.charles.livecaptionn.billing uses com.charles.livecaptionn.data, so a change to com.charles.livecaptionn.data can break com.charles.livecaptionn.billing, while a change to com.charles.livecaptionn.billing can't break com.charles.livecaptionn.data.
- Position
- Below the diagonal: com.charles.livecaptionn.billing uses a module listed above it, which is the healthy direction.
20→15 com.charles.livecaptionn.speech.ModelQuality uses com.charles.livecaptionn.speech✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.speech.ModelQuality uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.speech.ModelQuality.LARGE→com.charles.livecaptionn.speech.ModelQualitycom.charles.livecaptionn.speech.ModelQuality.SMALL→com.charles.livecaptionn.speech.ModelQuality
- Direction
- com.charles.livecaptionn.speech.ModelQuality uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.speech.ModelQuality, while a change to com.charles.livecaptionn.speech.ModelQuality can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.speech.ModelQuality uses a module listed above it, which is the healthy direction.
21→15 com.charles.livecaptionn.speech.RecognitionStatus uses com.charles.livecaptionn.speech✕
- Connections
- 5 pairs of types, where a type in com.charles.livecaptionn.speech.RecognitionStatus uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.speech.RecognitionStatus.ERROR→com.charles.livecaptionn.speech.RecognitionStatuscom.charles.livecaptionn.speech.RecognitionStatus.IDLE→com.charles.livecaptionn.speech.RecognitionStatuscom.charles.livecaptionn.speech.RecognitionStatus.LISTENING→com.charles.livecaptionn.speech.RecognitionStatuscom.charles.livecaptionn.speech.RecognitionStatus.PAUSED→com.charles.livecaptionn.speech.RecognitionStatuscom.charles.livecaptionn.speech.RecognitionStatus.PROCESSING→com.charles.livecaptionn.speech.RecognitionStatus
- Direction
- com.charles.livecaptionn.speech.RecognitionStatus uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.speech.RecognitionStatus, while a change to com.charles.livecaptionn.speech.RecognitionStatus can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.speech.RecognitionStatus uses a module listed above it, which is the healthy direction.
22→15 com.charles.livecaptionn.speech.VoskSource uses com.charles.livecaptionn.speech✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.speech.VoskSource uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.speech.VoskSource.BUNDLED→com.charles.livecaptionn.speech.VoskSourcecom.charles.livecaptionn.speech.VoskSource.DOWNLOADED→com.charles.livecaptionn.speech.VoskSource
- Direction
- com.charles.livecaptionn.speech.VoskSource uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.speech.VoskSource, while a change to com.charles.livecaptionn.speech.VoskSource can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.speech.VoskSource uses a module listed above it, which is the healthy direction.
23→5 com.charles.livecaptionn.translation uses com.charles.livecaptionn.settings✕
- Connections
- 4 pairs of types, where a type in com.charles.livecaptionn.translation uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.translation.LibreCatalogState→com.charles.livecaptionn.settings.Languagecom.charles.livecaptionn.translation.MlKitLanguages→com.charles.livecaptionn.settings.Languagecom.charles.livecaptionn.translation.ProStartGate→com.charles.livecaptionn.settings.TranslationBackendcom.charles.livecaptionn.translation.RoutingTranslationRepository→com.charles.livecaptionn.settings.TranslationBackend
- Direction
- com.charles.livecaptionn.translation uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.translation, while a change to com.charles.livecaptionn.translation can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.translation uses a module listed above it, which is the healthy direction.
23→10 com.charles.livecaptionn.translation uses com.charles.livecaptionn.data✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.translation uses a type in com.charles.livecaptionn.data.
- The types involved
com.charles.livecaptionn.translation.LanguageCatalogStore→com.charles.livecaptionn.data.SettingsRepositorycom.charles.livecaptionn.translation.LibreTranslateRepository→com.charles.livecaptionn.data.SettingsRepositorycom.charles.livecaptionn.translation.RoutingTranslationRepository→com.charles.livecaptionn.data.SettingsRepository
- Direction
- com.charles.livecaptionn.translation uses com.charles.livecaptionn.data, so a change to com.charles.livecaptionn.data can break com.charles.livecaptionn.translation, while a change to com.charles.livecaptionn.translation can't break com.charles.livecaptionn.data.
- Position
- Below the diagonal: com.charles.livecaptionn.translation uses a module listed above it, which is the healthy direction.
24→18 com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage uses com.charles.livecaptionn.ui.l10n.UiLocalizationRepository✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage uses a type in com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.
- The types involved
com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage.DOWNLOADING→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStagecom.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage.TRANSLATING→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage
- Direction
- com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage uses com.charles.livecaptionn.ui.l10n.UiLocalizationRepository, so a change to com.charles.livecaptionn.ui.l10n.UiLocalizationRepository can break com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage, while a change to com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage can't break com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage uses a module listed above it, which is the healthy direction.
25→19 com.charles.livecaptionn.ads uses com.charles.livecaptionn.billing✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ads uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.ads.AppOpenAdManager→com.charles.livecaptionn.billing.PremiumRepository
- Direction
- com.charles.livecaptionn.ads uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.ads, while a change to com.charles.livecaptionn.ads can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.ads uses a module listed above it, which is the healthy direction.
26→19 com.charles.livecaptionn.billing.Entitlement uses com.charles.livecaptionn.billing✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.billing.Entitlement uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.billing.Entitlement.AD_FREE→com.charles.livecaptionn.billing.Entitlementcom.charles.livecaptionn.billing.Entitlement.PRO→com.charles.livecaptionn.billing.Entitlement
- Direction
- com.charles.livecaptionn.billing.Entitlement uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.billing.Entitlement, while a change to com.charles.livecaptionn.billing.Entitlement can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.billing.Entitlement uses a module listed above it, which is the healthy direction.
27→19 com.charles.livecaptionn.billing.ManageAction uses com.charles.livecaptionn.billing✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.billing.ManageAction uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.billing.ManageAction.Failed→com.charles.livecaptionn.billing.ManageActioncom.charles.livecaptionn.billing.ManageAction.Opened→com.charles.livecaptionn.billing.ManageAction
- Direction
- com.charles.livecaptionn.billing.ManageAction uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.billing.ManageAction, while a change to com.charles.livecaptionn.billing.ManageAction can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.billing.ManageAction uses a module listed above it, which is the healthy direction.
28→19 com.charles.livecaptionn.billing.PremiumProduct uses com.charles.livecaptionn.billing✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.billing.PremiumProduct uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.billing.PremiumProduct.AD_FREE_MONTHLY→com.charles.livecaptionn.billing.PremiumProductcom.charles.livecaptionn.billing.PremiumProduct.PRO_MONTHLY→com.charles.livecaptionn.billing.PremiumProduct
- Direction
- com.charles.livecaptionn.billing.PremiumProduct uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.billing.PremiumProduct, while a change to com.charles.livecaptionn.billing.PremiumProduct can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.billing.PremiumProduct uses a module listed above it, which is the healthy direction.
29→19 com.charles.livecaptionn.billing.PremiumState uses com.charles.livecaptionn.billing✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.billing.PremiumState uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.billing.PremiumState.Companion→com.charles.livecaptionn.billing.PremiumState
- Direction
- com.charles.livecaptionn.billing.PremiumState uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.billing.PremiumState, while a change to com.charles.livecaptionn.billing.PremiumState can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.billing.PremiumState uses a module listed above it, which is the healthy direction.
30→19 com.charles.livecaptionn.billing.PurchaseFlowResult uses com.charles.livecaptionn.billing✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.billing.PurchaseFlowResult uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.billing.PurchaseFlowResult.Failed→com.charles.livecaptionn.billing.PurchaseFlowResultcom.charles.livecaptionn.billing.PurchaseFlowResult.Started→com.charles.livecaptionn.billing.PurchaseFlowResult
- Direction
- com.charles.livecaptionn.billing.PurchaseFlowResult uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.billing.PurchaseFlowResult, while a change to com.charles.livecaptionn.billing.PurchaseFlowResult can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.billing.PurchaseFlowResult uses a module listed above it, which is the healthy direction.
31→10 com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.data✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.l10n uses a type in com.charles.livecaptionn.data.
- The types involved
com.charles.livecaptionn.ui.l10n.UiLocalizationRepository→com.charles.livecaptionn.data.SettingsRepository
- Direction
- com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.data, so a change to com.charles.livecaptionn.data can break com.charles.livecaptionn.ui.l10n, while a change to com.charles.livecaptionn.ui.l10n can't break com.charles.livecaptionn.data.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.l10n uses a module listed above it, which is the healthy direction.
31→18 com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.ui.l10n.UiLocalizationRepository✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.ui.l10n uses a type in com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.
- The types involved
com.charles.livecaptionn.ui.l10n.UiLanguagePickerKt→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStagecom.charles.livecaptionn.ui.l10n.UiLocalizationRepository→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.State
- Direction
- com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.ui.l10n.UiLocalizationRepository, so a change to com.charles.livecaptionn.ui.l10n.UiLocalizationRepository can break com.charles.livecaptionn.ui.l10n, while a change to com.charles.livecaptionn.ui.l10n can't break com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.l10n uses a module listed above it, which is the healthy direction.
31→23 com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.translation✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.l10n uses a type in com.charles.livecaptionn.translation.
- The types involved
com.charles.livecaptionn.ui.l10n.UiLocalizationRepository→com.charles.livecaptionn.translation.TranslationRepository
- Direction
- com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.translation, so a change to com.charles.livecaptionn.translation can break com.charles.livecaptionn.ui.l10n, while a change to com.charles.livecaptionn.ui.l10n can't break com.charles.livecaptionn.translation.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.l10n uses a module listed above it, which is the healthy direction.
31→38 com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.di part of a loop✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.l10n uses a type in com.charles.livecaptionn.di.
- The types involved
com.charles.livecaptionn.ui.l10n.CompositionLocalsKt→com.charles.livecaptionn.di.AppContainer
- Direction
- com.charles.livecaptionn.ui.l10n uses com.charles.livecaptionn.di, so a change to com.charles.livecaptionn.di can break com.charles.livecaptionn.ui.l10n, while a change to com.charles.livecaptionn.ui.l10n can't break com.charles.livecaptionn.di.
- 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→19 com.charles.livecaptionn.ui.premium uses com.charles.livecaptionn.billing✕
- Connections
- 4 pairs of types, where a type in com.charles.livecaptionn.ui.premium uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.ui.premium.PremiumScreensKt→com.charles.livecaptionn.billing.PremiumProductcom.charles.livecaptionn.ui.premium.PremiumUiState→com.charles.livecaptionn.billing.PremiumStatecom.charles.livecaptionn.ui.premium.PremiumViewModel→com.charles.livecaptionn.billing.PremiumProductcom.charles.livecaptionn.ui.premium.PremiumViewModel→com.charles.livecaptionn.billing.PremiumRepository
- Direction
- com.charles.livecaptionn.ui.premium uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.ui.premium, while a change to com.charles.livecaptionn.ui.premium can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.premium uses a module listed above it, which is the healthy direction.
33→19 com.charles.livecaptionn.ui.premium.PremiumViewModel uses com.charles.livecaptionn.billing✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.premium.PremiumViewModel uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.ui.premium.PremiumViewModel.Factory→com.charles.livecaptionn.billing.PremiumRepository
- Direction
- com.charles.livecaptionn.ui.premium.PremiumViewModel uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.ui.premium.PremiumViewModel, while a change to com.charles.livecaptionn.ui.premium.PremiumViewModel can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.premium.PremiumViewModel uses a module listed above it, which is the healthy direction.
34→10 com.charles.livecaptionn.overlay uses com.charles.livecaptionn.data✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.overlay uses a type in com.charles.livecaptionn.data.
- The types involved
com.charles.livecaptionn.overlay.OverlayController→com.charles.livecaptionn.data.SettingsRepository
- Direction
- com.charles.livecaptionn.overlay uses com.charles.livecaptionn.data, so a change to com.charles.livecaptionn.data can break com.charles.livecaptionn.overlay, while a change to com.charles.livecaptionn.overlay can't break com.charles.livecaptionn.data.
- Position
- Below the diagonal: com.charles.livecaptionn.overlay uses a module listed above it, which is the healthy direction.
34→15 com.charles.livecaptionn.overlay uses com.charles.livecaptionn.speech✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.overlay uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.overlay.OverlayUiState→com.charles.livecaptionn.speech.RecognitionStatus
- Direction
- com.charles.livecaptionn.overlay uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.overlay, while a change to com.charles.livecaptionn.overlay can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.overlay uses a module listed above it, which is the healthy direction.
34→31 com.charles.livecaptionn.overlay uses com.charles.livecaptionn.ui.l10n✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.overlay uses a type in com.charles.livecaptionn.ui.l10n.
- The types involved
com.charles.livecaptionn.overlay.OverlayController→com.charles.livecaptionn.ui.l10n.UiStrings
- Direction
- com.charles.livecaptionn.overlay uses com.charles.livecaptionn.ui.l10n, so a change to com.charles.livecaptionn.ui.l10n can break com.charles.livecaptionn.overlay, while a change to com.charles.livecaptionn.overlay can't break com.charles.livecaptionn.ui.l10n.
- Position
- Below the diagonal: com.charles.livecaptionn.overlay uses a module listed above it, which is the healthy direction.
35→31 com.charles.livecaptionn.ui.l10n.UiStrings uses com.charles.livecaptionn.ui.l10n✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui.l10n.UiStrings uses a type in com.charles.livecaptionn.ui.l10n.
- The types involved
com.charles.livecaptionn.ui.l10n.UiStrings.Companion→com.charles.livecaptionn.ui.l10n.UiStrings
- Direction
- com.charles.livecaptionn.ui.l10n.UiStrings uses com.charles.livecaptionn.ui.l10n, so a change to com.charles.livecaptionn.ui.l10n can break com.charles.livecaptionn.ui.l10n.UiStrings, while a change to com.charles.livecaptionn.ui.l10n.UiStrings can't break com.charles.livecaptionn.ui.l10n.
- Position
- Below the diagonal: com.charles.livecaptionn.ui.l10n.UiStrings uses a module listed above it, which is the healthy direction.
36→31 com.charles.livecaptionn.update uses com.charles.livecaptionn.ui.l10n✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.update uses a type in com.charles.livecaptionn.ui.l10n.
- The types involved
com.charles.livecaptionn.update.UpdateNotifier→com.charles.livecaptionn.ui.l10n.UiStrings
- Direction
- com.charles.livecaptionn.update uses com.charles.livecaptionn.ui.l10n, so a change to com.charles.livecaptionn.ui.l10n can break com.charles.livecaptionn.update, while a change to com.charles.livecaptionn.update can't break com.charles.livecaptionn.ui.l10n.
- Position
- Below the diagonal: com.charles.livecaptionn.update uses a module listed above it, which is the healthy direction.
37→4 com.charles.livecaptionn.service uses com.charles.livecaptionn.service.CaptionForegroundService✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.service uses a type in com.charles.livecaptionn.service.CaptionForegroundService.
- The types involved
com.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.service.CaptionForegroundService.TranslationRequest
- Direction
- com.charles.livecaptionn.service uses com.charles.livecaptionn.service.CaptionForegroundService, so a change to com.charles.livecaptionn.service.CaptionForegroundService can break com.charles.livecaptionn.service, while a change to com.charles.livecaptionn.service can't break com.charles.livecaptionn.service.CaptionForegroundService.
- Position
- Below the diagonal: com.charles.livecaptionn.service uses a module listed above it, which is the healthy direction.
37→5 com.charles.livecaptionn.service uses com.charles.livecaptionn.settings✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.service uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.settings.AudioSourcecom.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.settings.CaptionSettings
- Direction
- com.charles.livecaptionn.service uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.service, while a change to com.charles.livecaptionn.service can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.service uses a module listed above it, which is the healthy direction.
37→15 com.charles.livecaptionn.service uses com.charles.livecaptionn.speech✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.service uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.speech.RecognitionStatuscom.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.speech.SpeechEnginecom.charles.livecaptionn.service.CaptionRuntimeState→com.charles.livecaptionn.speech.RecognitionStatus
- Direction
- com.charles.livecaptionn.service uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.service, while a change to com.charles.livecaptionn.service can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.service uses a module listed above it, which is the healthy direction.
37→34 com.charles.livecaptionn.service uses com.charles.livecaptionn.overlay✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.service uses a type in com.charles.livecaptionn.overlay.
- The types involved
com.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.overlay.OverlayControllercom.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.overlay.OverlayUiState
- Direction
- com.charles.livecaptionn.service uses com.charles.livecaptionn.overlay, so a change to com.charles.livecaptionn.overlay can break com.charles.livecaptionn.service, while a change to com.charles.livecaptionn.service can't break com.charles.livecaptionn.overlay.
- Position
- Below the diagonal: com.charles.livecaptionn.service uses a module listed above it, which is the healthy direction.
37→39 com.charles.livecaptionn.service uses com.charles.livecaptionn part of a loop✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.service uses a type in com.charles.livecaptionn.
- The types involved
com.charles.livecaptionn.service.CaptionForegroundService→com.charles.livecaptionn.LiveCaptionApp
- Direction
- com.charles.livecaptionn.service uses com.charles.livecaptionn, so a change to com.charles.livecaptionn can break com.charles.livecaptionn.service, while a change to com.charles.livecaptionn.service can't break com.charles.livecaptionn.
- 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.
38→3 com.charles.livecaptionn.di uses com.charles.livecaptionn.data.feedback✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.data.feedback.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.data.feedback.BugReportRepo
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.data.feedback, so a change to com.charles.livecaptionn.data.feedback can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.data.feedback.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→10 com.charles.livecaptionn.di uses com.charles.livecaptionn.data✕
- Connections
- 6 pairs of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.data.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.data.CaptionProfileRepositorycom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.data.GlossaryRepositorycom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.data.PremiumLocalStorecom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.data.SettingsRepositorycom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.data.TranscriptHistoryStorecom.charles.livecaptionn.di.PremiumRepositoryFactoryKt→com.charles.livecaptionn.data.PremiumLocalStore
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.data, so a change to com.charles.livecaptionn.data can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.data.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→15 com.charles.livecaptionn.di uses com.charles.livecaptionn.speech✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.speech.LocalVoskSttClientcom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.speech.VoskModelRegistry
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→19 com.charles.livecaptionn.di uses com.charles.livecaptionn.billing✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.billing.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.billing.PremiumRepositorycom.charles.livecaptionn.di.PremiumRepositoryFactoryKt→com.charles.livecaptionn.billing.PremiumRepository
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.billing, so a change to com.charles.livecaptionn.billing can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.billing.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→23 com.charles.livecaptionn.di uses com.charles.livecaptionn.translation✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.translation.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.translation.LanguageCatalogStorecom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.translation.TranslationRepository
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.translation, so a change to com.charles.livecaptionn.translation can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.translation.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→31 com.charles.livecaptionn.di uses com.charles.livecaptionn.ui.l10n✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.ui.l10n.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.ui.l10n, so a change to com.charles.livecaptionn.ui.l10n can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.ui.l10n.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→36 com.charles.livecaptionn.di uses com.charles.livecaptionn.update✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.update.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.update.UpdateCheckercom.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.update.UpdateNotifier
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.update, so a change to com.charles.livecaptionn.update can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.update.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
38→37 com.charles.livecaptionn.di uses com.charles.livecaptionn.service✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.di uses a type in com.charles.livecaptionn.service.
- The types involved
com.charles.livecaptionn.di.AppContainer→com.charles.livecaptionn.service.CaptionRuntimeStore
- Direction
- com.charles.livecaptionn.di uses com.charles.livecaptionn.service, so a change to com.charles.livecaptionn.service can break com.charles.livecaptionn.di, while a change to com.charles.livecaptionn.di can't break com.charles.livecaptionn.service.
- Position
- Below the diagonal: com.charles.livecaptionn.di uses a module listed above it, which is the healthy direction.
39→5 com.charles.livecaptionn uses com.charles.livecaptionn.settings✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.MainActivity→com.charles.livecaptionn.settings.AudioSource
- Direction
- com.charles.livecaptionn uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn, while a change to com.charles.livecaptionn can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn uses a module listed above it, which is the healthy direction.
39→25 com.charles.livecaptionn uses com.charles.livecaptionn.ads✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn uses a type in com.charles.livecaptionn.ads.
- The types involved
com.charles.livecaptionn.LiveCaptionApp→com.charles.livecaptionn.ads.AppOpenAdManager
- Direction
- com.charles.livecaptionn uses com.charles.livecaptionn.ads, so a change to com.charles.livecaptionn.ads can break com.charles.livecaptionn, while a change to com.charles.livecaptionn can't break com.charles.livecaptionn.ads.
- Position
- Below the diagonal: com.charles.livecaptionn uses a module listed above it, which is the healthy direction.
39→38 com.charles.livecaptionn uses com.charles.livecaptionn.di✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn uses a type in com.charles.livecaptionn.di.
- The types involved
com.charles.livecaptionn.LiveCaptionApp→com.charles.livecaptionn.di.AppContainer
- Direction
- com.charles.livecaptionn uses com.charles.livecaptionn.di, so a change to com.charles.livecaptionn.di can break com.charles.livecaptionn, while a change to com.charles.livecaptionn can't break com.charles.livecaptionn.di.
- Position
- Below the diagonal: com.charles.livecaptionn uses a module listed above it, which is the healthy direction.
40→2 com.charles.livecaptionn.ui uses com.charles.livecaptionn.compatibility✕
- Connections
- 5 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.compatibility.
- The types involved
com.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.compatibility.CompatibilityTiercom.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.compatibility.DeviceSpecscom.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.compatibility.DeviceSpecscom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.compatibility.CompatibilityTiercom.charles.livecaptionn.ui.TutorialScreenKt→com.charles.livecaptionn.compatibility.DeviceSpecs
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.compatibility, so a change to com.charles.livecaptionn.compatibility can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.compatibility.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→5 com.charles.livecaptionn.ui uses com.charles.livecaptionn.settings✕
- Connections
- 8 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.settings.
- The types involved
com.charles.livecaptionn.ui.FeatureToolsCardKt→com.charles.livecaptionn.settings.CaptionSettingscom.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.settings.Languagecom.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.settings.TranslationBackendcom.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.settings.CaptionSettingscom.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.settings.Languagecom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.settings.AudioSourcecom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.settings.SttBackendcom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.settings.TranslationBackend
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.settings, so a change to com.charles.livecaptionn.settings can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.settings.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→10 com.charles.livecaptionn.ui uses com.charles.livecaptionn.data✕
- Connections
- 6 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.data.
- The types involved
com.charles.livecaptionn.ui.FeatureToolsCardKt→com.charles.livecaptionn.data.CaptionProfilecom.charles.livecaptionn.ui.FeatureToolsCardKt→com.charles.livecaptionn.data.CaptionProfileRepositorycom.charles.livecaptionn.ui.FeatureToolsCardKt→com.charles.livecaptionn.data.GlossaryRepositorycom.charles.livecaptionn.ui.HistoryScreenKt→com.charles.livecaptionn.data.TranscriptEntrycom.charles.livecaptionn.ui.HistoryScreenKt→com.charles.livecaptionn.data.TranscriptHistoryStorecom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.data.CaptionProfile
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.data, so a change to com.charles.livecaptionn.data can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.data.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→15 com.charles.livecaptionn.ui uses com.charles.livecaptionn.speech✕
- Connections
- 4 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.speech.
- The types involved
com.charles.livecaptionn.ui.FeatureToolsCardKt→com.charles.livecaptionn.speech.VoskModelInfocom.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.speech.VoskModelInfocom.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.speech.VoskModelInfocom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.speech.VoskModelInfo
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.speech, so a change to com.charles.livecaptionn.speech can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.speech.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→18 com.charles.livecaptionn.ui uses com.charles.livecaptionn.ui.l10n.UiLocalizationRepository✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.
- The types involved
com.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStagecom.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.UiLocalizationStage
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.ui.l10n.UiLocalizationRepository, so a change to com.charles.livecaptionn.ui.l10n.UiLocalizationRepository can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.ui.l10n.UiLocalizationRepository.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→32 com.charles.livecaptionn.ui uses com.charles.livecaptionn.ui.premium✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.ui.premium.
- The types involved
com.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.ui.premium.PremiumUiState
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.ui.premium, so a change to com.charles.livecaptionn.ui.premium can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.ui.premium.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→36 com.charles.livecaptionn.ui uses com.charles.livecaptionn.update✕
- Connections
- 3 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.update.
- The types involved
com.charles.livecaptionn.ui.MainScreenKt→com.charles.livecaptionn.update.UpdateInfocom.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.update.UpdateInfocom.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.update.UpdateInfo
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.update, so a change to com.charles.livecaptionn.update can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.update.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→37 com.charles.livecaptionn.ui uses com.charles.livecaptionn.service✕
- Connections
- 1 pair of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.service.
- The types involved
com.charles.livecaptionn.ui.MainUiState→com.charles.livecaptionn.service.CaptionRuntimeState
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.service, so a change to com.charles.livecaptionn.service can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.service.
- Position
- Below the diagonal: com.charles.livecaptionn.ui uses a module listed above it, which is the healthy direction.
40→38 com.charles.livecaptionn.ui uses com.charles.livecaptionn.di✕
- Connections
- 2 pairs of types, where a type in com.charles.livecaptionn.ui uses a type in com.charles.livecaptionn.di.
- The types involved
com.charles.livecaptionn.ui.MainViewModel→com.charles.livecaptionn.di.AppContainercom.charles.livecaptionn.ui.MainViewModelFactory→com.charles.livecaptionn.di.AppContainer
- Direction
- com.charles.livecaptionn.ui uses com.charles.livecaptionn.di, so a change to com.charles.livecaptionn.di can break com.charles.livecaptionn.ui, while a change to com.charles.livecaptionn.ui can't break com.charles.livecaptionn.di.
- Position
- Below the diagonal: com.charles.livecaptionn.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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
Roadmap
Top priorities: Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run; 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; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +6.9 pts | Medium | Observability |
| 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.1 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +2.3 pts | Low | ADR Quality |
| 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.1 pts | Medium | Architecture documentation |
| Swallowed exception (empty catch) | +1.8 pts | Medium | Exception handling |
| Thread an AbortSignal or the coroutine's cancellation through functions that make requests, so the work stops when its caller gives up. | +1.6 pts | Medium | Cancellation propagation |
| Resolve the 8 MethodTooLong finding(s) in God Classes — start with FeedbackScreens.kt (2), CaptionForegroundService.kt, OverlayController.kt. | +1.3 pts | High | God Classes |
| Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TutorialScreenKt.TutorialScreen (cyclomatic 35), SystemAudioEngine.startCapture (cyclomatic 28), MainScreenKt.MainScreen (cyclomatic 25). | +0.9 pts | High | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt | 7.0 | Mixed | Cyclomatic Complexity: MainScreenKt.MainScreen (cyclomatic 25) |
| app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt | 7.0 | Mixed | Cognitive Complexity: FeedbackScreensKt.IssueDetailsDialog (cognitive 16) |
| app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt | 7.2 | Mixed | Cyclomatic Complexity: StreamingSttEngine.captureLoop (cyclomatic 16) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt | 7.4 | Mixed | Cyclomatic Complexity: SystemAudioEngine.startCapture (cyclomatic 28) |
| app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt | 7.4 | Mixed | Cyclomatic Complexity: CaptionForegroundService.startFlow (cyclomatic 17) |
| app/src/main/java/com/charles/livecaptionn/ui/FeatureToolsCard.kt | 7.4 | Mixed | Cyclomatic Complexity: FeatureToolsCardKt.FeatureToolsCard (cyclomatic 16) |
| app/src/main/java/com/charles/livecaptionn/ui/TutorialScreen.kt | 7.8 | Mixed | Cyclomatic Complexity: TutorialScreenKt.TutorialScreen (cyclomatic 35) |
| app/src/main/java/com/charles/livecaptionn/ui/l10n/UiLocalizationRepository.kt | 7.8 | Mixed | Cognitive Complexity: UiLocalizationRepository.selectInternal (cognitive 30) |
| app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackViewModel.kt | 7.8 | Mixed | Cognitive Complexity: FeedbackViewModel.submitReport (cognitive 17) |
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 49 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 49 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, 150 of 159 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 330 artifact(s) across its subprojects (90 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — 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 repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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/java/com/charles/livecaptionn/ui/MainScreen.kt`, `cloudflare-worker-feedback/src/index.ts` 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 defines its own container in app/src/main/java/com/charles/livecaptionn/di/AppContainer.kt, 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.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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: oogle-services.json, app/src/github/google-services.json, app/src/debug/google-services.json,…; runtime evidence skipped (launch chosen because app/build.gradle.kts 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.
- 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, Scala, Rust and Java source only, and this repository's Kotlin, Python 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.
- 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, Scala and Rust source only, and this repository's Kotlin, Python 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- X24 Document value interpolated into markup unescaped — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TutorialScreenKt.TutorialScreen at 35.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TutorialScreenKt.TutorialScreen (cyclomatic 35), SystemAudioEngine.startCapture (cyclomatic 28), MainScreenKt.MainScreen (cyclomatic 25). — 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 7 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was TutorialScreenKt.TutorialScreen at 54.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with TutorialScreenKt.TutorialScreen (cognitive 54), SystemAudioEngine.startCapture (cognitive 50). — 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 Cognitive Complexity from 6.8 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with FeedbackScreens.kt (2), CaptionForegroundService.kt, OverlayController.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with MainScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with MainViewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 4.0 % of the production lines (470 of 11,847) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with PremiumViewModel.kt, MainViewModel.kt, MlKitTranslationRepository.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with MainScreen.kt (2), UiLocalizationRepository.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with StreamingSttEngine.kt, FeedbackViewModel.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.
D6 · Cohesion (LCOM4)
0 of 31 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 9 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 13 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt (7×25=175); app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt (4×17=68)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainScreen.kt, CaptionForegroundService.kt. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 11847 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 3 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.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Gradle, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
41 finding(s): 0 critical, 39 high, 2 medium, 0 low. 30 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 1 file(s) — `cloudflare-worker-feedback/src/index.ts` (line 191) — 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 4 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 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 30 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 (30 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 50 of the 100 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 28 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
AX6 · Interface segregation
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- No logging call was found in the 97 Python, JVM, JavaScript/TypeScript production file(s) this check read across 4 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; Python: logging, structlog, loguru; 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 SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 10 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:7
- `cloudflare-worker-feedback/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — cloudflare-worker-feedback/package.json:10
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.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
- Only 1/5 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `stripeFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — cloudflare-worker/src/worker.js:282
- `check` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/charles/livecaptionn/update/UpdateChecker.kt:42
- `downloadAndInstall` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/charles/livecaptionn/speech/VoskModelRegistry.kt:129
- `transcribe` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/charles/livecaptionn/speech/WhisperSttClient.kt:40
What to do
- Thread an AbortSignal or the coroutine's cancellation through functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — app/src/main/java/com/charles/livecaptionn/MainActivity.kt:87, app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackViewModel.kt:328, app/src/main/java/com/charles/livecaptionn/translation/MlKitTranslationRepository.kt:138, …
- `catch (_: 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. (×8) — app/src/main/java/com/charles/livecaptionn/ui/MainViewModel.kt:47, app/src/main/java/com/charles/livecaptionn/ui/MainViewModel.kt:366, app/src/main/java/com/charles/livecaptionn/ui/l10n/UiStrings.kt:40, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. — app/src/main/java/com/charles/livecaptionn/speech/LocalVoskSttClient.kt:158
- `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. (×4) — app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:53, app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:67, app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:80, …
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67.0 | Adequate | Acceptable, with room to improve. |
| Architecture | 93.9 | Exemplary | Solid. |
| Maturity | 70.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56.0 | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74.0 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 6 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 — 64 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 Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- 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: oogle-services.json, app/src/github/google-services.json, app/src/debug/google-services.json,…; runtime evidence skipped (launch chosen because app/build.gradle.kts 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 — ~1580 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
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 330 artifact(s) across its subprojects (90 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — bus factor 1 — one contributor carries this repository
- 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; comments in this repository's .kt, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 45 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises 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, Scala, Rust and Java, 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
- 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — 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 — X24 reached only 7% of this repository's production lines — kotlin (11,413 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X28 Index access outside its own emptiness guard — 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.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 40 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 103 finding(s)
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/MainActivity.kt:87
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackViewModel.kt:328
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/translation/MlKitTranslationRepository.kt:138
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:68
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:69
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:70
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:77
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:222
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:223
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/LocalVoskSttClient.kt:158
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:70
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:71
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:79
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt:66
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt:69
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt:73
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:493
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:514
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:529
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/review/PlayReviewHelper.kt:16
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/overlay/OverlayController.kt:282
- Swallowed exception (empty catch) app/src/main/java/com/charles/livecaptionn/overlay/OverlayController.kt:288
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/ui/MainViewModel.kt:47
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/ui/MainViewModel.kt:366
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/ui/l10n/UiStrings.kt:40
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/ui/l10n/UiTranslationCache.kt:31
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/speech/AndroidSpeechRecognizerManager.kt:204
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/speech/LocalVoskSttClient.kt:105
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/speech/VoskModelRegistry.kt:234
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:53
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:67
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:80
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/data/feedback/DiagnosticsHelper.kt:91
- Swallowed exception (caught, then discarded) app/src/main/java/com/charles/livecaptionn/compatibility/DeviceCompatibilityChecker.kt:149
- MethodTooLong: FeedbackScreensKt.ReportProblemDialog app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:205
- MethodTooLong: FeedbackScreensKt.IssueDetailsDialog app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:395
- MethodTooLong: CaptionForegroundService.startFlow app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:166
- MethodTooLong: OverlayController.showInternal app/src/main/java/com/charles/livecaptionn/overlay/OverlayController.kt:57
- MethodTooLong: SystemAudioEngine.startCapture app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt:88
- MethodTooLong: UiLanguagePickerKt.UiLanguagePickerDialog app/src/main/java/com/charles/livecaptionn/ui/l10n/UiLanguagePicker.kt:43
- MethodTooLong: HistoryScreenKt.HistoryScreen app/src/main/java/com/charles/livecaptionn/ui/HistoryScreen.kt:65
- MethodTooLong: FeatureToolsCardKt.FeatureToolsCard app/src/main/java/com/charles/livecaptionn/ui/FeatureToolsCard.kt:43
- Edited copy of a member (8 corresponding lines) app/src/main/java/com/charles/livecaptionn/ui/premium/PremiumViewModel.kt:41
- Edited copy of a member (8 corresponding lines) app/src/main/java/com/charles/livecaptionn/ui/MainViewModel.kt:229
- Edited copy of a member (8 corresponding lines) app/src/main/java/com/charles/livecaptionn/translation/MlKitTranslationRepository.kt:71
- Duplicated block (10 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/l10n/UiLocalizationRepository.kt:134
- Duplicated block (10 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1163
- Duplicated block (10 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1004
- Suspend function with a blocking request: check app/src/main/java/com/charles/livecaptionn/update/UpdateChecker.kt:42
- Suspend function with a blocking request: downloadAndInstall app/src/main/java/com/charles/livecaptionn/speech/VoskModelRegistry.kt:129
- Suspend function with a blocking request: transcribe app/src/main/java/com/charles/livecaptionn/speech/WhisperSttClient.kt:40
- Hotspot: app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:123
- Hotspot: app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:166
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:301
- Duplicated block (9 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackViewModel.kt:159
- Duplicated block (8 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1707
- Duplicated block (8 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1805
- TutorialScreenKt.TutorialScreen (cyclomatic 35) app/src/main/java/com/charles/livecaptionn/ui/TutorialScreen.kt:141
- SystemAudioEngine.startCapture (cyclomatic 28) app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt:88
- MainScreenKt.MainScreen (cyclomatic 25) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:123
- MainScreenKt.CaptionControlCard (cyclomatic 19) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:446
- CaptionForegroundService.startFlow (cyclomatic 17) app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:166
- StreamingSttEngine.captureLoop (cyclomatic 16) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:163
- FeatureToolsCardKt.FeatureToolsCard (cyclomatic 16) app/src/main/java/com/charles/livecaptionn/ui/FeatureToolsCard.kt:43
- bus factor 1 — one contributor carries this repository
- TutorialScreenKt.TutorialScreen (cognitive 54) app/src/main/java/com/charles/livecaptionn/ui/TutorialScreen.kt:141
- SystemAudioEngine.startCapture (cognitive 50) app/src/main/java/com/charles/livecaptionn/speech/SystemAudioEngine.kt:88
- UiLocalizationRepository.selectInternal (cognitive 30) app/src/main/java/com/charles/livecaptionn/ui/l10n/UiLocalizationRepository.kt:102
- StreamingSttEngine.captureLoop (cognitive 28) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:163
- MainScreenKt.MainScreen (cognitive 28) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:123
- CaptionForegroundService.startFlow (cognitive 22) app/src/main/java/com/charles/livecaptionn/service/CaptionForegroundService.kt:166
- FeatureToolsCardKt.FeatureToolsCard (cognitive 21) app/src/main/java/com/charles/livecaptionn/ui/FeatureToolsCard.kt:43
- handleEntitlement (cognitive 20) cloudflare-worker/src/worker.js:177
- MainScreenKt.AudioSourceCard (cognitive 19) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:673
- MainScreenKt.CaptionControlCard (cognitive 17) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:446
- FeedbackViewModel.submitReport (cognitive 17) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackViewModel.kt:124
- UiLanguagePickerKt.UiLanguagePickerDialog (cognitive 17) app/src/main/java/com/charles/livecaptionn/ui/l10n/UiLanguagePicker.kt:43
- HistoryScreenKt.HistoryScreen (cognitive 16) app/src/main/java/com/charles/livecaptionn/ui/HistoryScreen.kt:65
- FeedbackScreensKt.IssueDetailsDialog (cognitive 16) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:395
- FileTooLong: ui/MainScreen.kt app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt
- TooManyMethods: MainViewModel app/src/main/java/com/charles/livecaptionn/ui/MainViewModel.kt:33
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (49 corresponding lines) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1706
- Edited copy of a member (15 corresponding lines) app/src/main/java/com/charles/livecaptionn/translation/LanguageCatalogStore.kt:93
- Edited copy of a member (14 corresponding lines) app/src/main/java/com/charles/livecaptionn/speech/StreamingSttEngine.kt:295
- Edited copy of a member (13 corresponding lines) app/src/main/java/com/charles/livecaptionn/data/TranscriptHistoryStore.kt:55
- Edited copy of a member (1 corresponding lines) app/src/main/java/com/charles/livecaptionn/data/CaptionProfileRepository.kt:34
- Edited copies of one member (4 members, 1+ corresponding lines) app/src/main/java/com/charles/livecaptionn/data/CaptionProfileRepository.kt:26
- Duplicated block (16 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:100
- Duplicated block (13–14 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1652
- Duplicated block (14 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:181
- Duplicated block (9–14 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:343
- Duplicated block (9–13 lines × 2) app/src/main/java/com/charles/livecaptionn/translation/LanguageCatalogStore.kt:99
- Duplicated block (12 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1148
- Duplicated block (11 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/feedback/FeedbackScreens.kt:75
- Duplicated block (13 lines × 2) app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:1716
- No structured logging
- JavaScript dependencies are not locked cloudflare-worker/package.json:8
- Async function without AbortSignal: stripeFetch cloudflare-worker/src/worker.js:282
Minor — 16 finding(s)
- Silent fallback default in catch app/src/main/java/com/charles/livecaptionn/compatibility/DeviceCompatibilityChecker.kt:149
- Silent fallback default in catch app/src/main/java/com/charles/livecaptionn/data/CaptionProfileRepository.kt:34
- Silent fallback default in catch app/src/main/java/com/charles/livecaptionn/data/GlossaryRepository.kt:24
- Silent fallback default in catch app/src/main/java/com/charles/livecaptionn/data/feedback/BugReportRepo.kt:62
- Silent fallback default in catch app/src/main/java/com/charles/livecaptionn/data/feedback/BugReportRepo.kt:75
- Silent fallback default in catch app/src/main/java/com/charles/livecaptionn/speech/LocalVoskSttClient.kt:105
- No ADRs found app/build.gradle.kts:4
- Projects may be oversized for their cohesion app/build.gradle.kts:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:7
- No dependency-update automation cloudflare-worker-feedback/package.json:10
- Duplicated predicate app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt:998
- Not all functions that make a request accept an AbortSignal or the coroutine's cancellation
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-96d3114190474183927650a2d96af81c/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-96d3114190474183927650a2d96af81c/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 . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| 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 2 file(s) — `app/src/main/java/com/charles/livecaptionn/ui/MainScreen.kt`, `cloudflare-worker-feedback/src/index.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |