Executive summary
YiiGuxing/TranslationPlugin falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 49 out of 100 and is rated Weak, and all 49 of its critical findings are security problems.
Security and Compliance, at 38, is the weakest lens and counts most in the score. The best first step is replacing the seven passwords or keys found in the code's history, worth about 6 points. Fixing the three weaknesses in the build pipeline's configuration would lift Security and Compliance itself, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 57.
Thirty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven passwords or keys in the code's history and four in the code are open to anyone who can read the repository. Pinning each tool to an exact version and replacing each exposed password or key would close both risks. Correcting the flagged pipeline settings would fix the four weaknesses in the build pipeline's configuration, and passing outside input through environment variables would deal with the two pipeline steps that put outside input straight into a shell command.
The product code is 27,384 lines, about €26,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 38 to 70, the lowest score rated Strong, the score would rise from 49 to about 57.
New since the last survey: 14 findings
- Code Duplication · Edited copy of a member (27 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/microsoft/BingTranslator.kt
- Code Duplication · Edited copy of a member (25 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/baidu/BaiduTranslator.kt
- Code Duplication · Edited copy of a member (20 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/util/UrlTrackingParametersProvider.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/action/SwitchEngineAction.kt
- Code Duplication · Edited copy of a member (17 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/config/OpenAiRequestConfigService.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/ui/FixedSizeCardLayout.kt
- Code Duplication · Edited copy of a member (17 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoSettingsDialog.kt
- Code Duplication · Edited copy of a member (16 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/util/CharSequences.kt
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/baidu/BaiduTranslator.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/microsoft/MicrosoftHttp.kt
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt
- Code Duplication · Edited copy of a member (7 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/TranslateService.kt
- Code Duplication · Duplicated block (7 lines × 2) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt
- Code Duplication · Duplicated block (5 lines × 2) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/text/ExampleDocument.kt
Fixed since the last survey: 3 findings
- Code Duplication · Duplicated block (5 lines × 2) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/text/ExampleDocument.kt
- Documentation (README) · README may be stale
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,800 to €44,000, for 146 to 464 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 27,384 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 trans.microsoft.models | 2 trans.openai.chat | 3 trans.text.TranslationDocument | 4 tts.sound.source | 5 util.Http | 6 util.credential | 7 openapi.data.AsyncExpiringData | 8 trans.openai.OpenAiSettings | 9 trans.openai.config.OpenAiRequestConfigService | 10 trans.youdao.YoudaoWebTranslationDocument | 11 ui.StyledViewer | 12 util | 13 openapi.data | 14 trans.text | 15 tts.sound | 16 ui.util | 17 wordbook | 18 tts | 19 ui.settings | 20 ui | 21 ui.wordbook | 22 service | 23 service.TranslationUIManager | 24 trans | 25 Presenter | 26 documentation | 27 trans.documentation | 28 trans.openai.config | 29 trans.openai.prompt | 30 tts.microsoft | 31 cn.yiiguxing.plugin.translate | 32 documentation.actions.FileInlineDocumentationTranslateActionProvider | 33 trans.ali | 34 trans.deepl | 35 trans.google | 36 trans.microsoft | 37 trans.openai | 38 action | 39 trans.openai.ui | 40 trans.youdao |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 trans.microsoft.models | ||||||||||||||||||||||||||||||||||||||||
| 2 trans.openai.chat | ||||||||||||||||||||||||||||||||||||||||
| 3 trans.text.TranslationDocument | ||||||||||||||||||||||||||||||||||||||||
| 4 tts.sound.source | ||||||||||||||||||||||||||||||||||||||||
| 5 util.Http | ||||||||||||||||||||||||||||||||||||||||
| 6 util.credential | ||||||||||||||||||||||||||||||||||||||||
| 7 openapi.data.AsyncExpiringData | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 trans.openai.OpenAiSettings | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 trans.openai.config.OpenAiRequestConfigService | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 trans.youdao.YoudaoWebTranslationDocument | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 ui.StyledViewer | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 openapi.data | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 trans.text | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 15 tts.sound | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 16 ui.util | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 wordbook | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 tts | 2 | 7 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 ui.settings | 1 | 1 | 4 | 6 | ||||||||||||||||||||||||||||||||||||
| 20 ui | 2 | 1 | 2 | 2 | 2 | 19 | 2 | 15 | ||||||||||||||||||||||||||||||||
| 21 ui.wordbook | 1 | 7 | 5 | |||||||||||||||||||||||||||||||||||||
| 22 service | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 23 service.TranslationUIManager | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 trans | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 Presenter | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 documentation | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 trans.documentation | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 trans.openai.config | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 trans.openai.prompt | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 tts.microsoft | 1 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 31 cn.yiiguxing.plugin.translate | 1 | 1 | 2 | 2 | 1 | 13 | 2 | |||||||||||||||||||||||||||||||||
| 32 documentation.actions.FileInlineDocumentationTranslateActionProvider | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 trans.ali | 1 | 9 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 trans.deepl | 1 | 1 | 11 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 trans.google | 2 | 2 | 13 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 trans.microsoft | 19 | 2 | 1 | 1 | 1 | 2 | 21 | 4 | ||||||||||||||||||||||||||||||||
| 37 trans.openai | 3 | 1 | 1 | 2 | 8 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||
| 38 action | 7 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 39 trans.openai.ui | 3 | 1 | 11 | |||||||||||||||||||||||||||||||||||||
| 40 trans.youdao | 1 | 2 | 2 | 11 | 1 | 1 |
7→13 openapi.data.AsyncExpiringData uses openapi.data part of a loop✕
- Connections
- 1 pair of types, where a type in openapi.data.AsyncExpiringData uses a type in openapi.data.
- The types involved
cn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData.Entry→cn.yiiguxing.plugin.translate.openapi.data.CachePolicy
- Direction
- openapi.data.AsyncExpiringData uses openapi.data, so a change to openapi.data can break openapi.data.AsyncExpiringData, while a change to openapi.data.AsyncExpiringData can't break openapi.data.
- 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.
8→37 trans.openai.OpenAiSettings uses trans.openai part of a loop✕
- Connections
- 4 pairs of types, where a type in trans.openai.OpenAiSettings uses a type in trans.openai.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.Azure→cn.yiiguxing.plugin.translate.trans.openai.AzureServiceVersioncn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.CommonState→cn.yiiguxing.plugin.translate.trans.openai.OpenAiTTSModelcn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.CommonState→cn.yiiguxing.plugin.translate.trans.openai.OpenAiTtsVoicecn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.OpenAi→cn.yiiguxing.plugin.translate.trans.openai.OpenAiGPTModel
- Direction
- trans.openai.OpenAiSettings uses trans.openai, so a change to trans.openai can break trans.openai.OpenAiSettings, while a change to trans.openai.OpenAiSettings can't break trans.openai.
- 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.
9→28 trans.openai.config.OpenAiRequestConfigService uses trans.openai.config part of a loop✕
- Connections
- 1 pair of types, where a type in trans.openai.config.OpenAiRequestConfigService uses a type in trans.openai.config.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService.CachedConfig→cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfig
- Direction
- trans.openai.config.OpenAiRequestConfigService uses trans.openai.config, so a change to trans.openai.config can break trans.openai.config.OpenAiRequestConfigService, while a change to trans.openai.config.OpenAiRequestConfigService can't break trans.openai.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→3 trans.youdao.YoudaoWebTranslationDocument uses trans.text.TranslationDocument✕
- Connections
- 1 pair of types, where a type in trans.youdao.YoudaoWebTranslationDocument uses a type in trans.text.TranslationDocument.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument.Factory→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument.Factory
- Direction
- trans.youdao.YoudaoWebTranslationDocument uses trans.text.TranslationDocument, so a change to trans.text.TranslationDocument can break trans.youdao.YoudaoWebTranslationDocument, while a change to trans.youdao.YoudaoWebTranslationDocument can't break trans.text.TranslationDocument.
- Position
- Below the diagonal: trans.youdao.YoudaoWebTranslationDocument uses a module listed above it, which is the healthy direction.
10→40 trans.youdao.YoudaoWebTranslationDocument uses trans.youdao part of a loop✕
- Connections
- 2 pairs of types, where a type in trans.youdao.YoudaoWebTranslationDocument uses a type in trans.youdao.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument.Factory→cn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslationcn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument.Factory→cn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument
- Direction
- trans.youdao.YoudaoWebTranslationDocument uses trans.youdao, so a change to trans.youdao can break trans.youdao.YoudaoWebTranslationDocument, while a change to trans.youdao.YoudaoWebTranslationDocument can't break trans.youdao.
- 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→20 ui.StyledViewer uses ui part of a loop✕
- Connections
- 3 pairs of types, where a type in ui.StyledViewer uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.ui.StyledViewer.ColoredMouseListener→cn.yiiguxing.plugin.translate.ui.StyledViewercn.yiiguxing.plugin.translate.ui.StyledViewer.FoldingMouseListener→cn.yiiguxing.plugin.translate.ui.StyledViewercn.yiiguxing.plugin.translate.ui.StyledViewer.MouseListener→cn.yiiguxing.plugin.translate.ui.StyledViewer
- Direction
- ui.StyledViewer uses ui, so a change to ui can break ui.StyledViewer, while a change to ui.StyledViewer can't break ui.
- 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→24 ui.StyledViewer uses trans part of a loop✕
- Connections
- 2 pairs of types, where a type in ui.StyledViewer uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.ui.StyledViewer.Companion→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.StyledViewer.Companion→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- ui.StyledViewer uses trans, so a change to trans can break ui.StyledViewer, while a change to ui.StyledViewer can't break trans.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→5 util uses util.Http✕
- Connections
- 1 pair of types, where a type in util uses a type in util.Http.
- The types involved
cn.yiiguxing.plugin.translate.util.Http→cn.yiiguxing.plugin.translate.util.Http.SendResult
- Direction
- util uses util.Http, so a change to util.Http can break util, while a change to util can't break util.Http.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
12→24 util uses trans part of a loop✕
- Connections
- 1 pair of types, where a type in util uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.util.LanguageTypeAdapter→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- util uses trans, so a change to trans can break util, while a change to util can't break trans.
- 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.
13→7 openapi.data uses openapi.data.AsyncExpiringData✕
- Connections
- 3 pairs of types, where a type in openapi.data uses a type in openapi.data.AsyncExpiringData.
- The types involved
cn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData→cn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData.Entrycn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData→cn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData.EntryStatecn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData→cn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData.Loading
- Direction
- openapi.data uses openapi.data.AsyncExpiringData, so a change to openapi.data.AsyncExpiringData can break openapi.data, while a change to openapi.data can't break openapi.data.AsyncExpiringData.
- Position
- Below the diagonal: openapi.data uses a module listed above it, which is the healthy direction.
14→11 trans.text uses ui.StyledViewer✕
- Connections
- 2 pairs of types, where a type in trans.text uses a type in ui.StyledViewer.
- The types involved
cn.yiiguxing.plugin.translate.trans.text.DictionaryKt→cn.yiiguxing.plugin.translate.ui.StyledViewer.FoldingMouseListenercn.yiiguxing.plugin.translate.trans.text.ExampleDocument→cn.yiiguxing.plugin.translate.ui.StyledViewer.FoldingMouseListener
- Direction
- trans.text uses ui.StyledViewer, so a change to ui.StyledViewer can break trans.text, while a change to trans.text can't break ui.StyledViewer.
- Position
- Below the diagonal: trans.text uses a module listed above it, which is the healthy direction.
14→20 trans.text uses ui part of a loop✕
- Connections
- 4 pairs of types, where a type in trans.text uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.trans.text.DictionaryDocument→cn.yiiguxing.plugin.translate.ui.StyledViewercn.yiiguxing.plugin.translate.trans.text.ExampleDocument→cn.yiiguxing.plugin.translate.ui.StyledViewercn.yiiguxing.plugin.translate.trans.text.NamedTranslationDocument→cn.yiiguxing.plugin.translate.ui.StyledViewercn.yiiguxing.plugin.translate.trans.text.TranslationDocument→cn.yiiguxing.plugin.translate.ui.StyledViewer
- Direction
- trans.text uses ui, so a change to ui can break trans.text, while a change to trans.text can't break ui.
- 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.
15→4 tts.sound uses tts.sound.source✕
- Connections
- 1 pair of types, where a type in tts.sound uses a type in tts.sound.source.
- The types involved
cn.yiiguxing.plugin.translate.tts.sound.AudioPlayer→cn.yiiguxing.plugin.translate.tts.sound.source.PlaybackSource
- Direction
- tts.sound uses tts.sound.source, so a change to tts.sound.source can break tts.sound, while a change to tts.sound can't break tts.sound.source.
- Position
- Below the diagonal: tts.sound uses a module listed above it, which is the healthy direction.
15→12 tts.sound uses util✕
- Connections
- 3 pairs of types, where a type in tts.sound uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.tts.sound.AudioPlayer→cn.yiiguxing.plugin.translate.util.Observablecn.yiiguxing.plugin.translate.tts.sound.AudioPlayer→cn.yiiguxing.plugin.translate.util.ObservableValuecn.yiiguxing.plugin.translate.tts.sound.PlaybackController→cn.yiiguxing.plugin.translate.util.Observable
- Direction
- tts.sound uses util, so a change to util can break tts.sound, while a change to tts.sound can't break util.
- Position
- Below the diagonal: tts.sound uses a module listed above it, which is the healthy direction.
16→6 ui.util uses util.credential✕
- Connections
- 1 pair of types, where a type in ui.util uses a type in util.credential.
- The types involved
cn.yiiguxing.plugin.translate.ui.util.CredentialEditor→cn.yiiguxing.plugin.translate.util.credential.StringCredentialManager
- Direction
- ui.util uses util.credential, so a change to util.credential can break ui.util, while a change to ui.util can't break util.credential.
- Position
- Below the diagonal: ui.util uses a module listed above it, which is the healthy direction.
16→12 ui.util uses util✕
- Connections
- 2 pairs of types, where a type in ui.util uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.ui.util.CredentialEditor→cn.yiiguxing.plugin.translate.util.Observablecn.yiiguxing.plugin.translate.ui.util.CredentialEditor→cn.yiiguxing.plugin.translate.util.WritableObservable
- Direction
- ui.util uses util, so a change to util can break ui.util, while a change to ui.util can't break util.
- Position
- Below the diagonal: ui.util uses a module listed above it, which is the healthy direction.
17→12 wordbook uses util✕
- Connections
- 3 pairs of types, where a type in wordbook uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.wordbook.WordBookService→cn.yiiguxing.plugin.translate.util.Observablecn.yiiguxing.plugin.translate.wordbook.WordBookService→cn.yiiguxing.plugin.translate.util.ObservableValuecn.yiiguxing.plugin.translate.wordbook.WordBookView→cn.yiiguxing.plugin.translate.util.ObservableValue
- Direction
- wordbook uses util, so a change to util can break wordbook, while a change to wordbook can't break util.
- Position
- Below the diagonal: wordbook uses a module listed above it, which is the healthy direction.
17→21 wordbook uses ui.wordbook part of a loop✕
- Connections
- 1 pair of types, where a type in wordbook uses a type in ui.wordbook.
- The types involved
cn.yiiguxing.plugin.translate.wordbook.WordBookView→cn.yiiguxing.plugin.translate.ui.wordbook.WordBookWindowComponent
- Direction
- wordbook uses ui.wordbook, so a change to ui.wordbook can break wordbook, while a change to wordbook can't break ui.wordbook.
- 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.
17→24 wordbook uses trans part of a loop✕
- Connections
- 2 pairs of types, where a type in wordbook uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.wordbook.WordBookItem→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.wordbook.WordBookService→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- wordbook uses trans, so a change to trans can break wordbook, while a change to wordbook can't break trans.
- 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.
18→12 tts uses util✕
- Connections
- 2 pairs of types, where a type in tts uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.tts.GoogleTTSPlayer→cn.yiiguxing.plugin.translate.util.Observablecn.yiiguxing.plugin.translate.tts.OpenAiTTSPlayer→cn.yiiguxing.plugin.translate.util.Observable
- Direction
- tts uses util, so a change to util can break tts, while a change to tts can't break util.
- Position
- Below the diagonal: tts uses a module listed above it, which is the healthy direction.
18→15 tts uses tts.sound✕
- Connections
- 7 pairs of types, where a type in tts uses a type in tts.sound.
- The types involved
cn.yiiguxing.plugin.translate.tts.GoogleTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.AudioPlayercn.yiiguxing.plugin.translate.tts.GoogleTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.PlaybackControllercn.yiiguxing.plugin.translate.tts.GoogleTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.PlaybackStatuscn.yiiguxing.plugin.translate.tts.OpenAiTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.AudioPlayercn.yiiguxing.plugin.translate.tts.OpenAiTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.PlaybackControllercn.yiiguxing.plugin.translate.tts.OpenAiTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.PlaybackStatuscn.yiiguxing.plugin.translate.tts.TextToSpeech→cn.yiiguxing.plugin.translate.tts.sound.PlaybackController
- Direction
- tts uses tts.sound, so a change to tts.sound can break tts, while a change to tts can't break tts.sound.
- Position
- Below the diagonal: tts uses a module listed above it, which is the healthy direction.
18→24 tts uses trans part of a loop✕
- Connections
- 2 pairs of types, where a type in tts uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.tts.GoogleTTSPlayer→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.tts.TextToSpeech→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- tts uses trans, so a change to trans can break tts, while a change to tts can't break trans.
- 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.
18→31 tts uses cn.yiiguxing.plugin.translate part of a loop✕
- Connections
- 1 pair of types, where a type in tts uses a type in cn.yiiguxing.plugin.translate.
- The types involved
cn.yiiguxing.plugin.translate.tts.TextToSpeech→cn.yiiguxing.plugin.translate.Settings
- Direction
- tts uses cn.yiiguxing.plugin.translate, so a change to cn.yiiguxing.plugin.translate can break tts, while a change to tts can't break cn.yiiguxing.plugin.translate.
- 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→18 ui.settings uses tts✕
- Connections
- 1 pair of types, where a type in ui.settings uses a type in tts.
- The types involved
cn.yiiguxing.plugin.translate.ui.settings.SettingsUi→cn.yiiguxing.plugin.translate.tts.TTSEngine
- Direction
- ui.settings uses tts, so a change to tts can break ui.settings, while a change to ui.settings can't break tts.
- Position
- Below the diagonal: ui.settings uses a module listed above it, which is the healthy direction.
19→20 ui.settings uses ui part of a loop✕
- Connections
- 1 pair of types, where a type in ui.settings uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.ui.settings.SettingsUi→cn.yiiguxing.plugin.translate.ui.WindowLocation
- Direction
- ui.settings uses ui, so a change to ui can break ui.settings, while a change to ui.settings can't break ui.
- 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→24 ui.settings uses trans part of a loop✕
- Connections
- 4 pairs of types, where a type in ui.settings uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.ui.settings.LanguageSelectionComboBox→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.settings.SettingsUi→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.settings.TranslationEngine→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.settings.TranslationEngine→cn.yiiguxing.plugin.translate.trans.Translator
- Direction
- ui.settings uses trans, so a change to trans can break ui.settings, while a change to ui.settings can't break trans.
- 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→31 ui.settings uses cn.yiiguxing.plugin.translate part of a loop✕
- Connections
- 6 pairs of types, where a type in ui.settings uses a type in cn.yiiguxing.plugin.translate.
- The types involved
cn.yiiguxing.plugin.translate.ui.settings.LanguageSelectionComboBox→cn.yiiguxing.plugin.translate.LanguageSelectioncn.yiiguxing.plugin.translate.ui.settings.SettingsPanel→cn.yiiguxing.plugin.translate.Settingscn.yiiguxing.plugin.translate.ui.settings.SettingsPanel→cn.yiiguxing.plugin.translate.TranslationStatescn.yiiguxing.plugin.translate.ui.settings.SettingsUi→cn.yiiguxing.plugin.translate.TTSSourcecn.yiiguxing.plugin.translate.ui.settings.TranslationEngine→cn.yiiguxing.plugin.translate.AppKeySettingscn.yiiguxing.plugin.translate.ui.settings.WordbookStoragePathBrowser→cn.yiiguxing.plugin.translate.Settings
- Direction
- ui.settings uses cn.yiiguxing.plugin.translate, so a change to cn.yiiguxing.plugin.translate can break ui.settings, while a change to ui.settings can't break cn.yiiguxing.plugin.translate.
- 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.
20→14 ui uses trans.text✕
- Connections
- 2 pairs of types, where a type in ui uses a type in trans.text.
- The types involved
cn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.trans.text.NamedTranslationDocumentcn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument
- Direction
- ui uses trans.text, so a change to trans.text can break ui, while a change to ui can't break trans.text.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
20→15 ui uses tts.sound✕
- Connections
- 1 pair of types, where a type in ui uses a type in tts.sound.
- The types involved
cn.yiiguxing.plugin.translate.ui.TTSButton→cn.yiiguxing.plugin.translate.tts.sound.PlaybackController
- Direction
- ui uses tts.sound, so a change to tts.sound can break ui, while a change to ui can't break tts.sound.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
20→16 ui uses ui.util✕
- Connections
- 2 pairs of types, where a type in ui uses a type in ui.util.
- The types involved
cn.yiiguxing.plugin.translate.ui.TranslationDialogUI→cn.yiiguxing.plugin.translate.ui.util.ScrollSynchronizercn.yiiguxing.plugin.translate.ui.TranslationDialogUiImpl→cn.yiiguxing.plugin.translate.ui.util.ScrollSynchronizer
- Direction
- ui uses ui.util, so a change to ui.util can break ui, while a change to ui can't break ui.util.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
20→18 ui uses tts✕
- Connections
- 2 pairs of types, where a type in ui uses a type in tts.
- The types involved
cn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.tts.TTSEnginecn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.tts.TTSEngine
- Direction
- ui uses tts, so a change to tts can break ui, while a change to ui can't break tts.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
20→19 ui uses ui.settings✕
- Connections
- 2 pairs of types, where a type in ui uses a type in ui.settings.
- The types involved
cn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.ui.settings.TranslationEnginecn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.ui.settings.TranslationEngine
- Direction
- ui uses ui.settings, so a change to ui.settings can break ui, while a change to ui can't break ui.settings.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
20→24 ui uses trans part of a loop✕
- Connections
- 19 pairs of types, where a type in ui uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.ui.BalloonTranslationPane→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.FixLangComponent→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.FixLangComponent→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.ui.HistoryRenderer→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.LangComboBoxLink→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.LanguageListModel→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.LanguageSelectPopupUI→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.SimpleLanguageListModel→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.SortedLanguageListModel→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.TTSButton→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.ui.TranslationDialogUI→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.ui.TranslationDialogUiImpl→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.ui.TranslationPane→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.ui.TranslationPane→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.ui.WordFavoritesUi→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- ui uses trans, so a change to trans can break ui, while a change to ui can't break trans.
- 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.
20→25 ui uses Presenter part of a loop✕
- Connections
- 2 pairs of types, where a type in ui uses a type in Presenter.
- The types involved
cn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.Presenter.Requestcn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.Presenter.Request
- Direction
- ui uses Presenter, so a change to Presenter can break ui, while a change to ui can't break Presenter.
- 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.
20→31 ui uses cn.yiiguxing.plugin.translate part of a loop✕
- Connections
- 15 pairs of types, where a type in ui uses a type in cn.yiiguxing.plugin.translate.
- The types involved
cn.yiiguxing.plugin.translate.ui.AppKeySettingsDialog→cn.yiiguxing.plugin.translate.HelpTopiccn.yiiguxing.plugin.translate.ui.AppKeySettingsPanel→cn.yiiguxing.plugin.translate.AppKeySettingscn.yiiguxing.plugin.translate.ui.BalloonTranslationPane→cn.yiiguxing.plugin.translate.Settingscn.yiiguxing.plugin.translate.ui.HistoryRenderer→cn.yiiguxing.plugin.translate.Presentercn.yiiguxing.plugin.translate.ui.SortedLanguageListModel→cn.yiiguxing.plugin.translate.TranslationStatescn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.Presentercn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.Settingscn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.SettingsChangeListenercn.yiiguxing.plugin.translate.ui.TranslationBalloon→cn.yiiguxing.plugin.translate.Viewcn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.Presentercn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.Settingscn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.SettingsChangeListenercn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.TranslationStatescn.yiiguxing.plugin.translate.ui.TranslationDialog→cn.yiiguxing.plugin.translate.Viewcn.yiiguxing.plugin.translate.ui.TranslationPane→cn.yiiguxing.plugin.translate.Settings
- Direction
- ui uses cn.yiiguxing.plugin.translate, so a change to cn.yiiguxing.plugin.translate can break ui, while a change to ui can't break cn.yiiguxing.plugin.translate.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→12 ui.wordbook uses util✕
- Connections
- 1 pair of types, where a type in ui.wordbook uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.ui.wordbook.WordBookWindowComponent→cn.yiiguxing.plugin.translate.util.Observable
- Direction
- ui.wordbook uses util, so a change to util can break ui.wordbook, while a change to ui.wordbook can't break util.
- Position
- Below the diagonal: ui.wordbook uses a module listed above it, which is the healthy direction.
21→17 ui.wordbook uses wordbook✕
- Connections
- 7 pairs of types, where a type in ui.wordbook uses a type in wordbook.
- The types involved
cn.yiiguxing.plugin.translate.ui.wordbook.ExplainsColumnInfo→cn.yiiguxing.plugin.translate.wordbook.WordBookItemcn.yiiguxing.plugin.translate.ui.wordbook.WordBookTableView→cn.yiiguxing.plugin.translate.wordbook.WordBookItemcn.yiiguxing.plugin.translate.ui.wordbook.WordBookWindowComponent→cn.yiiguxing.plugin.translate.wordbook.WordBookItemcn.yiiguxing.plugin.translate.ui.wordbook.WordBookWindowComponent→cn.yiiguxing.plugin.translate.wordbook.WordBookStatecn.yiiguxing.plugin.translate.ui.wordbook.WordColumnInfo→cn.yiiguxing.plugin.translate.wordbook.WordBookItemcn.yiiguxing.plugin.translate.ui.wordbook.WordDetailsDialog→cn.yiiguxing.plugin.translate.wordbook.WordBookItemcn.yiiguxing.plugin.translate.ui.wordbook.WordOfTheDayDialog→cn.yiiguxing.plugin.translate.wordbook.WordBookItem
- Direction
- ui.wordbook uses wordbook, so a change to wordbook can break ui.wordbook, while a change to ui.wordbook can't break wordbook.
- Position
- Below the diagonal: ui.wordbook uses a module listed above it, which is the healthy direction.
21→20 ui.wordbook uses ui✕
- Connections
- 5 pairs of types, where a type in ui.wordbook uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.ui.wordbook.WordBookWindowComponent→cn.yiiguxing.plugin.translate.ui.LoadingPanelcn.yiiguxing.plugin.translate.ui.wordbook.WordDetailsUI→cn.yiiguxing.plugin.translate.ui.TTSButtoncn.yiiguxing.plugin.translate.ui.wordbook.WordDetailsUI→cn.yiiguxing.plugin.translate.ui.Viewercn.yiiguxing.plugin.translate.ui.wordbook.WordOfTheDayDialog→cn.yiiguxing.plugin.translate.ui.TTSButtoncn.yiiguxing.plugin.translate.ui.wordbook.WordOfTheDayDialog→cn.yiiguxing.plugin.translate.ui.Viewer
- Direction
- ui.wordbook uses ui, so a change to ui can break ui.wordbook, while a change to ui.wordbook can't break ui.
- Position
- Below the diagonal: ui.wordbook uses a module listed above it, which is the healthy direction.
22→12 service uses util✕
- Connections
- 1 pair of types, where a type in service uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.service.CacheService→cn.yiiguxing.plugin.translate.util.LruCache
- Direction
- service uses util, so a change to util can break service, while a change to service can't break util.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
22→20 service uses ui✕
- Connections
- 2 pairs of types, where a type in service uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.service.TranslationUIManager→cn.yiiguxing.plugin.translate.ui.TranslationBallooncn.yiiguxing.plugin.translate.service.TranslationUIManager→cn.yiiguxing.plugin.translate.ui.TranslationDialog
- Direction
- service uses ui, so a change to ui can break service, while a change to service can't break ui.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
22→21 service uses ui.wordbook✕
- Connections
- 1 pair of types, where a type in service uses a type in ui.wordbook.
- The types involved
cn.yiiguxing.plugin.translate.service.TranslationUIManager→cn.yiiguxing.plugin.translate.ui.wordbook.WordOfTheDayDialog
- Direction
- service uses ui.wordbook, so a change to ui.wordbook can break service, while a change to service can't break ui.wordbook.
- Position
- Below the diagonal: service uses a module listed above it, which is the healthy direction.
22→24 service uses trans part of a loop✕
- Connections
- 2 pairs of types, where a type in service uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.service.CacheService→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.service.CacheService→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- service uses trans, so a change to trans can break service, while a change to service can't break trans.
- 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.
23→17 service.TranslationUIManager uses wordbook✕
- Connections
- 1 pair of types, where a type in service.TranslationUIManager uses a type in wordbook.
- The types involved
cn.yiiguxing.plugin.translate.service.TranslationUIManager.Companion→cn.yiiguxing.plugin.translate.wordbook.WordBookItem
- Direction
- service.TranslationUIManager uses wordbook, so a change to wordbook can break service.TranslationUIManager, while a change to service.TranslationUIManager can't break wordbook.
- Position
- Below the diagonal: service.TranslationUIManager uses a module listed above it, which is the healthy direction.
23→20 service.TranslationUIManager uses ui✕
- Connections
- 2 pairs of types, where a type in service.TranslationUIManager uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.service.TranslationUIManager.Companion→cn.yiiguxing.plugin.translate.ui.TranslationBallooncn.yiiguxing.plugin.translate.service.TranslationUIManager.Companion→cn.yiiguxing.plugin.translate.ui.TranslationDialog
- Direction
- service.TranslationUIManager uses ui, so a change to ui can break service.TranslationUIManager, while a change to service.TranslationUIManager can't break ui.
- Position
- Below the diagonal: service.TranslationUIManager uses a module listed above it, which is the healthy direction.
23→21 service.TranslationUIManager uses ui.wordbook✕
- Connections
- 1 pair of types, where a type in service.TranslationUIManager uses a type in ui.wordbook.
- The types involved
cn.yiiguxing.plugin.translate.service.TranslationUIManager.Companion→cn.yiiguxing.plugin.translate.ui.wordbook.WordOfTheDayDialog
- Direction
- service.TranslationUIManager uses ui.wordbook, so a change to ui.wordbook can break service.TranslationUIManager, while a change to service.TranslationUIManager can't break ui.wordbook.
- Position
- Below the diagonal: service.TranslationUIManager uses a module listed above it, which is the healthy direction.
23→22 service.TranslationUIManager uses service✕
- Connections
- 1 pair of types, where a type in service.TranslationUIManager uses a type in service.
- The types involved
cn.yiiguxing.plugin.translate.service.TranslationUIManager.Companion→cn.yiiguxing.plugin.translate.service.TranslationUIManager
- Direction
- service.TranslationUIManager uses service, so a change to service can break service.TranslationUIManager, while a change to service.TranslationUIManager can't break service.
- Position
- Below the diagonal: service.TranslationUIManager uses a module listed above it, which is the healthy direction.
24→12 trans uses util✕
- Connections
- 1 pair of types, where a type in trans uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.trans.Translation→cn.yiiguxing.plugin.translate.util.ObservableValue
- Direction
- trans uses util, so a change to util can break trans, while a change to trans can't break util.
- Position
- Below the diagonal: trans uses a module listed above it, which is the healthy direction.
24→14 trans uses trans.text✕
- Connections
- 2 pairs of types, where a type in trans uses a type in trans.text.
- The types involved
cn.yiiguxing.plugin.translate.trans.Translation→cn.yiiguxing.plugin.translate.trans.text.NamedTranslationDocumentcn.yiiguxing.plugin.translate.trans.Translation→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument
- Direction
- trans uses trans.text, so a change to trans.text can break trans, while a change to trans can't break trans.text.
- Position
- Below the diagonal: trans uses a module listed above it, which is the healthy direction.
24→17 trans uses wordbook✕
- Connections
- 1 pair of types, where a type in trans uses a type in wordbook.
- The types involved
cn.yiiguxing.plugin.translate.trans.TranslateService→cn.yiiguxing.plugin.translate.wordbook.WordBookItem
- Direction
- trans uses wordbook, so a change to wordbook can break trans, while a change to trans can't break wordbook.
- Position
- Below the diagonal: trans uses a module listed above it, which is the healthy direction.
24→19 trans uses ui.settings✕
- Connections
- 1 pair of types, where a type in trans uses a type in ui.settings.
- The types involved
cn.yiiguxing.plugin.translate.trans.TranslateService→cn.yiiguxing.plugin.translate.ui.settings.TranslationEngine
- Direction
- trans uses ui.settings, so a change to ui.settings can break trans, while a change to trans can't break ui.settings.
- Position
- Below the diagonal: trans uses a module listed above it, which is the healthy direction.
24→22 trans uses service✕
- Connections
- 1 pair of types, where a type in trans uses a type in service.
- The types involved
cn.yiiguxing.plugin.translate.trans.TranslateService→cn.yiiguxing.plugin.translate.service.CacheService
- Direction
- trans uses service, so a change to service can break trans, while a change to trans can't break service.
- Position
- Below the diagonal: trans uses a module listed above it, which is the healthy direction.
24→31 trans uses cn.yiiguxing.plugin.translate part of a loop✕
- Connections
- 1 pair of types, where a type in trans uses a type in cn.yiiguxing.plugin.translate.
- The types involved
cn.yiiguxing.plugin.translate.trans.LanguageBundle→cn.yiiguxing.plugin.translate.TranslationDynamicBundle
- Direction
- trans uses cn.yiiguxing.plugin.translate, so a change to cn.yiiguxing.plugin.translate can break trans, while a change to trans can't break cn.yiiguxing.plugin.translate.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→24 Presenter uses trans✕
- Connections
- 1 pair of types, where a type in Presenter uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.Presenter.Request→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- Presenter uses trans, so a change to trans can break Presenter, while a change to Presenter can't break trans.
- Position
- Below the diagonal: Presenter uses a module listed above it, which is the healthy direction.
26→24 documentation uses trans✕
- Connections
- 2 pairs of types, where a type in documentation uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.documentation.InlineDocTranslationInfo→cn.yiiguxing.plugin.translate.trans.Translatorcn.yiiguxing.plugin.translate.documentation.InlineDocumentationTranslationsKt→cn.yiiguxing.plugin.translate.trans.Translator
- Direction
- documentation uses trans, so a change to trans can break documentation, while a change to documentation can't break trans.
- Position
- Below the diagonal: documentation uses a module listed above it, which is the healthy direction.
27→24 trans.documentation uses trans✕
- Connections
- 1 pair of types, where a type in trans.documentation uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- trans.documentation uses trans, so a change to trans can break trans.documentation, while a change to trans.documentation can't break trans.
- Position
- Below the diagonal: trans.documentation uses a module listed above it, which is the healthy direction.
28→2 trans.openai.config uses trans.openai.chat✕
- Connections
- 1 pair of types, where a type in trans.openai.config uses a type in trans.openai.chat.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigKt→cn.yiiguxing.plugin.translate.trans.openai.chat.ChatMessage
- Direction
- trans.openai.config uses trans.openai.chat, so a change to trans.openai.chat can break trans.openai.config, while a change to trans.openai.config can't break trans.openai.chat.
- Position
- Below the diagonal: trans.openai.config uses a module listed above it, which is the healthy direction.
28→9 trans.openai.config uses trans.openai.config.OpenAiRequestConfigService✕
- Connections
- 2 pairs of types, where a type in trans.openai.config uses a type in trans.openai.config.OpenAiRequestConfigService.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService→cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService.CachedConfigcn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService→cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService.PromptKind
- Direction
- trans.openai.config uses trans.openai.config.OpenAiRequestConfigService, so a change to trans.openai.config.OpenAiRequestConfigService can break trans.openai.config, while a change to trans.openai.config can't break trans.openai.config.OpenAiRequestConfigService.
- Position
- Below the diagonal: trans.openai.config uses a module listed above it, which is the healthy direction.
28→24 trans.openai.config uses trans✕
- Connections
- 2 pairs of types, where a type in trans.openai.config uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigResolver→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- trans.openai.config uses trans, so a change to trans can break trans.openai.config, while a change to trans.openai.config can't break trans.
- Position
- Below the diagonal: trans.openai.config uses a module listed above it, which is the healthy direction.
28→37 trans.openai.config uses trans.openai part of a loop✕
- Connections
- 1 pair of types, where a type in trans.openai.config uses a type in trans.openai.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService→cn.yiiguxing.plugin.translate.trans.openai.ChatRequestContext
- Direction
- trans.openai.config uses trans.openai, so a change to trans.openai can break trans.openai.config, while a change to trans.openai.config can't break trans.openai.
- 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.
29→2 trans.openai.prompt uses trans.openai.chat✕
- Connections
- 1 pair of types, where a type in trans.openai.prompt uses a type in trans.openai.chat.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.prompt.Prompt→cn.yiiguxing.plugin.translate.trans.openai.chat.ChatMessage
- Direction
- trans.openai.prompt uses trans.openai.chat, so a change to trans.openai.chat can break trans.openai.prompt, while a change to trans.openai.prompt can't break trans.openai.chat.
- Position
- Below the diagonal: trans.openai.prompt uses a module listed above it, which is the healthy direction.
29→9 trans.openai.prompt uses trans.openai.config.OpenAiRequestConfigService✕
- Connections
- 1 pair of types, where a type in trans.openai.prompt uses a type in trans.openai.config.OpenAiRequestConfigService.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.prompt.PromptService→cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService.PromptKind
- Direction
- trans.openai.prompt uses trans.openai.config.OpenAiRequestConfigService, so a change to trans.openai.config.OpenAiRequestConfigService can break trans.openai.prompt, while a change to trans.openai.prompt can't break trans.openai.config.OpenAiRequestConfigService.
- Position
- Below the diagonal: trans.openai.prompt uses a module listed above it, which is the healthy direction.
29→24 trans.openai.prompt uses trans✕
- Connections
- 2 pairs of types, where a type in trans.openai.prompt uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.prompt.PromptService→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.openai.prompt.PromptTemplate→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- trans.openai.prompt uses trans, so a change to trans can break trans.openai.prompt, while a change to trans.openai.prompt can't break trans.
- Position
- Below the diagonal: trans.openai.prompt uses a module listed above it, which is the healthy direction.
30→4 tts.microsoft uses tts.sound.source✕
- Connections
- 1 pair of types, where a type in tts.microsoft uses a type in tts.sound.source.
- The types involved
cn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSSource→cn.yiiguxing.plugin.translate.tts.sound.source.PushablePlaybackSource
- Direction
- tts.microsoft uses tts.sound.source, so a change to tts.sound.source can break tts.microsoft, while a change to tts.microsoft can't break tts.sound.source.
- Position
- Below the diagonal: tts.microsoft uses a module listed above it, which is the healthy direction.
30→12 tts.microsoft uses util✕
- Connections
- 1 pair of types, where a type in tts.microsoft uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSPlayer→cn.yiiguxing.plugin.translate.util.Observable
- Direction
- tts.microsoft uses util, so a change to util can break tts.microsoft, while a change to tts.microsoft can't break util.
- Position
- Below the diagonal: tts.microsoft uses a module listed above it, which is the healthy direction.
30→15 tts.microsoft uses tts.sound✕
- Connections
- 3 pairs of types, where a type in tts.microsoft uses a type in tts.sound.
- The types involved
cn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.AudioPlayercn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.PlaybackControllercn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSPlayer→cn.yiiguxing.plugin.translate.tts.sound.PlaybackStatus
- Direction
- tts.microsoft uses tts.sound, so a change to tts.sound can break tts.microsoft, while a change to tts.microsoft can't break tts.sound.
- Position
- Below the diagonal: tts.microsoft uses a module listed above it, which is the healthy direction.
30→24 tts.microsoft uses trans✕
- Connections
- 3 pairs of types, where a type in tts.microsoft uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSPlayer→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSSource→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.tts.microsoft.EdgeTTSVoiceManager→cn.yiiguxing.plugin.translate.trans.Lang
- Direction
- tts.microsoft uses trans, so a change to trans can break tts.microsoft, while a change to tts.microsoft can't break trans.
- Position
- Below the diagonal: tts.microsoft uses a module listed above it, which is the healthy direction.
31→6 cn.yiiguxing.plugin.translate uses util.credential✕
- Connections
- 1 pair of types, where a type in cn.yiiguxing.plugin.translate uses a type in util.credential.
- The types involved
cn.yiiguxing.plugin.translate.AppKeySettings→cn.yiiguxing.plugin.translate.util.credential.SimpleStringCredentialManager
- Direction
- cn.yiiguxing.plugin.translate uses util.credential, so a change to util.credential can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break util.credential.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
31→12 cn.yiiguxing.plugin.translate uses util✕
- Connections
- 1 pair of types, where a type in cn.yiiguxing.plugin.translate uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.Settings→cn.yiiguxing.plugin.translate.util.SelectionMode
- Direction
- cn.yiiguxing.plugin.translate uses util, so a change to util can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break util.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
31→18 cn.yiiguxing.plugin.translate uses tts✕
- Connections
- 2 pairs of types, where a type in cn.yiiguxing.plugin.translate uses a type in tts.
- The types involved
cn.yiiguxing.plugin.translate.Settings→cn.yiiguxing.plugin.translate.tts.TTSEnginecn.yiiguxing.plugin.translate.SettingsChangeListener→cn.yiiguxing.plugin.translate.tts.TTSEngine
- Direction
- cn.yiiguxing.plugin.translate uses tts, so a change to tts can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break tts.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
31→19 cn.yiiguxing.plugin.translate uses ui.settings✕
- Connections
- 2 pairs of types, where a type in cn.yiiguxing.plugin.translate uses a type in ui.settings.
- The types involved
cn.yiiguxing.plugin.translate.Settings→cn.yiiguxing.plugin.translate.ui.settings.TranslationEnginecn.yiiguxing.plugin.translate.SettingsChangeListener→cn.yiiguxing.plugin.translate.ui.settings.TranslationEngine
- Direction
- cn.yiiguxing.plugin.translate uses ui.settings, so a change to ui.settings can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break ui.settings.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
31→20 cn.yiiguxing.plugin.translate uses ui✕
- Connections
- 1 pair of types, where a type in cn.yiiguxing.plugin.translate uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.Settings→cn.yiiguxing.plugin.translate.ui.WindowLocation
- Direction
- cn.yiiguxing.plugin.translate uses ui, so a change to ui can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break ui.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
31→24 cn.yiiguxing.plugin.translate uses trans✕
- Connections
- 13 pairs of types, where a type in cn.yiiguxing.plugin.translate uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.Presenter→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.Presenter→cn.yiiguxing.plugin.translate.trans.SupportedLanguagesDatacn.yiiguxing.plugin.translate.Presenter→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.Presenter→cn.yiiguxing.plugin.translate.trans.Translatorcn.yiiguxing.plugin.translate.Settings→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.TranslationPresenter→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.TranslationPresenter→cn.yiiguxing.plugin.translate.trans.SupportedLanguagesDatacn.yiiguxing.plugin.translate.TranslationPresenter→cn.yiiguxing.plugin.translate.trans.TranslateServicecn.yiiguxing.plugin.translate.TranslationPresenter→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.TranslationPresenter→cn.yiiguxing.plugin.translate.trans.Translatorcn.yiiguxing.plugin.translate.TranslationStates→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.TranslationStates→cn.yiiguxing.plugin.translate.trans.LanguagePaircn.yiiguxing.plugin.translate.View→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- cn.yiiguxing.plugin.translate uses trans, so a change to trans can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break trans.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
31→25 cn.yiiguxing.plugin.translate uses Presenter✕
- Connections
- 2 pairs of types, where a type in cn.yiiguxing.plugin.translate uses a type in Presenter.
- The types involved
cn.yiiguxing.plugin.translate.TranslationPresenter→cn.yiiguxing.plugin.translate.Presenter.Requestcn.yiiguxing.plugin.translate.View→cn.yiiguxing.plugin.translate.Presenter.Request
- Direction
- cn.yiiguxing.plugin.translate uses Presenter, so a change to Presenter can break cn.yiiguxing.plugin.translate, while a change to cn.yiiguxing.plugin.translate can't break Presenter.
- Position
- Below the diagonal: cn.yiiguxing.plugin.translate uses a module listed above it, which is the healthy direction.
32→12 documentation.actions.FileInlineDocumentationTranslateActionProvider uses util✕
- Connections
- 1 pair of types, where a type in documentation.actions.FileInlineDocumentationTranslateActionProvider uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.documentation.actions.FileInlineDocumentationTranslateActionProvider.FileInlineDocumentationTranslateAction→cn.yiiguxing.plugin.translate.util.RateLimiter
- Direction
- documentation.actions.FileInlineDocumentationTranslateActionProvider uses util, so a change to util can break documentation.actions.FileInlineDocumentationTranslateActionProvider, while a change to documentation.actions.FileInlineDocumentationTranslateActionProvider can't break util.
- Position
- Below the diagonal: documentation.actions.FileInlineDocumentationTranslateActionProvider uses a module listed above it, which is the healthy direction.
32→24 documentation.actions.FileInlineDocumentationTranslateActionProvider uses trans✕
- Connections
- 1 pair of types, where a type in documentation.actions.FileInlineDocumentationTranslateActionProvider uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.documentation.actions.FileInlineDocumentationTranslateActionProvider.FileInlineDocumentationTranslateAction→cn.yiiguxing.plugin.translate.trans.Translator
- Direction
- documentation.actions.FileInlineDocumentationTranslateActionProvider uses trans, so a change to trans can break documentation.actions.FileInlineDocumentationTranslateActionProvider, while a change to documentation.actions.FileInlineDocumentationTranslateActionProvider can't break trans.
- Position
- Below the diagonal: documentation.actions.FileInlineDocumentationTranslateActionProvider uses a module listed above it, which is the healthy direction.
32→26 documentation.actions.FileInlineDocumentationTranslateActionProvider uses documentation✕
- Connections
- 1 pair of types, where a type in documentation.actions.FileInlineDocumentationTranslateActionProvider uses a type in documentation.
- The types involved
cn.yiiguxing.plugin.translate.documentation.actions.FileInlineDocumentationTranslateActionProvider.FileInlineDocumentationTranslateAction→cn.yiiguxing.plugin.translate.documentation.InlineDocTranslationInfo
- Direction
- documentation.actions.FileInlineDocumentationTranslateActionProvider uses documentation, so a change to documentation can break documentation.actions.FileInlineDocumentationTranslateActionProvider, while a change to documentation.actions.FileInlineDocumentationTranslateActionProvider can't break documentation.
- Position
- Below the diagonal: documentation.actions.FileInlineDocumentationTranslateActionProvider uses a module listed above it, which is the healthy direction.
33→5 trans.ali uses util.Http✕
- Connections
- 1 pair of types, where a type in trans.ali uses a type in util.Http.
- The types involved
cn.yiiguxing.plugin.translate.trans.ali.AliTranslator→cn.yiiguxing.plugin.translate.util.Http.StatusException
- Direction
- trans.ali uses util.Http, so a change to util.Http can break trans.ali, while a change to trans.ali can't break util.Http.
- Position
- Below the diagonal: trans.ali uses a module listed above it, which is the healthy direction.
33→24 trans.ali uses trans✕
- Connections
- 9 pairs of types, where a type in trans.ali uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.ali.AliLanguageAdapter→cn.yiiguxing.plugin.translate.trans.BaseLanguageAdaptercn.yiiguxing.plugin.translate.trans.ali.AliLanguageAdapter→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.ali.AliLanguageAdapter→cn.yiiguxing.plugin.translate.trans.SupportedLanguagescn.yiiguxing.plugin.translate.trans.ali.AliLanguageAdapterKt→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.ali.AliTranslationResultException→cn.yiiguxing.plugin.translate.trans.TranslationResultExceptioncn.yiiguxing.plugin.translate.trans.ali.AliTranslator→cn.yiiguxing.plugin.translate.trans.AbstractTranslatorcn.yiiguxing.plugin.translate.trans.ali.AliTranslator→cn.yiiguxing.plugin.translate.trans.ErrorInfocn.yiiguxing.plugin.translate.trans.ali.AliTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.ali.AliTranslator→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- trans.ali uses trans, so a change to trans can break trans.ali, while a change to trans.ali can't break trans.
- Position
- Below the diagonal: trans.ali uses a module listed above it, which is the healthy direction.
33→27 trans.ali uses trans.documentation✕
- Connections
- 1 pair of types, where a type in trans.ali uses a type in trans.documentation.
- The types involved
cn.yiiguxing.plugin.translate.trans.ali.AliTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator
- Direction
- trans.ali uses trans.documentation, so a change to trans.documentation can break trans.ali, while a change to trans.ali can't break trans.documentation.
- Position
- Below the diagonal: trans.ali uses a module listed above it, which is the healthy direction.
34→6 trans.deepl uses util.credential✕
- Connections
- 1 pair of types, where a type in trans.deepl uses a type in util.credential.
- The types involved
cn.yiiguxing.plugin.translate.trans.deepl.DeeplCredential→cn.yiiguxing.plugin.translate.util.credential.StringCredentialManager
- Direction
- trans.deepl uses util.credential, so a change to util.credential can break trans.deepl, while a change to trans.deepl can't break util.credential.
- Position
- Below the diagonal: trans.deepl uses a module listed above it, which is the healthy direction.
34→16 trans.deepl uses ui.util✕
- Connections
- 1 pair of types, where a type in trans.deepl uses a type in ui.util.
- The types involved
cn.yiiguxing.plugin.translate.trans.deepl.DeeplSettingsDialog→cn.yiiguxing.plugin.translate.ui.util.CredentialEditor
- Direction
- trans.deepl uses ui.util, so a change to ui.util can break trans.deepl, while a change to trans.deepl can't break ui.util.
- Position
- Below the diagonal: trans.deepl uses a module listed above it, which is the healthy direction.
34→24 trans.deepl uses trans✕
- Connections
- 11 pairs of types, where a type in trans.deepl uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.deepl.DeeplService→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.deepl.DeeplSupportedLanguages→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.deepl.DeeplSupportedLanguages→cn.yiiguxing.plugin.translate.trans.SupportedLanguagescn.yiiguxing.plugin.translate.trans.deepl.DeeplSupportedLanguagesKt→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslations→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslations→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslations→cn.yiiguxing.plugin.translate.trans.TranslationAdaptercn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslator→cn.yiiguxing.plugin.translate.trans.AbstractTranslatorcn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslator→cn.yiiguxing.plugin.translate.trans.ErrorInfocn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslator→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- trans.deepl uses trans, so a change to trans can break trans.deepl, while a change to trans.deepl can't break trans.
- Position
- Below the diagonal: trans.deepl uses a module listed above it, which is the healthy direction.
34→27 trans.deepl uses trans.documentation✕
- Connections
- 1 pair of types, where a type in trans.deepl uses a type in trans.documentation.
- The types involved
cn.yiiguxing.plugin.translate.trans.deepl.DeeplTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator
- Direction
- trans.deepl uses trans.documentation, so a change to trans.documentation can break trans.deepl, while a change to trans.deepl can't break trans.documentation.
- Position
- Below the diagonal: trans.deepl uses a module listed above it, which is the healthy direction.
35→3 trans.google uses trans.text.TranslationDocument✕
- Connections
- 2 pairs of types, where a type in trans.google uses a type in trans.text.TranslationDocument.
- The types involved
cn.yiiguxing.plugin.translate.trans.google.GoogleDictionaryDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument.Factorycn.yiiguxing.plugin.translate.trans.google.GoogleExampleDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument.Factory
- Direction
- trans.google uses trans.text.TranslationDocument, so a change to trans.text.TranslationDocument can break trans.google, while a change to trans.google can't break trans.text.TranslationDocument.
- Position
- Below the diagonal: trans.google uses a module listed above it, which is the healthy direction.
35→14 trans.google uses trans.text✕
- Connections
- 2 pairs of types, where a type in trans.google uses a type in trans.text.
- The types involved
cn.yiiguxing.plugin.translate.trans.google.GoogleDictionaryDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.DictionaryDocumentcn.yiiguxing.plugin.translate.trans.google.GoogleExampleDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.ExampleDocument
- Direction
- trans.google uses trans.text, so a change to trans.text can break trans.google, while a change to trans.google can't break trans.text.
- Position
- Below the diagonal: trans.google uses a module listed above it, which is the healthy direction.
35→24 trans.google uses trans✕
- Connections
- 13 pairs of types, where a type in trans.google uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.google.GDetectedLanguages→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.google.GoogleLanguageAdapter→cn.yiiguxing.plugin.translate.trans.BaseLanguageAdaptercn.yiiguxing.plugin.translate.trans.google.GoogleLanguageAdapter→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.google.GoogleLanguageAdapter→cn.yiiguxing.plugin.translate.trans.SupportedLanguagescn.yiiguxing.plugin.translate.trans.google.GoogleLanguageAdapterKt→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.google.GoogleTranslation→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.google.GoogleTranslation→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.google.GoogleTranslation→cn.yiiguxing.plugin.translate.trans.TranslationAdaptercn.yiiguxing.plugin.translate.trans.google.GoogleTranslator→cn.yiiguxing.plugin.translate.trans.AbstractTranslatorcn.yiiguxing.plugin.translate.trans.google.GoogleTranslator→cn.yiiguxing.plugin.translate.trans.ErrorInfocn.yiiguxing.plugin.translate.trans.google.GoogleTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.google.GoogleTranslator→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.google.GoogleTranslator→cn.yiiguxing.plugin.translate.trans.TranslationCacheType
- Direction
- trans.google uses trans, so a change to trans can break trans.google, while a change to trans.google can't break trans.
- Position
- Below the diagonal: trans.google uses a module listed above it, which is the healthy direction.
35→27 trans.google uses trans.documentation✕
- Connections
- 1 pair of types, where a type in trans.google uses a type in trans.documentation.
- The types involved
cn.yiiguxing.plugin.translate.trans.google.GoogleTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator
- Direction
- trans.google uses trans.documentation, so a change to trans.documentation can break trans.google, while a change to trans.google can't break trans.documentation.
- Position
- Below the diagonal: trans.google uses a module listed above it, which is the healthy direction.
36→1 trans.microsoft uses trans.microsoft.models✕
- Connections
- 19 pairs of types, where a type in trans.microsoft uses a type in trans.microsoft.models.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.AzureAuthenticationcn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryExamplecn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryLookupcn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.MicrosoftTranslationcn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.TextTypecn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.BingAuthenticationcn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryExamplecn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryLookupcn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.MicrosoftTranslationcn.yiiguxing.plugin.translate.trans.microsoft.EdgeDocumentationTranslator→cn.yiiguxing.plugin.translate.trans.microsoft.models.MicrosoftTranslationcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftDictionaryDocumentFactory→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryLookupcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftExampleDocumentFactory→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryExamplecn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftExampleDocumentFactory→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryExampleItemcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftHttp→cn.yiiguxing.plugin.translate.trans.microsoft.models.AzureAuthenticationcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftHttp→cn.yiiguxing.plugin.translate.trans.microsoft.models.MicrosoftErrorcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftStatusException→cn.yiiguxing.plugin.translate.trans.microsoft.models.MicrosoftErrorMessagecn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationFactory→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryExamplecn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationFactory→cn.yiiguxing.plugin.translate.trans.microsoft.models.DictionaryLookupcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationFactory→cn.yiiguxing.plugin.translate.trans.microsoft.models.MicrosoftTranslation
- Direction
- trans.microsoft uses trans.microsoft.models, so a change to trans.microsoft.models can break trans.microsoft, while a change to trans.microsoft can't break trans.microsoft.models.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→3 trans.microsoft uses trans.text.TranslationDocument✕
- Connections
- 2 pairs of types, where a type in trans.microsoft uses a type in trans.text.TranslationDocument.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftDictionaryDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument.Factorycn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftExampleDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument.Factory
- Direction
- trans.microsoft uses trans.text.TranslationDocument, so a change to trans.text.TranslationDocument can break trans.microsoft, while a change to trans.microsoft can't break trans.text.TranslationDocument.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→5 trans.microsoft uses util.Http✕
- Connections
- 1 pair of types, where a type in trans.microsoft uses a type in util.Http.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftHttp→cn.yiiguxing.plugin.translate.util.Http.StatusException
- Direction
- trans.microsoft uses util.Http, so a change to util.Http can break trans.microsoft, while a change to trans.microsoft can't break util.Http.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→12 trans.microsoft uses util✕
- Connections
- 1 pair of types, where a type in trans.microsoft uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.util.UrlBuilder
- Direction
- trans.microsoft uses util, so a change to util can break trans.microsoft, while a change to trans.microsoft can't break util.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→13 trans.microsoft uses openapi.data✕
- Connections
- 1 pair of types, where a type in trans.microsoft uses a type in openapi.data.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.openapi.data.AsyncExpiringData
- Direction
- trans.microsoft uses openapi.data, so a change to openapi.data can break trans.microsoft, while a change to trans.microsoft can't break openapi.data.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→14 trans.microsoft uses trans.text✕
- Connections
- 2 pairs of types, where a type in trans.microsoft uses a type in trans.text.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftDictionaryDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.DictionaryDocumentcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftExampleDocumentFactory→cn.yiiguxing.plugin.translate.trans.text.ExampleDocument
- Direction
- trans.microsoft uses trans.text, so a change to trans.text can break trans.microsoft, while a change to trans.microsoft can't break trans.text.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→24 trans.microsoft uses trans✕
- Connections
- 21 pairs of types, where a type in trans.microsoft uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.TextTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.TextTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.BingTranslator→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.microsoft.EdgeDocumentationTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftLanguageAdapter→cn.yiiguxing.plugin.translate.trans.BaseLanguageAdaptercn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftLanguageAdapter→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftLanguageAdapter→cn.yiiguxing.plugin.translate.trans.SupportedLanguagescn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftLanguageAdapterKt→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationFactory→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationFactory→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationService→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationService→cn.yiiguxing.plugin.translate.trans.TextTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationService→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslator→cn.yiiguxing.plugin.translate.trans.AbstractTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslator→cn.yiiguxing.plugin.translate.trans.ErrorInfocn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslator→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslator→cn.yiiguxing.plugin.translate.trans.TranslationCacheType
- Direction
- trans.microsoft uses trans, so a change to trans can break trans.microsoft, while a change to trans.microsoft can't break trans.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
36→27 trans.microsoft uses trans.documentation✕
- Connections
- 4 pairs of types, where a type in trans.microsoft uses a type in trans.documentation.
- The types involved
cn.yiiguxing.plugin.translate.trans.microsoft.AzureTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.EdgeDocumentationTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslationService→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslatorcn.yiiguxing.plugin.translate.trans.microsoft.MicrosoftTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator
- Direction
- trans.microsoft uses trans.documentation, so a change to trans.documentation can break trans.microsoft, while a change to trans.microsoft can't break trans.documentation.
- Position
- Below the diagonal: trans.microsoft uses a module listed above it, which is the healthy direction.
37→2 trans.openai uses trans.openai.chat✕
- Connections
- 3 pairs of types, where a type in trans.openai uses a type in trans.openai.chat.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.Azure→cn.yiiguxing.plugin.translate.trans.openai.chat.ChatCompletioncn.yiiguxing.plugin.translate.trans.openai.OpenAI→cn.yiiguxing.plugin.translate.trans.openai.chat.ChatCompletioncn.yiiguxing.plugin.translate.trans.openai.OpenAiService→cn.yiiguxing.plugin.translate.trans.openai.chat.ChatCompletion
- Direction
- trans.openai uses trans.openai.chat, so a change to trans.openai.chat can break trans.openai, while a change to trans.openai can't break trans.openai.chat.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→5 trans.openai uses util.Http✕
- Connections
- 1 pair of types, where a type in trans.openai uses a type in util.Http.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.OpenAiHttp→cn.yiiguxing.plugin.translate.util.Http.StatusException
- Direction
- trans.openai uses util.Http, so a change to util.Http can break trans.openai, while a change to trans.openai can't break util.Http.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→6 trans.openai uses util.credential✕
- Connections
- 1 pair of types, where a type in trans.openai uses a type in util.credential.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.OpenAiCredentials→cn.yiiguxing.plugin.translate.util.credential.StringCredentialManager
- Direction
- trans.openai uses util.credential, so a change to util.credential can break trans.openai, while a change to trans.openai can't break util.credential.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→8 trans.openai uses trans.openai.OpenAiSettings✕
- Connections
- 2 pairs of types, where a type in trans.openai uses a type in trans.openai.OpenAiSettings.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings→cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.Azurecn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings→cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.OpenAi
- Direction
- trans.openai uses trans.openai.OpenAiSettings, so a change to trans.openai.OpenAiSettings can break trans.openai, while a change to trans.openai can't break trans.openai.OpenAiSettings.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→24 trans.openai uses trans✕
- Connections
- 8 pairs of types, where a type in trans.openai uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.ChatRequestContext→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.openai.OpenAiSupportedLanguages→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.openai.OpenAiSupportedLanguages→cn.yiiguxing.plugin.translate.trans.SupportedLanguagescn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.AbstractTranslatorcn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.ErrorInfocn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.TranslationCacheType
- Direction
- trans.openai uses trans, so a change to trans can break trans.openai, while a change to trans.openai can't break trans.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→27 trans.openai uses trans.documentation✕
- Connections
- 1 pair of types, where a type in trans.openai uses a type in trans.documentation.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator
- Direction
- trans.openai uses trans.documentation, so a change to trans.documentation can break trans.openai, while a change to trans.openai can't break trans.documentation.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→28 trans.openai uses trans.openai.config✕
- Connections
- 1 pair of types, where a type in trans.openai uses a type in trans.openai.config.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.openai.config.OpenAiRequestConfigService
- Direction
- trans.openai uses trans.openai.config, so a change to trans.openai.config can break trans.openai, while a change to trans.openai can't break trans.openai.config.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
37→29 trans.openai uses trans.openai.prompt✕
- Connections
- 5 pairs of types, where a type in trans.openai uses a type in trans.openai.prompt.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.Azure→cn.yiiguxing.plugin.translate.trans.openai.prompt.Promptcn.yiiguxing.plugin.translate.trans.openai.OpenAI→cn.yiiguxing.plugin.translate.trans.openai.prompt.Promptcn.yiiguxing.plugin.translate.trans.openai.OpenAiService→cn.yiiguxing.plugin.translate.trans.openai.prompt.Promptcn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.openai.prompt.Promptcn.yiiguxing.plugin.translate.trans.openai.OpenAiTranslator→cn.yiiguxing.plugin.translate.trans.openai.prompt.PromptService
- Direction
- trans.openai uses trans.openai.prompt, so a change to trans.openai.prompt can break trans.openai, while a change to trans.openai can't break trans.openai.prompt.
- Position
- Below the diagonal: trans.openai uses a module listed above it, which is the healthy direction.
38→12 action uses util✕
- Connections
- 7 pairs of types, where a type in action uses a type in util.
- The types involved
cn.yiiguxing.plugin.translate.action.AutoSelectAction→cn.yiiguxing.plugin.translate.util.SelectionModecn.yiiguxing.plugin.translate.action.EditorTranslateAction→cn.yiiguxing.plugin.translate.util.SelectionModecn.yiiguxing.plugin.translate.action.ExclusiveTranslateAction→cn.yiiguxing.plugin.translate.util.SelectionModecn.yiiguxing.plugin.translate.action.InclusiveTranslateAction→cn.yiiguxing.plugin.translate.util.SelectionModecn.yiiguxing.plugin.translate.action.ReplaceWithTranslationAction→cn.yiiguxing.plugin.translate.util.SelectionModecn.yiiguxing.plugin.translate.action.ShowTranslationDialogAction→cn.yiiguxing.plugin.translate.util.SelectionModecn.yiiguxing.plugin.translate.action.TranslateAction→cn.yiiguxing.plugin.translate.util.SelectionMode
- Direction
- action uses util, so a change to util can break action, while a change to action can't break util.
- Position
- Below the diagonal: action uses a module listed above it, which is the healthy direction.
38→18 action uses tts✕
- Connections
- 1 pair of types, where a type in action uses a type in tts.
- The types involved
cn.yiiguxing.plugin.translate.action.TTSEngineAction→cn.yiiguxing.plugin.translate.tts.TTSEngine
- Direction
- action uses tts, so a change to tts can break action, while a change to action can't break tts.
- Position
- Below the diagonal: action uses a module listed above it, which is the healthy direction.
38→19 action uses ui.settings✕
- Connections
- 2 pairs of types, where a type in action uses a type in ui.settings.
- The types involved
cn.yiiguxing.plugin.translate.action.TranslationEngineAction→cn.yiiguxing.plugin.translate.ui.settings.TranslationEnginecn.yiiguxing.plugin.translate.action.TranslationEngineSettingsAction→cn.yiiguxing.plugin.translate.ui.settings.TranslationEngine
- Direction
- action uses ui.settings, so a change to ui.settings can break action, while a change to action can't break ui.settings.
- Position
- Below the diagonal: action uses a module listed above it, which is the healthy direction.
38→31 action uses cn.yiiguxing.plugin.translate✕
- Connections
- 3 pairs of types, where a type in action uses a type in cn.yiiguxing.plugin.translate.
- The types involved
cn.yiiguxing.plugin.translate.action.TTSEngineAction→cn.yiiguxing.plugin.translate.Settingscn.yiiguxing.plugin.translate.action.TranslationEngineAction→cn.yiiguxing.plugin.translate.Settingscn.yiiguxing.plugin.translate.action.TranslationEngineSettingsAction→cn.yiiguxing.plugin.translate.Settings
- Direction
- action uses cn.yiiguxing.plugin.translate, so a change to cn.yiiguxing.plugin.translate can break action, while a change to action can't break cn.yiiguxing.plugin.translate.
- Position
- Below the diagonal: action uses a module listed above it, which is the healthy direction.
39→8 trans.openai.ui uses trans.openai.OpenAiSettings✕
- Connections
- 3 pairs of types, where a type in trans.openai.ui uses a type in trans.openai.OpenAiSettings.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsDialog→cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.Azurecn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsDialog→cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.CommonStatecn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsDialog→cn.yiiguxing.plugin.translate.trans.openai.OpenAiSettings.OpenAi
- Direction
- trans.openai.ui uses trans.openai.OpenAiSettings, so a change to trans.openai.OpenAiSettings can break trans.openai.ui, while a change to trans.openai.ui can't break trans.openai.OpenAiSettings.
- Position
- Below the diagonal: trans.openai.ui uses a module listed above it, which is the healthy direction.
39→16 trans.openai.ui uses ui.util✕
- Connections
- 1 pair of types, where a type in trans.openai.ui uses a type in ui.util.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsDialog→cn.yiiguxing.plugin.translate.ui.util.CredentialEditor
- Direction
- trans.openai.ui uses ui.util, so a change to ui.util can break trans.openai.ui, while a change to trans.openai.ui can't break ui.util.
- Position
- Below the diagonal: trans.openai.ui uses a module listed above it, which is the healthy direction.
39→37 trans.openai.ui uses trans.openai✕
- Connections
- 11 pairs of types, where a type in trans.openai.ui uses a type in trans.openai.
- The types involved
cn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsDialog→cn.yiiguxing.plugin.translate.trans.openai.ConfigTypecn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsDialog→cn.yiiguxing.plugin.translate.trans.openai.ServiceProvidercn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUI→cn.yiiguxing.plugin.translate.trans.openai.AzureServiceVersioncn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUI→cn.yiiguxing.plugin.translate.trans.openai.OpenAiModelcn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUI→cn.yiiguxing.plugin.translate.trans.openai.OpenAiTtsVoicecn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUI→cn.yiiguxing.plugin.translate.trans.openai.ServiceProvidercn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUiImpl→cn.yiiguxing.plugin.translate.trans.openai.AzureServiceVersioncn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUiImpl→cn.yiiguxing.plugin.translate.trans.openai.ConfigTypecn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUiImpl→cn.yiiguxing.plugin.translate.trans.openai.OpenAiModelcn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUiImpl→cn.yiiguxing.plugin.translate.trans.openai.OpenAiTtsVoicecn.yiiguxing.plugin.translate.trans.openai.ui.OpenAISettingsUiImpl→cn.yiiguxing.plugin.translate.trans.openai.ServiceProvider
- Direction
- trans.openai.ui uses trans.openai, so a change to trans.openai can break trans.openai.ui, while a change to trans.openai.ui can't break trans.openai.
- Position
- Below the diagonal: trans.openai.ui uses a module listed above it, which is the healthy direction.
40→10 trans.youdao uses trans.youdao.YoudaoWebTranslationDocument✕
- Connections
- 1 pair of types, where a type in trans.youdao uses a type in trans.youdao.YoudaoWebTranslationDocument.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument→cn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument.WebTranslation
- Direction
- trans.youdao uses trans.youdao.YoudaoWebTranslationDocument, so a change to trans.youdao.YoudaoWebTranslationDocument can break trans.youdao, while a change to trans.youdao can't break trans.youdao.YoudaoWebTranslationDocument.
- Position
- Below the diagonal: trans.youdao uses a module listed above it, which is the healthy direction.
40→14 trans.youdao uses trans.text✕
- Connections
- 2 pairs of types, where a type in trans.youdao uses a type in trans.text.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoDictDocument→cn.yiiguxing.plugin.translate.trans.text.TranslationDocumentcn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument→cn.yiiguxing.plugin.translate.trans.text.TranslationDocument
- Direction
- trans.youdao uses trans.text, so a change to trans.text can break trans.youdao, while a change to trans.youdao can't break trans.text.
- Position
- Below the diagonal: trans.youdao uses a module listed above it, which is the healthy direction.
40→20 trans.youdao uses ui✕
- Connections
- 2 pairs of types, where a type in trans.youdao uses a type in ui.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoDictDocument→cn.yiiguxing.plugin.translate.ui.StyledViewercn.yiiguxing.plugin.translate.trans.youdao.YoudaoWebTranslationDocument→cn.yiiguxing.plugin.translate.ui.StyledViewer
- Direction
- trans.youdao uses ui, so a change to ui can break trans.youdao, while a change to trans.youdao can't break ui.
- Position
- Below the diagonal: trans.youdao uses a module listed above it, which is the healthy direction.
40→24 trans.youdao uses trans✕
- Connections
- 11 pairs of types, where a type in trans.youdao uses a type in trans.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoLanguageAdapter→cn.yiiguxing.plugin.translate.trans.BaseLanguageAdaptercn.yiiguxing.plugin.translate.trans.youdao.YoudaoLanguageAdapter→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.youdao.YoudaoLanguageAdapter→cn.yiiguxing.plugin.translate.trans.SupportedLanguagescn.yiiguxing.plugin.translate.trans.youdao.YoudaoLanguageAdapterKt→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslation→cn.yiiguxing.plugin.translate.trans.Translationcn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslation→cn.yiiguxing.plugin.translate.trans.TranslationAdaptercn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslator→cn.yiiguxing.plugin.translate.trans.AbstractTranslatorcn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslator→cn.yiiguxing.plugin.translate.trans.BaseTranslationcn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslator→cn.yiiguxing.plugin.translate.trans.ErrorInfocn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslator→cn.yiiguxing.plugin.translate.trans.Langcn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslator→cn.yiiguxing.plugin.translate.trans.Translation
- Direction
- trans.youdao uses trans, so a change to trans can break trans.youdao, while a change to trans.youdao can't break trans.
- Position
- Below the diagonal: trans.youdao uses a module listed above it, which is the healthy direction.
40→27 trans.youdao uses trans.documentation✕
- Connections
- 1 pair of types, where a type in trans.youdao uses a type in trans.documentation.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoTranslator→cn.yiiguxing.plugin.translate.trans.documentation.DocumentationTranslator
- Direction
- trans.youdao uses trans.documentation, so a change to trans.documentation can break trans.youdao, while a change to trans.youdao can't break trans.documentation.
- Position
- Below the diagonal: trans.youdao uses a module listed above it, which is the healthy direction.
40→31 trans.youdao uses cn.yiiguxing.plugin.translate✕
- Connections
- 1 pair of types, where a type in trans.youdao uses a type in cn.yiiguxing.plugin.translate.
- The types involved
cn.yiiguxing.plugin.translate.trans.youdao.YoudaoSettingsDialog→cn.yiiguxing.plugin.translate.YoudaoTranslateSettings
- Direction
- trans.youdao uses cn.yiiguxing.plugin.translate, so a change to cn.yiiguxing.plugin.translate can break trans.youdao, while a change to trans.youdao can't break cn.yiiguxing.plugin.translate.
- Position
- Below the diagonal: trans.youdao 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 39 | High / Critical |
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Top priorities: Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2); Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). | +6.1 pts | Low | Secrets (history) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +2.9 pts | Low | Static Analysis (SAST) |
| Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4). | +2.5 pts | Low | REDACTED Scanning |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +2.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 `GoogleTranslateAPIKt` spells `API` where 28 names in the project spell… finding(s) in Naming Consistency — start with REDACTED. | +1.8 pts | Low | Naming Consistency |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.5 pts | Medium | Visual & motion safety |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.1 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialog.kt | 5.9 | Mixed | God Classes: TooManyMethods: TranslationDialog |
| src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoSettingsDialog.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/kotlin/cn/yiiguxing/plugin/translate/util/CamelCaseSplitter.kt | 7.8 | Mixed | Cyclomatic Complexity: CamelCaseSplitter.split (cyclomatic 17) |
| src/main/kotlin/cn/yiiguxing/plugin/translate/trans/baidu/BaiduTranslator.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (25 corresponding lines) |
| src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 7+ corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/main/kotlin/cn/yiiguxing/plugin/translate/ui/StyledViewer.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/OpenAiService.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/cn/yiiguxing/plugin/translate/documentation/TranslatableDocumentationTarget.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoDictDocument.kt | 8.5 | Near-clean | Cognitive Complexity: Factory.getDocument (cognitive 25) |
| src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookView.kt | 8.5 | Near-clean | Cognitive Complexity: WordBookView.updateContent (cognitive 25) |
| src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/ui/OpenAISettingsDialog.kt | 8.5 | Near-clean | Cognitive Complexity: OpenAISettingsDialog.initValidators (cognitive 20) |
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 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 45 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, 112 of 122 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because maven.aliyun.com — the registry that answers it — was asked and did not reply (the build stopped because maven.aliyun.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add maven.aliyun.com to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (13 contributor(s) across 4081 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 12 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — 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. 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 — 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. 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.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (27384 LoC, 946 module-visible types across 56 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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. `src/main/kotlin/cn/yiiguxing/plugin/translate/Settings.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/OpenAiService.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/tts/sound/AudioPlayer.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/ui/ProcessComponent.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialogUiImpl.kt`, … (+7 more) 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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 3 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — 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. 'java.sql.ResultSet' is imported (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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.
- C3 Audit Trail — 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. 'java.sql.ResultSet' is imported (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'java.sql.ResultSet' is imported (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'java.sql.ResultSet' is imported (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
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.
- 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 REDACTED Scanning: REDACTED 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CamelCaseSplitter.split at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with CamelCaseSplitter.split (cyclomatic 17). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was Factory.getDocument at 25.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with Factory.getDocument (cognitive 25), WordBookView.updateContent (cognitive 25), CamelCaseSplitter.split (cognitive 24). — 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 5 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with TranslationDialog.kt, TranslationPane.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with TranslationDialog.kt, WordBookService.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with TranslationDialog.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. A further 12 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with OpenAiRequestConfigService.kt, YoudaoSettingsDialog.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (27 corresponding lines) finding(s) in Code Duplication — start with BingTranslator.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (25 corresponding lines) finding(s) in Code Duplication — start with BaiduTranslator.kt. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 91 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with CacheService.kt, TranslationFailedComponent.kt. — One of this dimension's main actionable groups (2 warning-level).
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
D14 · License Compliance
0 of 5 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted task-comment markers across 27384 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with StyledViewer.kt, YoudaoSettingsDialog.kt, OpenAiService.kt. — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D21 · Naming Consistency
1 naming inconsistencies among 24 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `GoogleTranslateAPIKt` spells `API` where 28 names in the project spell… finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
53 % of calls cross a namespace and 8 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
39 finding(s): 0 critical, 38 high, 1 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 6 file(s) — `.github/ISSUE_TEMPLATE/bug_report.yml`, `.github/ISSUE_TEMPLATE/bug_report_zh.yml`, `gradlew` (line 72, line 178), `src/main/kotlin/cn/yiiguxing/plugin/translate/Settings.kt` (lines 43–45, line 47, line 258), `src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationPane.kt` (lines 93–95, lines 97–99, line 568), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 121 of the 327 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: TranslationDialog.kt↔WordFavoritesUi.kt 73%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with TranslationDialog.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 5 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
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — src/main/resources/web/error.html:2, src/main/resources/web/loading.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.loading > .logo > .bg::before` moves (`animation: rotate 5s linear infinite, move 12s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — src/main/resources/web/error.html:63, src/main/resources/web/loading.html:63
- `a.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/main/resources/web/release-notes.html:66
- `iframe` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/main/resources/web/release-notes.html:169
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `CONTRIBUTING.md`, but `CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:343
What to do
- Reconcile the README with reality: README.md links to `CONTRIBUTING.md`, but `CONTRIBUTING.md` does not exist.
P1 · CI/CD gates
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 4 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:29
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `YoudaoTranslator.translateDocumentation` is public and takes `documentation: Document` from its caller, and it calls itself at line 133 with a piece of `documentation` — the function is not `tailrec`, so every call is a real frame — and nowhere in `YoudaoTranslator.translateDocumentation` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `YoudaoTranslator.translateDocumentation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoTranslator.kt:133
- `DeeplTranslator.translateDocumentation` is public and takes `documentation: Document` from its caller, and it calls itself at line 81 with a piece of `documentation` — the function is not `tailrec`, so every call is a real frame — and nowhere in `DeeplTranslator.translateDocumentation` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `DeeplTranslator.translateDocumentation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — src/main/kotlin/cn/yiiguxing/plugin/translate/trans/deepl/DeeplTranslator.kt:81
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `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. (×3) — src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:660, src/main/kotlin/cn/yiiguxing/plugin/translate/ui/BalloonPositionTracker.kt:87, src/main/kotlin/cn/yiiguxing/plugin/translate/action/TranslationEngineAction.kt:21
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/imports/XmlWordBookImporter.kt:51, src/main/kotlin/cn/yiiguxing/plugin/translate/util/Translations.kt:13
- `catch (e: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/main/kotlin/cn/yiiguxing/plugin/translate/util/Strings.kt:13, src/main/kotlin/cn/yiiguxing/plugin/translate/action/TTSEngineAction.kt:14
- 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. (×3) — src/main/kotlin/cn/yiiguxing/plugin/translate/tts/sound/source/PushablePlaybackSource.kt:74, src/main/kotlin/cn/yiiguxing/plugin/translate/trans/microsoft/MicrosoftHttp.kt:121, src/main/kotlin/cn/yiiguxing/plugin/translate/service/CacheService.kt:166
- `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. (×3) — src/main/kotlin/cn/yiiguxing/plugin/translate/tts/microsoft/EdgeTTSVoiceManager.kt:277, src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/config/OpenAiRequestConfigService.kt:234, src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt:216
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 38% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 49% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'java.sql.ResultSet' (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'java.sql.ResultSet' (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'java.sql.ResultSet' (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'java.sql.ResultSet' (src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:33) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- 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.
- D10 Test Quality — ~1155 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 — Dependency currency not established — maven.aliyun.com did not answer
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host; this repository builds only code that other code links in, and runs nothing itself, so no ADR log is required here.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 12 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (97 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P2 Observability — This repository's JVM source (1 module(s), 352 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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
- 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
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- 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
- X24 Document value interpolated into markup unescaped — 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
- 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
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 49 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 59 finding(s)
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:660
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/imports/XmlWordBookImporter.kt:51
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/util/Strings.kt:13
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/util/Translations.kt:13
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/ui/BalloonPositionTracker.kt:87
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/tts/microsoft/EdgeTTSVoiceManager.kt:277
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/config/OpenAiRequestConfigService.kt:234
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt:216
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/action/TTSEngineAction.kt:14
- Swallowed exception (caught, then discarded) src/main/kotlin/cn/yiiguxing/plugin/translate/action/TranslationEngineAction.kt:21
- TodoComment src/main/kotlin/cn/yiiguxing/plugin/translate/ui/StyledViewer.kt:258
- TodoComment src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoSettingsDialog.kt:38
- TodoComment src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/OpenAiService.kt:38
- TodoComment src/main/kotlin/cn/yiiguxing/plugin/translate/documentation/TranslatableDocumentationTarget.kt:107
- Swallowed exception (empty catch) src/main/kotlin/cn/yiiguxing/plugin/translate/tts/sound/source/PushablePlaybackSource.kt:74
- Swallowed exception (empty catch) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/microsoft/MicrosoftHttp.kt:121
- Swallowed exception (empty catch) src/main/kotlin/cn/yiiguxing/plugin/translate/service/CacheService.kt:166
- Page without a main landmark src/main/resources/web/error.html:2
- Page without a main landmark src/main/resources/web/loading.html:2
- Animation without a prefers-reduced-motion guard src/main/resources/web/error.html:63
- Animation without a prefers-reduced-motion guard src/main/resources/web/loading.html:63
- Focus outline removed in CSS without a :focus replacement src/main/resources/web/release-notes.html:66
- Focus outline removed in CSS without a :focus replacement src/main/resources/web/release-notes.html:169
- TooManyMethods: TranslationDialog src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialog.kt:58
- TooManyMethods: TranslationPane src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationPane.kt:46
- ClassTooLong: TranslationDialog src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialog.kt:58
- ClassTooLong: WordBookService src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookService.kt:42
- Edited copy of a member (17 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/config/OpenAiRequestConfigService.kt:140
- Edited copy of a member (17 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoSettingsDialog.kt:120
- Low cohesion: CacheService (LCOM4 5) src/main/kotlin/cn/yiiguxing/plugin/translate/service/CacheService.kt:20
- Low cohesion: TranslationFailedComponent (LCOM4 4) src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationFailedComponent.kt:29
- Recursive walk over a caller-supplied document has no depth cap src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoTranslator.kt:133
- Recursive walk over a caller-supplied document has no depth cap src/main/kotlin/cn/yiiguxing/plugin/translate/trans/deepl/DeeplTranslator.kt:81
- CamelCaseSplitter.split (cyclomatic 17) src/main/kotlin/cn/yiiguxing/plugin/translate/util/CamelCaseSplitter.kt:5
- Factory.getDocument (cognitive 25) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/youdao/YoudaoDictDocument.kt:104
- WordBookView.updateContent (cognitive 25) src/main/kotlin/cn/yiiguxing/plugin/translate/wordbook/WordBookView.kt:250
- CamelCaseSplitter.split (cognitive 24) src/main/kotlin/cn/yiiguxing/plugin/translate/util/CamelCaseSplitter.kt:5
- OpenAISettingsDialog.initValidators (cognitive 20) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/ui/OpenAISettingsDialog.kt:232
- ReplaceWithTranslationAction.onActionPerformed (cognitive 17) src/main/kotlin/cn/yiiguxing/plugin/translate/action/ReplaceWithTranslationAction.kt:77
- REDACTED
- FileTooLong: ui/TranslationDialog.kt src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialog.kt
- MethodTooLong: SettingsUi.doLayout src/main/kotlin/cn/yiiguxing/plugin/translate/ui/settings/SettingsUi.kt:209
- Change coupling: TranslationDialog.kt ↔ WordFavoritesUi.kt src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialog.kt:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (27 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/microsoft/BingTranslator.kt:327
- Edited copy of a member (25 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/baidu/BaiduTranslator.kt:140
- Edited copy of a member (20 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/util/UrlTrackingParametersProvider.kt:11
- Edited copy of a member (21 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/action/SwitchEngineAction.kt:56
- Edited copy of a member (19 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/ui/FixedSizeCardLayout.kt:17
- Edited copy of a member (16 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/util/CharSequences.kt:7
- Edited copies of one member (3 members, 12+ corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/baidu/BaiduTranslator.kt:126
- Edited copy of a member (11 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/microsoft/MicrosoftHttp.kt:163
- Edited copies of one member (3 members, 7+ corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt:55
- Edited copy of a member (7 corresponding lines) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/TranslateService.kt:191
- Duplicated block (7 lines × 2) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt:65
- Duplicated block (5 lines × 2) src/main/kotlin/cn/yiiguxing/plugin/translate/trans/text/ExampleDocument.kt:109
- Coverage collected but not gated
Minor — 14 finding(s)
- Duplicated predicate src/main/kotlin/cn/yiiguxing/plugin/translate/trans/ali/AliTranslator.kt:57
- Duplicated predicate src/main/kotlin/cn/yiiguxing/plugin/translate/ui/FixLangComponent.kt:34
- `GoogleTranslateAPIKt` spells `API` where 28 names in the project spell it `Api` REDACTED:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- README/code drift README.md:343
- No SAST REDACTED:29
- Hand-rolled JSON/XML parsing via regex src/main/kotlin/cn/yiiguxing/plugin/translate/trans/google/GoogleExampleDocumentFactory.kt:10
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-48b4ccaa465743b5a528340e5fc763b8/history.json --exit-code 0 --source . | 8 | 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-48b4ccaa465743b5a528340e5fc763b8/tree.json --exit-code 0 --source . | 2 | 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 . | 39 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 12 file(s) — `src/main/kotlin/cn/yiiguxing/plugin/translate/Settings.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/trans/openai/OpenAiService.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/tts/sound/AudioPlayer.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/ui/ProcessComponent.kt`, `src/main/kotlin/cn/yiiguxing/plugin/translate/ui/TranslationDialogUiImpl.kt`, … (+7 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |