getmydia / mydia
Code health
Hotspots average 6.6, the place fixes pay off most.
Explore this codebase
- Code health map690hotspots across 6,055 files
- Ownership5,596sole-owned files: one author, no second reader
- Architecture20modules, 48 entry points
- Decisions107recorded, of which 0 in force and 107 background
- Refactoring37open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 4
5 things worth doing in the week to Nov 15, the last indexed commit, 1 of them now.
Worth planning
Tidy the code shape this week's commits left: 14 findings in 9 files
13 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
player/lib/core/backup/backup_sync_service.dart(4 findings): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 14
- files
- 9
- commits
- 13
Medium effortSimplify
_initializePlayerinplayer/lib/presentation/screens/player/player_screen.dart: tests reach it, and fixes keep landingChanged 201 times in 90 days, and 89 of those commits were bug fixes.
- commits in 90 days
- 201
- bug-fix commits
- 89
- line coverage
- Unknown, no report
- tests that reach it
- 10 test files, call graph(inferred)
Large effort, worth a checkReview why fixes keep landing in
player/lib/presentation/widgets/app_shell.dart: tests reach itChanged 53 times in 90 days, and 26 of those commits were bug fixes.
- commits in 90 days
- 53
- bug-fix commits
- 26
- line coverage
- Unknown, no report
- tests that reach it
- 17 test files, call graph(inferred)
Large effort, worth a checkReview why fixes keep landing in
native/mydia_p2p_core/src/lib.rs: tests reach itChanged 46 times in 90 days, and 28 of those commits were bug fixes.
- commits in 90 days
- 46
- bug-fix commits
- 28
- line coverage
- Unknown, no report
- tests that reach it
- 14 test files, call graph(inferred)
Large effort, worth a check
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effort
Everything we found
5 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health3,989 open findingsCriticalChange entropy · player/lib/core/downloads/download_service_native.dart47 findings · 12.0 deducted
- Refactoring37 open opportunitiesLowmain+0.3 health, S effort · scripts/check_rust_lints.py
- Doc drift44Mediumdesign/plans/2026-11-06-discover-people-tab.mdDocument names test/mydia_web/live/discover_live/url_params_test.exs, which no longer exists.
- Decisions0 drifting from the codeMediumplayer/lib/presentation/screens/player/player_screen.dartHigh-churn file with no governing decision
- Ownership5,596 sole-owned filesMediumplayer/lib/presentation/screens/player/player_screen.dartOne author, no second reader