Public report of kodjodevf/mangayomi, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 14:01 UTC · Survey ID cd_fd3c0cb4e6674663b28dad3bf0f226ad
kodjodevf/mangayomi
Measured 23 October 2026, 13:49 UTC, at code version e683aa8
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskUp 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 138,784 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Production Readiness, 39
Findings by how serious they are
99 critical766 serious69 minor
8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 13:49 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
70of 73 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
915of 934 findings point to an exact file and line, so you can open each one in the code. The other 19 concern the repository as a whole, such as missing documentation.
73dimensions across 7 lenses, read from 138,784 lines of product code in 11 projects.
kodjodevf/mangayomi scores 51 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 39 and is rated Weak. Its Security & performance tooling dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing and to pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker, and if Production Readiness rose to 70, the score would rise from 51 to about 60.
99 findings are critical: 73 in Static Analysis (SAST), 14 in Captive dependencies, six in Change Coupling, four in Dependency Vulnerabilities, one in CQS / query purity and one in Knowledge Freshness.
Watchdog couldn't measure 6 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 138,784 lines, which would take an estimated 1.0 person-years, around €150,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 51 to about 60.
Code composition: what the lines of code are
Product code 87%Tests 13%
New since the last survey: 187 findings
These 187 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 445 findings
These 445 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one. The first 100 are listed here.
God Classes · MethodTooLong: _CodeEditorPageState.build lib/modules/browse/extension/edit_code.dart
God Classes · MethodTooLong: _NovelWebViewState._bottomBar lib/modules/novel/novel_reader_view.dart
God Classes · MethodTooLong: _ExtensionServerScreenState.build lib/modules/more/settings/browse/extension_server_screen.dart
God Classes · MethodTooLong: _ExtensionDetailState.build lib/modules/browse/extension/extension_detail.dart
God Classes · MethodTooLong: _AnimeStreamPageState._handleMpvNodeEvents lib/modules/anime/anime_player_view.dart
God Classes · MethodTooLong: _HistoryTabState.build lib/modules/history/history_screen.dart
God Classes · MethodTooLong: _MangaDetailViewState._showDraggableMenu lib/modules/manga/detail/manga_detail_view.dart
God Classes · MethodTooLong: _SourcePreferenceWidgetState.build lib/modules/browse/extension/widgets/source_preference_widget.dart
God Classes · MethodTooLong: _SourceRepositoriesState.build REDACTED
God Classes · ClassTooLong: ReaderScreen lib/modules/more/settings/reader/reader_screen.dart
God Classes · MethodTooLong: _ChapterListTileState.build lib/modules/manga/reader/widgets/btn_chapter_list_dialog.dart
God Classes · FileTooLong: reader/reader_screen.dart lib/modules/more/settings/reader/reader_screen.dart
God Classes · MethodTooLong: _TtsSettingsTabState.build lib/modules/novel/tts/tts_settings_tab.dart
God Classes · MethodTooLong: _LeftInfo.build lib/modules/manga/detail/tv/tv_anime_detail_view.dart
God Classes · MethodTooLong: GeneralSettingsTab.build lib/modules/novel/widgets/novel_general_settings_tab.dart
God Classes · FileTooLong: browse/extension_server_screen.dart lib/modules/more/settings/browse/extension_server_screen.dart
God Classes · MethodTooLong: _TrackerWidgetSearchState.build lib/modules/manga/detail/widgets/tracker_search_widget.dart
God Classes · FileTooLong: widgets/unified_settings_sheet.dart lib/modules/anime/widgets/unified_settings_sheet.dart
God Classes · FileTooLong: widgets/desktop.dart lib/modules/anime/widgets/desktop.dart
God Classes · ClassTooLong: _GeneralStateScreen lib/modules/more/settings/general/general_screen.dart
God Classes · MethodTooLong: _NovelWebViewState._showFontSizeBottomSheet lib/modules/novel/novel_reader_view.dart
God Classes · FileTooLong: tv/tv_anime_detail_view.dart lib/modules/manga/detail/tv/tv_anime_detail_view.dart
God Classes · MethodTooLong: _PlayerDecoderScreenState.build lib/modules/more/settings/player/player_decoder_screen.dart
God Classes · ClassTooLong: _TrackerLibraryScreenState lib/modules/tracker_library/tracker_library_screen.dart
God Classes · ClassTooLong: _MassMigrationRunnerScreenState lib/modules/mass_migration/mass_migration_runner_screen.dart
God Classes · FileTooLong: general/general_screen.dart lib/modules/more/settings/general/general_screen.dart
God Classes · ClassTooLong: _MainScreenState lib/modules/main_view/main_screen.dart
God Classes · FileTooLong: tracker_library/tracker_library_screen.dart lib/modules/tracker_library/tracker_library_screen.dart
God Classes · MethodTooLong: _MangaDetailsViewState.build lib/modules/manga/detail/manga_details_view.dart
God Classes · MethodTooLong: AboutScreen.build lib/modules/more/about/about_screen.dart
God Classes · MethodTooLong: _CreateBackupState.build lib/modules/more/data_and_storage/create_backup.dart
God Classes · FileTooLong: providers/file_scanner.dart lib/modules/library/providers/file_scanner.dart
God Classes · FileTooLong: widgets/manga_info_header.dart lib/modules/manga/detail/widgets/manga_info_header.dart
God Classes · MethodTooLong: FilterWidget.build lib/modules/manga/home/widget/filter_widget.dart
God Classes · MethodTooLong: _OnboardingScreenState._stepBody lib/modules/onboarding/onboarding_screen.dart
God Classes · FileTooLong: main_view/main_screen.dart lib/modules/main_view/main_screen.dart
God Classes · FileTooLong: widgets/floating_nav_bar.dart lib/modules/widgets/floating_nav_bar.dart
God Classes · MethodTooLong: _AnimeStreamPageState._buildSettingsEntries lib/modules/anime/anime_player_view.dart
God Classes · FileTooLong: mass_migration/mass_migration_runner_screen.dart lib/modules/mass_migration/mass_migration_runner_screen.dart
God Classes · TooManyMethods: _SubsamplingScaleImageViewState lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart
God Classes · ClassTooLong: _ReaderSettingsTabState lib/modules/novel/widgets/novel_reader_settings_sheet.dart
God Classes · MethodTooLong: _MainScreenState._buildNavigationWidgetsDesktop lib/modules/main_view/main_screen.dart
God Classes · ClassTooLong: _OnboardingScreenState lib/modules/onboarding/onboarding_screen.dart
God Classes · MethodTooLong: _MassMigrationRunnerScreenState._buildSummaryPhase lib/modules/mass_migration/mass_migration_runner_screen.dart
God Classes · MethodTooLong: _CustomButtonScreenState._showEditForm lib/modules/more/settings/player/custom_button_screen.dart
God Classes · MethodTooLong: TrackScreen.build lib/modules/more/settings/track/track.dart
God Classes · TooManyMethods: _NovelWebViewState lib/modules/novel/novel_reader_view.dart
God Classes · MethodTooLong: _SubtitlesWidgetSearchState._showImdbList lib/modules/anime/widgets/search_subtitles.dart
God Classes · MethodTooLong: _PlayerAudioScreenState.build lib/modules/more/settings/player/player_audio_screen.dart
God Classes · MethodTooLong: _SubsamplingScaleImageViewState._loadFromProvider lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart
God Classes · FileTooLong: widgets/library_settings_sheet.dart lib/modules/library/widgets/library_settings_sheet.dart
God Classes · ClassTooLong: _MangaInfoHeaderState lib/modules/manga/detail/widgets/manga_info_header.dart
Rebuild cost: about €150,000 · Estimate
Cost to rebuild
€50,000 to €250,000, for 834 to 2,645 hours of work, about 1.0 person-years for 1 to 2 engineers
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 51. 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
Large: 138,784 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Raises the score by about 2 points · Medium effort · DR & Backup
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Production Readiness, at 39 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 236,685 lines over the last 90 days, which is about 959,889 lines a year. At that pace, the extra work comes to an estimated 53.2 to 320 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
43 modules, with 32 dependencies between them. 2 loops run through 8 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 3 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
repository.models uses repository.eval, so a change to repository.eval can break repository.models, while a change to repository.models can't break repository.eval.
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.
rust_lib_mangayomi.aidoku_wasm.host_html uses rust_lib_mangayomi.aidoku_wasm.store, so a change to rust_lib_mangayomi.aidoku_wasm.store can break rust_lib_mangayomi.aidoku_wasm.host_html, while a change to rust_lib_mangayomi.aidoku_wasm.host_html can't break rust_lib_mangayomi.aidoku_wasm.store.
Position
Below the diagonal: rust_lib_mangayomi.aidoku_wasm.host_html uses a module listed above it, which is the healthy direction.
30→33 rust_lib_mangayomi.api.aidoku_wasm uses rust_lib_mangayomi.aidoku_wasm.modelspart of a loop✕
Connections
7 pairs of types, where a type in rust_lib_mangayomi.api.aidoku_wasm uses a type in rust_lib_mangayomi.aidoku_wasm.models.
rust_lib_mangayomi.api.aidoku_wasm uses rust_lib_mangayomi.aidoku_wasm.models, so a change to rust_lib_mangayomi.aidoku_wasm.models can break rust_lib_mangayomi.api.aidoku_wasm, while a change to rust_lib_mangayomi.api.aidoku_wasm can't break rust_lib_mangayomi.aidoku_wasm.models.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→36 rust_lib_mangayomi.api.aidoku_wasm uses rust_lib_mangayomi.aidoku_wasm.interpreterpart of a loop✕
Connections
1 pair of types, where a type in rust_lib_mangayomi.api.aidoku_wasm uses a type in rust_lib_mangayomi.aidoku_wasm.interpreter.
rust_lib_mangayomi.api.aidoku_wasm uses rust_lib_mangayomi.aidoku_wasm.interpreter, so a change to rust_lib_mangayomi.aidoku_wasm.interpreter can break rust_lib_mangayomi.api.aidoku_wasm, while a change to rust_lib_mangayomi.api.aidoku_wasm can't break rust_lib_mangayomi.aidoku_wasm.interpreter.
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.
rust_lib_mangayomi.api.rhttp.http uses rust_lib_mangayomi.api.rhttp.client, so a change to rust_lib_mangayomi.api.rhttp.client can break rust_lib_mangayomi.api.rhttp.http, while a change to rust_lib_mangayomi.api.rhttp.http can't break rust_lib_mangayomi.api.rhttp.client.
Position
Below the diagonal: rust_lib_mangayomi.api.rhttp.http uses a module listed above it, which is the healthy direction.
repository.eval uses repository.models, so a change to repository.models can break repository.eval, while a change to repository.eval can't break repository.models.
Position
Below the diagonal: repository.eval uses a module listed above it, which is the healthy direction.
32→37 repository.eval uses repository.servicespart of a loop✕
Connections
2 pairs of types, where a type in repository.eval uses a type in repository.services.
repository.eval uses repository.services, so a change to repository.services can break repository.eval, while a change to repository.eval can't break repository.services.
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.
rust_lib_mangayomi.aidoku_wasm.models uses rust_lib_mangayomi.aidoku_wasm.postcard, so a change to rust_lib_mangayomi.aidoku_wasm.postcard can break rust_lib_mangayomi.aidoku_wasm.models, while a change to rust_lib_mangayomi.aidoku_wasm.models can't break rust_lib_mangayomi.aidoku_wasm.postcard.
Position
Below the diagonal: rust_lib_mangayomi.aidoku_wasm.models uses a module listed above it, which is the healthy direction.
rust_lib_mangayomi.aidoku_wasm.models uses rust_lib_mangayomi.aidoku_wasm.store, so a change to rust_lib_mangayomi.aidoku_wasm.store can break rust_lib_mangayomi.aidoku_wasm.models, while a change to rust_lib_mangayomi.aidoku_wasm.models can't break rust_lib_mangayomi.aidoku_wasm.store.
Position
Below the diagonal: rust_lib_mangayomi.aidoku_wasm.models uses a module listed above it, which is the healthy direction.
rust_lib_mangayomi.aidoku_wasm.models uses rust_lib_mangayomi.api.aidoku_wasm, so a change to rust_lib_mangayomi.api.aidoku_wasm can break rust_lib_mangayomi.aidoku_wasm.models, while a change to rust_lib_mangayomi.aidoku_wasm.models can't break rust_lib_mangayomi.api.aidoku_wasm.
Position
Below the diagonal: rust_lib_mangayomi.aidoku_wasm.models uses a module listed above it, which is the healthy direction.
33→36 rust_lib_mangayomi.aidoku_wasm.models uses rust_lib_mangayomi.aidoku_wasm.interpreterpart of a loop✕
Connections
1 pair of types, where a type in rust_lib_mangayomi.aidoku_wasm.models uses a type in rust_lib_mangayomi.aidoku_wasm.interpreter.
rust_lib_mangayomi.aidoku_wasm.models uses rust_lib_mangayomi.aidoku_wasm.interpreter, so a change to rust_lib_mangayomi.aidoku_wasm.interpreter can break rust_lib_mangayomi.aidoku_wasm.models, while a change to rust_lib_mangayomi.aidoku_wasm.models can't break rust_lib_mangayomi.aidoku_wasm.interpreter.
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.
repository.providers uses repository.models, so a change to repository.models can break repository.providers, while a change to repository.providers can't break repository.models.
Position
Below the diagonal: repository.providers uses a module listed above it, which is the healthy direction.
repository.providers uses repository.eval, so a change to repository.eval can break repository.providers, while a change to repository.providers can't break repository.eval.
Position
Below the diagonal: repository.providers uses a module listed above it, which is the healthy direction.
34→37 repository.providers uses repository.servicespart of a loop✕
Connections
1 pair of types, where a type in repository.providers uses a type in repository.services.
repository.providers uses repository.services, so a change to repository.services can break repository.providers, while a change to repository.providers can't break repository.services.
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.
repository.repositories uses repository.models, so a change to repository.models can break repository.repositories, while a change to repository.repositories can't break repository.models.
Position
Below the diagonal: repository.repositories uses a module listed above it, which is the healthy direction.
repository.repositories uses repository.eval, so a change to repository.eval can break repository.repositories, while a change to repository.repositories can't break repository.eval.
Position
Below the diagonal: repository.repositories uses a module listed above it, which is the healthy direction.
rust_lib_mangayomi.aidoku_wasm.interpreter uses rust_lib_mangayomi.aidoku_wasm.store, so a change to rust_lib_mangayomi.aidoku_wasm.store can break rust_lib_mangayomi.aidoku_wasm.interpreter, while a change to rust_lib_mangayomi.aidoku_wasm.interpreter can't break rust_lib_mangayomi.aidoku_wasm.store.
Position
Below the diagonal: rust_lib_mangayomi.aidoku_wasm.interpreter uses a module listed above it, which is the healthy direction.
rust_lib_mangayomi.aidoku_wasm.interpreter uses rust_lib_mangayomi.aidoku_wasm.models, so a change to rust_lib_mangayomi.aidoku_wasm.models can break rust_lib_mangayomi.aidoku_wasm.interpreter, while a change to rust_lib_mangayomi.aidoku_wasm.interpreter can't break rust_lib_mangayomi.aidoku_wasm.models.
Position
Below the diagonal: rust_lib_mangayomi.aidoku_wasm.interpreter uses a module listed above it, which is the healthy direction.
repository.services uses repository.l10n, so a change to repository.l10n can break repository.services, while a change to repository.services can't break repository.l10n.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
repository.services uses repository.models, so a change to repository.models can break repository.services, while a change to repository.services can't break repository.models.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
repository.services uses repository.eval, so a change to repository.eval can break repository.services, while a change to repository.services can't break repository.eval.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
repository.services uses repository.providers, so a change to repository.providers can break repository.services, while a change to repository.services can't break repository.providers.
Position
Below the diagonal: repository.services uses a module listed above it, which is the healthy direction.
37→38 repository.services uses repository.srcpart of a loop✕
Connections
1 pair of types, where a type in repository.services uses a type in repository.src.
repository.services uses repository.src, so a change to repository.src can break repository.services, while a change to repository.services can't break repository.src.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30 pairs of types, where a type in repository.src uses a type in repository.services. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository.src uses repository.services, so a change to repository.services can break repository.src, while a change to repository.src can't break repository.services.
Position
Below the diagonal: repository.src uses a module listed above it, which is the healthy direction.
repository.modules uses repository.l10n, so a change to repository.l10n can break repository.modules, while a change to repository.modules can't break repository.l10n.
Position
Below the diagonal: repository.modules uses a module listed above it, which is the healthy direction.
repository.modules uses repository.utils, so a change to repository.utils can break repository.modules, while a change to repository.modules can't break repository.utils.
Position
Below the diagonal: repository.modules uses a module listed above it, which is the healthy direction.
170 pairs of types, where a type in repository.modules uses a type in repository.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository.modules uses repository.models, so a change to repository.models can break repository.modules, while a change to repository.modules can't break repository.models.
Position
Below the diagonal: repository.modules uses a module listed above it, which is the healthy direction.
115 pairs of types, where a type in repository.modules uses a type in repository.eval. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository.modules uses repository.eval, so a change to repository.eval can break repository.modules, while a change to repository.modules can't break repository.eval.
Position
Below the diagonal: repository.modules uses a module listed above it, which is the healthy direction.
35 pairs of types, where a type in repository.modules uses a type in repository.services. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository.modules uses repository.services, so a change to repository.services can break repository.modules, while a change to repository.modules can't break repository.services.
Position
Below the diagonal: repository.modules uses a module listed above it, which is the healthy direction.
repository.modules uses repository.src, so a change to repository.src can break repository.modules, while a change to repository.modules can't break repository.src.
Position
Below the diagonal: repository.modules uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
79
High / Critical
A03:2025 — Software Supply Chain Failures
30
High / Critical
Roadmap
First, integrate static security analysis into the CI pipeline to block regressions and enforce timeout and retry policies on all outbound HTTP calls to prevent hangs. Second, document disaster recovery procedures with tested restore steps and replace weak cryptographic hashes with stronger alternatives where security is relevant. Finally, implement a manual approval gate for releases to ensure bad builds are stopped before they reach users.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_image_resolver.dart:13` (md5.convert(…)), `lib/utils/cryptoaes/crypto_aes.dart:73` (md5.convert(…)), `lib/utils/extensions/others.dart:214` (md5.convert(…)). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 99
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.
Serious — 766
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.
Minor — 69
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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
Watchdog 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. 70 of 73 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 73 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 915 of 934 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog 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 (.dart, .rs) 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. To have real coverage read, produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`), or lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`), or lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog 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 (.dart, .rs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Cargo manifest, but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D22 Internal API Consistency — not measured this run — Watchdog 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 a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — Watchdog 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 — Watchdog 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: 1 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. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 116 further occurrence(s) are not listed individually; the score already reflects all 156.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
101 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rust_lib_mangayomi::aidoku_wasm::host_html::link at 119. A further 12 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being server.getContentType at 35 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: go/server.go (server.getContentType at 35), rust/src/aidoku_wasm/selector.rs (rust_lib_mangayomi::aidoku_wasm::selector::matches_pseudo at 28), lib/modules/more/settings/reader/reader_switches.dart (ReaderSwitch.title at 22), lib/modules/reader_common/mixins/reader_gestures.dart (ReaderKeyboardHandler.handleKeyEvent at 20), lib/modules/reader_common/key_bindings.dart (KeyCombo.label at 19), and 3 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 90 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with rust_lib_mangayomi::aidoku_wasm::host_html::link (cyclomatic 119), NovelPaginator.paginate (cyclomatic 74), _MangaHomeScreenState.build (cyclomatic 64). — 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 4 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 161 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with NovelPaginator.paginate (cognitive 145), rust_lib_mangayomi::aidoku_wasm::host_html::link (cognitive 145), MangayomiRestoreService.restore (cognitive 131). — 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 3 together lifts Cognitive Complexity from 4.1 to about 4.4/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.3 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 85 MethodTooLong finding(s) in God Classes — start with settings.dart (3), service.dart (3), reader_settings_modal.dart (3). — One of this dimension's main actionable groups (85 warning-level).
Resolve the 30 FileTooLong finding(s) in God Classes — start with service.dart (2), main.dart (2), settings.dart. — One of this dimension's main actionable groups (30 warning-level).
Resolve the 22 ClassTooLong finding(s) in God Classes — start with service.dart (2), settings.dart, REDACTED. — One of this dimension's main actionable groups (22 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
154 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 57 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with host_html.rs (3), service.dart (2), models.dart. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 11 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with host_html.rs (3), anime_track_selection_mixin.dart, desktop.dart. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 11 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with library_app_bar.dart, navigation_overlay.dart, reader_gesture_handler.dart. — One of this dimension's main actionable groups (11 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
11 production modules (Gradle+Cargo+Go+pub+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 7 of the 11 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: shiori
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 22 Low cohesion finding(s) in Cohesion (LCOM4) — start with service.dart (3), generated_bindings.dart, anime_player_view.dart. — One of this dimension's main actionable groups (22 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
23 test methods: 23 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 12 `#[test]` function(s) across 3 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Go suite contributes 9 test case(s) across 1 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
0 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 229 resolved pub package(s) use a banned license. Licences were read from pub.dev's analysis of each package's licence file, over every package this repository's pubspec.lock resolves from pub.dev, direct and transitive, at the locked version; the 8 package(s) the lock marks direct dev are excluded, and SDK, path and git packages have no registry release to read. pub.dev analyses only recent releases, so for 9 package(s) locked at an older version the licence read is that of the package's latest analysed release, not of the locked one. 1 of them carry no licence pub.dev recognises; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's pub package dependencies and nothing else. The repository also declares a Cargo manifest, a Go module (REDACTED/go.sum) and a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: REDACTED (49×64=3136); lib/modules/anime/anime_player_view.dart (62×29=1798); lib/modules/manga/detail/manga_detail_view.dart (32×48=1536) Repeated repair below the complexity floor: lib/services/http/m_client.dart (12 of 18 changes were fixes); lib/services/crash_report.dart (6 of 7 changes were fixes); lib/modules/manga/reader/widgets/double_page_view.dart (5 of 9 changes were fixes)
Resolve the 47 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, anime_player_view.dart, manga_detail_view.dart. — One of this dimension's main actionable groups (47 warning-level).
Resolve the 6 Repeated repair finding(s) in Churn × Complexity Hotspots — start with m_client.dart, crash_report.dart, double_page_view.dart. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.7 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
64 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/eval/aidoku/service.dart. Counted over 483 of the 787 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
12 deducted task-comment markers across 138784 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.
Resolve the 12 TodoComment finding(s) in Explicit Debt — start with extension_templates.dart (10), http.rs, bridge_cast_test.dart. — One of this dimension's main actionable groups (12 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
Mangayomi's root README is clear and complete: it states what the project is (an open-source Flutter app for reading manga, novels, and watching animes across multiple platforms), a warning that only GitHub releases and Discord are official sources, features, download instructions, and a disclaimer. The rust_builder/README.md, widgetbook/README.md, and ios/Runner/Assets.xcassets/LaunchImage.imageset/README.md each document their own directories (glue to build Rust with Flutter, Shiori catalogue in browser-only, launch-image assets) rather than the repository as a whole, so they are not flagged. The architecture reference docs are excellent: an active architectural contract status, a top-down dependency graph diagram, Layer 1-4 with import rules and forbidden imports for each layer, and a full design document covering Shiori's colour system, typography, spacing, motion, components, density, Android TV, patterns, accessibility, and migration. The only unflagged element is the absence of an overview section (the opening paragraph about Mangayomi being a multi-platform client) in any document; it does not contradict anything else and is unflaggable.
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 of 9 build units (Cargo, Go, Gradle, Xcode, pub) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
79 finding(s): 0 critical, 73 high, 3 medium, 3 low. 68 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `.github/ISSUE_TEMPLATE/config.yml`, `lib/ffi/image_decoder.h` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. 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 1 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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 68 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 (68 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
2 of 483 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/services/anime_extractors/quarkuc_extractor.dart. Counted over 483 of the 787 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with quarkuc_extractor.dart. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Orphaned file finding(s) in Knowledge Freshness — start with update_source.py. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Boundary-crossing change coupling finding(s) in Change Coupling — start with settings.dart (2), anime_player_view.dart, track_state_providers.dart. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 6 Change coupling finding(s) in Change Coupling — start with anilist.dart (2), extension_screen.dart (2), library_gridview_widget.dart. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with manga_detail_view.dart, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 0 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.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
`overrideAssSubtitlesStateProvider` is a keep-alive Riverpod provider and calls `ref.watch(subtitleSettingsStateProvider…)`, which is declared auto-dispose (lib/modules/anime/providers/state_provider.dart:7). The keep-alive provider listens to it for the life of the ProviderContainer, so `subtitleSettingsStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `subtitleSettingsStateProvider` keepAlive too, make `overrideAssSubtitlesStateProvider` auto-dispose, or read it per use outside build. — lib/modules/anime/providers/state_provider.dart:142
`visibleNavDestinationsProvider` is a keep-alive Riverpod provider and calls `ref.watch(navigationOrderStateProvider…)`, which is declared auto-dispose (lib/providers/reader_state_provider.dart:184). The keep-alive provider listens to it for the life of the ProviderContainer, so `navigationOrderStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `navigationOrderStateProvider` keepAlive too, make `visibleNavDestinationsProvider` auto-dispose, or read it per use outside build. — lib/modules/main_view/nav_groups.dart:92
`visibleNavDestinationsProvider` is a keep-alive Riverpod provider and calls `ref.watch(hideItemsStateProvider…)`, which is declared auto-dispose (lib/providers/reader_state_provider.dart:217). The keep-alive provider listens to it for the life of the ProviderContainer, so `hideItemsStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `hideItemsStateProvider` keepAlive too, make `visibleNavDestinationsProvider` auto-dispose, or read it per use outside build. — lib/modules/main_view/nav_groups.dart:93
`lightThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(flexSchemeColorStateProvider…)`, which is declared auto-dispose (lib/providers/flex_scheme_color_state_provider.dart:13). The keep-alive provider listens to it for the life of the ProviderContainer, so `flexSchemeColorStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `flexSchemeColorStateProvider` keepAlive too, make `lightThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:55
`lightThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(tintSurfacesStateProvider…)`, which is declared auto-dispose (lib/providers/tint_surfaces_state_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `tintSurfacesStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `tintSurfacesStateProvider` keepAlive too, make `lightThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:62
`lightThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(blendLevelStateProvider…)`, which is declared auto-dispose (lib/providers/blend_level_state_provider.dart:5). The keep-alive provider listens to it for the life of the ProviderContainer, so `blendLevelStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `blendLevelStateProvider` keepAlive too, make `lightThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:63
`darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(flexSchemeColorStateProvider…)`, which is declared auto-dispose (lib/providers/flex_scheme_color_state_provider.dart:13). The keep-alive provider listens to it for the life of the ProviderContainer, so `flexSchemeColorStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `flexSchemeColorStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:72
`darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(tintSurfacesStateProvider…)`, which is declared auto-dispose (lib/providers/tint_surfaces_state_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `tintSurfacesStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `tintSurfacesStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:79
`darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(blendLevelStateProvider…)`, which is declared auto-dispose (lib/providers/blend_level_state_provider.dart:5). The keep-alive provider listens to it for the life of the ProviderContainer, so `blendLevelStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `blendLevelStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:80
`darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(pureBlackDarkModeStateProvider…)`, which is declared auto-dispose (lib/providers/pure_black_dark_mode_state_provider.dart:5). The keep-alive provider listens to it for the life of the ProviderContainer, so `pureBlackDarkModeStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `pureBlackDarkModeStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build. — lib/modules/more/settings/appearance/providers/theme_provider.dart:82
`fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(checkForExtensionsUpdateStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:213). The keep-alive provider listens to it for the life of the ProviderContainer, so `checkForExtensionsUpdateStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `checkForExtensionsUpdateStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build. — lib/services/fetch_item_sources.dart:16
`fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(extensionsRepoStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:116). The keep-alive provider listens to it for the life of the ProviderContainer, so `extensionsRepoStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `extensionsRepoStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build. — lib/services/fetch_item_sources.dart:17
`fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(androidProxyServerStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:19). The keep-alive provider listens to it for the life of the ProviderContainer, so `androidProxyServerStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `androidProxyServerStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build. — lib/services/fetch_item_sources.dart:24
`fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(autoUpdateExtensionsStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:200). The keep-alive provider listens to it for the life of the ProviderContainer, so `autoUpdateExtensionsStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `autoUpdateExtensionsStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build. — lib/services/fetch_item_sources.dart:25
What to do
Riverpod: a keepAlive provider must only watch, listen to or read in build other keepAlive providers — mark the dependency @Riverpod(keepAlive: true) (or drop .autoDispose), make the consumer auto-dispose too, or read the dependency per use from a Notifier method instead of in build (riverpod_lint: only_use_keep_alive_inside_keep_alive).
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
`AidokuInterpreter.get_image_request` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — rust/src/aidoku_wasm/interpreter.rs:347
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (an encrypted Hive box, a Realm/Isar encryptionKey, SQLCipher) — partial coverage still leaves gaps.
Enforce HTTPS on the server that receives this data: serve TLS (HttpServer.bindSecure, or shelf_io/dart_frog serve(…, securityContext: …)) and send Strict-Transport-Security, or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
Do you agree with this assessment?
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Other · Domain Modelling — Whether an entity protects its own invariants — a class whose identity is derived from its fields (value equality) but whose fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain entity fused to a persistence ORM (drift/floor/isar/objectbox/hive) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Code Health — Unreviewed-generation residue in this repository's Dart: methods whose whole body still throws UnimplementedError or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Dart: methods that only throw UnimplementedError or a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`displayScore`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. (×3) — lib/services/trackers/kitsu.dart:437, lib/services/trackers/myanimelist.dart:452, lib/services/trackers/simkl.dart:448
`getScoreValue`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. (×3) — lib/services/trackers/kitsu.dart:442, lib/services/trackers/myanimelist.dart:457, lib/services/trackers/simkl.dart:453
What to do
Clear the softer debt: re-enable or delete tests marked `skip:`, decide whether each empty method or UnsupportedError is deliberate (and say so in a comment), and replace `// ignore_for_file: type=lint` with targeted, justified ignores.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Only 4/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `macos`, `widgetbook`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your shelf router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 29653 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.
What to do
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — repo/update_source.py:101, repo/update_source.py:123
What to do
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 26 use(s) across 142,581 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Dart: on hot paths, hold numbers in dart:typed_data lists (Int32List, Float64List …) instead of boxed List<int>/List<double>, read through views (sublistView, buffer.asInt32List, asByteData) instead of copying, make lists that never grow growable: false, compute in the SIMD types (Float32x4List …), and build bytes with BytesBuilder(copy: false).
Go: on hot paths, reuse buffers and objects through sync.Pool, preallocate slices and maps with make([]T, 0, n) / make(map[K]V, n), size builders with Grow, append with strconv.Append*, and reslice with buf[:0] instead of allocating anew.
Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`trimCache` is async and calls listSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/services/chapter_cache.dart:137
`clear` is async and calls listSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/services/chapter_cache.dart:184
`download` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. (×2) — lib/services/download_manager/m3u8/m3u8_downloader.dart:97, lib/services/download_manager/m_downloader.dart:79
`getInfohash` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/services/torrent_server.dart:153
`_getPrecompiledArtifacts` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — rust_builder/cargokit/build_tool/lib/src/artifacts_provider.dart:99
`_tryDownloadArtifacts` is async and calls writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — rust_builder/cargokit/build_tool/lib/src/artifacts_provider.dart:184
`build` is async and calls copySync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — rust_builder/cargokit/build_tool/lib/src/build_cmake.dart:19
`build` is async and calls createSync, copySync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — rust_builder/cargokit/build_tool/lib/src/build_gradle.dart:22
`build` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — rust_builder/cargokit/build_tool/lib/src/build_pod.dart:20
`run` is async and calls createSync, readAsBytesSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — rust_builder/cargokit/build_tool/lib/src/precompile_binaries.dart:52
What to do
Dart: await the async dart:io API (readAsString, writeAsString, Process.run, Future.delayed) instead of the *Sync variant or sleep(), or move heavy synchronous work to another isolate with Isolate.run.
Other · Security — Read from this repository's Dart source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS certificate validation — facts about code that hold whether or not it serves anything itself. The TLS protocol version is not read: `dart:io` leaves the protocol floor to the platform's TLS library and has no switch that admits an obsolete version. This repository serves HTTP itself (lib/services/m_extension_server.dart:60 — `HttpServer.bind(`), so its Dart source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Dart spelling appears in production source, not proven on every route. Every server it binds listens on the loopback interface only, so its traffic never leaves the device and HTTPS enforcement is N/A, as it is for a native app's loopback redirect listener (RFC 8252 §7.3).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_image_resolver.dart:13, lib/utils/cryptoaes/crypto_aes.dart:73, lib/utils/extensions/others.dart:214
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: lib/services/m_extension_server.dart:60 — `HttpServer.bind(`.
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_image_resolver.dart:13` (md5.convert(…)), `lib/utils/cryptoaes/crypto_aes.dart:73` (md5.convert(…)), `lib/utils/extensions/others.dart:214` (md5.convert(…)). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Set security response headers on what the server sends — `response.headers.set('X-Content-Type-Options', 'nosniff')` in a `dart:io` handler, or a shelf middleware that adds `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy to every `Response`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`Setting.fromJson` is public and takes `Map<String, dynamic> json` from its caller, and it calls itself at line 297 (`Setting.fromJson`) with a piece of `json` (and at line 424) — and nowhere in `Setting.fromJson` 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. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `Setting.fromJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/eval/aidoku/src/models/setting.dart:297
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`NovelTtsService` carries a disposal duty — it declares its own release — and it creates `_stateController` itself (line 33, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_stateController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_stateController.close();` in `dispose()` before `super.dispose()`. — lib/modules/novel/tts/novel_tts_service.dart:33
`NovelTtsService` carries a disposal duty — it declares its own release — and it creates `_paragraphIndexController` itself (line 34, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_paragraphIndexController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_paragraphIndexController.close();` in `dispose()` before `super.dispose()`. — lib/modules/novel/tts/novel_tts_service.dart:34
`NovelTtsService` carries a disposal duty — it declares its own release — and it creates `_wordProgressController` itself (line 35, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_wordProgressController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_wordProgressController.close();` in `dispose()` before `super.dispose()`. — lib/modules/novel/tts/novel_tts_service.dart:35
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`finer` at line 109 is called with an argument built by `arguments.join('…')` (line 109), whose cost grows with the collection it walks. Dart evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because finer is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLoggable` test, no `kDebugMode` or debug flag, no `assert`, no closure the logger calls only when the level is on. — rust_builder/cargokit/build_tool/lib/src/util.dart:109
What to do
In Dart, put the construction behind the logger's own check (`if (log.isLoggable(Level.FINE))` for package:logging, `if (kDebugMode)` for a line only a debug build needs), or hand the logger a closure it calls only when the record is written (`log.fine(() => 'rows: ${rows.map((r) => r.id).join(', ')}')`; package:logger's `logger.d(() => …)` likewise). Interpolating the value into the message is not the fix: Dart builds the string, and every `map`, `join` or `jsonEncode` inside it, before the call is entered.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`if err != nil` 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) — go/server.go:384, go/server.go:665
`catch (_)` 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. (×14) — lib/main.dart:636, lib/eval/dart/service.dart:44, lib/eval/dart/service.dart:55, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — lib/eval/aidoku/service.dart:153, lib/eval/aidoku/service.dart:187, lib/eval/aidoku/service.dart:233, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. (×3) — lib/eval/aidoku/src/interpreter/js_manager.dart:277, lib/eval/aidoku/src/interpreter/js_manager.dart:284, lib/eval/aidoku/src/interpreter/js_manager.dart:446
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table, collection or model — a Drift table, an Isar collection, a Hive type or a Serverpod table named for it — or a Drift QueryInterceptor that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
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
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — ~20311 lines of test source are present (.dart, .rs) 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 — no .dart test runner
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.
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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Aggregate boundaries — not scored for Dart: aggregate-vs-value-object classification cannot be told apart in source (every class-holding-class reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — reported as guidance rather than measured
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — not scored for Dart: a cross-package domain leak cannot be told apart in source from a legitimate shared-kernel package, and most repositories ship a single package — reported as guidance rather than measured
DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
DM7 Repository granularity — not scored for Dart: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — no C# was loaded; this repository's Dart, Python and Rust were read, and no request in it can be cancelled by a caller (Dio, or package:http's Abortable requests) — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
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 Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Captive dependency: keepAlive provider overrideAssSubtitlesStateProvider captures autoDispose subtitleSettingsStateProvider lib/modules/anime/providers/state_provider.dart:142— `overrideAssSubtitlesStateProvider` is a keep-alive Riverpod provider and calls `ref.watch(subtitleSettingsStateProvider…)`, which is declared auto-dispose (lib/modules/anime/providers/state_provider.dart:7). The keep-alive provider listens to it for the life of the ProviderContainer, so `subtitleSettingsStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `subtitleSettingsStateProvider` keepAlive too, make `overrideAssSubtitlesStateProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider visibleNavDestinationsProvider captures autoDispose navigationOrderStateProvider lib/modules/main_view/nav_groups.dart:92— `visibleNavDestinationsProvider` is a keep-alive Riverpod provider and calls `ref.watch(navigationOrderStateProvider…)`, which is declared auto-dispose (lib/providers/reader_state_provider.dart:184). The keep-alive provider listens to it for the life of the ProviderContainer, so `navigationOrderStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `navigationOrderStateProvider` keepAlive too, make `visibleNavDestinationsProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider visibleNavDestinationsProvider captures autoDispose hideItemsStateProvider lib/modules/main_view/nav_groups.dart:93— `visibleNavDestinationsProvider` is a keep-alive Riverpod provider and calls `ref.watch(hideItemsStateProvider…)`, which is declared auto-dispose (lib/providers/reader_state_provider.dart:217). The keep-alive provider listens to it for the life of the ProviderContainer, so `hideItemsStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `hideItemsStateProvider` keepAlive too, make `visibleNavDestinationsProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider lightThemeProvider captures autoDispose flexSchemeColorStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:55— `lightThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(flexSchemeColorStateProvider…)`, which is declared auto-dispose (lib/providers/flex_scheme_color_state_provider.dart:13). The keep-alive provider listens to it for the life of the ProviderContainer, so `flexSchemeColorStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `flexSchemeColorStateProvider` keepAlive too, make `lightThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider lightThemeProvider captures autoDispose tintSurfacesStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:62— `lightThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(tintSurfacesStateProvider…)`, which is declared auto-dispose (lib/providers/tint_surfaces_state_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `tintSurfacesStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `tintSurfacesStateProvider` keepAlive too, make `lightThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider lightThemeProvider captures autoDispose blendLevelStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:63— `lightThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(blendLevelStateProvider…)`, which is declared auto-dispose (lib/providers/blend_level_state_provider.dart:5). The keep-alive provider listens to it for the life of the ProviderContainer, so `blendLevelStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `blendLevelStateProvider` keepAlive too, make `lightThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider darkThemeProvider captures autoDispose flexSchemeColorStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:72— `darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(flexSchemeColorStateProvider…)`, which is declared auto-dispose (lib/providers/flex_scheme_color_state_provider.dart:13). The keep-alive provider listens to it for the life of the ProviderContainer, so `flexSchemeColorStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `flexSchemeColorStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider darkThemeProvider captures autoDispose tintSurfacesStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:79— `darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(tintSurfacesStateProvider…)`, which is declared auto-dispose (lib/providers/tint_surfaces_state_provider.dart:6). The keep-alive provider listens to it for the life of the ProviderContainer, so `tintSurfacesStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `tintSurfacesStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider darkThemeProvider captures autoDispose blendLevelStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:80— `darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(blendLevelStateProvider…)`, which is declared auto-dispose (lib/providers/blend_level_state_provider.dart:5). The keep-alive provider listens to it for the life of the ProviderContainer, so `blendLevelStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `blendLevelStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider darkThemeProvider captures autoDispose pureBlackDarkModeStateProvider lib/modules/more/settings/appearance/providers/theme_provider.dart:82— `darkThemeProvider` is a keep-alive Riverpod provider and calls `ref.watch(pureBlackDarkModeStateProvider…)`, which is declared auto-dispose (lib/providers/pure_black_dark_mode_state_provider.dart:5). The keep-alive provider listens to it for the life of the ProviderContainer, so `pureBlackDarkModeStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `pureBlackDarkModeStateProvider` keepAlive too, make `darkThemeProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider fetchItemSourcesListProvider captures autoDispose checkForExtensionsUpdateStateProvider lib/services/fetch_item_sources.dart:16— `fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(checkForExtensionsUpdateStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:213). The keep-alive provider listens to it for the life of the ProviderContainer, so `checkForExtensionsUpdateStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `checkForExtensionsUpdateStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider fetchItemSourcesListProvider captures autoDispose extensionsRepoStateProvider lib/services/fetch_item_sources.dart:17— `fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(extensionsRepoStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:116). The keep-alive provider listens to it for the life of the ProviderContainer, so `extensionsRepoStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `extensionsRepoStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider fetchItemSourcesListProvider captures autoDispose androidProxyServerStateProvider lib/services/fetch_item_sources.dart:24— `fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(androidProxyServerStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:19). The keep-alive provider listens to it for the life of the ProviderContainer, so `androidProxyServerStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `androidProxyServerStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build.
Captive dependency: keepAlive provider fetchItemSourcesListProvider captures autoDispose autoUpdateExtensionsStateProvider lib/services/fetch_item_sources.dart:25— `fetchItemSourcesListProvider` is a keep-alive Riverpod provider and calls `ref.watch(autoUpdateExtensionsStateProvider…)`, which is declared auto-dispose (lib/providers/browse_state_provider.dart:200). The keep-alive provider listens to it for the life of the ProviderContainer, so `autoUpdateExtensionsStateProvider` is never disposed — the auto-dispose lifetime it declares never happens, and whatever it holds (a socket, a controller, a stale value) is kept for every later reader. Mark `autoUpdateExtensionsStateProvider` keepAlive too, make `fetchItemSourcesListProvider` auto-dispose, or read it per use outside build.
Boundary-crossing change coupling: anime_player_view.dart ↔ player_screen.dart lib/modules/anime/anime_player_view.dart:1— `lib/modules/anime/anime_player_view.dart` (context anime) and `lib/modules/more/settings/player/player_screen.dart` (context more) sit in DIFFERENT parts of the tree yet change together 70% of the time (14 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `79ee4b4f` add a force landscapre mode on mobile; `72dd2d76` removed iOS PiP; `20c943e5` testing iOS Picture-in-Picture — run `git show` on any of them.
Boundary-crossing change coupling: track_state_providers.dart ↔ myanimelist.dart lib/modules/manga/detail/providers/track_state_providers.dart:1— `lib/modules/manga/detail/providers/track_state_providers.dart` (context manga) and `lib/services/trackers/myanimelist.dart` (context services) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `92c167d5` merged trackers together and added search; `06ca4416` added Kitsu and Anilist; `e994d323` + — run `git show` on any of them.
Boundary-crossing change coupling: settings.dart ↔ player_screen.dart lib/models/settings.dart:1— `lib/models/settings.dart` (context models) and `lib/modules/more/settings/player/player_screen.dart` (context more) sit in DIFFERENT parts of the tree yet change together 55% of the time (11 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `79ee4b4f` add a force landscapre mode on mobile; `72dd2d76` removed iOS PiP; `20c943e5` testing iOS Picture-in-Picture — run `git show` on any of them.
Boundary-crossing change coupling: manga_detail_view.dart ↔ downloads_screen.dart lib/modules/manga/detail/manga_detail_view.dart:1— `lib/modules/manga/detail/manga_detail_view.dart` (context manga) and `lib/modules/more/settings/downloads/downloads_screen.dart` (context more) sit in DIFFERENT parts of the tree yet change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `6a446eb2` Update FilePicker package; `265531f3` ix(download): restore downloads to downloads folder instead of local …; `c11b8751` adding virtual local folders — run `git show` on any of them.
Boundary-crossing change coupling: settings.dart ↔ downloads_state_provider.dart lib/models/settings.dart:1— `lib/models/settings.dart` (context models) and `lib/modules/more/settings/downloads/providers/downloads_state_provider.dart` (context more) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c11b8751` adding virtual local folders; `c59d6067` feat(downloads): concurrency toggle and download rate limit; `77b912d4` added download all option — run `git show` on any of them.
Boundary-crossing change coupling: download_page_widget.dart ↔ downloads_state_provider.dart lib/modules/manga/download/download_page_widget.dart:1— `lib/modules/manga/download/download_page_widget.dart` (context manga) and `lib/modules/more/settings/downloads/providers/downloads_state_provider.dart` (context more) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c11b8751` adding virtual local folders; `1457b05b` Reapply "Merge pull request #332 from NBA2K1/main"; `645bda03` Revert "Merge pull request #332 from NBA2K1/main" — run `git show` on any of them.
AX9 · CQS / query purity· Query writes persistent state on the read path · ×1
Query writes persistent state on the read path: AidokuInterpreter.get_image_request rust/src/aidoku_wasm/interpreter.rs:347— `AidokuInterpreter.get_image_request` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
Orphaned knowledge lib/services/anime_extractors/quarkuc_extractor.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
MethodTooLong: _MangaChapterPageGalleryState.build REDACTED:568— MethodTooLong — build runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _MangaDetailViewState._buildWidget lib/modules/manga/detail/manga_detail_view.dart:190— MethodTooLong — _buildWidget runs 379 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 279 over it, 3.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _MangaHomeScreenState.build lib/modules/manga/home/manga_home_screen.dart:270— MethodTooLong — build runs 365 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 265 over it, 3.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _MobileControllerWidgetState.build REDACTED:457— MethodTooLong — build runs 346 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Settings.fromJson lib/models/settings.dart:722— MethodTooLong — fromJson runs 337 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 237 over it, 3.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JsCheerio.init lib/eval/lnreader/js_cheerio.dart:15— MethodTooLong — init runs 324 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NovelBottomBar.build lib/modules/novel/widgets/novel_bottom_bar.dart:173— MethodTooLong — build runs 315 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 215 over it, 3.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _ReaderSettingsTabState.build lib/modules/novel/widgets/novel_reader_settings_sheet.dart:53— MethodTooLong — build runs 302 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JsDomSelector.init lib/eval/javascript/dom_selector.dart:13— MethodTooLong — init runs 300 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 200 over it, 3.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _TvAnimeHomeViewState.build lib/modules/library/tv_home/tv_anime_home_view.dart:129— MethodTooLong — build runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _DesktopControllerWidgetState.build lib/modules/anime/widgets/desktop.dart:326— MethodTooLong — build runs 270 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 170 over it, 2.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TachiyomiRestoreService.restore lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:30— MethodTooLong — restore runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Settings.toJson lib/models/settings.dart:1084— MethodTooLong — toJson runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _TrackerWidgetState.build lib/modules/manga/detail/widgets/tracker_widget.dart:61— MethodTooLong — build runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MProviderBridged.registerBridgedClasses lib/eval/dart/bridge/m_provider.dart:62— MethodTooLong — registerBridgedClasses runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ReaderScreen.build lib/modules/more/settings/reader/reader_screen.dart:47— MethodTooLong — build runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NovelPaginator.paginate lib/modules/novel/utils/novel_paginator.dart:107— MethodTooLong — paginate runs 237 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 137 over it, 2.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _SubtitleAppearanceWidgetState.build lib/modules/anime/widgets/subtitle_setting_widget.dart:146— MethodTooLong — build runs 235 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 135 over it, 2.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _NovelWebViewState.build lib/modules/novel/novel_reader_view.dart:301— MethodTooLong — build runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Settings.Settings lib/models/settings.dart:495— MethodTooLong — Settings runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AnimeMpvBridgeMixin._handleMpvNodeEvents lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:92— MethodTooLong — _handleMpvNodeEvents runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AidokuExtensionService.getSourcePreferences lib/eval/aidoku/service.dart:607— MethodTooLong — getSourcePreferences runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExtensionStoreService._parseLegacyJsonStore lib/services/extension_store_service.dart:328— MethodTooLong — _parseLegacyJsonStore runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Setting.fromJson lib/eval/aidoku/src/models/setting.dart:279— MethodTooLong — fromJson runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _GeneralStateScreen.build lib/modules/more/settings/general/general_screen.dart:42— MethodTooLong — build runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: REDACTED REDACTED:568— REDACTED changed 49 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in _MangaChapterPageGalleryState.build at line 568. 15 of those changes were fix/bug commits, and the other 34 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/anime/anime_player_view.dart lib/modules/anime/anime_player_view.dart:954— lib/modules/anime/anime_player_view.dart changed 62 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in _AnimeStreamPageState._videoPlayer at line 954. 21 of those changes were fix/bug commits, and the other 41 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/anime/anime_player_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/detail/manga_detail_view.dart lib/modules/manga/detail/manga_detail_view.dart:190— lib/modules/manga/detail/manga_detail_view.dart changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in _MangaDetailViewState._buildWidget at line 190. 9 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/detail/manga_detail_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/models/settings.dart lib/models/settings.dart:722— lib/models/settings.dart changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in Settings.fromJson at line 722. 2 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/models/settings.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/main.dart lib/main.dart:493— lib/main.dart changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in _MyAppState._initDeepLinks at line 493. 7 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/main.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:457— REDACTED changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in _MobileControllerWidgetState.build at line 457. 5 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/main_view/main_screen.dart lib/modules/main_view/main_screen.dart:127— lib/modules/main_view/main_screen.dart changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in _MainScreenState.build at line 127. 3 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/main_view/main_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/home/manga_home_screen.dart lib/modules/manga/home/manga_home_screen.dart:270— lib/modules/manga/home/manga_home_screen.dart changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in _MangaHomeScreenState.build at line 270. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/home/manga_home_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/novel/novel_reader_view.dart lib/modules/novel/novel_reader_view.dart:301— lib/modules/novel/novel_reader_view.dart changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in _NovelWebViewState.build at line 301. 7 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/novel/novel_reader_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/services/extension_store_service.dart lib/services/extension_store_service.dart:328— lib/services/extension_store_service.dart changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in ExtensionStoreService._parseLegacyJsonStore at line 328. 3 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/services/extension_store_service.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:1245— lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in _SubsamplingScaleImageViewState.build at line 1245. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/reader/providers/reader_controller_provider.dart lib/modules/manga/reader/providers/reader_controller_provider.dart:134— lib/modules/manga/reader/providers/reader_controller_provider.dart changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in ReaderController.setPageIndex at line 134. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/reader/providers/reader_controller_provider.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/services/sync_server.dart lib/services/sync_server.dart:152— lib/services/sync_server.dart changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in SyncServer.startSync at line 152. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/services/sync_server.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/updates/updates_screen.dart lib/modules/updates/updates_screen.dart:192— lib/modules/updates/updates_screen.dart changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in _UpdateTabState.build at line 192. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/updates/updates_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:234— REDACTED changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in _SourceRepositoriesState._showAddRepoDialog at line 234. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/anime/widgets/desktop.dart lib/modules/anime/widgets/desktop.dart:326— lib/modules/anime/widgets/desktop.dart changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in _DesktopControllerWidgetState.build at line 326. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/anime/widgets/desktop.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/reader/image_view_webtoon.dart lib/modules/manga/reader/image_view_webtoon.dart:293— lib/modules/manga/reader/image_view_webtoon.dart changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in _ImageViewWebtoonState._handleScaleUpdate at line 293. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/reader/image_view_webtoon.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/novel/utils/novel_paginator.dart lib/modules/novel/utils/novel_paginator.dart:107— lib/modules/novel/utils/novel_paginator.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in NovelPaginator.paginate at line 107. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/novel/utils/novel_paginator.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/library/tv_home/tv_anime_home_view.dart lib/modules/library/tv_home/tv_anime_home_view.dart:129— lib/modules/library/tv_home/tv_anime_home_view.dart changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in _TvAnimeHomeViewState.build at line 129. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/library/tv_home/tv_anime_home_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/browse/browse_screen.dart lib/modules/browse/browse_screen.dart:337— lib/modules/browse/browse_screen.dart changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in _BrowseScreenState.build at line 337. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/browse/browse_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/eval/model/m_bridge.dart lib/eval/model/m_bridge.dart:519— lib/eval/model/m_bridge.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in MBridge.parseChapterDate at line 519. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/eval/model/m_bridge.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/browse/extension/widgets/create_extension.dart lib/modules/browse/extension/widgets/create_extension.dart:43— lib/modules/browse/extension/widgets/create_extension.dart changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in _CreateExtensionState.build at line 43. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/browse/extension/widgets/create_extension.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:349— lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in _MinSubsamplingImageState.build at line 349. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/reader/image_view_paged.dart lib/modules/manga/reader/image_view_paged.dart:168— lib/modules/manga/reader/image_view_paged.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in _ImageViewPagedState._performLandscapeZoom at line 168. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/reader/image_view_paged.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/modules/manga/detail/widgets/manga_info_header.dart lib/modules/manga/detail/widgets/manga_info_header.dart:74— lib/modules/manga/detail/widgets/manga_info_header.dart changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in _MangaInfoHeaderState.build at line 74. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/detail/widgets/manga_info_header.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: models/settings.dart lib/models/settings.dart— FileTooLong — 1440 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: Settings (8-1332). The bar is 500 significant lines; this is 940 over it, 2.88× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 979 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: _MangaChapterPageGalleryState (190-1380). The bar is 500 significant lines; this is 479 over it, 1.96× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: anime/anime_player_view.dart lib/modules/anime/anime_player_view.dart— FileTooLong — 918 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: _AnimeStreamPageState (242-1236). The bar is 500 significant lines; this is 418 over it, 1.84× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: aidoku_wasm/host_html.rs rust/src/aidoku_wasm/host_html.rs— FileTooLong — 914 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 414 over it, 1.83× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: go/server.go go/server.go— FileTooLong — 911 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 411 over it, 1.82× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/subsampling_scale_image_view.dart lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart— FileTooLong — 869 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: _SubsamplingScaleImageViewState (369-1351). The bar is 500 significant lines; this is 369 over it, 1.74× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: settings/settings_index.dart lib/modules/more/settings/settings_index.dart— FileTooLong — 856 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 356 over it, 1.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: aidoku/service.dart lib/eval/aidoku/service.dart— FileTooLong — 832 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: AidokuExtensionService (22-1107). The bar is 500 significant lines; this is 332 over it, 1.66× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: model/m_bridge.dart lib/eval/model/m_bridge.dart— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: MBridge (74-820). The bar is 500 significant lines; this is 206 over it, 1.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/main.dart widgetbook/lib/main.dart— FileTooLong — 702 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 202 over it, 1.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: aidoku_wasm/models.rs rust/src/aidoku_wasm/models.rs— FileTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 186 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: _MobileControllerWidgetState (63-972). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: services/extension_store_service.dart lib/services/extension_store_service.dart— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ExtensionStoreService (25-763). The bar is 500 significant lines; this is 110 over it, 1.22× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: novel/novel_reader_view.dart lib/modules/novel/novel_reader_view.dart— FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: _NovelWebViewState (72-821). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: discovery/trakt_discovery.dart lib/services/discovery/trakt_discovery.dart— FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: lib/main.dart lib/main.dart— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: _MyAppState (272-805). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: home/manga_home_screen.dart lib/modules/manga/home/manga_home_screen.dart— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: _MangaHomeScreenState (64-776). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: extension/edit_code.dart lib/modules/browse/extension/edit_code.dart— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: _CodeEditorPageState (39-721). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: library/library_screen.dart lib/modules/library/library_screen.dart— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: _LibraryScreenState (61-691). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: download_manager/download_isolate_pool.dart lib/services/download_manager/download_isolate_pool.dart— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: widgets/watch_order_screen.dart lib/modules/manga/detail/widgets/watch_order_screen.dart— FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: _WatchOrderScreenState (41-786). The bar is 500 significant lines; this is 32 over it, 1.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/source.dart lib/eval/aidoku/src/source.dart— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: Source (24-711). The bar is 500 significant lines; this is 31 over it, 1.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: detail/manga_detail_view.dart lib/modules/manga/detail/manga_detail_view.dart— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: _MangaDetailViewState (63-683). The bar is 500 significant lines; this is 26 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: http/m_client.dart lib/services/http/m_client.dart— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 26 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: providers/reader_state_provider.dart lib/providers/reader_state_provider.dart— FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 17 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:153— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:187— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:233— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:250— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:357— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:449— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:457— 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.
Swallowed exception (empty catch) lib/eval/aidoku/service.dart:669— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:277— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:284— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:319— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:366— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:398— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:424— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:438— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/interpreter/js_manager.dart:446— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
Swallowed exception (empty catch) lib/eval/aidoku/src/store/settings_store.dart:24— 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.
Swallowed exception (empty catch) lib/eval/aidoku/src/store/settings_store.dart:56— 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.
Swallowed exception (empty catch) lib/eval/lnreader/service.dart:202— 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.
Swallowed exception (empty catch) lib/eval/lnreader/service.dart:438— 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.
Swallowed exception (empty catch) lib/eval/lnreader/service.dart:579— 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.
Swallowed exception (empty catch) lib/eval/lnreader/service.dart:619— 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.
Swallowed exception (empty catch) lib/eval/lnreader/service.dart:637— 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.
Swallowed exception (empty catch) lib/eval/model/m_bridge.dart:478— 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.
ClassTooLong: Settings lib/models/settings.dart:6— ClassTooLong — 1053 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 653 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _MangaChapterPageGalleryState REDACTED:190— ClassTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 439 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AidokuExtensionService lib/eval/aidoku/service.dart:22— ClassTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 413 over it, 2.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _AnimeStreamPageState lib/modules/anime/anime_player_view.dart:242— ClassTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods. The bar is 400 significant lines; this is 337 over it, 1.84× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _SubsamplingScaleImageViewState lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:369— ClassTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 269 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _MobileControllerWidgetState REDACTED:63— ClassTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 207 over it, 1.52× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExtensionStoreService lib/services/extension_store_service.dart:25— ClassTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 192 over it, 1.48× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _NovelWebViewState lib/modules/novel/novel_reader_view.dart:72— ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 131 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MBridge lib/eval/model/m_bridge.dart:74— ClassTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 120 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Source lib/eval/aidoku/src/source.dart:23— ClassTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 112 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _MangaHomeScreenState lib/modules/manga/home/manga_home_screen.dart:64— ClassTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 110 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _WatchOrderScreenState lib/modules/manga/detail/widgets/watch_order_screen.dart:41— ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 100 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _CodeEditorPageState lib/modules/browse/extension/edit_code.dart:39— ClassTooLong — 498 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 98 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LNReaderExtensionService lib/eval/lnreader/service.dart:32— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 79 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _MangaDetailViewState lib/modules/manga/detail/manga_detail_view.dart:63— ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 70 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _DesktopControllerWidgetState lib/modules/anime/widgets/desktop.dart:72— ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 36 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Anilist lib/services/trackers/anilist.dart:27— ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 35 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _LibraryScreenState lib/modules/library/library_screen.dart:61— ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 35 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TraktTv lib/services/trackers/trakt_tv.dart:22— ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 34 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _ExtensionServerScreenState lib/modules/more/settings/browse/extension_server_screen.dart:34— ClassTooLong — 422 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 22 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: QuarkUcExtractor lib/services/anime_extractors/quarkuc_extractor.dart:11— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 21 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MangaRepository lib/repositories/manga_repository.dart:21— ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 19 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: TorrentLibrary (LCOM4 67) lib/ffi/generated_bindings.dart:13— TorrentLibrary's methods fall into 67 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 67 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _AnimeStreamPageState (LCOM4 13) lib/modules/anime/anime_player_view.dart:242— _AnimeStreamPageState's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _MangaChapterPageGalleryState (LCOM4 9) REDACTED:190— _MangaChapterPageGalleryState's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NovelPaginationResult (LCOM4 9) lib/modules/novel/utils/novel_paginator.dart:7— NovelPaginationResult's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _MyAppState (LCOM4 8) lib/main.dart:272— _MyAppState's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RustLibWire (LCOM4 8) lib/src/rust/frb_generated.io.dart:1712— RustLibWire's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MyAnimeList (LCOM4 7) lib/services/trackers/myanimelist.dart:25— MyAnimeList's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TraktTv (LCOM4 7) lib/services/trackers/trakt_tv.dart:22— TraktTv's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Anilist (LCOM4 6) lib/services/trackers/anilist.dart:27— Anilist's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Kitsu (LCOM4 6) lib/services/trackers/kitsu.dart:22— Kitsu's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Simkl (LCOM4 6) lib/services/trackers/simkl.dart:37— Simkl's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AidokuRustRunner (LCOM4 5) lib/eval/aidoku/src/interpreter/rust_runner.dart:10— AidokuRustRunner's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LNReaderExtensionService (LCOM4 5) lib/eval/lnreader/service.dart:32— LNReaderExtensionService's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AnimeStreamController (LCOM4 5) lib/modules/anime/providers/anime_player_controller_provider.dart:17— AnimeStreamController's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _TvAnimeDetailViewState (LCOM4 5) lib/modules/manga/detail/tv/tv_anime_detail_view.dart:43— _TvAnimeDetailViewState's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _OnboardingScreenState (LCOM4 5) lib/modules/onboarding/onboarding_screen.dart:92— _OnboardingScreenState's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _UpdatesScreenState (LCOM4 5) lib/modules/updates/updates_screen.dart:33— _UpdatesScreenState's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MyInAppBrowser (LCOM4 5) lib/modules/webview/webview.dart:478— MyInAppBrowser's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AidokuExtensionService (LCOM4 4) lib/eval/aidoku/service.dart:22— AidokuExtensionService's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MihonExtensionService (LCOM4 4) lib/eval/mihon/service.dart:35— MihonExtensionService's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NovelReaderController (LCOM4 4) lib/modules/novel/novel_reader_controller_provider.dart:10— NovelReaderController's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DiscordRPC (LCOM4 4) lib/services/discord_rpc.dart:10— DiscordRPC's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Swallowed exception (caught, then discarded) go/server.go:384— `if err != nil` 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.
Swallowed exception (caught, then discarded) go/server.go:665— `if err != nil` 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.
Swallowed exception (caught, then discarded) lib/main.dart:636— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/dart/service.dart:44— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/dart/service.dart:55— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/dart/service.dart:64— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/dart/service.dart:158— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/javascript/service.dart:221— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/lnreader/service.dart:301— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/lnreader/service.dart:376— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/lnreader/service.dart:421— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/lnreader/service.dart:575— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/model/m_bridge.dart:99— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/model/m_bridge.dart:135— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/model/m_bridge.dart:144— `catch (_)` 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.
Swallowed exception (caught, then discarded) lib/eval/model/m_bridge.dart:157— `catch (_)` 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.
Duplicated block (8 lines × 2) lib/eval/aidoku/service.dart:258— lib/eval/aidoku/service.dart:258-265 | lib/eval/aidoku/service.dart:278-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/eval/mihon/models.dart:62— lib/eval/mihon/models.dart:62-69 | lib/eval/mihon/service.dart:190-199 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/eval/mihon/service.dart:212— lib/eval/mihon/service.dart:212-219 | lib/eval/mihon/service.dart:236-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/modules/anime/mixins/anime_track_selection_mixin.dart:252— lib/modules/anime/mixins/anime_track_selection_mixin.dart:252-259 | lib/modules/anime/mixins/anime_track_selection_mixin.dart:274-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/modules/browse/sources/sources_screen.dart:176— lib/modules/browse/sources/sources_screen.dart:176-183 | lib/modules/browse/sources/sources_screen.dart:190-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/modules/manga/detail/providers/state_providers.dart:259— lib/modules/manga/detail/providers/state_providers.dart:259-266 | lib/modules/manga/detail/providers/state_providers.dart:280-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/modules/manga/reader/image_view_webtoon.dart:322— lib/modules/manga/reader/image_view_webtoon.dart:322-329 | lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:1095-1102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:144— lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:144-151 | lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:280-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/services/trackers/anilist.dart:544— lib/services/trackers/anilist.dart:544-551 | lib/services/trackers/myanimelist.dart:306-313 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/services/trackers/myanimelist.dart:283— lib/services/trackers/myanimelist.dart:283-290 | lib/services/trackers/myanimelist.dart:319-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) rust/src/aidoku_wasm/host_html.rs:747— rust/src/aidoku_wasm/host_html.rs:747-754 | rust/src/aidoku_wasm/host_html.rs:832-839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) rust/src/aidoku_wasm/host_html.rs:63— rust/src/aidoku_wasm/host_html.rs:63-70 | rust/src/aidoku_wasm/host_html.rs:85-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) rust/src/aidoku_wasm/host_net.rs:249— rust/src/aidoku_wasm/host_net.rs:249-256 | rust/src/aidoku_wasm/host_net.rs:279-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) rust/src/aidoku_wasm/host_html.rs:344— rust/src/aidoku_wasm/host_html.rs:344-351 | rust/src/aidoku_wasm/host_html.rs:952-959 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:67— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:80— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:105— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:160— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:170— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:178— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:214— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:224— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:258— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/modules/browse/extension/widgets/extension_templates.dart:284— // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment rust/src/api/rhttp/http.rs:283— // TODO: This is a hacky way to check if the error is a certificate error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/eval/bridge_cast_test.dart:23— // TODO: implement callableRuntimeType — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (13 lines × 2) lib/modules/anime/mixins/anime_track_selection_mixin.dart:127— lib/modules/anime/mixins/anime_track_selection_mixin.dart:127-139 | lib/modules/anime/mixins/anime_track_selection_mixin.dart:259-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/modules/anime/widgets/desktop.dart:430— lib/modules/anime/widgets/desktop.dart:430-442 | REDACTED:464-476 — before extracting anything, compare `lib/modules/anime/widgets/desktop.dart` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/modules/library/tv_home/widgets/tv_home_hero.dart:388— lib/modules/library/tv_home/widgets/tv_home_hero.dart:388-400 | lib/modules/widgets/tv_pill.dart:127-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/modules/manga/reader/widgets/reader_gesture_handler.dart:102— lib/modules/manga/reader/widgets/reader_gesture_handler.dart:102-114 | lib/modules/manga/reader/widgets/reader_gesture_handler.dart:116-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:178— lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:178-190 | lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:310-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) repo/update_source.py:92— repo/update_source.py:92-104 | repo/update_source.py:111-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) rust/src/aidoku_wasm/host_html.rs:32— rust/src/aidoku_wasm/host_html.rs:32-44 | rust/src/aidoku_wasm/host_html.rs:55-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) rust/src/aidoku_wasm/host_html.rs:234— rust/src/aidoku_wasm/host_html.rs:234-246 | rust/src/aidoku_wasm/host_html.rs:566-578 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) rust/src/aidoku_wasm/host_html.rs:707— rust/src/aidoku_wasm/host_html.rs:707-719 | rust/src/aidoku_wasm/host_html.rs:736-748 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) rust/src/api/aidoku_wasm.rs:444— rust/src/api/aidoku_wasm.rs:444-456 | rust/src/api/aidoku_wasm.rs:460-472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) rust/src/api/rar.rs:64— rust/src/api/rar.rs:64-76 | rust/src/api/rar.rs:118-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/modules/library/widgets/library_app_bar.dart:328— lib/modules/library/widgets/library_app_bar.dart:328-337 | lib/modules/manga/detail/widgets/detail_app_bar.dart:76-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/modules/manga/reader/widgets/navigation_overlay.dart:93— lib/modules/manga/reader/widgets/navigation_overlay.dart:93-102 | lib/modules/manga/reader/widgets/navigation_overlay.dart:179-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/modules/manga/reader/widgets/reader_gesture_handler.dart:195— lib/modules/manga/reader/widgets/reader_gesture_handler.dart:195-204 | lib/modules/manga/reader/widgets/reader_gesture_handler.dart:294-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/modules/manga/reader/widgets/reader_settings_modal.dart:326— lib/modules/manga/reader/widgets/reader_settings_modal.dart:326-335 | lib/modules/more/settings/reader/reader_screen.dart:111-120 — before extracting anything, compare `lib/modules/manga/reader/widgets/reader_settings_modal.dart` and `lib/modules/more/settings/reader/reader_screen.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/services/discovery/trakt_discovery.dart:261— lib/services/discovery/trakt_discovery.dart:261-270 | lib/services/discovery/trakt_discovery.dart:277-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/services/trackers/kitsu.dart:179— lib/services/trackers/kitsu.dart:179-188 | lib/services/trackers/kitsu.dart:272-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/services/trackers/simkl.dart:204— lib/services/trackers/simkl.dart:204-213 | lib/services/trackers/trakt_tv.dart:277-286 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) rust/src/aidoku_wasm/host_html.rs:380— rust/src/aidoku_wasm/host_html.rs:380-389 | rust/src/aidoku_wasm/host_html.rs:918-927 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) rust/src/aidoku_wasm/host_net.rs:215— rust/src/aidoku_wasm/host_net.rs:215-224 | rust/src/aidoku_wasm/host_net.rs:265-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) rust/src/aidoku_wasm/host_canvas.rs:157— rust/src/aidoku_wasm/host_canvas.rs:157-166 | rust/src/aidoku_wasm/host_canvas.rs:167-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) rust/src/aidoku_wasm/host_env.rs:34— rust/src/aidoku_wasm/host_env.rs:34-43 | rust/src/aidoku_wasm/host_std.rs:138-147 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Sync-over-async blocking lib/services/chapter_cache.dart:137— `trimCache` is async and calls listSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/services/chapter_cache.dart:184— `clear` is async and calls listSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/services/download_manager/m3u8/m3u8_downloader.dart:97— `download` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/services/download_manager/m_downloader.dart:79— `download` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/services/torrent_server.dart:153— `getInfohash` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking rust_builder/cargokit/build_tool/lib/src/artifacts_provider.dart:99— `_getPrecompiledArtifacts` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking rust_builder/cargokit/build_tool/lib/src/artifacts_provider.dart:184— `_tryDownloadArtifacts` is async and calls writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking rust_builder/cargokit/build_tool/lib/src/build_cmake.dart:19— `build` is async and calls copySync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking rust_builder/cargokit/build_tool/lib/src/build_gradle.dart:22— `build` is async and calls createSync, copySync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking rust_builder/cargokit/build_tool/lib/src/build_pod.dart:20— `build` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking rust_builder/cargokit/build_tool/lib/src/precompile_binaries.dart:52— `run` is async and calls createSync, readAsBytesSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
rust_lib_mangayomi::aidoku_wasm::host_html::link (cognitive 145) rust/src/aidoku_wasm/host_html.rs:19— rust_lib_mangayomi::aidoku_wasm::host_html::link has cognitive complexity 145 (threshold 15). Drivers by points: match/switch 69 (75 pts), if/else 35 (57 pts), loops 8 (11 pts), boolean chains 2 (nesting depth added 31). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
rust_lib_mangayomi::aidoku_wasm::host_js::link (cognitive 61) rust/src/aidoku_wasm/host_js.rs:51— rust_lib_mangayomi::aidoku_wasm::host_js::link has cognitive complexity 61 (threshold 15). Drivers by points: if/else 27 (39 pts), match/switch 21, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rust_lib_mangayomi::api::rhttp::client::create_client (cognitive 59) rust/src/api/rhttp/client.rs:159— rust_lib_mangayomi::api::rhttp::client::create_client has cognitive complexity 59 (threshold 15). Drivers by points: if/else 18 (34 pts), match/switch 6 (16 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rust_lib_mangayomi::aidoku_wasm::host_net::link (cognitive 29) rust/src/aidoku_wasm/host_net.rs:93— rust_lib_mangayomi::aidoku_wasm::host_net::link has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 23 (25 pts), if/else 1 (2 pts), loops 2 (nesting depth added 3). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
rust_lib_mangayomi::api::rhttp::http::make_http_request_helper (cognitive 29) rust/src/api/rhttp/http.rs:210— rust_lib_mangayomi::api::rhttp::http::make_http_request_helper has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 7 (11 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rust_lib_mangayomi::aidoku_wasm::host_std::link (cognitive 26) rust/src/aidoku_wasm/host_std.rs:10— rust_lib_mangayomi::aidoku_wasm::host_std::link has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 4, boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rust_lib_mangayomi::aidoku_wasm::selector::parse_chain (cognitive 21) rust/src/aidoku_wasm/selector.rs:124— rust_lib_mangayomi::aidoku_wasm::selector::parse_chain has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rust_lib_mangayomi::aidoku_wasm::host_html::insert_html (cognitive 17) rust/src/aidoku_wasm/host_html.rs:1102— rust_lib_mangayomi::aidoku_wasm::host_html::insert_html has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (8 pts), loops 3 (7 pts), if/else 2 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
rust_lib_mangayomi::aidoku_wasm::selector::matches_compound (cognitive 16) rust/src/aidoku_wasm/selector.rs:597— rust_lib_mangayomi::aidoku_wasm::selector::matches_compound has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rust_lib_mangayomi::aidoku_wasm::selector::select_chain (cognitive 16) rust/src/aidoku_wasm/selector.rs:664— rust_lib_mangayomi::aidoku_wasm::selector::select_chain has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (6 pts), if/else 2 (5 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium CVE · ×10
Duplicated block (17 lines × 2) lib/eval/aidoku/src/interpreter/js_manager.dart:70— lib/eval/aidoku/src/interpreter/js_manager.dart:70-86 | lib/eval/aidoku/src/interpreter/js_manager.dart:98-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/eval/lnreader/service.dart:454— lib/eval/lnreader/service.dart:454-470 | lib/eval/lnreader/service.dart:490-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/modules/anime/widgets/desktop.dart:516— lib/modules/anime/widgets/desktop.dart:516-532 | REDACTED:516-532 — before extracting anything, compare `lib/modules/anime/widgets/desktop.dart` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) lib/modules/anime/widgets/desktop.dart:604— lib/modules/anime/widgets/desktop.dart:604-620 | REDACTED:689-705 — before extracting anything, compare `lib/modules/anime/widgets/desktop.dart` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) lib/modules/anime/widgets/mobile_seek_indicator.dart:126— lib/modules/anime/widgets/mobile_seek_indicator.dart:126-142 | lib/modules/anime/widgets/mobile_seek_indicator.dart:145-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/modules/library/widgets/library_body.dart:106— lib/modules/library/widgets/library_body.dart:106-122 | lib/modules/library/widgets/library_body.dart:261-277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/modules/manga/reader/providers/reader_controller_provider.dart:84— lib/modules/manga/reader/providers/reader_controller_provider.dart:84-100 | lib/modules/novel/novel_reader_controller_provider.dart:44-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) lib/modules/manga/widgets/manga_image_card_widget.dart:53— lib/modules/manga/widgets/manga_image_card_widget.dart:53-69 | lib/modules/manga/widgets/manga_image_card_widget.dart:126-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/modules/novel/widgets/novel_bottom_bar.dart:285— lib/modules/novel/widgets/novel_bottom_bar.dart:285-302 | lib/modules/novel/widgets/novel_bottom_bar.dart:352-368 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/modules/widgets/cover_view_widget.dart:260— lib/modules/widgets/cover_view_widget.dart:260-276 | packages/shiori/lib/src/components/cover.dart:273-289 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/eval/javascript/dom_selector.dart:151— lib/eval/javascript/dom_selector.dart:151-161 | lib/eval/javascript/dom_selector.dart:170-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/modules/history/history_screen.dart:252— lib/modules/history/history_screen.dart:252-262 | lib/modules/updates/updates_screen.dart:342-352 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/modules/library/tv_home/tv_anime_home_view.dart:321— lib/modules/library/tv_home/tv_anime_home_view.dart:321-332 | lib/modules/library/tv_home/tv_anime_home_view.dart:367-377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/modules/manga/detail/widgets/recommendation_screen.dart:126— lib/modules/manga/detail/widgets/recommendation_screen.dart:126-136 | lib/modules/manga/detail/widgets/related_screen.dart:122-132 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:164— lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:164-174 | lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:298-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/services/trackers/trakt_tv.dart:134— lib/services/trackers/trakt_tv.dart:134-144 | lib/services/trackers/trakt_tv.dart:149-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) rust/src/aidoku_wasm/host_html.rs:426— rust/src/aidoku_wasm/host_html.rs:426-436 | rust/src/aidoku_wasm/host_html.rs:445-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) rust/src/aidoku_wasm/host_html.rs:586— rust/src/aidoku_wasm/host_html.rs:586-596 | rust/src/aidoku_wasm/host_html.rs:600-610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) rust/src/aidoku_wasm/host_html.rs:406— rust/src/aidoku_wasm/host_html.rs:406-416 | rust/src/aidoku_wasm/host_html.rs:787-797 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) rust/src/aidoku_wasm/host_canvas.rs:118— rust/src/aidoku_wasm/host_canvas.rs:118-128 | rust/src/aidoku_wasm/host_canvas.rs:152-162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
TooManyMethods: _AnimeStreamPageState lib/modules/anime/anime_player_view.dart:242— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MangaRepository lib/repositories/manga_repository.dart:21— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: _MangaChapterPageGalleryState REDACTED:190— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MBridge lib/eval/model/m_bridge.dart:74— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: _ExtensionServerScreenState lib/modules/more/settings/browse/extension_server_screen.dart:34— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ChapterRepository lib/repositories/chapter_repository.dart:12— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TrackRepository lib/repositories/track_repository.dart:12— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NovelTtsService lib/modules/novel/tts/novel_tts_service.dart:25— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (12 lines × 2) lib/eval/aidoku/service.dart:422— lib/eval/aidoku/service.dart:422-433 | lib/eval/aidoku/service.dart:613-624 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/eval/aidoku/service.dart:751— lib/eval/aidoku/service.dart:751-762 | lib/eval/aidoku/service.dart:817-828 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/main.dart:550— lib/main.dart:550-561 | lib/main.dart:689-700 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/modules/manga/reader/widgets/reader_settings_modal.dart:190— lib/modules/manga/reader/widgets/reader_settings_modal.dart:190-201 | lib/modules/more/settings/reader/reader_screen.dart:177-188 — before extracting anything, compare `lib/modules/manga/reader/widgets/reader_settings_modal.dart` and `lib/modules/more/settings/reader/reader_screen.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) lib/services/trackers/myanimelist.dart:182— lib/services/trackers/myanimelist.dart:182-193 | lib/services/trackers/myanimelist.dart:222-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/services/trackers/myanimelist.dart:193— lib/services/trackers/myanimelist.dart:193-204 | lib/services/trackers/myanimelist.dart:234-245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/eval/javascript/service.dart:215— lib/eval/javascript/service.dart:215-226 | lib/eval/lnreader/service.dart:370-381 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) rust/src/aidoku_wasm/interpreter.rs:62— rust/src/aidoku_wasm/interpreter.rs:62-73 | rust/src/api/aidoku_wasm.rs:338-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
rust_lib_mangayomi::aidoku_wasm::host_html::link (cyclomatic 119) rust/src/aidoku_wasm/host_html.rs:19— rust_lib_mangayomi::aidoku_wasm::host_html::link has cyclomatic complexity 119 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
rust_lib_mangayomi::aidoku_wasm::host_js::link (cyclomatic 49) rust/src/aidoku_wasm/host_js.rs:51— rust_lib_mangayomi::aidoku_wasm::host_js::link has cyclomatic complexity 49 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
rust_lib_mangayomi::api::rhttp::client::create_client (cyclomatic 30) rust/src/api/rhttp/client.rs:159— rust_lib_mangayomi::api::rhttp::client::create_client has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rust_lib_mangayomi::aidoku_wasm::host_net::link (cyclomatic 27) rust/src/aidoku_wasm/host_net.rs:93— rust_lib_mangayomi::aidoku_wasm::host_net::link has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
rust_lib_mangayomi::api::rhttp::http::make_http_request_helper (cyclomatic 21) rust/src/api/rhttp/http.rs:210— rust_lib_mangayomi::api::rhttp::http::make_http_request_helper has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
rust_lib_mangayomi::aidoku_wasm::host_defaults::link (cyclomatic 19) rust/src/aidoku_wasm/host_defaults.rs:78— rust_lib_mangayomi::aidoku_wasm::host_defaults::link has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
rust_lib_mangayomi::aidoku_wasm::host_std::link (cyclomatic 17) rust/src/aidoku_wasm/host_std.rs:10— rust_lib_mangayomi::aidoku_wasm::host_std::link has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Duplicated block (9 lines × 2) lib/modules/anime/mixins/anime_track_selection_mixin.dart:160— lib/modules/anime/mixins/anime_track_selection_mixin.dart:160-168 | lib/modules/anime/mixins/anime_track_selection_mixin.dart:293-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/modules/more/settings/track/manage_trackers/tracking_detail.dart:100— lib/modules/more/settings/track/manage_trackers/tracking_detail.dart:100-108 | lib/modules/more/settings/track/manage_trackers/tracking_detail.dart:162-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/services/trackers/anilist.dart:161— lib/services/trackers/anilist.dart:161-169 | lib/services/trackers/anilist.dart:257-265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/services/trackers/anilist.dart:141— lib/services/trackers/anilist.dart:141-166 | lib/services/trackers/anilist.dart:337-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/modules/library/providers/tri_state_filter.dart:50— lib/modules/library/providers/tri_state_filter.dart:50-58 | lib/modules/manga/detail/providers/per_manga_tri_state_filter.dart:45-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) go/server.go:868— go/server.go:868-876 | go/server.go:886-894 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/server.go:868` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) rust/src/aidoku_wasm/host_js.rs:198— rust/src/aidoku_wasm/host_js.rs:198-206 | rust/src/aidoku_wasm/host_js.rs:227-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/modules/library/tv_home/tv_anime_home_view.dart:300— lib/modules/library/tv_home/tv_anime_home_view.dart:300-305 | lib/modules/library/tv_home/tv_anime_home_view.dart:441-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/modules/manga/reader/mixins/reader_zoom_control.dart:39— lib/modules/manga/reader/mixins/reader_zoom_control.dart:39-44 | lib/modules/manga/reader/mixins/reader_zoom_control.dart:63-68 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/services/trackers/anilist.dart:482— lib/services/trackers/anilist.dart:482-487 | lib/services/trackers/kitsu.dart:372-377 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) lib/services/trackers/kitsu.dart:163— lib/services/trackers/kitsu.dart:163-168 | lib/services/trackers/kitsu.dart:201-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) rust/src/aidoku_wasm/selector.rs:539— rust/src/aidoku_wasm/selector.rs:539-544 | rust/src/aidoku_wasm/selector.rs:555-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) rust/src/aidoku_wasm/selector.rs:547— rust/src/aidoku_wasm/selector.rs:547-552 | rust/src/aidoku_wasm/selector.rs:563-568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) rust/src/api/rhttp/http.rs:247— rust/src/api/rhttp/http.rs:247-252 | rust/src/api/rhttp/http.rs:256-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Repeated repair: lib/services/http/m_client.dart lib/services/http/m_client.dart:124— lib/services/http/m_client.dart changed 18 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is MClient.getCookiesPref at line 124), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “chore(analysis): strengthen static analysis with bug-preventing linter rules and resolve code diagnostics”; “fix(linux): send browser identity for JS sources”; “fix(player): defer fallback Cloudflare alerts”; “fix(errors): avoid false Cloudflare alerts”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/services/http/m_client.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/services/crash_report.dart lib/services/crash_report.dart:335— lib/services/crash_report.dart changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is CrashReports._init at line 335), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep source failures out of the app tracker”; “fix: make error reports actionable and deduplicated”; “fix: recognise the other two extension runtimes and the http stack”; “fix: a failed download decoding badly is the same failure, not a new one”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/services/crash_report.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/modules/manga/reader/widgets/double_page_view.dart lib/modules/manga/reader/widgets/double_page_view.dart:192— lib/modules/manga/reader/widgets/double_page_view.dart changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is _DoublePageViewState._toggleScale at line 192), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix reader page indexing and widget key stability”; “fix grey screen on double page mode”; “fix(reader): isolate wide page spreads in double-page mode and fix RTL resume order (#1008)”; “fix(reader): optimize webtoon performance, smooth autoscroll and fix retry button hit-testing”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/manga/reader/widgets/double_page_view.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/utils/chapter_recognition.dart lib/utils/chapter_recognition.dart:117— lib/utils/chapter_recognition.dart changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ChapterRecognition._decimalAddition at line 117), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: recognise "T1" seasons and "Episodio" episodes”; “fix: a season is part of which chapter a chapter is”; “Fix unnumbered chapters (Special, Prologue, ...) being treated as duplicates of each other”; “Fix chapter sort incorrectly bucketing by season for non-reset manga”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/utils/chapter_recognition.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/services/download_manager/download_isolate_pool.dart lib/services/download_manager/download_isolate_pool.dart:143— lib/services/download_manager/download_isolate_pool.dart changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is DownloadIsolatePool._listenToTask at line 143), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(download): harden workers and HLS recovery”; “fix(downloads): time out the connection phase so a dropped network fails instead of hanging”; “fix(downloads): stop the UI freezing and make concurrency limits actually apply”; “fix(downloads): fail stalled downloads instead of hanging forever”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/services/download_manager/download_isolate_pool.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/modules/more/about/error_reports_screen.dart lib/modules/more/about/error_reports_screen.dart:79— lib/modules/more/about/error_reports_screen.dart changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is _ReportTile.build at line 79), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep source failures out of the app tracker”; “fix: make error reports actionable and deduplicated”; “fix: keep extension bugs and repeat reports out of the tracker”; “fix: stop filing network hiccups as crashes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 14:43:37 +01:00' --until='2026-10-23 14:43:37 +01:00' --full-history --no-merges -- lib/modules/more/about/error_reports_screen.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FunctionTooLong: rust_lib_mangayomi::aidoku_wasm::host_html::link rust/src/aidoku_wasm/host_html.rs:19— FunctionTooLong — rust_lib_mangayomi::aidoku_wasm::host_html::link runs 764 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 664 over it, 7.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rust_lib_mangayomi::aidoku_wasm::host_js::link rust/src/aidoku_wasm/host_js.rs:51— FunctionTooLong — rust_lib_mangayomi::aidoku_wasm::host_js::link runs 353 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 253 over it, 3.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rust_lib_mangayomi::aidoku_wasm::host_net::link rust/src/aidoku_wasm/host_net.rs:93— FunctionTooLong — rust_lib_mangayomi::aidoku_wasm::host_net::link runs 195 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rust_lib_mangayomi::aidoku_wasm::host_canvas::link rust/src/aidoku_wasm/host_canvas.rs:12— FunctionTooLong — rust_lib_mangayomi::aidoku_wasm::host_canvas::link runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rust_lib_mangayomi::api::rhttp::client::create_client rust/src/api/rhttp/client.rs:159— FunctionTooLong — rust_lib_mangayomi::api::rhttp::client::create_client runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rust_lib_mangayomi::aidoku_wasm::host_std::link rust/src/aidoku_wasm/host_std.rs:10— FunctionTooLong — rust_lib_mangayomi::aidoku_wasm::host_std::link runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change coupling: library_gridview_widget.dart ↔ library_listview_widget.dart lib/modules/library/widgets/library_gridview_widget.dart:1— `lib/modules/library/widgets/library_gridview_widget.dart` and `lib/modules/library/widgets/library_listview_widget.dart` change together 91% of the time (39 of the 43 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 39 shared commits counted here, the most recent 3 are `ea358340` fix: avoid sync Isar read in unread count; `d0e318d9` chore: remove download-queue reordering (moved to the downloads PR); `b1499e4b` fix: don't crash on library entries with a null source/lang (#708) — run `git show` on any of them.
Change coupling: anime_player_view.dart ↔ unified_settings_sheet.dart lib/modules/anime/anime_player_view.dart:1— `lib/modules/anime/anime_player_view.dart` and `lib/modules/anime/widgets/unified_settings_sheet.dart` change together 79% of the time (11 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `3bd489a0` fix(player): settings sections switch faster, and the skip pill lines…; `eccb49ff` feat(player): simplify portrait controls; `ac2fa4fc` fix(player): align compact portrait controls — run `git show` on any of them.
Change coupling: anilist.dart ↔ myanimelist.dart lib/services/trackers/anilist.dart:1— `lib/services/trackers/anilist.dart` and `lib/services/trackers/myanimelist.dart` change together 61% of the time (11 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `31ead933` Use read instead of watch; `304f6530` adjusted fetch tracking data; `0801b2b8` fixed some tracker provider bugs — run `git show` on any of them.
Change coupling: extension_screen.dart ↔ sources_screen.dart lib/modules/browse/extension/extension_screen.dart:1— `lib/modules/browse/extension/extension_screen.dart` and `lib/modules/browse/sources/sources_screen.dart` change together 59% of the time (22 of the 37 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `6002f3e4` refactor(architecture): make lib/modules/widgets feature-agnostic; `11f5b094` fix(tv): make browse layout overscan safe; `e047f63c` Integrate floating navigation bar on latest main — run `git show` on any of them.
Change coupling: extension_screen.dart ↔ extension_preferences_providers.dart lib/modules/browse/extension/extension_screen.dart:1— `lib/modules/browse/extension/extension_screen.dart` and `lib/modules/browse/extension/providers/extension_preferences_providers.dart` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `fddf98d3` Fix browser source & extension tab lag & some fix; `12ccedf1` Revert "improve browser source & extension tab lag & some fix"; `fb8754df` improve browser source & extension tab lag & some fix — run `git show` on any of them.
Change coupling: anilist.dart ↔ kitsu.dart lib/services/trackers/anilist.dart:1— `lib/services/trackers/anilist.dart` and `lib/services/trackers/kitsu.dart` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `31ead933` Use read instead of watch; `92c167d5` merged trackers together and added search; `06ca4416` added Kitsu and Anilist — run `git show` on any of them.
Duplicated block (7 lines × 2) lib/eval/mihon/service.dart:171— lib/eval/mihon/service.dart:171-177 | lib/eval/mihon/service.dart:210-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:216— lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:216-222 | lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:224-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) REDACTED:267— REDACTED:267-273 | REDACTED:297-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/utils/cryptoaes/crypto_aes.dart:12— lib/utils/cryptoaes/crypto_aes.dart:12-18 | lib/utils/cryptoaes/crypto_aes.dart:38-44 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/modules/anime/providers/anime_player_controller_provider.dart:20— lib/modules/anime/providers/anime_player_controller_provider.dart:20-26 | lib/modules/manga/reader/providers/reader_controller_provider.dart:47-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) rust/src/aidoku_wasm/host_net.rs:100— rust/src/aidoku_wasm/host_net.rs:100-106 | rust/src/aidoku_wasm/host_net.rs:297-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×5
Duplicated block (16 lines × 2) lib/modules/anime/providers/state_provider.dart:96— lib/modules/anime/providers/state_provider.dart:96-111 | lib/modules/anime/providers/state_provider.dart:119-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) REDACTED:649— REDACTED:649-664 | REDACTED:788-803 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/services/trackers/myanimelist.dart:58— lib/services/trackers/myanimelist.dart:58-73 | lib/services/trackers/trakt_tv.dart:58-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) lib/modules/anime/widgets/custom_seekbar.dart:376— lib/modules/anime/widgets/custom_seekbar.dart:376-390 | lib/modules/manga/reader/widgets/custom_value_indicator_shape.dart:12-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) lib/modules/more/data_and_storage/widgets/backup_encryption_password_dialog.dart:122— lib/modules/more/data_and_storage/widgets/backup_encryption_password_dialog.dart:122-136 | lib/modules/more/data_and_storage/widgets/backup_encryption_password_dialog.dart:215-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/services/trackers/simkl.dart:62— lib/services/trackers/simkl.dart:62-76 | lib/services/trackers/trakt_tv.dart:49-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) lib/eval/model/m_bridge.dart:627— lib/eval/model/m_bridge.dart:627-640 | lib/eval/model/m_bridge.dart:647-660 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/services/trackers/myanimelist.dart:104— lib/services/trackers/myanimelist.dart:104-117 | lib/services/trackers/simkl.dart:373-386 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) rust/src/aidoku_wasm/host_js.rs:256— rust/src/aidoku_wasm/host_js.rs:256-269 | rust/src/aidoku_wasm/host_js.rs:453-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/services/extension_store_service.dart:613— lib/services/extension_store_service.dart:613-617 | lib/services/extension_store_service.dart:646-654 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/repositories/chapter_repository.dart:19— lib/repositories/chapter_repository.dart:19-23 | lib/repositories/update_repository.dart:27-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) rust/src/aidoku_wasm/interpreter.rs:239— rust/src/aidoku_wasm/interpreter.rs:239-243 | rust/src/aidoku_wasm/interpreter.rs:339-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Weak hash algorithm lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_image_resolver.dart:13— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm lib/utils/cryptoaes/crypto_aes.dart:73— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm lib/utils/extensions/others.dart:214— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×3
Owned disposable field is never released lib/modules/novel/tts/novel_tts_service.dart:33— `NovelTtsService` carries a disposal duty — it declares its own release — and it creates `_stateController` itself (line 33, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_stateController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_stateController.close();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/modules/novel/tts/novel_tts_service.dart:34— `NovelTtsService` carries a disposal duty — it declares its own release — and it creates `_paragraphIndexController` itself (line 34, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_paragraphIndexController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_paragraphIndexController.close();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/modules/novel/tts/novel_tts_service.dart:35— `NovelTtsService` carries a disposal duty — it declares its own release — and it creates `_wordProgressController` itself (line 35, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_wordProgressController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_wordProgressController.close();` in `dispose()` before `super.dispose()`.
Change-coupling hub: manga_detail_view.dart → readmore.dart, tracker_search_widget.dart, tracker_widget.dart lib/modules/manga/detail/manga_detail_view.dart— `lib/modules/manga/detail/manga_detail_view.dart` changes together with 3 other files — `lib/modules/manga/detail/widgets/readmore.dart`, `lib/modules/manga/detail/widgets/tracker_search_widget.dart`, `lib/modules/manga/detail/widgets/tracker_widget.dart` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: REDACTED → readmore.dart, image_view_vertical.dart, image_view_webtoon.dart REDACTED— `REDACTED` changes together with 3 other files — `lib/modules/manga/detail/widgets/readmore.dart`, `lib/modules/manga/reader/image_view_vertical.dart`, `lib/modules/manga/reader/image_view_webtoon.dart` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Duplicated block (26 lines × 2) lib/eval/aidoku/src/interpreter/js_manager.dart:311— lib/eval/aidoku/src/interpreter/js_manager.dart:311-336 | lib/eval/aidoku/src/interpreter/js_manager.dart:358-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) lib/modules/browse/global_search/global_search_screen.dart:123— lib/modules/browse/global_search/global_search_screen.dart:123-148 | lib/modules/manga/detail/widgets/migrate_screen.dart:74-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (23 lines × 2) lib/modules/anime/widgets/tv_player_settings_panel.dart:369— lib/modules/anime/widgets/tv_player_settings_panel.dart:369-391 | lib/modules/anime/widgets/tv_player_settings_panel.dart:428-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:78— lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:78-100 | lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:209-231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19–20 lines × 2) lib/modules/anime/widgets/search_subtitles.dart:126— lib/modules/anime/widgets/search_subtitles.dart:126-144 | lib/modules/manga/detail/widgets/tracker_search_widget.dart:98-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19–20 lines × 2) lib/services/extension_store_service.dart:568— lib/services/extension_store_service.dart:568-586 | lib/services/extension_store_service.dart:656-675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/modules/more/download_queue/download_queue_screen.dart:35— lib/modules/more/download_queue/download_queue_screen.dart:35-54 | lib/modules/more/download_queue/download_queue_screen.dart:70-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/services/trackers/simkl.dart:205— lib/services/trackers/simkl.dart:205-224 | lib/services/trackers/simkl.dart:236-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/modules/anime/widgets/desktop.dart:639— lib/modules/anime/widgets/desktop.dart:639-657 | REDACTED:767-785 — before extracting anything, compare `lib/modules/anime/widgets/desktop.dart` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) lib/modules/manga/reader/widgets/reader_settings_modal.dart:393— lib/modules/manga/reader/widgets/reader_settings_modal.dart:393-411 | lib/modules/more/settings/reader/reader_screen.dart:253-271 — before extracting anything, compare `lib/modules/manga/reader/widgets/reader_settings_modal.dart` and `lib/modules/more/settings/reader/reader_screen.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) lib/services/extension_store_service.dart:285— lib/services/extension_store_service.dart:285-298 | lib/services/extension_store_service.dart:569-582 | lib/services/extension_store_service.dart:657-670 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) rust/src/aidoku_wasm/host_html.rs:651— rust/src/aidoku_wasm/host_html.rs:651-664 | rust/src/aidoku_wasm/host_html.rs:710-723 | rust/src/aidoku_wasm/host_html.rs:739-752 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–11 lines × 2) lib/eval/mihon/service.dart:234— lib/eval/mihon/service.dart:234-244 | lib/eval/mihon/service.dart:255-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–11 lines × 2) lib/modules/library/library_screen.dart:331— lib/modules/library/library_screen.dart:331-341 | lib/modules/library/library_screen.dart:426-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) lib/modules/browse/extension/extension_screen.dart:236— lib/modules/browse/extension/extension_screen.dart:236-244 | lib/modules/browse/extension/extension_screen.dart:258-266 | lib/modules/browse/extension/extension_screen.dart:281-289 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) rust/src/aidoku_wasm/host_html.rs:130— rust/src/aidoku_wasm/host_html.rs:130-138 | rust/src/aidoku_wasm/host_html.rs:149-157 | rust/src/aidoku_wasm/host_html.rs:888-896 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–9 lines × 2) lib/eval/aidoku/service.dart:1046— lib/eval/aidoku/service.dart:1046-1053 | lib/eval/aidoku/service.dart:1079-1087 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) lib/modules/browse/sources/sources_screen.dart:165— lib/modules/browse/sources/sources_screen.dart:165-172 | lib/modules/browse/sources/sources_screen.dart:178-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 3) lib/services/anime_extractors/sendvid_extractor.dart:27— lib/services/anime_extractors/sendvid_extractor.dart:27-33 | lib/services/anime_extractors/sendvid_extractor.dart:53-59 | lib/services/anime_extractors/streamwish_extractor.dart:41-47 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) lib/services/trackers/anilist.dart:609— lib/services/trackers/anilist.dart:609-615 | lib/services/trackers/kitsu.dart:446-452 | lib/services/trackers/simkl.dart:457-463 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) lib/services/trackers/simkl.dart:119— lib/services/trackers/simkl.dart:119-123 | lib/services/trackers/simkl.dart:221-225 | lib/services/trackers/simkl.dart:252-256 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) lib/modules/browse/extension/extension_detail.dart:50— lib/modules/browse/extension/extension_detail.dart:50-54 | lib/modules/more/about/providers/download_file_screen.dart:422-426 | REDACTED:44-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Outbound HTTP without resilience repo/update_source.py:101— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience repo/update_source.py:123— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
NovelPaginator.paginate (cyclomatic 74) lib/modules/novel/utils/novel_paginator.dart:107— NovelPaginator.paginate has cyclomatic complexity 74 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MangaHomeScreenState.build (cyclomatic 64) lib/modules/manga/home/manga_home_screen.dart:270— _MangaHomeScreenState.build has cyclomatic complexity 64 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MangaChapterPageGalleryState.build (cyclomatic 64) REDACTED:568— _MangaChapterPageGalleryState.build has cyclomatic complexity 64 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TachiyomiRestoreService.restore (cyclomatic 55) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:30— TachiyomiRestoreService.restore has cyclomatic complexity 55 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MangaDetailViewState._buildWidget (cyclomatic 48) lib/modules/manga/detail/manga_detail_view.dart:190— _MangaDetailViewState._buildWidget has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsCheerio.init (cyclomatic 46) lib/eval/lnreader/js_cheerio.dart:15— JsCheerio.init has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ExtensionStoreService._parseLegacyJsonStore (cyclomatic 46) lib/services/extension_store_service.dart:328— ExtensionStoreService._parseLegacyJsonStore has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnimeMpvBridgeMixin._handleMpvNodeEvents (cyclomatic 44) lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:92— AnimeMpvBridgeMixin._handleMpvNodeEvents has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AidokuExtensionService.getSourcePreferences (cyclomatic 42) lib/eval/aidoku/service.dart:607— AidokuExtensionService.getSourcePreferences has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AidokuExtensionService.getFilterList (cyclomatic 41) lib/eval/aidoku/service.dart:418— AidokuExtensionService.getFilterList has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MangayomiRestoreService._mergeMangayomiBackup (cyclomatic 41) lib/modules/more/data_and_storage/providers/mangayomi_restore_service.dart:234— MangayomiRestoreService._mergeMangayomiBackup has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MobileControllerWidgetState.build (cyclomatic 38) REDACTED:457— _MobileControllerWidgetState.build has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Settings.fromJson (cyclomatic 37) lib/models/settings.dart:722— Settings.fromJson has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MBridge.parseChapterDate (cyclomatic 36) lib/eval/model/m_bridge.dart:519— MBridge.parseChapterDate has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SubtitleSettingsState.build (cyclomatic 36) lib/modules/anime/providers/state_provider.dart:9— SubtitleSettingsState.build has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SubsamplingScaleImageViewState.build (cyclomatic 35) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:1245— _SubsamplingScaleImageViewState.build has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MangayomiRestoreService.restore (cyclomatic 35) lib/modules/more/data_and_storage/providers/mangayomi_restore_service.dart:34— MangayomiRestoreService.restore has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MainScreenState.build (cyclomatic 34) lib/modules/main_view/main_screen.dart:127— _MainScreenState.build has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SourceRepositoriesState._showAddRepoDialog (cyclomatic 32) REDACTED:234— _SourceRepositoriesState._showAddRepoDialog has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AidokuExtensionService._mapMangayomiFiltersToAidoku (cyclomatic 31) lib/eval/aidoku/service.dart:952— AidokuExtensionService._mapMangayomiFiltersToAidoku has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsDomSelector.init (cyclomatic 29) lib/eval/javascript/dom_selector.dart:13— JsDomSelector.init has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
_AnimeStreamPageState._videoPlayer (cyclomatic 29) lib/modules/anime/anime_player_view.dart:954— _AnimeStreamPageState._videoPlayer has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TvAnimeHomeViewState.build (cyclomatic 29) lib/modules/library/tv_home/tv_anime_home_view.dart:129— _TvAnimeHomeViewState.build has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReaderController.setPageIndex (cyclomatic 29) lib/modules/manga/reader/providers/reader_controller_provider.dart:134— ReaderController.setPageIndex has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_NovelWebViewState.build (cyclomatic 29) lib/modules/novel/novel_reader_view.dart:301— _NovelWebViewState.build has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WesternWatchOrderPlanner._buildListItems (cyclomatic 29) lib/services/discovery/western_watch_order.dart:245— WesternWatchOrderPlanner._buildListItems has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExpandableTextState.build (cyclomatic 28) lib/modules/manga/detail/widgets/expandable_text.dart:146— ExpandableTextState.build has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MyAppState._initDeepLinks (cyclomatic 26) lib/main.dart:493— _MyAppState._initDeepLinks has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AidokuJsManager.handleJsRequest (cyclomatic 26) lib/eval/aidoku/src/interpreter/js_manager.dart:39— AidokuJsManager.handleJsRequest has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SubsamplingScaleImageViewState._initImage (cyclomatic 26) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:775— _SubsamplingScaleImageViewState._initImage has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DetailAppBar.build (cyclomatic 25) lib/modules/manga/detail/widgets/detail_app_bar.dart:48— DetailAppBar.build has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NovelBottomBar.build (cyclomatic 25) lib/modules/novel/widgets/novel_bottom_bar.dart:173— NovelBottomBar.build has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AidokuExtensionService._ensureInitialized (cyclomatic 24) lib/eval/aidoku/service.dart:99— AidokuExtensionService._ensureInitialized has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Source._loadDefaults (cyclomatic 24) lib/eval/aidoku/src/source.dart:428— Source._loadDefaults has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_CreateExtensionState.build (cyclomatic 24) lib/modules/browse/extension/widgets/create_extension.dart:43— _CreateExtensionState.build has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ChapterListTileState.build (cyclomatic 24) lib/modules/reader_common/widgets/btn_chapter_list_dialog.dart:221— _ChapterListTileState.build has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PlayerShortcutPills.build (cyclomatic 23) lib/modules/anime/widgets/player_shortcut_pills.dart:64— PlayerShortcutPills.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_UpdateTabState.build (cyclomatic 23) lib/modules/updates/updates_screen.dart:192— _UpdateTabState.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MangaWebViewState.build (cyclomatic 23) lib/modules/webview/webview.dart:221— _MangaWebViewState.build has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_FloatingNavBarState._bar (cyclomatic 23) lib/modules/widgets/floating_nav_bar.dart:575— _FloatingNavBarState._bar has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TvPillState.build (cyclomatic 23) lib/modules/widgets/tv_pill.dart:58— _TvPillState.build has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HlsProxyService._handleRequest (cyclomatic 23) lib/services/http/hls_proxy.dart:166— HlsProxyService._handleRequest has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SyncServer.startSync (cyclomatic 23) lib/services/sync_server.dart:152— SyncServer.startSync has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LNReaderExtensionService._mapPluginSettingToSourcePreference (cyclomatic 22) lib/eval/lnreader/service.dart:426— LNReaderExtensionService._mapPluginSettingToSourcePreference has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnimePlayerSettingsMixin.buildPlayerSettingsEntries (cyclomatic 22) lib/modules/anime/mixins/anime_player_settings_mixin.dart:92— AnimePlayerSettingsMixin.buildPlayerSettingsEntries has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_DesktopControllerWidgetState.build (cyclomatic 22) lib/modules/anime/widgets/desktop.dart:326— _DesktopControllerWidgetState.build has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LibraryAppBar.build (cyclomatic 22) lib/modules/library/widgets/library_app_bar.dart:114— LibraryAppBar.build has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NavDestinationBuilders.buildNavigationWidgetsDesktop (cyclomatic 22) lib/modules/main_view/widgets/nav_destination_builders.dart:48— NavDestinationBuilders.buildNavigationWidgetsDesktop has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChapterListTileWidget.build (cyclomatic 22) lib/modules/manga/detail/widgets/chapter_list_tile_widget.dart:40— ChapterListTileWidget.build has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ImageViewWebtoonState._handleScaleUpdate (cyclomatic 22) lib/modules/manga/reader/image_view_webtoon.dart:293— _ImageViewWebtoonState._handleScaleUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NovelPaginationAndTtsMixin.buildPaginatedSpreadView (cyclomatic 22) lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:189— NovelPaginationAndTtsMixin.buildPaginatedSpreadView has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MangaRepository.mergeGroup (cyclomatic 22) lib/repositories/manga_repository.dart:491— MangaRepository.mergeGroup has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppDelegate.didInitializeImplicitFlutterEngine (cyclomatic 22) ios/Runner/AppDelegate.swift:37— AppDelegate.didInitializeImplicitFlutterEngine has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MangaGlobalImageCardState.build (cyclomatic 21) lib/modules/browse/global_search/global_search_screen.dart:530— _MangaGlobalImageCardState.build has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MinSubsamplingImageState.build (cyclomatic 21) lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:349— _MinSubsamplingImageState.build has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NovelPaginationAndTtsMixin.syncPaginationModeTransition (cyclomatic 21) lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:129— NovelPaginationAndTtsMixin.syncPaginationModeTransition has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_CoverViewWidgetState.build (cyclomatic 21) lib/modules/widgets/cover_view_widget.dart:107— _CoverViewWidgetState.build has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MTorrentServer.getTorrentPlaylist (cyclomatic 21) lib/services/torrent_server.dart:182— MTorrentServer.getTorrentPlaylist has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MangaInfoHeaderState.build (cyclomatic 20) lib/modules/manga/detail/widgets/manga_info_header.dart:74— _MangaInfoHeaderState.build has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TrackerWidgetState.build (cyclomatic 20) lib/modules/manga/detail/widgets/tracker_widget.dart:61— _TrackerWidgetState.build has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ImageViewPagedState.build (cyclomatic 20) lib/modules/manga/reader/image_view_paged.dart:246— _ImageViewPagedState.build has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ReaderPrefetchMixin.checkAndReloadEvictedPages (cyclomatic 20) lib/modules/manga/reader/mixins/reader_prefetch_mixin.dart:107— ReaderPrefetchMixin.checkAndReloadEvictedPages has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReaderPageIndexMath.currentIndexLabel (cyclomatic 20) lib/modules/manga/reader/utils/reader_page_index_math.dart:244— ReaderPageIndexMath.currentIndexLabel has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RhttpCompatibleClient.send (cyclomatic 20) lib/services/http/rhttp/src/client/compatible_client.dart:35— RhttpCompatibleClient.send has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
_ImageViewPagedState._performLandscapeZoom (cyclomatic 19) lib/modules/manga/reader/image_view_paged.dart:168— _ImageViewPagedState._performLandscapeZoom has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ReaderInputAndModeMixin.handlePageNavigation (cyclomatic 19) lib/modules/manga/reader/mixins/reader_input_and_mode_mixin.dart:67— ReaderInputAndModeMixin.handlePageNavigation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SubsamplingScaleImageViewState.didUpdateWidget (cyclomatic 19) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:453— _SubsamplingScaleImageViewState.didUpdateWidget has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CustomExtendedNetworkImageProvider._loadAsync (cyclomatic 19) lib/services/http/custom_extended_image_provider.dart:312— CustomExtendedNetworkImageProvider._loadAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LNReaderExtensionService.getDetail (cyclomatic 18) lib/eval/lnreader/service.dart:276— LNReaderExtensionService.getDetail has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SeekIndicatorState.build (cyclomatic 18) lib/modules/anime/widgets/mobile_seek_indicator.dart:88— _SeekIndicatorState.build has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TabletLayoutState.build (cyclomatic 18) lib/modules/main_view/widgets/tablet_layout.dart:121— _TabletLayoutState.build has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MangaChapterPageGalleryState._setReaderMode (cyclomatic 18) REDACTED:1286— _MangaChapterPageGalleryState._setReaderMode has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MinSubsamplingImageState._loadImage (cyclomatic 18) lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:117— _MinSubsamplingImageState._loadImage has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SubsamplingScaleImageViewState._handleScaleUpdate (cyclomatic 18) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:1078— _SubsamplingScaleImageViewState._handleScaleUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReaderPageContent.build (cyclomatic 18) lib/modules/manga/reader/widgets/reader_page_content.dart:104— ReaderPageContent.build has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ExtensionServerScreenState.build (cyclomatic 18) lib/modules/more/settings/browse/extension_server_screen.dart:83— _ExtensionServerScreenState.build has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_GlobalSearchResultCardState.build (cyclomatic 18) lib/modules/widgets/global_search_result_card.dart:48— _GlobalSearchResultCardState.build has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LNReaderExtensionService.getSourcePreferences (cyclomatic 17) lib/eval/lnreader/service.dart:383— LNReaderExtensionService.getSourcePreferences has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_BrowseScreenState.build (cyclomatic 17) lib/modules/browse/browse_screen.dart:337— _BrowseScreenState.build has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LibraryBody.build (cyclomatic 17) lib/modules/library/widgets/library_body.dart:73— LibraryBody.build has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NavDestinationBuilders.buildNavigationWidgetsMobile (cyclomatic 17) lib/modules/main_view/widgets/nav_destination_builders.dart:249— NavDestinationBuilders.buildNavigationWidgetsMobile has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MinSubsamplingImageState._loadFromPath (cyclomatic 17) lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:226— _MinSubsamplingImageState._loadFromPath has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SubsamplingScaleImageViewState._loadFromProvider (cyclomatic 17) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:522— _SubsamplingScaleImageViewState._loadFromProvider has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MExtensionServerPlatform._startServer (cyclomatic 17) lib/services/m_extension_server.dart:45— MExtensionServerPlatform._startServer has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AidokuExtensionService.getHeaders (cyclomatic 16) lib/eval/aidoku/service.dart:212— AidokuExtensionService.getHeaders has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LNReaderExtensionService._getStoredPreference (cyclomatic 16) lib/eval/lnreader/service.dart:540— LNReaderExtensionService._getStoredPreference has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TvPlayerControlsState.build (cyclomatic 16) lib/modules/anime/widgets/tv_player_controls.dart:155— _TvPlayerControlsState.build has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_CodeEditorPageState._execute (cyclomatic 16) lib/modules/browse/extension/edit_code.dart:200— _CodeEditorPageState._execute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ExtensionScreenState.build (cyclomatic 16) lib/modules/browse/extension/extension_screen.dart:60— _ExtensionScreenState.build has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ImageViewWebtoonState._estimateExtent (cyclomatic 16) lib/modules/manga/reader/image_view_webtoon.dart:533— _ImageViewWebtoonState._estimateExtent has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MangaChapterPageGalleryState._readProgressListener (cyclomatic 16) REDACTED:1083— _MangaChapterPageGalleryState._readProgressListener has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_DownloadFileScreenState._downloadApk (cyclomatic 16) lib/modules/more/about/providers/download_file_screen.dart:315— _DownloadFileScreenState._downloadApk has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExtensionStoreService.fetchStore (cyclomatic 16) lib/services/extension_store_service.dart:42— ExtensionStoreService.fetchStore has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: ExtensionStoreService.convertLnreaderLang (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
ExtensionStoreService._parseProtobufStore (cyclomatic 16) lib/services/extension_store_service.dart:129— ExtensionStoreService._parseProtobufStore has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: ExtensionStoreService.convertLnreaderLang (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
NovelPaginator.paginate (cognitive 145) lib/modules/novel/utils/novel_paginator.dart:107— NovelPaginator.paginate has cognitive complexity 145 (threshold 15). Drivers by points: if/else 52 (103 pts), loops 10 (20 pts), boolean chains 16, ternaries 5 (6 pts) (nesting depth added 62). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MangayomiRestoreService.restore (cognitive 131) lib/modules/more/data_and_storage/providers/mangayomi_restore_service.dart:34— MangayomiRestoreService.restore has cognitive complexity 131 (threshold 15). Drivers by points: if/else 21 (73 pts), loops 11 (53 pts), ternaries 1 (4 pts), error handling 1 (nesting depth added 97). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TachiyomiRestoreService.restore (cognitive 117) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:30— TachiyomiRestoreService.restore has cognitive complexity 117 (threshold 15). Drivers by points: if/else 23 (57 pts), ternaries 13 (31 pts), loops 10 (19 pts), boolean chains 10 (nesting depth added 61). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MangayomiRestoreService._mergeMangayomiBackup (cognitive 99) lib/modules/more/data_and_storage/providers/mangayomi_restore_service.dart:234— MangayomiRestoreService._mergeMangayomiBackup has cognitive complexity 99 (threshold 15). Drivers by points: if/else 25 (65 pts), ternaries 6 (18 pts), loops 6 (12 pts), boolean chains 4 (nesting depth added 58). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService.getFilterList (cognitive 93) lib/eval/aidoku/service.dart:418— AidokuExtensionService.getFilterList has cognitive complexity 93 (threshold 15). Drivers by points: if/else 23 (51 pts), ternaries 5 (17 pts), loops 4 (11 pts), boolean chains 9, error handling 2 (5 pts) (nesting depth added 50). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AidokuExtensionService.getSourcePreferences (cognitive 91) lib/eval/aidoku/service.dart:607— AidokuExtensionService.getSourcePreferences has cognitive complexity 91 (threshold 15). Drivers by points: if/else 28 (60 pts), ternaries 7 (15 pts), loops 4 (9 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 47). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ExtensionStoreService._parseLegacyJsonStore (cognitive 85) lib/services/extension_store_service.dart:328— ExtensionStoreService._parseLegacyJsonStore has cognitive complexity 85 (threshold 15). Drivers by points: boolean chains 26, if/else 9 (24 pts), ternaries 6 (21 pts), loops 3 (10 pts), error handling 2 (4 pts) (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MangaChapterPageGalleryState.build (cognitive 83) REDACTED:568— _MangaChapterPageGalleryState.build has cognitive complexity 83 (threshold 15). Drivers by points: if/else 37 (48 pts), ternaries 12 (19 pts), boolean chains 13, loops 1 (2 pts), match/switch 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MangaHomeScreenState.build (cognitive 82) lib/modules/manga/home/manga_home_screen.dart:270— _MangaHomeScreenState.build has cognitive complexity 82 (threshold 15). Drivers by points: if/else 35 (49 pts), boolean chains 15, ternaries 15, loops 1 (2 pts), match/switch 1 (nesting depth added 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_MangaDetailViewState._buildWidget (cognitive 81) lib/modules/manga/detail/manga_detail_view.dart:190— _MangaDetailViewState._buildWidget has cognitive complexity 81 (threshold 15). Drivers by points: if/else 18 (35 pts), ternaries 16 (30 pts), boolean chains 10, loops 4 (6 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService._mapMangayomiFiltersToAidoku (cognitive 77) lib/eval/aidoku/service.dart:952— AidokuExtensionService._mapMangayomiFiltersToAidoku has cognitive complexity 77 (threshold 15). Drivers by points: if/else 24 (63 pts), ternaries 2 (7 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 46). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MBridge.parseChapterDate (cognitive 75) lib/eval/model/m_bridge.dart:519— MBridge.parseChapterDate has cognitive complexity 75 (threshold 15). Drivers by points: if/else 24 (43 pts), error handling 4 (17 pts), loops 5 (12 pts), boolean chains 2, ternaries 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MobileControllerWidgetState.build (cognitive 55) REDACTED:457— _MobileControllerWidgetState.build has cognitive complexity 55 (threshold 15). Drivers by points: if/else 21 (27 pts), ternaries 14 (23 pts), boolean chains 5 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderController.setPageIndex (cognitive 55) lib/modules/manga/reader/providers/reader_controller_provider.dart:134— ReaderController.setPageIndex has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (37 pts), boolean chains 9, loops 2 (6 pts), ternaries 2 (3 pts) (nesting depth added 26). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_TvAnimeHomeViewState.build (cognitive 54) lib/modules/library/tv_home/tv_anime_home_view.dart:129— _TvAnimeHomeViewState.build has cognitive complexity 54 (threshold 15). Drivers by points: if/else 15 (28 pts), ternaries 9 (13 pts), loops 3 (10 pts), boolean chains 3 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NovelPaginationAndTtsMixin.syncPaginationModeTransition (cognitive 54) lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:129— NovelPaginationAndTtsMixin.syncPaginationModeTransition has cognitive complexity 54 (threshold 15). Drivers by points: if/else 11 (25 pts), ternaries 7 (25 pts), boolean chains 4 (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MangaRepository.mergeGroup (cognitive 49) lib/repositories/manga_repository.dart:491— MangaRepository.mergeGroup has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 6 (10 pts), ternaries 3 (9 pts), boolean chains 4 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MTorrentServer.getTorrentPlaylist (cognitive 49) lib/services/torrent_server.dart:182— MTorrentServer.getTorrentPlaylist has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (38 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (2 pts), error handling 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MyAppState._initDeepLinks (cognitive 48) lib/main.dart:493— _MyAppState._initDeepLinks has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 6 (14 pts), boolean chains 5, error handling 1 (3 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SubtitleSettingsState.build (cognitive 48) lib/modules/anime/providers/state_provider.dart:9— SubtitleSettingsState.build has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 13 (26 pts), boolean chains 21, if/else 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MExtensionServerPlatform._startServer (cognitive 48) lib/services/m_extension_server.dart:45— MExtensionServerPlatform._startServer has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (34 pts), error handling 2 (6 pts), boolean chains 3, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnimeMpvBridgeMixin._handleMpvNodeEvents (cognitive 46) lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:92— AnimeMpvBridgeMixin._handleMpvNodeEvents has cognitive complexity 46 (threshold 15). Drivers by points: if/else 18 (36 pts), match/switch 4 (7 pts), ternaries 1 (3 pts) (nesting depth added 23). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WesternWatchOrderPlanner._buildListItems (cognitive 46) lib/services/discovery/western_watch_order.dart:245— WesternWatchOrderPlanner._buildListItems has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (33 pts), boolean chains 4, loops 4, ternaries 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsCheerio.init (cognitive 45) lib/eval/lnreader/js_cheerio.dart:15— JsCheerio.init has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 9 (18 pts), match/switch 1, ternaries 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MainScreenState.build (cognitive 45) lib/modules/main_view/main_screen.dart:127— _MainScreenState.build has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 11, ternaries 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_AnimeStreamPageState._videoPlayer (cognitive 44) lib/modules/anime/anime_player_view.dart:954— _AnimeStreamPageState._videoPlayer has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 11 (21 pts), if/else 11 (16 pts), boolean chains 7 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SubsamplingScaleImageViewState.build (cognitive 44) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:1245— _SubsamplingScaleImageViewState.build has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 11 (13 pts), boolean chains 11, match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderInputAndModeMixin.handlePageNavigation (cognitive 43) lib/modules/manga/reader/mixins/reader_input_and_mode_mixin.dart:67— ReaderInputAndModeMixin.handlePageNavigation has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (34 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_DownloadFileScreenState._handleDownloadOrOpen (cognitive 43) lib/modules/more/about/providers/download_file_screen.dart:249— _DownloadFileScreenState._handleDownloadOrOpen has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 2 (7 pts), ternaries 2 (6 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExpandableTextState.build (cognitive 40) lib/modules/manga/detail/widgets/expandable_text.dart:146— ExpandableTextState.build has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 11 (20 pts), if/else 11 (14 pts), boolean chains 6 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NovelWebViewState.build (cognitive 40) lib/modules/novel/novel_reader_view.dart:301— _NovelWebViewState.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 8, ternaries 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionStoreService.fetchStore (cognitive 40) lib/services/extension_store_service.dart:42— ExtensionStoreService.fetchStore has cognitive complexity 40 (threshold 15). Drivers by points: if/else 9 (30 pts), error handling 2 (4 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
HlsProxyService._handleRequest (cognitive 40) lib/services/http/hls_proxy.dart:166— HlsProxyService._handleRequest has cognitive complexity 40 (threshold 15). Drivers by points: if/else 9 (19 pts), ternaries 4 (11 pts), boolean chains 6, error handling 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Settings.fromJson (cognitive 39) lib/models/settings.dart:722— Settings.fromJson has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23, ternaries 13 (16 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_SourceRepositoriesState._showAddRepoDialog (cognitive 39) REDACTED:234— _SourceRepositoriesState._showAddRepoDialog has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 17, error handling 2, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService._ensureInitialized (cognitive 38) lib/eval/aidoku/service.dart:99— AidokuExtensionService._ensureInitialized has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 5, error handling 3 (5 pts), ternaries 1 (4 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Source._loadDefaults (cognitive 38) lib/eval/aidoku/src/source.dart:428— Source._loadDefaults has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (28 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DetailAppBar.build (cognitive 38) lib/modules/manga/detail/widgets/detail_app_bar.dart:48— DetailAppBar.build has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (23 pts), loops 4 (7 pts), ternaries 5, boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderPrefetchMixin.checkAndReloadEvictedPages (cognitive 37) lib/modules/manga/reader/mixins/reader_prefetch_mixin.dart:107— ReaderPrefetchMixin.checkAndReloadEvictedPages has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 8, loops 2 (5 pts), error handling 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LNReaderExtensionService.getSourcePreferences (cognitive 36) lib/eval/lnreader/service.dart:383— LNReaderExtensionService.getSourcePreferences has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (27 pts), boolean chains 5, loops 1 (3 pts), error handling 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_MangaInfoHeaderState.build (cognitive 36) lib/modules/manga/detail/widgets/manga_info_header.dart:74— _MangaInfoHeaderState.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 7 (15 pts), loops 2, boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SubsamplingScaleImageViewState._initImage (cognitive 36) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:775— _SubsamplingScaleImageViewState._initImage has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 9, error handling 1 (2 pts), ternaries 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderPageIndexMath.currentIndexLabel (cognitive 36) lib/modules/manga/reader/utils/reader_page_index_math.dart:244— ReaderPageIndexMath.currentIndexLabel has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 9 (15 pts), boolean chains 5 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_UpdateTabState.build (cognitive 36) lib/modules/updates/updates_screen.dart:192— _UpdateTabState.build has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 7 (12 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CacheManager.evictOldestIfNeeded (cognitive 36) lib/services/http/custom_extended_image_provider.dart:71— _CacheManager.evictOldestIfNeeded has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 3 (8 pts), ternaries 1 (5 pts), loops 2 (4 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SyncServer.startSync (cognitive 36) lib/services/sync_server.dart:152— SyncServer.startSync has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 6, ternaries 2 (4 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FfiImageDecoder.dylib (cognitive 35) lib/modules/manga/reader/subsampling_scale_image_view/src/ffi_image_decoder.dart:141— FfiImageDecoder.dylib has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 3 (11 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FfiImageDecoder._processNext (cognitive 35) lib/modules/manga/reader/subsampling_scale_image_view/src/ffi_image_decoder.dart:444— FfiImageDecoder._processNext has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (29 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CrashReports._init (cognitive 35) lib/services/crash_report.dart:335— CrashReports._init has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 3 (8 pts), ternaries 2 (6 pts), error handling 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LNReaderExtensionService._mapPluginSettingToSourcePreference (cognitive 34) lib/eval/lnreader/service.dart:426— LNReaderExtensionService._mapPluginSettingToSourcePreference has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 6 (10 pts), boolean chains 6, loops 2 (4 pts), error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CreateExtensionState.build (cognitive 34) lib/modules/browse/extension/widgets/create_extension.dart:43— _CreateExtensionState.build has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (17 pts), if/else 4 (8 pts), boolean chains 3, loops 3, error handling 1 (2 pts), match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomExtendedNetworkImageProvider._loadAsync (cognitive 34) lib/services/http/custom_extended_image_provider.dart:312— CustomExtendedNetworkImageProvider._loadAsync has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (23 pts), error handling 3 (7 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SubsamplingScaleImageViewState.didUpdateWidget (cognitive 33) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:453— _SubsamplingScaleImageViewState.didUpdateWidget has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 2 (7 pts), boolean chains 6 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LNReaderExtensionService._getStoredPreference (cognitive 32) lib/eval/lnreader/service.dart:540— LNReaderExtensionService._getStoredPreference has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ReaderPrefetchMixin.prefetchPagesInOrder (cognitive 32) lib/modules/manga/reader/mixins/reader_prefetch_mixin.dart:159— ReaderPrefetchMixin.prefetchPagesInOrder has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 3, error handling 1 (2 pts), boolean chains 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FfiImageDecoder._cIsolateEntryPoint (cognitive 32) lib/modules/manga/reader/subsampling_scale_image_view/src/ffi_image_decoder.dart:243— FfiImageDecoder._cIsolateEntryPoint has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (24 pts), error handling 2 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ExtensionStoreService._parseProtobufStore (cognitive 32) lib/services/extension_store_service.dart:129— ExtensionStoreService._parseProtobufStore has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (6 pts), boolean chains 5, ternaries 2 (4 pts), error handling 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AppDelegate.didInitializeImplicitFlutterEngine (cognitive 32) ios/Runner/AppDelegate.swift:37— AppDelegate.didInitializeImplicitFlutterEngine has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (25 pts), match/switch 5, boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NavDestinationBuilders.buildNavigationWidgetsDesktop (cognitive 31) lib/modules/main_view/widgets/nav_destination_builders.dart:48— NavDestinationBuilders.buildNavigationWidgetsDesktop has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 11 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NovelBottomBar.build (cognitive 31) lib/modules/novel/widgets/novel_bottom_bar.dart:173— NovelBottomBar.build has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 17 (22 pts), if/else 7 (8 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_MangaWebViewState.build (cognitive 31) lib/modules/webview/webview.dart:221— _MangaWebViewState.build has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (23 pts), ternaries 8 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_CoverViewWidgetState.build (cognitive 31) lib/modules/widgets/cover_view_widget.dart:107— _CoverViewWidgetState.build has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (22 pts), ternaries 6, boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GogoCdnExtractor.videosFromUrl (cognitive 31) lib/services/anime_extractors/gogocdn_extractor.dart:18— GogoCdnExtractor.videosFromUrl has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (7 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlayerShortcutPills.build (cognitive 30) lib/modules/anime/widgets/player_shortcut_pills.dart:64— PlayerShortcutPills.build has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 8 (9 pts), boolean chains 7 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ImageViewWebtoonState._handleScaleUpdate (cognitive 30) lib/modules/manga/reader/image_view_webtoon.dart:293— _ImageViewWebtoonState._handleScaleUpdate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 6 (12 pts), boolean chains 6 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChapterPreloadManager.preloadPrevChapter (cognitive 30) lib/modules/manga/reader/managers/chapter_preload_manager.dart:188— ChapterPreloadManager.preloadPrevChapter has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SubsamplingScaleImageViewState._handleScaleUpdate (cognitive 29) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:1078— _SubsamplingScaleImageViewState._handleScaleUpdate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DownloadFileScreenState._downloadApk (cognitive 29) lib/modules/more/about/providers/download_file_screen.dart:315— _DownloadFileScreenState._downloadApk has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (22 pts), error handling 3 (6 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionStoreService._parseAidokuJsonStore (cognitive 29) lib/services/extension_store_service.dart:243— ExtensionStoreService._parseAidokuJsonStore has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 2 (5 pts), loops 2 (5 pts), boolean chains 3, error handling 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PrecompileBinaries.run (cognitive 29) rust_builder/cargokit/build_tool/lib/src/precompile_binaries.dart:52— PrecompileBinaries.run has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 4 (8 pts), error handling 1 (4 pts), ternaries 1 (nesting depth added 17). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
_MinSubsamplingImageState._loadFromPath (cognitive 28) lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:226— _MinSubsamplingImageState._loadFromPath has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 4, error handling 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ChapterListTileState.build (cognitive 28) lib/modules/reader_common/widgets/btn_chapter_list_dialog.dart:221— _ChapterListTileState.build has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 6, if/else 5 (6 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
CustomExtendedNetworkImageProvider._loadCache (cognitive 28) lib/services/http/custom_extended_image_provider.dart:418— CustomExtendedNetworkImageProvider._loadCache has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), error handling 3 (11 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuJsManager.handleJsRequest (cognitive 27) lib/eval/aidoku/src/interpreter/js_manager.dart:39— AidokuJsManager.handleJsRequest has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (24 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DesktopControllerWidgetState.build (cognitive 27) lib/modules/anime/widgets/desktop.dart:326— _DesktopControllerWidgetState.build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 9 (12 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LibraryAppBar.build (cognitive 27) lib/modules/library/widgets/library_app_bar.dart:114— LibraryAppBar.build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 6 (7 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ChapterListTileWidget.build (cognitive 27) lib/modules/manga/detail/widgets/chapter_list_tile_widget.dart:40— ChapterListTileWidget.build has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 8 (13 pts), if/else 9 (10 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MinSubsamplingImageState._loadImage (cognitive 27) lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:117— _MinSubsamplingImageState._loadImage has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_FloatingNavBarState._bar (cognitive 27) lib/modules/widgets/floating_nav_bar.dart:575— _FloatingNavBarState._bar has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 16 (18 pts), loops 3 (5 pts), boolean chains 2, if/else 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TraktTv.update (cognitive 27) lib/services/trackers/trakt_tv.dart:328— TraktTv.update has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 5 (7 pts), boolean chains 3, loops 1 (3 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ImageViewPagedState._checkIfAnimated (cognitive 26) lib/modules/manga/reader/image_view_paged.dart:80— _ImageViewPagedState._checkIfAnimated has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (19 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SubsamplingScaleImageViewState._loadFromProvider (cognitive 26) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:522— _SubsamplingScaleImageViewState._loadFromProvider has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (23 pts), error handling 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NovelPaginationAndTtsMixin.buildPaginatedSpreadView (cognitive 26) lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:189— NovelPaginationAndTtsMixin.buildPaginatedSpreadView has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 9, ternaries 7 (9 pts), if/else 6 (8 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_TvPillState.build (cognitive 26) lib/modules/widgets/tv_pill.dart:58— _TvPillState.build has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 7, boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
StorageProvider.initDB (cognitive 26) lib/providers/storage_provider.dart:317— StorageProvider.initDB has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), error handling 2 (4 pts), loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService.getHeaders (cognitive 25) lib/eval/aidoku/service.dart:212— AidokuExtensionService.getHeaders has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 4 (5 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderPageIndexMath.buildSpreads (cognitive 25) lib/modules/manga/reader/utils/reader_page_index_math.dart:83— ReaderPageIndexMath.buildSpreads has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MangaWebViewState._runWebViewDesktop (cognitive 25) lib/modules/webview/webview.dart:105— _MangaWebViewState._runWebViewDesktop has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (6 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuarkUcExtractor.lcs (cognitive 25) lib/services/anime_extractors/quarkuc_extractor.dart:557— QuarkUcExtractor.lcs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VoeExtractor.videosFromUrl (cognitive 25) lib/services/anime_extractors/voe_extractor.dart:26— VoeExtractor.videosFromUrl has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 2 (6 pts), boolean chains 2, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionStoreService._convertJsonExtensionsToSources (cognitive 25) lib/services/extension_store_service.dart:604— ExtensionStoreService._convertJsonExtensionsToSources has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 3 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Source.initSettings (cognitive 24) lib/eval/aidoku/src/source.dart:344— Source.initSettings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LNReaderExtensionService.getDetail (cognitive 24) lib/eval/lnreader/service.dart:276— LNReaderExtensionService.getDetail has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 4, error handling 1 (3 pts), ternaries 2 (3 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnimePlayerSettingsMixin.buildPlayerSettingsEntries (cognitive 24) lib/modules/anime/mixins/anime_player_settings_mixin.dart:92— AnimePlayerSettingsMixin.buildPlayerSettingsEntries has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 7 (9 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_ImageViewWebtoonState._estimateExtent (cognitive 24) lib/modules/manga/reader/image_view_webtoon.dart:533— _ImageViewWebtoonState._estimateExtent has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, ternaries 2 (4 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TraktDiscovery.findWatchOrderLists (cognitive 24) lib/services/discovery/trakt_discovery.dart:346— TraktDiscovery.findWatchOrderLists has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (4 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChapterPreloadManager.preloadNextChapter (cognitive 23) lib/modules/manga/reader/managers/chapter_preload_manager.dart:101— ChapterPreloadManager.preloadNextChapter has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MinSubsamplingImageState.build (cognitive 23) lib/modules/manga/reader/subsampling_scale_image_view/src/min_subsampling_image_view.dart:349— _MinSubsamplingImageState.build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 7 (8 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_SubsamplingScaleImageViewState._loadTile (cognitive 23) lib/modules/manga/reader/subsampling_scale_image_view/src/subsampling_scale_image_view.dart:960— _SubsamplingScaleImageViewState._loadTile has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LNReaderExtensionService._setStoredPreference (cognitive 22) lib/eval/lnreader/service.dart:583— LNReaderExtensionService._setStoredPreference has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, ternaries 1 (3 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_BrowseScreenState.build (cognitive 22) lib/modules/browse/browse_screen.dart:337— _BrowseScreenState.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (9 pts), loops 4 (6 pts), ternaries 3 (5 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
VerifyBinaries.run (cognitive 22) rust_builder/cargokit/build_tool/lib/src/verify_binaries.dart:23— VerifyBinaries.run has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (5 pts) (nesting depth added 14). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Source.loadFromAixBytes (cognitive 21) lib/eval/aidoku/src/source.dart:89— Source.loadFromAixBytes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LibraryBody.build (cognitive 21) lib/modules/library/widgets/library_body.dart:73— LibraryBody.build has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10 (15 pts), if/else 3, boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MangaHomeScreenState._loadMore (cognitive 21) lib/modules/manga/home/manga_home_screen.dart:90— _MangaHomeScreenState._loadMore has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MangaChapterPageGalleryState._setReaderMode (cognitive 21) REDACTED:1286— _MangaChapterPageGalleryState._setReaderMode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CargokitCrateOptions.parse (cognitive 21) rust_builder/cargokit/build_tool/lib/src/options.dart:176— CargokitCrateOptions.parse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (4 pts) (nesting depth added 12). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
_SubtitleSectionWidgetState.build (cognitive 20) lib/modules/anime/widgets/subtitle_section_widget.dart:58— _SubtitleSectionWidgetState.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, error handling 3, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ExtensionScreenState.build (cognitive 20) lib/modules/browse/extension/extension_screen.dart:60— _ExtensionScreenState.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, loops 2, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MangaGlobalImageCardState.build (cognitive 20) lib/modules/browse/global_search/global_search_screen.dart:530— _MangaGlobalImageCardState.build has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9, boolean chains 7, if/else 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FilterWidget.build (cognitive 20) lib/modules/manga/home/widget/filter_widget.dart:87— FilterWidget.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ImageViewPagedState._performLandscapeZoom (cognitive 20) lib/modules/manga/reader/image_view_paged.dart:168— _ImageViewPagedState._performLandscapeZoom has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, boolean chains 5, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MangaChapterPageGalleryState._readProgressListener (cognitive 20) REDACTED:1083— _MangaChapterPageGalleryState._readProgressListener has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 5, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderPageContent.build (cognitive 20) lib/modules/manga/reader/widgets/reader_page_content.dart:104— ReaderPageContent.build has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_SettingsHome.build (cognitive 20) lib/modules/widgets/settings/settings_drilldown.dart:203— _SettingsHome.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 6 (10 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChapterCache.getPageListFromCache (cognitive 20) lib/services/chapter_cache.dart:53— ChapterCache.getPageListFromCache has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChapterCache.trimCache (cognitive 20) lib/services/chapter_cache.dart:137— ChapterCache.trimCache has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 3 (7 pts), loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
M3u8Downloader.download (cognitive 20) lib/services/download_manager/m3u8/m3u8_downloader.dart:97— M3u8Downloader.download has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MyAppState._setupMpvConfig (cognitive 19) lib/main.dart:742— _MyAppState._setupMpvConfig has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 1 (3 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnimeTrackSelectionMixin.initializeDefaultSubtitleAndAudioTracks (cognitive 19) lib/modules/anime/mixins/anime_track_selection_mixin.dart:38— AnimeTrackSelectionMixin.initializeDefaultSubtitleAndAudioTracks has cognitive complexity 19 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 7, ternaries 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_CodeEditorPageState._execute (cognitive 19) lib/modules/browse/extension/edit_code.dart:200— _CodeEditorPageState._execute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (6 pts), match/switch 2 (5 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SourcePreferenceWidgetState._row (cognitive 19) lib/modules/browse/extension/widgets/source_preference_widget.dart:29— _SourcePreferenceWidgetState._row has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (6 pts), loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NavDestinationBuilders.buildNavigationWidgetsMobile (cognitive 19) lib/modules/main_view/widgets/nav_destination_builders.dart:249— NavDestinationBuilders.buildNavigationWidgetsMobile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, ternaries 3 (6 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_MigrationMangaGlobalImageCardState._showMigrateDialog (cognitive 19) lib/modules/manga/detail/widgets/migrate_screen.dart:329— _MigrationMangaGlobalImageCardState._showMigrateDialog has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (8 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TrackerWidgetState.build (cognitive 19) lib/modules/manga/detail/widgets/tracker_widget.dart:61— _TrackerWidgetState.build has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8, if/else 7, boolean chains 2, loops 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExtensionServerReleaseService.fetchLatestRelease (cognitive 19) lib/modules/more/settings/browse/extension_server/extension_server_release_service.dart:16— ExtensionServerReleaseService.fetchLatestRelease has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ExtensionServerScreenState.build (cognitive 19) lib/modules/more/settings/browse/extension_server_screen.dart:83— _ExtensionServerScreenState.build has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 5, boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
QuarkUcExtractor.save (cognitive 19) lib/services/anime_extractors/quarkuc_extractor.dart:330— QuarkUcExtractor.save has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionStoreService._parseJsonNetworkStore (cognitive 19) lib/services/extension_store_service.dart:187— ExtensionStoreService._parseJsonNetworkStore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService.getHtmlContent (cognitive 18) lib/eval/aidoku/service.dart:373— AidokuExtensionService.getHtmlContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnimeMpvBridgeMixin.handleMpvEvents (cognitive 18) lib/modules/anime/mixins/anime_mpv_bridge_mixin.dart:58— AnimeMpvBridgeMixin.handleMpvEvents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 2, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SpeedMenuState.build (cognitive 18) lib/modules/anime/widgets/tv_player_pills.dart:254— _SpeedMenuState.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TabletLayoutState.build (cognitive 18) lib/modules/main_view/widgets/tablet_layout.dart:121— _TabletLayoutState.build has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9, if/else 5 (6 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_MigrationSourceSearchScreenState._init (cognitive 18) lib/modules/manga/detail/widgets/migrate_screen.dart:175— _MigrationSourceSearchScreenState._init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChapterPageDownload.build (cognitive 18) lib/modules/manga/download/download_page_widget.dart:97— ChapterPageDownload.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_PlayerAdvancedScreenState._checkMpvConfig (cognitive 18) lib/modules/more/settings/player/player_advanced_screen.dart:59— _PlayerAdvancedScreenState._checkMpvConfig has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QuarkUcExtractor.api (cognitive 18) lib/services/anime_extractors/quarkuc_extractor.dart:71— QuarkUcExtractor.api has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SyncEntityApplier._applyTombstones (cognitive 18) lib/services/sync/sync_entity_applier.dart:361— SyncEntityApplier._applyTombstones has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 6 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService.getPageList (cognitive 17) lib/eval/aidoku/service.dart:322— AidokuExtensionService.getPageList has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), error handling 1 (3 pts) (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_AnimeStreamPageState.initState (cognitive 17) lib/modules/anime/anime_player_view.dart:614— _AnimeStreamPageState.initState has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 2, boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_SeekIndicatorState.build (cognitive 17) lib/modules/anime/widgets/mobile_seek_indicator.dart:88— _SeekIndicatorState.build has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 17. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TvPlayerControlsState.build (cognitive 17) lib/modules/anime/widgets/tv_player_controls.dart:155— _TvPlayerControlsState.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_TvSeekBarState.build (cognitive 17) lib/modules/anime/widgets/tv_player_seek_bar.dart:77— _TvSeekBarState.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_OnboardingLocalFolderSectionState.build (cognitive 17) lib/modules/onboarding/widgets/onboarding_local_folder_section.dart:172— _OnboardingLocalFolderSectionState.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderAppBar.build (cognitive 17) lib/modules/reader_common/widgets/reader_app_bar.dart:70— ReaderAppBar.build has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9, if/else 5 (7 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_CustomSliverGroupedListViewState._prepareElements (cognitive 17) lib/modules/widgets/custom_sliver_grouped_list_view.dart:160— _CustomSliverGroupedListViewState._prepareElements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_GlobalSearchResultCardState.build (cognitive 17) lib/modules/widgets/global_search_result_card.dart:48— _GlobalSearchResultCardState.build has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CustomExtendedNetworkImageProvider._loadNetwork (cognitive 17) lib/services/http/custom_extended_image_provider.dart:484— CustomExtendedNetworkImageProvider._loadNetwork has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 1 (3 pts), error handling 2, loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SyncServer._syncLoop (cognitive 17) lib/services/sync_server.dart:234— SyncServer._syncLoop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CargoBuildOptions.parse (cognitive 17) rust_builder/cargokit/build_tool/lib/src/options.dart:78— CargoBuildOptions.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (nesting depth added 9). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
AidokuExtensionService._resolveFilterId (cognitive 16) lib/eval/aidoku/service.dart:916— AidokuExtensionService._resolveFilterId has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AidokuExtensionService._extractChapterKey (cognitive 16) lib/eval/aidoku/service.dart:1076— AidokuExtensionService._extractChapterKey has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Source.loadFromDirectory (cognitive 16) lib/eval/aidoku/src/source.dart:231— Source.loadFromDirectory has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomTrackShape.paint (cognitive 16) lib/modules/anime/widgets/custom_track_shape.dart:52— CustomTrackShape.paint has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 2 (4 pts), boolean chains 2, ternaries 2 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TvPlayerPillBar.build (cognitive 16) lib/modules/anime/widgets/tv_player_pills.dart:44— TvPlayerPillBar.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (5 pts), loops 3 (5 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_LibraryScreenState._buildWithCategories (cognitive 16) lib/modules/library/library_screen.dart:364— _LibraryScreenState._buildWithCategories has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 5, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_ImageViewWebtoonState.initState (cognitive 16) lib/modules/manga/reader/image_view_webtoon.dart:160— _ImageViewWebtoonState.initState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3 (nesting depth added 7). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_DownloadQueueScreenState.build (cognitive 16) lib/modules/more/download_queue/download_queue_screen.dart:25— _DownloadQueueScreenState.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionServerActionsGroup.build (cognitive 16) lib/modules/more/settings/browse/extension_server/widgets/extension_server_actions_group.dart:48— ExtensionServerActionsGroup.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 11 (13 pts), boolean chains 2, if/else 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_GeneralStateScreen.build (cognitive 16) lib/modules/more/settings/general/general_screen.dart:42— _GeneralStateScreen.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 6, loops 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NovelTtsService._highlightWordInElement (cognitive 16) lib/modules/novel/tts/novel_tts_service.dart:426— NovelTtsService._highlightWordInElement has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChapterCache.clear (cognitive 16) lib/services/chapter_cache.dart:184— ChapterCache.clear has cognitive complexity 16 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 2 (6 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DoHResolver._parseDoHResponse (cognitive 16) lib/services/http/doh/doh_resolver.dart:230— DoHResolver._parseDoHResponse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 1 (4 pts), boolean chains 3, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Anilist._executeGraphQL (cognitive 16) lib/services/trackers/anilist.dart:374— Anilist._executeGraphQL has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TraktTv._parseTraktItems (cognitive 16) lib/services/trackers/trakt_tv.dart:162— TraktTv._parseTraktItems has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling clique: get_chapter_pages.dart, get_detail.dart, get_latest_updates.dart, get_popular.dart, search.dart lib/services/get_chapter_pages.dart— 5 files — `lib/services/get_chapter_pages.dart`, `lib/services/get_detail.dart`, `lib/services/get_latest_updates.dart`, `lib/services/get_popular.dart`, `lib/services/search.dart` — all change together with no explicit dependency: a fully-connected co-change clique, not 10 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Near-duplicate member pair (66 shared lines) lib/modules/manga/reader/widgets/reader_settings_modal.dart:275— lib/modules/manga/reader/widgets/reader_settings_modal.dart:275-457 | lib/modules/more/settings/reader/reader_screen.dart:47-344 — These two members are variants of one another: 66 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/modules/browse/global_search/global_search_screen.dart:530— lib/modules/browse/global_search/global_search_screen.dart:530-680 | lib/modules/widgets/global_search_result_card.dart:48-189 | lib/modules/widgets/tv_pill.dart:58-163 | lib/modules/widgets/tv_row_button.dart:157-222 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (37 lines × 2) lib/modules/manga/reader/widgets/reader_settings_modal.dart:418— lib/modules/manga/reader/widgets/reader_settings_modal.dart:418-454 | lib/modules/more/settings/reader/reader_screen.dart:278-314 — before extracting anything, compare `lib/modules/manga/reader/widgets/reader_settings_modal.dart` and `lib/modules/more/settings/reader/reader_screen.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33 lines × 2) lib/modules/manga/detail/widgets/chapter_list_tile_widget.dart:315— lib/modules/manga/detail/widgets/chapter_list_tile_widget.dart:315-347 | lib/modules/manga/detail/widgets/watch_order_screen.dart:753-785 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (26 lines × 3) lib/eval/mihon/service.dart:70— lib/eval/mihon/service.dart:70-95 | lib/eval/mihon/service.dart:104-129 | lib/eval/mihon/service.dart:139-164 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (25 lines × 2) lib/modules/widgets/settings/settings_drilldown.dart:381— lib/modules/widgets/settings/settings_drilldown.dart:381-405 | lib/modules/widgets/settings/settings_drilldown.dart:595-619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19–23 lines × 2) lib/modules/anime/widgets/desktop.dart:270— lib/modules/anime/widgets/desktop.dart:270-292 | lib/modules/anime/widgets/desktop.dart:295-313 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) lib/modules/browse/global_search/global_search_screen.dart:568— lib/modules/browse/global_search/global_search_screen.dart:568-589 | lib/modules/widgets/global_search_result_card.dart:82-103 — before extracting anything, compare `lib/modules/browse/global_search/global_search_screen.dart` and `lib/modules/widgets/global_search_result_card.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) lib/modules/anime/widgets/search_subtitles.dart:162— lib/modules/anime/widgets/search_subtitles.dart:162-182 | lib/modules/manga/detail/widgets/tracker_search_widget.dart:123-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18–19 lines × 2) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:122— lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:122-139 | lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:260-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–18 lines × 3) lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:288— lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:288-304 | lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:315-332 | lib/modules/novel/mixins/novel_pagination_tts_mixin.dart:340-356 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16–18 lines × 2) lib/modules/browse/global_search/global_search_screen.dart:619— lib/modules/browse/global_search/global_search_screen.dart:619-634 | lib/modules/widgets/global_search_result_card.dart:126-143 — before extracting anything, compare `lib/modules/browse/global_search/global_search_screen.dart` and `lib/modules/widgets/global_search_result_card.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15–18 lines × 2) lib/modules/manga/detail/widgets/recommendation_screen.dart:78— lib/modules/manga/detail/widgets/recommendation_screen.dart:78-92 | lib/modules/manga/detail/widgets/related_screen.dart:72-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–17 lines × 2) lib/modules/history/history_screen.dart:162— lib/modules/history/history_screen.dart:162-170 | lib/modules/updates/updates_screen.dart:213-229 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15–17 lines × 2) lib/modules/widgets/cover_view_widget.dart:220— lib/modules/widgets/cover_view_widget.dart:220-234 | lib/modules/widgets/tv_pill.dart:95-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12–16 lines × 4) lib/modules/novel/widgets/novel_reader_settings_sheet.dart:77— lib/modules/novel/widgets/novel_reader_settings_sheet.dart:77-92 | lib/modules/novel/widgets/novel_reader_settings_sheet.dart:94-109 | lib/modules/novel/widgets/novel_reader_settings_sheet.dart:111-126 | lib/modules/novel/widgets/novel_reader_settings_sheet.dart:127-138 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 3) lib/eval/lnreader/service.dart:220— lib/eval/lnreader/service.dart:220-234 | lib/eval/lnreader/service.dart:240-254 | lib/eval/lnreader/service.dart:261-274 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–14 lines × 2) lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:102— lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:102-113 | lib/modules/more/data_and_storage/providers/tachiyomi_restore_service.dart:233-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–13 lines × 2) lib/modules/anime/widgets/desktop.dart:658— lib/modules/anime/widgets/desktop.dart:658-670 | REDACTED:785-795 — before extracting anything, compare `lib/modules/anime/widgets/desktop.dart` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) lib/modules/browse/global_search/global_search_screen.dart:540— lib/modules/browse/global_search/global_search_screen.dart:540-551 | lib/modules/widgets/global_search_result_card.dart:59-70 | lib/modules/widgets/tv_pill.dart:76-87 | lib/modules/widgets/tv_row_button.dart:163-174 — before extracting anything, compare `lib/modules/browse/global_search/global_search_screen.dart` and `lib/modules/widgets/global_search_result_card.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) lib/repositories/source_repository.dart:64— lib/repositories/source_repository.dart:64-75 | lib/repositories/source_repository.dart:79-90 | lib/repositories/source_repository.dart:94-105 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11–12 lines × 2) lib/modules/manga/reader/widgets/reader_bottom_bar.dart:137— lib/modules/manga/reader/widgets/reader_bottom_bar.dart:137-148 | lib/modules/novel/widgets/novel_bottom_bar.dart:177-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–10 lines × 2) lib/services/trackers/anilist.dart:73— lib/services/trackers/anilist.dart:73-81 | lib/services/trackers/kitsu.dart:67-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–10 lines × 2) lib/services/trackers/trakt_tv.dart:192— lib/services/trackers/trakt_tv.dart:192-199 | lib/services/trackers/trakt_tv.dart:306-315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 3) lib/services/anime_extractors/mystream_extractor.dart:45— lib/services/anime_extractors/mystream_extractor.dart:45-53 | lib/services/anime_extractors/okru_extractor.dart:38-46 | lib/services/anime_extractors/voe_extractor.dart:89-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6–8 lines × 2) lib/services/anime_extractors/sendvid_extractor.dart:28— lib/services/anime_extractors/sendvid_extractor.dart:28-33 | lib/services/anime_extractors/streamwish_extractor.dart:42-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6–7 lines × 3) lib/services/trackers/simkl.dart:112— lib/services/trackers/simkl.dart:112-117 | lib/services/trackers/simkl.dart:215-221 | lib/services/trackers/simkl.dart:246-252 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) lib/eval/model/document.dart:37— lib/eval/model/document.dart:37-42 | lib/eval/model/document.dart:44-49 | lib/eval/model/element.dart:47-52 | lib/eval/model/element.dart:54-59 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 6) lib/repositories/category_repository.dart:23— lib/repositories/category_repository.dart:23-28 | lib/repositories/chapter_repository.dart:39-44 | lib/repositories/history_repository.dart:57-62 | lib/repositories/manga_repository.dart:78-83 | lib/repositories/track_repository.dart:111-116 | lib/repositories/update_repository.dart:20-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
Duplicated block (6 lines × 3) lib/repositories/category_repository.dart:66— lib/repositories/category_repository.dart:66-71 | lib/repositories/chapter_repository.dart:115-120 | lib/repositories/track_repository.dart:160-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (16 lines × 5) rust/src/aidoku_wasm/host_js.rs:94— rust/src/aidoku_wasm/host_js.rs:94-109 | rust/src/aidoku_wasm/host_js.rs:131-146 | rust/src/aidoku_wasm/host_js.rs:168-183 | rust/src/aidoku_wasm/host_js.rs:343-358 | rust/src/aidoku_wasm/host_js.rs:380-395 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) rust/src/aidoku_wasm/host_js.rs:105— rust/src/aidoku_wasm/host_js.rs:105-117 | rust/src/aidoku_wasm/host_js.rs:142-154 | rust/src/aidoku_wasm/host_js.rs:316-329 | rust/src/aidoku_wasm/host_js.rs:354-366 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 5) rust/src/aidoku_wasm/host_js.rs:68— rust/src/aidoku_wasm/host_js.rs:68-80 | rust/src/aidoku_wasm/host_js.rs:105-117 | rust/src/aidoku_wasm/host_js.rs:142-154 | rust/src/aidoku_wasm/host_js.rs:317-329 | rust/src/aidoku_wasm/host_js.rs:354-366 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 5) rust/src/aidoku_wasm/host_html.rs:360— rust/src/aidoku_wasm/host_html.rs:360-370 | rust/src/aidoku_wasm/host_html.rs:384-394 | rust/src/aidoku_wasm/host_html.rs:430-440 | rust/src/aidoku_wasm/host_html.rs:449-459 | rust/src/aidoku_wasm/host_html.rs:689-699 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 10) rust/src/aidoku_wasm/host_html.rs:360— rust/src/aidoku_wasm/host_html.rs:360-370 | rust/src/aidoku_wasm/host_html.rs:384-394 | rust/src/aidoku_wasm/host_html.rs:410-420 | rust/src/aidoku_wasm/host_html.rs:430-440 | rust/src/aidoku_wasm/host_html.rs:449-459 | rust/src/aidoku_wasm/host_html.rs:634-644 | rust/src/aidoku_wasm/host_html.rs:659-669 | rust/src/aidoku_wasm/host_html.rs:689-699 | rust/src/aidoku_wasm/host_html.rs:718-728 | rust/src/aidoku_wasm/host_html.rs:791-801 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) rust/src/aidoku_wasm/host_html.rs:243— rust/src/aidoku_wasm/host_html.rs:243-252 | rust/src/aidoku_wasm/host_html.rs:272-281 | rust/src/aidoku_wasm/host_html.rs:493-502 | rust/src/aidoku_wasm/host_html.rs:534-543 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 7) rust/src/aidoku_wasm/host_html.rs:175— rust/src/aidoku_wasm/host_html.rs:175-183 | rust/src/aidoku_wasm/host_html.rs:245-253 | rust/src/aidoku_wasm/host_html.rs:274-282 | rust/src/aidoku_wasm/host_html.rs:297-305 | rust/src/aidoku_wasm/host_html.rs:468-476 | rust/src/aidoku_wasm/host_html.rs:495-503 | rust/src/aidoku_wasm/host_html.rs:536-544 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) rust/src/aidoku_wasm/host_html.rs:747— rust/src/aidoku_wasm/host_html.rs:747-754 | rust/src/aidoku_wasm/host_html.rs:832-839 | rust/src/aidoku_wasm/host_html.rs:862-869 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Off the main sequence: shiori — shiori: abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap lib/eval/aidoku/src/models/setting.dart:297— `Setting.fromJson` is public and takes `Map<String, dynamic> json` from its caller, and it calls itself at line 297 (`Setting.fromJson`) with a piece of `json` (and at line 424) — and nowhere in `Setting.fromJson` 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. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `Setting.fromJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Duplicated predicate lib/main.dart:749— `!(await mpvFile.exists()) && !(await inputFile.exists())` appears character-identically in 2 files — lib/main.dart, lib/modules/more/settings/player/player_advanced_screen.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/library/widgets/category_selection_dialog.dart:51— `!snapshot.hasData || snapshot.data!.isEmpty` appears character-identically in 3 files — lib/modules/library/widgets/category_selection_dialog.dart, lib/modules/main_view/widgets/nav_badges.dart, lib/modules/more/download_queue/download_queue_screen.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/manga/detail/widgets/related_screen.dart:231— `'ALTERNATIVE' || 'ALTERNATIVE_SETTING' || 'ALTERNATIVE_VERSION'` appears character-identically in 2 files — lib/modules/manga/detail/widgets/related_screen.dart, lib/services/related_titles.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/manga/detail/widgets/chapter_list_tile_widget.dart:157— `chapter.dateUpload == null || chapter.dateUpload!.isEmpty` appears character-identically in 2 files — lib/modules/manga/detail/widgets/chapter_list_tile_widget.dart, lib/modules/reader_common/widgets/btn_chapter_list_dialog.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/manga/download/providers/download_provider.dart:97— `connectivity.contains(ConnectivityResult.wifi) || connectivity.contains(ConnectivityResult.ethernet)` appears character-identically in 2 files — lib/modules/manga/download/providers/download_provider.dart, lib/services/library_updater.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/services/extension_store_service.dart:439— `e['id'] is String && e['name'] != null && e['site'] != null && e['lang'] != null && e['version'] != null && e['url'] != null && e['iconUrl']…` appears character-identically in 2 files — lib/services/extension_store_service.dart, lib/services/fetch_sources_list.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/mixins/anime_track_selection_mixin.dart:557— `effective == null || effective.id == "no"` appears character-identically in 2 files — lib/modules/anime/mixins/anime_track_selection_mixin.dart, lib/modules/anime/widgets/subtitle_section_widget.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/mixins/anime_player_settings_mixin.dart:120— `effective == null || effective.id == 'no'` appears character-identically in 2 files — lib/modules/anime/mixins/anime_player_settings_mixin.dart, lib/modules/anime/mixins/anime_track_selection_mixin.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/widgets/tv_player_controls.dart:185— `event is KeyDownEvent && isTvPlayerSelectKey(k)` appears character-identically in 3 files — lib/modules/anime/widgets/tv_player_controls.dart, lib/modules/anime/widgets/tv_player_pills.dart, lib/modules/anime/widgets/tv_player_seek_bar.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/library/tv_home/widgets/tv_empty_home.dart:50— `event is KeyDownEvent && isTvSelectKey(event.logicalKey)` appears character-identically in 5 files — lib/modules/library/tv_home/widgets/tv_empty_home.dart, lib/modules/library/tv_home/widgets/tv_home_hero.dart, lib/modules/manga/detail/tv/widgets/tv_detail_episodes_panel.dart, lib/modules/manga/detail/tv/widgets/tv_detail_left_info.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/browse/global_search/global_search_screen.dart:552— `event is KeyDownEvent && tvIsSelectKey(event.logicalKey)` appears character-identically in 3 files — lib/modules/browse/global_search/global_search_screen.dart, lib/modules/widgets/global_search_result_card.dart, lib/modules/widgets/tv_menu.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/mixins/anime_player_controls_mixin.dart:572— `event is KeyDownEvent || event is KeyRepeatEvent` appears character-identically in 7 files — lib/modules/anime/mixins/anime_player_controls_mixin.dart, lib/modules/anime/widgets/tv_player_controls.dart, lib/modules/anime/widgets/tv_player_seek_bar.dart, lib/modules/anime/widgets/tv_player_settings_panel.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/widgets/tv_player_pills.dart:269— `event is! KeyDownEvent && event is! KeyRepeatEvent` appears character-identically in 5 files — lib/modules/anime/widgets/tv_player_pills.dart, lib/modules/library/tv_home/tv_anime_home_view.dart, lib/modules/main_view/widgets/tablet_layout.dart, lib/modules/widgets/tv_menu.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/browse/global_search/global_search_screen.dart:542— `f && context.mounted && Scrollable.maybeOf(context) != null` appears character-identically in 5 files — lib/modules/browse/global_search/global_search_screen.dart, lib/modules/more/settings/appearance/widgets/theme_selector.dart, lib/modules/widgets/global_search_result_card.dart, lib/modules/widgets/tv_pill.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/mixins/anime_track_selection_mixin.dart:58— `file.startsWith("http") || file.startsWith("file")` appears character-identically in 2 files — lib/modules/anime/mixins/anime_track_selection_mixin.dart, lib/modules/anime/utils/track_list_builder.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/services/downloaded_chapter.dart:59— `folderPath == null || folderPath.isEmpty` appears character-identically in 3 files — lib/services/downloaded_chapter.dart, lib/services/local_folders.dart, lib/utils/extensions/chapter_extensions.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/widgets/cover_view_widget.dart:98— `hasFocus && (isTv || FocusManager.instance.highlightMode == FocusHighlightMode.traditional)` appears character-identically in 2 files — lib/modules/widgets/cover_view_widget.dart, packages/shiori/lib/src/components/cover.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/widgets/tv_player_pills.dart:282— `k == LogicalKeyboardKey.arrowLeft || k == LogicalKeyboardKey.arrowRight` appears character-identically in 2 files — lib/modules/anime/widgets/tv_player_pills.dart, lib/modules/widgets/tv_menu.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/widgets/tv_player_focusable.dart:7— `k == LogicalKeyboardKey.select || k == LogicalKeyboardKey.enter || k == LogicalKeyboardKey.numpadEnter || k == LogicalKeyboardKey.gameButton…` appears character-identically in 5 files — lib/modules/anime/widgets/tv_player_focusable.dart, lib/modules/anime/widgets/tv_player_settings_panel.dart, lib/modules/library/tv_home/tv_home_layout.dart, lib/modules/manga/detail/tv/widgets/tv_key_utils.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/mass_migration/services/mass_migration_service.dart:502— `leftTokens.isEmpty || rightTokens.isEmpty` appears character-identically in 2 files — lib/modules/mass_migration/services/mass_migration_service.dart, lib/services/discovery/title_match.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/main_view/widgets/mobile_bottom_navigation.dart:105— `location == null || validLocations.contains(location)` appears character-identically in 2 files — lib/modules/main_view/widgets/mobile_bottom_navigation.dart, lib/modules/main_view/widgets/tablet_layout.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/library/library_screen.dart:285— `m.categories == null || m.categories!.isEmpty` appears character-identically in 3 files — lib/modules/library/library_screen.dart, lib/modules/library/widgets/library_app_bar.dart, lib/modules/library/widgets/library_body.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/modules/anime/mixins/anime_track_selection_mixin.dart:412— `normalized == null || normalized.isEmpty` appears character-identically in 2 files — lib/modules/anime/mixins/anime_track_selection_mixin.dart, lib/modules/anime/utils/audio_track_fallback.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/eval/aidoku/service.dart:165— `p.entryValues != null && p.valueIndex != null && p.valueIndex! < p.entryValues!.length` appears character-identically in 2 files — lib/eval/aidoku/service.dart, lib/services/extension_preferences_service.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:270— `rUrl == clean || rUrl == '$clean/' || '$rUrl/' == clean` appears character-identically in 2 files — REDACTED, lib/providers/browse_state_provider.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default in catch lib/eval/dart/service.dart:44— `getHeaders` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/eval/dart/service.dart:158— `getSourcePreferences` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/eval/lnreader/service.dart:421— `getSourcePreferences` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/eval/model/m_bridge.dart:99— `xpath` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/eval/model/m_bridge.dart:135— `unpackJs` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/eval/model/m_bridge.dart:144— `unpackJsAndCombine` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/eval/model/m_bridge.dart:157— `getMapValue` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/services/torrent_server.dart:126— `getActiveTorrents` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/utils/memory_probe.dart:77— `_rss` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/host_canvas.rs:133— `link` turns every `Err` into `-3` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/host_defaults.rs:89— `link` turns every `Err` into `-1` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/host_html.rs:32— `link` turns every `Err` into `-3` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/host_js.rs:85— `link` turns every `Err` into `-3` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/host_net.rs:204— `link` turns every `Err` into `-1` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/host_std.rs:95— `link` turns every `Err` into `-5.0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/aidoku_wasm/selector.rs:385— `parse_nth` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err rust/src/crash.rs:206— `mangayomi_install_crash_handler` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
IC1 · Incompleteness & stubs· Member throws UnsupportedError · ×6
Member throws UnsupportedError lib/services/trackers/kitsu.dart:437— `displayScore`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/services/trackers/kitsu.dart:442— `getScoreValue`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/services/trackers/myanimelist.dart:452— `displayScore`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/services/trackers/myanimelist.dart:457— `getScoreValue`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/services/trackers/simkl.dart:448— `displayScore`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/services/trackers/simkl.dart:453— `getScoreValue`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 50 significant file(s) lose their only recent owner: lib/eval/aidoku/service.dart, go/server.go, lib/services/extension_store_service.dart, lib/modules/anime/widgets/subtitle_setting_widget.dart, lib/eval/aidoku/src/source.dart, lib/modules/manga/reader/subsampling_scale_image_view/src/ffi_image_decoder.dart, lib/services/sync/sync_entity_applier.dart, lib/eval/aidoku/src/models/setting.dart (+42 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 10 significant file(s) lose their only recent owner: lib/modules/manga/detail/widgets/watch_order_screen.dart, lib/services/crash_report.dart, lib/modules/manga/detail/widgets/related_screen.dart, lib/services/http/doh/doh_providers.dart, lib/services/crash_report_issue.dart, lib/services/crash_native.dart, lib/modules/more/data_and_storage/providers/kotatsu_backup.dart, lib/modules/widgets/app_ui_scale.dart (+2 more). Pair on, review, or document these before any departure.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (64 single-owned of 483 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 483 of the 787 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: lib/utils/downloaded_page_file.dart, lib/services/backup_password_storage.dart, lib/modules/more/data_and_storage/providers/delete_source.dart, lib/modules/anime/utils/audio_track_fallback.dart.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 7.8/10. The most over is `(repository root)` (122695 LoC, 1190 module-visible types across 147 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 1 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: repo/update_source.py (2 orphaned of 483 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 483 of the 787 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file repo/update_source.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No ADRs — 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.
Logging is not universal — Only 4/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `macos`, `widgetbook`.
No SAST — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 29653 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.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: lib/services/m_extension_server.dart:60 — `HttpServer.bind(`.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted rust_builder/cargokit/build_tool/lib/src/util.dart:109— `finer` at line 109 is called with an argument built by `arguments.join('…')` (line 109), whose cost grows with the collection it walks. Dart evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because finer is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLoggable` test, no `kDebugMode` or debug flag, no `assert`, no closure the logger calls only when the level is on.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
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.
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.
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.
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.
Run 01a16905-b50e-7107-9461-0b234e620637 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 99 · Warnings: 766 · Recommendations: 69 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 13:49 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.