Executive summary
puemos/hls-downloader falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 55 out of 100 and is rated Adequate, and nine of its 13 critical findings are security problems.
Accessibility, at 42, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 7 points. Automating accessibility checks comes next, worth about 3 points. Raising Accessibility to 70 would lift the score to about 64.
Four weaknesses in the code could be used by an attacker. Two automatic updates take new releases before a bad one can be spotted, and two passwords or keys are open to anyone who can read the repository. Fixing the weaknesses the scanner points to, setting a waiting period for automatic updates and replacing each exposed password or key would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The two form fields without a label need a label.
The product code is 23,817 lines, about €37,000 to rebuild.
If Accessibility rose from 42 to 70, the lowest score rated Strong, the score would rise from 55 to about 64.
New since the last survey: 83 findings
- Cyclomatic Complexity · BulkDownloadSheet.BulkDownloadSheet (cyclomatic 31) src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx
- Cyclomatic Complexity · SnifferView.SnifferView (cyclomatic 27) src/popup/src/modules/Sniffer/SnifferView.tsx
- Cyclomatic Complexity · SnifferView.PlaylistRow (cyclomatic 24) src/popup/src/modules/Sniffer/SnifferView.tsx
- Cognitive Complexity · BulkDownloadSheet.BulkDownloadSheet (cognitive 27) src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx
- Cognitive Complexity · get-subtitle-text.getSubtitleTextFactory.run (cognitive 19) src/core/src/use-cases/get-subtitle-text.ts
- Cognitive Complexity · SnifferView.PlaylistRow (cognitive 18) src/popup/src/modules/Sniffer/SnifferView.tsx
- Cognitive Complexity · fetch-loader.fetchWithRetry (cognitive 17) src/background/src/services/fetch-loader.ts
- Cognitive Complexity · SnifferView.SnifferView (cognitive 16) src/popup/src/modules/Sniffer/SnifferView.tsx
- God Classes · FunctionTooLong: BulkDownloadSheet.BulkDownloadSheet src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx
- God Classes · FunctionTooLong: SnifferView.PlaylistRow src/popup/src/modules/Sniffer/SnifferView.tsx
- Code Coverage · Low coverage: src/core/src/use-cases/generate-sequence-iv.ts src/core/src/use-cases/generate-sequence-iv.ts
- Code Coverage · Low coverage: src/core/src/use-cases/generate-track-id.ts src/core/src/use-cases/generate-track-id.ts
- Code Coverage · Low coverage: src/core/src/use-cases/get-subtitle-text.ts src/core/src/use-cases/get-subtitle-text.ts
- Code Coverage · Low coverage: src/core/src/use-cases/is-hls-response.ts src/core/src/use-cases/is-hls-response.ts
- Code Coverage · Low coverage: src/core/src/use-cases/store-subtitle-text.ts src/core/src/use-cases/store-subtitle-text.ts
- Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
- Churn × Complexity Hotspots · Hotspot: scripts/e2e-firefox-local.mjs scripts/e2e-firefox-local.mjs
- Churn × Complexity Hotspots · Hotspot: scripts/e2e-aes128-local.mjs scripts/e2e-aes128-local.mjs
- Churn × Complexity Hotspots · Hotspot: src/background/src/services/ffmpeg-muxer.ts src/background/src/services/ffmpeg-muxer.ts
- Churn × Complexity Hotspots · Repeated repair: src/background/src/services/fetch-loader.ts src/background/src/services/fetch-loader.ts
- Churn × Complexity Hotspots · Repeated repair: src/background/src/services/m3u8-parser.ts src/background/src/services/m3u8-parser.ts
- Churn × Complexity Hotspots · Repeated repair: src/background/src/services/disk-backed-fs.ts src/background/src/services/disk-backed-fs.ts
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
- Code Duplication · Duplicated block with local edits (187 matched lines × 2 locations) scripts/e2e-preparation-local.mjs
- Code Duplication · Duplicated block with local edits (127 matched lines × 2 locations) src/popup/src/modules/Downloads/DownloadsView.tsx
- Code Duplication · Duplicated block (41 lines × 3 locations) REDACTED
- Code Duplication · Duplicated block (37 lines × 2 locations) src/popup/src/modules/Playlist/PlaylistView.tsx
- Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) scripts/e2e-mkv-local.mjs
- Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) scripts/e2e-aes128-local.mjs
- Code Duplication · Duplicated block (25 lines × 3 locations) REDACTED
- Code Duplication · Duplicated block (22 lines × 4 locations) REDACTED
- Code Duplication · Duplicated block (19 lines × 2 locations) scripts/e2e-firefox-local.mjs
- Code Duplication · Duplicated block (19 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (18 lines × 3 locations) scripts/e2e-aes128-local.mjs
- Code Duplication · Duplicated block (15 lines × 2 locations) src/popup/src/modules/Playlist/PlaylistView.tsx
- Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (13 lines × 2 locations) scripts/e2e-aes128-local.mjs
- Code Duplication · Duplicated block (12 lines × 2 locations) scripts/e2e-aes128-local.mjs
- Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 53, cognitive 125) scripts/e2e-aes128-local.mjs
- Cyclomatic Complexity · Complex function serve (cyclomatic 47, cognitive 61) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 46, cognitive 141) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 41, cognitive 113) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 40, cognitive 124) scripts/e2e-preparation-local.mjs
- Cyclomatic Complexity · Complex function main (cyclomatic 39, cognitive 53) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 37, cognitive 101) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 34, cognitive 75) REDACTED
- Cyclomatic Complexity · Complex function main (cyclomatic 34, cognitive 53) scripts/e2e-mkv-local.mjs
- Cyclomatic Complexity · Complex function main (cyclomatic 30, cognitive 51) scripts/e2e-firefox-local.mjs
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 28) scripts/e2e-preparation-local.mjs
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 25) REDACTED
- Cyclomatic Complexity · Complex function SnifferView (cyclomatic 21, cognitive 16) src/popup/src/modules/Sniffer/SnifferView.tsx
- Large Files · src/background/src/services/disk-backed-fs.ts: 1302 lines of code src/background/src/services/disk-backed-fs.ts
- Large Files · src/popup/src/modules/Job/JobView.tsx: 739 lines of code src/popup/src/modules/Job/JobView.tsx
- Large Files · src/popup/src/modules/Sniffer/SnifferView.tsx: 438 lines of code src/popup/src/modules/Sniffer/SnifferView.tsx
- Test Coverage · No test reaches this file scripts/e2e-aes128-local.mjs
- Test Coverage · No test reaches this file REDACTED
- Test Coverage · No test reaches this file REDACTED
- Test Coverage · No test reaches this file scripts/e2e-preparation-local.mjs
- Test Coverage · No test reaches this file REDACTED
- Test Coverage · No test reaches this file REDACTED
- Test Coverage · No test reaches this file REDACTED
- Test Coverage · No test reaches this file scripts/e2e-mkv-local.mjs
- Test Coverage · No test reaches this file scripts/e2e-firefox-local.mjs
- Test Coverage · No test reaches this file scripts/e2e-job-faults.mjs
- Exception handling · Swallowed exception (empty catch) src/background/src/workers/disk-mux-worker.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/workers/disk-mux-worker.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/services/disk-backed-fs.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/services/disk-backed-fs.ts
- Forms & labels · <Input> field component without a label src/popup/src/modules/Direct/DirectView.tsx
Fixed since the last survey: 59 findings
- Code Coverage · Low coverage: src/core/src/controllers/fetch-level-duration-epic.ts src/core/src/controllers/fetch-level-duration-epic.ts
- Code Coverage · Low coverage: src/core/src/store/slices/playlist-preferences-slice.ts src/core/src/store/slices/playlist-preferences-slice.ts
- Code Coverage · Low coverage: src/popup/src/modules/Job/JobController.ts src/popup/src/modules/Job/JobController.ts
- Churn × Complexity Hotspots · Hotspot: src/popup/src/modules/Storage/StorageSummary.tsx src/popup/src/modules/Storage/StorageSummary.tsx
- Boundary Type-Coupling · Cross-context type OutputContainer (core → popup) src/popup/src/modules/Settings/SettingsController.ts
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] src/popup/package.json
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] src/background/package.json
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
- Code Duplication · Duplicated block with local edits (123 matched lines × 2 locations) src/popup/src/modules/Downloads/DownloadsView.tsx
- Code Duplication · Duplicated block (44 lines × 3 locations) src/popup/src/modules/Playlist/PlaylistView.tsx
- Code Duplication · Duplicated block (15 lines × 2 locations) src/background/src/services/m3u8-parser.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) src/core/src/store/slices/jobs-slice.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (11 lines × 3 locations) src/core/src/controllers/cancel-job-delete-job-epic.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) src/background/src/services/m3u8-parser.ts
- Code Duplication · Duplicated block (9 lines × 3 locations) src/core/src/controllers/add-download-job-epic.ts
- Code Duplication · Duplicated block (8 lines × 4 locations) src/design-system/src/components/ui/progress.tsx
- Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) src/background/src/services/disk-backed-fs.ts
- Code Duplication · Duplicated block (6 lines × 3 locations) src/core/src/controllers/download-job-epic.ts
- Import Boundaries · Boundary violation [package:relative-cross-package] src/background/src/blocklist.ts
- Cyclomatic Complexity · Complex function buildMuxArgs (cyclomatic 20, cognitive 23) src/background/src/services/ffmpeg-muxer.ts
- Cyclomatic Complexity · Complex function DownloadsView (cyclomatic 20, cognitive 17) src/popup/src/modules/Downloads/DownloadsView.tsx
- Cyclomatic Complexity · Complex function mux (cyclomatic 17, cognitive 25) src/background/src/workers/disk-mux-worker.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 13) src/core/src/use-cases/get-storage-stats.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 15) src/popup/src/modules/Playlist/PlaylistModule.tsx
- Cyclomatic Complexity · Complex function write (cyclomatic 13, cognitive 13) src/background/src/services/disk-backed-fs.ts
- Cyclomatic Complexity · Complex function Metadata (cyclomatic 13, cognitive 11) src/popup/src/components/Metadata.tsx
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 17) src/background/src/services/m3u8-parser.ts
- Cyclomatic Complexity · Complex function initializeDownloadTracking (cyclomatic 11, cognitive 16) src/background/src/services/disk-backed-fs.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 12) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 10) src/background/src/listeners/addPlaylistListener.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 10) src/popup/src/modules/Playlist/PlaylistModule.tsx
- Large Files · src/background/src/services/disk-backed-fs.ts: 1287 lines of code src/background/src/services/disk-backed-fs.ts
- Large Files · src/popup/src/modules/Job/JobView.tsx: 724 lines of code src/popup/src/modules/Job/JobView.tsx
- Test Coverage · No test reaches this file src/background/src/listeners/addPlaylistListener.ts
- Test Coverage · No test reaches this file src/core/src/store/configure-store.ts
- Cancellation propagation · Async function without AbortSignal: fetchText src/background/src/services/fetch-loader.ts
- Cancellation propagation · Async function without AbortSignal: fetchArrayBuffer src/background/src/services/fetch-loader.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/services/disk-backed-fs.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/services/disk-backed-fs.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/workers/disk-mux-worker.ts
- Exception handling · Swallowed exception (empty catch) src/background/src/workers/disk-mux-worker.ts
Rebuild cost: about €37,000 · Estimate
| Cost to rebuild | €12,000 to €61,000, for 204 to 647 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 23,817 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 background.src.offscreen | 2 background.src.services.disk-backed-fs | 3 background.src.services.disk-mux-protocol | 4 background.src.services.opfs-storage | 5 core.src.controllers.root-epic | 6 core.src.entities.inspection | 7 core.src.entities.key | 8 core.src.entities.level | 9 core.src.entities.output-container | 10 core.src.entities.playlist | 11 core.src.entities.tab | 12 core.src.services.decryptor | 13 core.src.services.fs | 14 core.src.services.loader | 15 core.src.services.parser | 16 core.src.store.slices.storage-slice | 17 popup.src.modules.About.AboutController | 18 popup.src.modules.About.AboutView | 19 background.src | 20 background.src.listeners | 21 background.src.services | 22 background.src.workers | 23 core.src.controllers | 24 core.src.entities.fragment | 25 core.src.entities.job | 26 core.src.store.slices.level-inspections-slice | 27 core.src.use-cases.select-bulk-downloads | 28 popup.src.components | 29 popup.src.modules.About | 30 popup.src.modules.Job | 31 popup.src.modules.Playlist | 32 popup.src.modules.Settings | 33 popup.src.modules.Settings.SettingsView | 34 popup.src.modules.Sniffer | 35 popup.src.modules.Storage.StorageBanner | 36 popup.src.modules.Storage.StorageSummary | 37 core.src.use-cases | 38 popup.src.modules.Downloads | 39 popup.src.modules.Playlist.PlaylistController | 40 popup.src.modules.Storage |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 background.src.offscreen | ||||||||||||||||||||||||||||||||||||||||
| 2 background.src.services.disk-backed-fs | ||||||||||||||||||||||||||||||||||||||||
| 3 background.src.services.disk-mux-protocol | ||||||||||||||||||||||||||||||||||||||||
| 4 background.src.services.opfs-storage | ||||||||||||||||||||||||||||||||||||||||
| 5 core.src.controllers.root-epic | ||||||||||||||||||||||||||||||||||||||||
| 6 core.src.entities.inspection | ||||||||||||||||||||||||||||||||||||||||
| 7 core.src.entities.key | ||||||||||||||||||||||||||||||||||||||||
| 8 core.src.entities.level | ||||||||||||||||||||||||||||||||||||||||
| 9 core.src.entities.output-container | ||||||||||||||||||||||||||||||||||||||||
| 10 core.src.entities.playlist | ||||||||||||||||||||||||||||||||||||||||
| 11 core.src.entities.tab | ||||||||||||||||||||||||||||||||||||||||
| 12 core.src.services.decryptor | ||||||||||||||||||||||||||||||||||||||||
| 13 core.src.services.fs | ||||||||||||||||||||||||||||||||||||||||
| 14 core.src.services.loader | ||||||||||||||||||||||||||||||||||||||||
| 15 core.src.services.parser | ||||||||||||||||||||||||||||||||||||||||
| 16 core.src.store.slices.storage-slice | ||||||||||||||||||||||||||||||||||||||||
| 17 popup.src.modules.About.AboutController | ||||||||||||||||||||||||||||||||||||||||
| 18 popup.src.modules.About.AboutView | ||||||||||||||||||||||||||||||||||||||||
| 19 background.src | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 background.src.listeners | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 background.src.services | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 background.src.workers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 core.src.controllers | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 core.src.entities.fragment | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 core.src.entities.job | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 core.src.store.slices.level-inspections-slice | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 core.src.use-cases.select-bulk-downloads | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 popup.src.components | 5 | |||||||||||||||||||||||||||||||||||||||
| 29 popup.src.modules.About | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 popup.src.modules.Job | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 popup.src.modules.Playlist | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 popup.src.modules.Settings | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 popup.src.modules.Settings.SettingsView | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 popup.src.modules.Sniffer | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 popup.src.modules.Storage.StorageBanner | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 popup.src.modules.Storage.StorageSummary | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 core.src.use-cases | 1 | 1 | 8 | 1 | 4 | 4 | 9 | 11 | 6 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 38 popup.src.modules.Downloads | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 popup.src.modules.Playlist.PlaylistController | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 popup.src.modules.Storage | 1 | 1 |
19→1 background.src uses background.src.offscreen✕
- Connections
- 1 pair of types, where a type in background.src uses a type in background.src.offscreen.
- The types involved
src.background.src.offscreen→src.background.src.offscreen.OffscreenResponse
- Direction
- background.src uses background.src.offscreen, so a change to background.src.offscreen can break background.src, while a change to background.src can't break background.src.offscreen.
- Position
- Below the diagonal: background.src uses a module listed above it, which is the healthy direction.
19→17 background.src uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in background.src uses a type in popup.src.modules.About.AboutController.
- The types involved
src.background.src.index→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- background.src uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break background.src, while a change to background.src can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: background.src uses a module listed above it, which is the healthy direction.
20→17 background.src.listeners uses popup.src.modules.About.AboutController✕
- Connections
- 2 pairs of types, where a type in background.src.listeners uses a type in popup.src.modules.About.AboutController.
- The types involved
src.background.src.listeners.addPlaylistListener→src.popup.src.modules.About.AboutController.ReturnTypesrc.background.src.listeners.setTabListener→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- background.src.listeners uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break background.src.listeners, while a change to background.src.listeners can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: background.src.listeners uses a module listed above it, which is the healthy direction.
21→2 background.src.services uses background.src.services.disk-backed-fs✕
- Connections
- 2 pairs of types, where a type in background.src.services uses a type in background.src.services.disk-backed-fs.
- The types involved
src.background.src.services.disk-backed-fs→src.background.src.services.disk-backed-fs.IndexedDBBucketsrc.background.src.services.disk-backed-fs→src.background.src.services.disk-backed-fs.SubtitlesDB
- Direction
- background.src.services uses background.src.services.disk-backed-fs, so a change to background.src.services.disk-backed-fs can break background.src.services, while a change to background.src.services can't break background.src.services.disk-backed-fs.
- Position
- Below the diagonal: background.src.services uses a module listed above it, which is the healthy direction.
21→4 background.src.services uses background.src.services.opfs-storage✕
- Connections
- 1 pair of types, where a type in background.src.services uses a type in background.src.services.opfs-storage.
- The types involved
src.background.src.services.opfs-storage→src.background.src.services.opfs-storage.MediaTrack
- Direction
- background.src.services uses background.src.services.opfs-storage, so a change to background.src.services.opfs-storage can break background.src.services, while a change to background.src.services can't break background.src.services.opfs-storage.
- Position
- Below the diagonal: background.src.services uses a module listed above it, which is the healthy direction.
22→3 background.src.workers uses background.src.services.disk-mux-protocol✕
- Connections
- 1 pair of types, where a type in background.src.workers uses a type in background.src.services.disk-mux-protocol.
- The types involved
src.background.src.workers.disk-mux-worker→src.background.src.services.disk-mux-protocol.DiskMuxResponse
- Direction
- background.src.workers uses background.src.services.disk-mux-protocol, so a change to background.src.services.disk-mux-protocol can break background.src.workers, while a change to background.src.workers can't break background.src.services.disk-mux-protocol.
- Position
- Below the diagonal: background.src.workers uses a module listed above it, which is the healthy direction.
22→4 background.src.workers uses background.src.services.opfs-storage✕
- Connections
- 1 pair of types, where a type in background.src.workers uses a type in background.src.services.opfs-storage.
- The types involved
src.background.src.workers.disk-mux-worker→src.background.src.services.opfs-storage.MediaTrack
- Direction
- background.src.workers uses background.src.services.opfs-storage, so a change to background.src.services.opfs-storage can break background.src.workers, while a change to background.src.workers can't break background.src.services.opfs-storage.
- Position
- Below the diagonal: background.src.workers uses a module listed above it, which is the healthy direction.
23→5 core.src.controllers uses core.src.controllers.root-epic✕
- Connections
- 1 pair of types, where a type in core.src.controllers uses a type in core.src.controllers.root-epic.
- The types involved
src.core.src.controllers.root-epic→src.core.src.controllers.root-epic.RootEpic
- Direction
- core.src.controllers uses core.src.controllers.root-epic, so a change to core.src.controllers.root-epic can break core.src.controllers, while a change to core.src.controllers can't break core.src.controllers.root-epic.
- Position
- Below the diagonal: core.src.controllers uses a module listed above it, which is the healthy direction.
24→7 core.src.entities.fragment uses core.src.entities.key✕
- Connections
- 1 pair of types, where a type in core.src.entities.fragment uses a type in core.src.entities.key.
- The types involved
src.core.src.entities.fragment.Fragment→src.core.src.entities.key.Key
- Direction
- core.src.entities.fragment uses core.src.entities.key, so a change to core.src.entities.key can break core.src.entities.fragment, while a change to core.src.entities.fragment can't break core.src.entities.key.
- Position
- Below the diagonal: core.src.entities.fragment uses a module listed above it, which is the healthy direction.
25→8 core.src.entities.job uses core.src.entities.level✕
- Connections
- 1 pair of types, where a type in core.src.entities.job uses a type in core.src.entities.level.
- The types involved
src.core.src.entities.job.JobSource→src.core.src.entities.level.Level
- Direction
- core.src.entities.job uses core.src.entities.level, so a change to core.src.entities.level can break core.src.entities.job, while a change to core.src.entities.job can't break core.src.entities.level.
- Position
- Below the diagonal: core.src.entities.job uses a module listed above it, which is the healthy direction.
25→9 core.src.entities.job uses core.src.entities.output-container✕
- Connections
- 1 pair of types, where a type in core.src.entities.job uses a type in core.src.entities.output-container.
- The types involved
src.core.src.entities.job.Job→src.core.src.entities.output-container.OutputContainer
- Direction
- core.src.entities.job uses core.src.entities.output-container, so a change to core.src.entities.output-container can break core.src.entities.job, while a change to core.src.entities.job can't break core.src.entities.output-container.
- Position
- Below the diagonal: core.src.entities.job uses a module listed above it, which is the healthy direction.
25→10 core.src.entities.job uses core.src.entities.playlist✕
- Connections
- 1 pair of types, where a type in core.src.entities.job uses a type in core.src.entities.playlist.
- The types involved
src.core.src.entities.job.JobSource→src.core.src.entities.playlist.Playlist
- Direction
- core.src.entities.job uses core.src.entities.playlist, so a change to core.src.entities.playlist can break core.src.entities.job, while a change to core.src.entities.job can't break core.src.entities.playlist.
- Position
- Below the diagonal: core.src.entities.job uses a module listed above it, which is the healthy direction.
26→6 core.src.store.slices.level-inspections-slice uses core.src.entities.inspection✕
- Connections
- 1 pair of types, where a type in core.src.store.slices.level-inspections-slice uses a type in core.src.entities.inspection.
- The types involved
src.core.src.store.slices.level-inspections-slice.IInspectLevelSuccessPayload→src.core.src.entities.inspection.LevelInspection
- Direction
- core.src.store.slices.level-inspections-slice uses core.src.entities.inspection, so a change to core.src.entities.inspection can break core.src.store.slices.level-inspections-slice, while a change to core.src.store.slices.level-inspections-slice can't break core.src.entities.inspection.
- Position
- Below the diagonal: core.src.store.slices.level-inspections-slice uses a module listed above it, which is the healthy direction.
27→8 core.src.use-cases.select-bulk-downloads uses core.src.entities.level✕
- Connections
- 1 pair of types, where a type in core.src.use-cases.select-bulk-downloads uses a type in core.src.entities.level.
- The types involved
src.core.src.use-cases.select-bulk-downloads.BulkDownloadSelection→src.core.src.entities.level.Level
- Direction
- core.src.use-cases.select-bulk-downloads uses core.src.entities.level, so a change to core.src.entities.level can break core.src.use-cases.select-bulk-downloads, while a change to core.src.use-cases.select-bulk-downloads can't break core.src.entities.level.
- Position
- Below the diagonal: core.src.use-cases.select-bulk-downloads uses a module listed above it, which is the healthy direction.
27→10 core.src.use-cases.select-bulk-downloads uses core.src.entities.playlist✕
- Connections
- 1 pair of types, where a type in core.src.use-cases.select-bulk-downloads uses a type in core.src.entities.playlist.
- The types involved
src.core.src.use-cases.select-bulk-downloads.BulkDownloadSelection→src.core.src.entities.playlist.Playlist
- Direction
- core.src.use-cases.select-bulk-downloads uses core.src.entities.playlist, so a change to core.src.entities.playlist can break core.src.use-cases.select-bulk-downloads, while a change to core.src.use-cases.select-bulk-downloads can't break core.src.entities.playlist.
- Position
- Below the diagonal: core.src.use-cases.select-bulk-downloads uses a module listed above it, which is the healthy direction.
28→18 popup.src.components uses popup.src.modules.About.AboutView✕
- Connections
- 5 pairs of types, where a type in popup.src.components uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.components.BackButton→src.popup.src.modules.About.AboutView.Propssrc.popup.src.components.BottomSheet→src.popup.src.modules.About.AboutView.Propssrc.popup.src.components.DetailScreen→src.popup.src.modules.About.AboutView.Propssrc.popup.src.components.Metadata→src.popup.src.modules.About.AboutView.Propssrc.popup.src.components.ScreenHeader→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.components uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.components, while a change to popup.src.components can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.components uses a module listed above it, which is the healthy direction.
29→17 popup.src.modules.About uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in popup.src.modules.About uses a type in popup.src.modules.About.AboutController.
- The types involved
src.popup.src.modules.About.AboutController→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- popup.src.modules.About uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break popup.src.modules.About, while a change to popup.src.modules.About can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: popup.src.modules.About uses a module listed above it, which is the healthy direction.
29→18 popup.src.modules.About uses popup.src.modules.About.AboutView✕
- Connections
- 1 pair of types, where a type in popup.src.modules.About uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.modules.About.AboutView→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.modules.About uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.modules.About, while a change to popup.src.modules.About can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.modules.About uses a module listed above it, which is the healthy direction.
30→17 popup.src.modules.Job uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Job uses a type in popup.src.modules.About.AboutController.
- The types involved
src.popup.src.modules.Job.JobController→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- popup.src.modules.Job uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break popup.src.modules.Job, while a change to popup.src.modules.Job can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: popup.src.modules.Job uses a module listed above it, which is the healthy direction.
30→18 popup.src.modules.Job uses popup.src.modules.About.AboutView✕
- Connections
- 2 pairs of types, where a type in popup.src.modules.Job uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.modules.Job.JobFilename→src.popup.src.modules.About.AboutView.Propssrc.popup.src.modules.Job.JobView→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.modules.Job uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.modules.Job, while a change to popup.src.modules.Job can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.modules.Job uses a module listed above it, which is the healthy direction.
31→17 popup.src.modules.Playlist uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Playlist uses a type in popup.src.modules.About.AboutController.
- The types involved
src.popup.src.modules.Playlist.PlaylistController→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- popup.src.modules.Playlist uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break popup.src.modules.Playlist, while a change to popup.src.modules.Playlist can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: popup.src.modules.Playlist uses a module listed above it, which is the healthy direction.
31→18 popup.src.modules.Playlist uses popup.src.modules.About.AboutView✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Playlist uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.modules.Playlist.PlaylistView→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.modules.Playlist uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.modules.Playlist, while a change to popup.src.modules.Playlist can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.modules.Playlist uses a module listed above it, which is the healthy direction.
32→9 popup.src.modules.Settings uses core.src.entities.output-container✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Settings uses a type in core.src.entities.output-container.
- The types involved
src.popup.src.modules.Settings.SettingsController→src.core.src.entities.output-container.OutputContainer
- Direction
- popup.src.modules.Settings uses core.src.entities.output-container, so a change to core.src.entities.output-container can break popup.src.modules.Settings, while a change to popup.src.modules.Settings can't break core.src.entities.output-container.
- Position
- Below the diagonal: popup.src.modules.Settings uses a module listed above it, which is the healthy direction.
32→17 popup.src.modules.Settings uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Settings uses a type in popup.src.modules.About.AboutController.
- The types involved
src.popup.src.modules.Settings.SettingsController→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- popup.src.modules.Settings uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break popup.src.modules.Settings, while a change to popup.src.modules.Settings can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: popup.src.modules.Settings uses a module listed above it, which is the healthy direction.
32→18 popup.src.modules.Settings uses popup.src.modules.About.AboutView✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Settings uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.modules.Settings.SettingsView→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.modules.Settings uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.modules.Settings, while a change to popup.src.modules.Settings can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.modules.Settings uses a module listed above it, which is the healthy direction.
33→9 popup.src.modules.Settings.SettingsView uses core.src.entities.output-container✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Settings.SettingsView uses a type in core.src.entities.output-container.
- The types involved
src.popup.src.modules.Settings.SettingsView.Props→src.core.src.entities.output-container.OutputContainer
- Direction
- popup.src.modules.Settings.SettingsView uses core.src.entities.output-container, so a change to core.src.entities.output-container can break popup.src.modules.Settings.SettingsView, while a change to popup.src.modules.Settings.SettingsView can't break core.src.entities.output-container.
- Position
- Below the diagonal: popup.src.modules.Settings.SettingsView uses a module listed above it, which is the healthy direction.
33→16 popup.src.modules.Settings.SettingsView uses core.src.store.slices.storage-slice✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Settings.SettingsView uses a type in core.src.store.slices.storage-slice.
- The types involved
src.popup.src.modules.Settings.SettingsView.Props→src.core.src.store.slices.storage-slice.StorageState
- Direction
- popup.src.modules.Settings.SettingsView uses core.src.store.slices.storage-slice, so a change to core.src.store.slices.storage-slice can break popup.src.modules.Settings.SettingsView, while a change to popup.src.modules.Settings.SettingsView can't break core.src.store.slices.storage-slice.
- Position
- Below the diagonal: popup.src.modules.Settings.SettingsView uses a module listed above it, which is the healthy direction.
34→10 popup.src.modules.Sniffer uses core.src.entities.playlist✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Sniffer uses a type in core.src.entities.playlist.
- The types involved
src.popup.src.modules.Sniffer.SnifferController→src.core.src.entities.playlist.Playlist
- Direction
- popup.src.modules.Sniffer uses core.src.entities.playlist, so a change to core.src.entities.playlist can break popup.src.modules.Sniffer, while a change to popup.src.modules.Sniffer can't break core.src.entities.playlist.
- Position
- Below the diagonal: popup.src.modules.Sniffer uses a module listed above it, which is the healthy direction.
34→17 popup.src.modules.Sniffer uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Sniffer uses a type in popup.src.modules.About.AboutController.
- The types involved
src.popup.src.modules.Sniffer.SnifferController→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- popup.src.modules.Sniffer uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break popup.src.modules.Sniffer, while a change to popup.src.modules.Sniffer can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: popup.src.modules.Sniffer uses a module listed above it, which is the healthy direction.
34→18 popup.src.modules.Sniffer uses popup.src.modules.About.AboutView✕
- Connections
- 2 pairs of types, where a type in popup.src.modules.Sniffer uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.modules.Sniffer.PlaylistPreview→src.popup.src.modules.About.AboutView.Propssrc.popup.src.modules.Sniffer.SnifferView→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.modules.Sniffer uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.modules.Sniffer, while a change to popup.src.modules.Sniffer can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.modules.Sniffer uses a module listed above it, which is the healthy direction.
35→16 popup.src.modules.Storage.StorageBanner uses core.src.store.slices.storage-slice✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Storage.StorageBanner uses a type in core.src.store.slices.storage-slice.
- The types involved
src.popup.src.modules.Storage.StorageBanner.StorageBannerProps→src.core.src.store.slices.storage-slice.CleanupStatus
- Direction
- popup.src.modules.Storage.StorageBanner uses core.src.store.slices.storage-slice, so a change to core.src.store.slices.storage-slice can break popup.src.modules.Storage.StorageBanner, while a change to popup.src.modules.Storage.StorageBanner can't break core.src.store.slices.storage-slice.
- Position
- Below the diagonal: popup.src.modules.Storage.StorageBanner uses a module listed above it, which is the healthy direction.
36→16 popup.src.modules.Storage.StorageSummary uses core.src.store.slices.storage-slice✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Storage.StorageSummary uses a type in core.src.store.slices.storage-slice.
- The types involved
src.popup.src.modules.Storage.StorageSummary.StorageSummaryProps→src.core.src.store.slices.storage-slice.CleanupStatus
- Direction
- popup.src.modules.Storage.StorageSummary uses core.src.store.slices.storage-slice, so a change to core.src.store.slices.storage-slice can break popup.src.modules.Storage.StorageSummary, while a change to popup.src.modules.Storage.StorageSummary can't break core.src.store.slices.storage-slice.
- Position
- Below the diagonal: popup.src.modules.Storage.StorageSummary uses a module listed above it, which is the healthy direction.
37→6 core.src.use-cases uses core.src.entities.inspection✕
- Connections
- 1 pair of types, where a type in core.src.use-cases uses a type in core.src.entities.inspection.
- The types involved
src.core.src.use-cases.inspect-level-encryption→src.core.src.entities.inspection.LevelInspection
- Direction
- core.src.use-cases uses core.src.entities.inspection, so a change to core.src.entities.inspection can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.inspection.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→7 core.src.use-cases uses core.src.entities.key✕
- Connections
- 1 pair of types, where a type in core.src.use-cases uses a type in core.src.entities.key.
- The types involved
src.core.src.use-cases.decrypt-single-fragment→src.core.src.entities.key.Key
- Direction
- core.src.use-cases uses core.src.entities.key, so a change to core.src.entities.key can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.key.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→8 core.src.use-cases uses core.src.entities.level✕
- Connections
- 8 pairs of types, where a type in core.src.use-cases uses a type in core.src.entities.level.
- The types involved
src.core.src.use-cases.download-subtitle-track→src.core.src.entities.level.Levelsrc.core.src.use-cases.generate-file-name→src.core.src.entities.level.Levelsrc.core.src.use-cases.generate-subtitle-file-name→src.core.src.entities.level.Levelsrc.core.src.use-cases.get-fragments-details→src.core.src.entities.level.Levelsrc.core.src.use-cases.get-playlist-document→src.core.src.entities.level.Levelsrc.core.src.use-cases.get-subtitle-text→src.core.src.entities.level.Levelsrc.core.src.use-cases.inspect-level-encryption→src.core.src.entities.level.Levelsrc.core.src.use-cases.store-subtitle-text→src.core.src.entities.level.Level
- Direction
- core.src.use-cases uses core.src.entities.level, so a change to core.src.entities.level can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.level.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→9 core.src.use-cases uses core.src.entities.output-container✕
- Connections
- 1 pair of types, where a type in core.src.use-cases uses a type in core.src.entities.output-container.
- The types involved
src.core.src.use-cases.rename-job-filename→src.core.src.entities.output-container.OutputContainer
- Direction
- core.src.use-cases uses core.src.entities.output-container, so a change to core.src.entities.output-container can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.output-container.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→10 core.src.use-cases uses core.src.entities.playlist✕
- Connections
- 4 pairs of types, where a type in core.src.use-cases uses a type in core.src.entities.playlist.
- The types involved
src.core.src.use-cases.download-subtitle-track→src.core.src.entities.playlist.Playlistsrc.core.src.use-cases.generate-file-name→src.core.src.entities.playlist.Playlistsrc.core.src.use-cases.generate-subtitle-file-name→src.core.src.entities.playlist.Playlistsrc.core.src.use-cases.store-subtitle-text→src.core.src.entities.playlist.Playlist
- Direction
- core.src.use-cases uses core.src.entities.playlist, so a change to core.src.entities.playlist can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.playlist.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→12 core.src.use-cases uses core.src.services.decryptor✕
- Connections
- 4 pairs of types, where a type in core.src.use-cases uses a type in core.src.services.decryptor.
- The types involved
src.core.src.use-cases.decrypt-single-fragment→src.core.src.services.decryptor.IDecryptorsrc.core.src.use-cases.download-subtitle-track→src.core.src.services.decryptor.IDecryptorsrc.core.src.use-cases.get-subtitle-text→src.core.src.services.decryptor.IDecryptorsrc.core.src.use-cases.prepare-job→src.core.src.services.decryptor.IDecryptor
- Direction
- core.src.use-cases uses core.src.services.decryptor, so a change to core.src.services.decryptor can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.services.decryptor.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→13 core.src.use-cases uses core.src.services.fs✕
- Connections
- 9 pairs of types, where a type in core.src.use-cases uses a type in core.src.services.fs.
- The types involved
src.core.src.use-cases.create-bucket→src.core.src.services.fs.IFSsrc.core.src.use-cases.delete-bucket→src.core.src.services.fs.IFSsrc.core.src.use-cases.download-subtitle-track→src.core.src.services.fs.IFSsrc.core.src.use-cases.fs-cleanup→src.core.src.services.fs.IFSsrc.core.src.use-cases.get-storage-stats→src.core.src.services.fs.IFSsrc.core.src.use-cases.prepare-download-bucket→src.core.src.services.fs.IFSsrc.core.src.use-cases.store-subtitle-text→src.core.src.services.fs.IFSsrc.core.src.use-cases.write-to-bucket→src.core.src.services.fs.IFSsrc.core.src.use-cases.write-to-file→src.core.src.services.fs.IFS
- Direction
- core.src.use-cases uses core.src.services.fs, so a change to core.src.services.fs can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.services.fs.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→14 core.src.use-cases uses core.src.services.loader✕
- Connections
- 11 pairs of types, where a type in core.src.use-cases uses a type in core.src.services.loader.
- The types involved
src.core.src.use-cases.decrypt-single-fragment→src.core.src.services.loader.ILoadersrc.core.src.use-cases.download-single-fragment→src.core.src.services.loader.ILoadersrc.core.src.use-cases.download-subtitle-track→src.core.src.services.loader.ILoadersrc.core.src.use-cases.get-fragments-details→src.core.src.services.loader.ILoadersrc.core.src.use-cases.get-levels→src.core.src.services.loader.ILoadersrc.core.src.use-cases.get-playlist-document→src.core.src.services.loader.ILoadersrc.core.src.use-cases.get-playlist-document→src.core.src.services.loader.LoadedTextsrc.core.src.use-cases.get-playlist-duration→src.core.src.services.loader.ILoadersrc.core.src.use-cases.get-subtitle-text→src.core.src.services.loader.ILoadersrc.core.src.use-cases.inspect-level-encryption→src.core.src.services.loader.ILoadersrc.core.src.use-cases.prepare-job→src.core.src.services.loader.ILoader
- Direction
- core.src.use-cases uses core.src.services.loader, so a change to core.src.services.loader can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.services.loader.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→15 core.src.use-cases uses core.src.services.parser✕
- Connections
- 6 pairs of types, where a type in core.src.use-cases uses a type in core.src.services.parser.
- The types involved
src.core.src.use-cases.download-subtitle-track→src.core.src.services.parser.IParsersrc.core.src.use-cases.get-fragments-details→src.core.src.services.parser.IParsersrc.core.src.use-cases.get-levels→src.core.src.services.parser.IParsersrc.core.src.use-cases.get-subtitle-text→src.core.src.services.parser.IParsersrc.core.src.use-cases.inspect-level-encryption→src.core.src.services.parser.IParsersrc.core.src.use-cases.prepare-job→src.core.src.services.parser.IParser
- Direction
- core.src.use-cases uses core.src.services.parser, so a change to core.src.services.parser can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.services.parser.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→24 core.src.use-cases uses core.src.entities.fragment✕
- Connections
- 1 pair of types, where a type in core.src.use-cases uses a type in core.src.entities.fragment.
- The types involved
src.core.src.use-cases.download-single-fragment→src.core.src.entities.fragment.Fragment
- Direction
- core.src.use-cases uses core.src.entities.fragment, so a change to core.src.entities.fragment can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.fragment.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→25 core.src.use-cases uses core.src.entities.job✕
- Connections
- 1 pair of types, where a type in core.src.use-cases uses a type in core.src.entities.job.
- The types involved
src.core.src.use-cases.prepare-job→src.core.src.entities.job.Job
- Direction
- core.src.use-cases uses core.src.entities.job, so a change to core.src.entities.job can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.entities.job.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
37→27 core.src.use-cases uses core.src.use-cases.select-bulk-downloads✕
- Connections
- 1 pair of types, where a type in core.src.use-cases uses a type in core.src.use-cases.select-bulk-downloads.
- The types involved
src.core.src.use-cases.select-bulk-downloads→src.core.src.use-cases.select-bulk-downloads.Options
- Direction
- core.src.use-cases uses core.src.use-cases.select-bulk-downloads, so a change to core.src.use-cases.select-bulk-downloads can break core.src.use-cases, while a change to core.src.use-cases can't break core.src.use-cases.select-bulk-downloads.
- Position
- Below the diagonal: core.src.use-cases uses a module listed above it, which is the healthy direction.
38→17 popup.src.modules.Downloads uses popup.src.modules.About.AboutController✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Downloads uses a type in popup.src.modules.About.AboutController.
- The types involved
src.popup.src.modules.Downloads.DownloadsController→src.popup.src.modules.About.AboutController.ReturnType
- Direction
- popup.src.modules.Downloads uses popup.src.modules.About.AboutController, so a change to popup.src.modules.About.AboutController can break popup.src.modules.Downloads, while a change to popup.src.modules.Downloads can't break popup.src.modules.About.AboutController.
- Position
- Below the diagonal: popup.src.modules.Downloads uses a module listed above it, which is the healthy direction.
38→18 popup.src.modules.Downloads uses popup.src.modules.About.AboutView✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Downloads uses a type in popup.src.modules.About.AboutView.
- The types involved
src.popup.src.modules.Downloads.DownloadsView→src.popup.src.modules.About.AboutView.Props
- Direction
- popup.src.modules.Downloads uses popup.src.modules.About.AboutView, so a change to popup.src.modules.About.AboutView can break popup.src.modules.Downloads, while a change to popup.src.modules.Downloads can't break popup.src.modules.About.AboutView.
- Position
- Below the diagonal: popup.src.modules.Downloads uses a module listed above it, which is the healthy direction.
38→25 popup.src.modules.Downloads uses core.src.entities.job✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Downloads uses a type in core.src.entities.job.
- The types involved
src.popup.src.modules.Downloads.DownloadsController→src.core.src.entities.job.Job
- Direction
- popup.src.modules.Downloads uses core.src.entities.job, so a change to core.src.entities.job can break popup.src.modules.Downloads, while a change to popup.src.modules.Downloads can't break core.src.entities.job.
- Position
- Below the diagonal: popup.src.modules.Downloads uses a module listed above it, which is the healthy direction.
39→26 popup.src.modules.Playlist.PlaylistController uses core.src.store.slices.level-inspections-slice✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Playlist.PlaylistController uses a type in core.src.store.slices.level-inspections-slice.
- The types involved
src.popup.src.modules.Playlist.PlaylistController.ReturnType→src.core.src.store.slices.level-inspections-slice.ILevelInspectionsState
- Direction
- popup.src.modules.Playlist.PlaylistController uses core.src.store.slices.level-inspections-slice, so a change to core.src.store.slices.level-inspections-slice can break popup.src.modules.Playlist.PlaylistController, while a change to popup.src.modules.Playlist.PlaylistController can't break core.src.store.slices.level-inspections-slice.
- Position
- Below the diagonal: popup.src.modules.Playlist.PlaylistController uses a module listed above it, which is the healthy direction.
40→35 popup.src.modules.Storage uses popup.src.modules.Storage.StorageBanner✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Storage uses a type in popup.src.modules.Storage.StorageBanner.
- The types involved
src.popup.src.modules.Storage.StorageBanner→src.popup.src.modules.Storage.StorageBanner.StorageBannerProps
- Direction
- popup.src.modules.Storage uses popup.src.modules.Storage.StorageBanner, so a change to popup.src.modules.Storage.StorageBanner can break popup.src.modules.Storage, while a change to popup.src.modules.Storage can't break popup.src.modules.Storage.StorageBanner.
- Position
- Below the diagonal: popup.src.modules.Storage uses a module listed above it, which is the healthy direction.
40→36 popup.src.modules.Storage uses popup.src.modules.Storage.StorageSummary✕
- Connections
- 1 pair of types, where a type in popup.src.modules.Storage uses a type in popup.src.modules.Storage.StorageSummary.
- The types involved
src.popup.src.modules.Storage.StorageSummary→src.popup.src.modules.Storage.StorageSummary.StorageSummaryProps
- Direction
- popup.src.modules.Storage uses popup.src.modules.Storage.StorageSummary, so a change to popup.src.modules.Storage.StorageSummary can break popup.src.modules.Storage, while a change to popup.src.modules.Storage can't break popup.src.modules.Storage.StorageSummary.
- Position
- Below the diagonal: popup.src.modules.Storage uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +6.7 pts | Medium | Keyboard semantics |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +3.1 pts | Medium | A11y enforcement |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.3 pts | Medium | Visual & motion safety |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.1 pts | Medium | Forms & labels |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.9 pts | Medium | Page structure |
| Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). | +0.8 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/popup/src/modules/Job/JobView.tsx | 5.5 | Mixed | Cyclomatic Complexity: JobView.JobView (cyclomatic 43) |
| src/popup/src/modules/Playlist/PlaylistView.tsx | 5.9 | Mixed | Cyclomatic Complexity: PlaylistView.PlaylistView (cyclomatic 47) |
| src/popup/src/modules/Sniffer/PlaylistPreview.tsx | 5.9 | Mixed | Cyclomatic Complexity: PlaylistPreview.PlaylistPreview (cyclomatic 23) |
| REDACTED | 6.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/core/src/use-cases/get-subtitle-text.ts | 7.0 | Mixed | Cognitive Complexity: get-subtitle-text.getSubtitleTextFactory.run (cognitive 19) |
| src/popup/src/modules/Sniffer/SnifferView.tsx | 7.1 | Mixed | Cyclomatic Complexity: SnifferView.SnifferView (cyclomatic 27) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/popup/src/modules/Playlist/PlaylistModule.tsx | 7.4 | Mixed | Cyclomatic Complexity: PlaylistModule.PlaylistModule (cyclomatic 58) |
| src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx | 7.4 | Mixed | Cyclomatic Complexity: BulkDownloadSheet.BulkDownloadSheet (cyclomatic 31) |
| src/popup/src/modules/Storage/StorageSummary.tsx | 7.4 | Mixed | Cyclomatic Complexity: StorageSummary.StorageSummary (cyclomatic 26) |
| src/popup/src/modules/Downloads/DownloadsView.tsx | 7.4 | Mixed | Cyclomatic Complexity: DownloadsView.DownloadsView (cyclomatic 23) |
| src/popup/src/modules/Job/JobController.ts | 7.8 | Mixed | Cyclomatic Complexity: JobController.buildJobViewDerived (cyclomatic 18) |
| src/background/src/services/ffmpeg-muxer.ts | 7.8 | Mixed | Cyclomatic Complexity: ffmpeg-muxer.buildMuxArgs (cyclomatic 16) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 80 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 206 of 224 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (10 contributor(s) across 394 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 9 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (src/design-system/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/popup/src/modules/Job/JobView.tsx` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> predev / > pnpm run clean && pnpm run copy-assets / sh: 1: pnpm: not found" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> predev / > pnpm run clean && pnpm run copy-assets / sh: 1: pnpm: not found" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 161 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PlaylistModule.PlaylistModule at 58.
What to do
- Bring the 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PlaylistModule.PlaylistModule (cyclomatic 58), PlaylistView.PlaylistView (cyclomatic 47), JobView.JobView (cyclomatic 43). — 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 12 together lifts Cyclomatic Complexity from 7.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was JobView.JobView at 58.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with JobView.JobView (cognitive 58), PlaylistView.PlaylistView (cognitive 58), PlaylistModule.PlaylistModule (cognitive 55). — 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 Cognitive Complexity from 6.4 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.
D3 · God Classes
13 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 11 FunctionTooLong finding(s) in God Classes — start with JobView.tsx (2), SnifferView.tsx (2), PlaylistView.tsx. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with disk-backed-fs.ts, JobView.tsx. — One of this dimension's main actionable groups (2 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.
D5 · Coupling
4 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 74.8% — 18 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in src/background/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in src/core/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in src/design-system/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in src/popup/).
What to do
- Resolve the 18 Low coverage finding(s) in Code Coverage — start with download-subtitle-epic.ts, inspect-level-epic.ts, tab.ts. — One of this dimension's main actionable groups (18 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
380 test methods: 365 unit, 0 integration, 0 BDD, 15 e2e. The JavaScript/TypeScript suite contributes 380 `it`/`test` case(s) across 60 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 380 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in src/background/ (239 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in src/core/ (166 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in src/design-system/ (2 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in src/popup/ (25 tests)): measured (0 flaky).
D12 · Dependency Hygiene
4 outdated direct production npm dependency(ies) of 29 graded, 0 pinning defect(s), across 5 package.json (5 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry 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, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 83 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 83 package(s) this repository's committed lockfile installs for a consumer — its 29 production, optional and peer dependency(ies), across 5 product package.json manifest(s), and everything those install in turn. Its 58 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: REDACTED (7×50=350); scripts/e2e-firefox-local.mjs (5×44=220); scripts/e2e-aes128-local.mjs (3×55=165) Repeated repair below the complexity floor: src/background/src/services/fetch-loader.ts (3 of 3 changes were fixes); src/background/src/services/m3u8-parser.ts (3 of 3 changes were fixes); src/background/src/services/disk-backed-fs.ts (3 of 3 changes were fixes)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, e2e-firefox-local.mjs, e2e-aes128-local.mjs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with fetch-loader.ts, m3u8-parser.ts, disk-backed-fs.ts. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 11908 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 5 document(s) read across 5 unit(s).
D23 · Boundary Type-Coupling
1 domain type(s) cross context boundaries across 4 contexts; they are measured and withheld (not published, not scored). Contexts: background, core, design-system, popup.
D24 · Comment Value
3 of 159 judged comments only repeat the code they sit on (1.9 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with build-variant.mjs, root-epic.test.ts, use-localstorage.ts. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
0 of 5 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
17 % of calls cross a namespace and 3 % go through an interface, but 81 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 6 high, 7 medium, 3 low. semgrep hit a parse error in 2 file(s) — `src/assets/assets/ffmpeg/ffmpeg-core.js`, `src/popup/src/modules/Job/JobView.tsx` (lines 44–45, line 46, line 47, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 0 medium, 1 low.
D31 · IaC & Container Security
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 43 of the 188 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — src/popup/src/modules/Direct/DirectView.tsx:52
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — src/popup/src/modules/Settings/SettingsView.tsx:185, src/popup/src/modules/Settings/SettingsView.tsx:306
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — src/popup/popup.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — src/popup/popup.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <section role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/popup/src/components/BottomSheet.tsx:66
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/popup/src/index.css:92
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 45 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:62
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
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.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 1 of 4 project(s) that lack one — worth up to 0.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 4007 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene
- `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:621
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- scripts/e2e-preparation-local.mjs:95 · REDACTED:82 — the two spans are one implementation copied and then locally edited — 1167 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/e2e-preparation-local.mjs:95
- src/popup/src/modules/Downloads/DownloadsView.tsx:49 · src/popup/src/modules/Sniffer/SnifferView.tsx:57 — the two spans are one implementation copied and then locally edited — 583 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/popup/src/modules/Downloads/DownloadsView.tsx:49
- REDACTED:338 · scripts/e2e-preparation-local.mjs:319 · REDACTED:314 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:338
- src/popup/src/modules/Playlist/PlaylistView.tsx:255 · src/popup/src/modules/Playlist/PlaylistView.tsx:302 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/popup/src/modules/Playlist/PlaylistView.tsx:255
- scripts/e2e-mkv-local.mjs:18 · REDACTED:17 — the two spans are one implementation copied and then locally edited — 251 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/e2e-mkv-local.mjs:18
- src/popup/src/modules/Settings/SettingsView.tsx:200 · src/popup/src/modules/Settings/SettingsView.tsx:234 — 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. — src/popup/src/modules/Settings/SettingsView.tsx:200
- scripts/e2e-aes128-local.mjs:284 · REDACTED:123 — the two spans are one implementation copied and then locally edited — 174 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/e2e-aes128-local.mjs:284
- REDACTED:29 · scripts/e2e-preparation-local.mjs:97 · REDACTED:84 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — REDACTED:29
- REDACTED:388 · REDACTED:317 · scripts/e2e-preparation-local.mjs:381 · REDACTED:368 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:388
- src/popup/src/modules/Job/JobView.tsx:604 · src/popup/src/modules/Job/JobView.tsx:625 · src/popup/src/modules/Job/JobView.tsx:646 · src/popup/src/modules/Job/JobView.tsx:668 — 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. — src/popup/src/modules/Job/JobView.tsx:604
- scripts/e2e-firefox-local.mjs:289 · REDACTED:1028 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — scripts/e2e-firefox-local.mjs:289
- REDACTED:514 · scripts/e2e-preparation-local.mjs:493 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:514
- scripts/e2e-aes128-local.mjs:619 · scripts/e2e-mkv-local.mjs:73 · REDACTED:38 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — scripts/e2e-aes128-local.mjs:619
- src/popup/src/modules/Settings/SettingsController.ts:53 · src/popup/src/modules/Settings/SettingsController.ts:90 — 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. — src/popup/src/modules/Settings/SettingsController.ts:53
- src/design-system/src/components/ui/select.tsx:33 · src/design-system/src/components/ui/select.tsx:50 — 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. — src/design-system/src/components/ui/select.tsx:33
- src/popup/src/modules/Navbar/RouterView.tsx:53 · src/popup/src/modules/Navbar/RouterView.tsx:71 — 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. — src/popup/src/modules/Navbar/RouterView.tsx:53
- src/popup/src/modules/Playlist/PlaylistView.tsx:312 · src/popup/src/modules/Playlist/PlaylistView.tsx:361 — 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. — src/popup/src/modules/Playlist/PlaylistView.tsx:312
- REDACTED:297 · scripts/e2e-preparation-local.mjs:421 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:297
- REDACTED:833 · REDACTED:922 — 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. — REDACTED:833
- scripts/e2e-aes128-local.mjs:798 · scripts/e2e-mkv-local.mjs:417 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/e2e-aes128-local.mjs:798
- src/background/src/services/disk-backed-fs.ts:1324 · src/background/src/services/disk-backed-fs.ts:1346 — 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. — src/background/src/services/disk-backed-fs.ts:1324
- src/popup/src/modules/Direct/DirectController.ts:18 · src/popup/src/modules/Sniffer/SnifferController.ts:52 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/popup/src/modules/Direct/DirectController.ts:18
- scripts/e2e-aes128-local.mjs:823 · scripts/e2e-mkv-local.mjs:429 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/e2e-aes128-local.mjs:823
- REDACTED:147 · REDACTED:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:147
- REDACTED:126 · REDACTED:169 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:126
- src/background/src/offscreen.ts:33 · src/background/src/offscreen.ts:46 · src/background/src/offscreen.ts:59 · src/background/src/offscreen.ts:72 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/background/src/offscreen.ts:33
- src/background/src/services/m3u8-parser.ts:139 · src/background/src/services/m3u8-parser.ts:154 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/background/src/services/m3u8-parser.ts:139
- src/popup/src/modules/Downloads/DownloadsController.ts:13 · src/popup/src/modules/Sniffer/SnifferController.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/popup/src/modules/Downloads/DownloadsController.ts:13
- src/popup/src/modules/Settings/SettingsView.tsx:267 · src/popup/src/modules/Settings/SettingsView.tsx: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. — src/popup/src/modules/Settings/SettingsView.tsx:267
- REDACTED:18 · REDACTED:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:18
- src/core/src/controllers/add-playlist-epic.ts:5 · src/core/src/controllers/inc-download-status-epic.ts:5 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/core/src/controllers/add-playlist-epic.ts:5
- src/popup/src/modules/Settings/SettingsView.tsx:174 · src/popup/src/modules/Settings/SettingsView.tsx:199 · src/popup/src/modules/Settings/SettingsView.tsx:233 · src/popup/src/modules/Settings/SettingsView.tsx:295 — 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. — src/popup/src/modules/Settings/SettingsView.tsx:174
- src/background/src/services/disk-backed-fs.ts:1364 · src/background/src/services/disk-backed-fs.ts:1378 — 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. — src/background/src/services/disk-backed-fs.ts:1364
- src/background/src/services/opfs-storage.ts:126 · src/background/src/services/opfs-storage.ts: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. — src/background/src/services/opfs-storage.ts:126
- src/core/src/controllers/delete-job-epic.ts:9 · src/core/src/controllers/save-as-job-epic.ts:9 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/core/src/controllers/delete-job-epic.ts:9
- src/popup/src/modules/Playlist/PlaylistView.tsx:161 · src/popup/src/modules/Playlist/PlaylistView.tsx:176 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/popup/src/modules/Playlist/PlaylistView.tsx:161
- REDACTED:286 · REDACTED:208 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:286
- src/background/src/services/seekable-opfs-output.ts:16 · src/background/src/services/seekable-opfs-output.ts:26 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/background/src/services/seekable-opfs-output.ts:16
- REDACTED:718 · REDACTED:764 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:718
- src/background/src/services/disk-backed-fs.ts:124 · src/background/src/services/disk-mux-client.ts:30 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/background/src/services/disk-backed-fs.ts:124
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- main has cyclomatic complexity 53 and cognitive complexity 125; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/e2e-aes128-local.mjs:448
- serve has cyclomatic complexity 47 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:193
- main has cyclomatic complexity 46 and cognitive complexity 141; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:67
- main has cyclomatic complexity 41 and cognitive complexity 113; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:150
- main has cyclomatic complexity 40 and cognitive complexity 124; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/e2e-preparation-local.mjs:140
- JobView has cyclomatic complexity 40 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Job/JobView.tsx:49
- main has cyclomatic complexity 39 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:606
- JobDetailView has cyclomatic complexity 38 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Job/JobView.tsx:415
- main has cyclomatic complexity 37 and cognitive complexity 101; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:128
- main has cyclomatic complexity 34 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:59
- main has cyclomatic complexity 34 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/e2e-mkv-local.mjs:94
- PlaylistModule has cyclomatic complexity 32 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Playlist/PlaylistModule.tsx:10
- main has cyclomatic complexity 30 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/e2e-firefox-local.mjs:32
- PlaylistView has cyclomatic complexity 30 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Playlist/PlaylistView.tsx:61
- buildJobViewDerived has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Job/JobController.ts:94
- StorageSummary has cyclomatic complexity 26 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Storage/StorageSummary.tsx:30
- (anonymous) has cyclomatic complexity 24 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/e2e-preparation-local.mjs:215
- (anonymous) has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:134
- SnifferView has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Sniffer/SnifferView.tsx:38
- PlaylistRow has cyclomatic complexity 20 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/popup/src/modules/Sniffer/SnifferView.tsx:329
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- src/background/src/services/disk-backed-fs.ts has 1302 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/background/src/services/disk-backed-fs.ts:1
- src/popup/src/modules/Job/JobView.tsx has 739 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/popup/src/modules/Job/JobView.tsx:1
- src/popup/src/modules/Playlist/PlaylistView.tsx has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/popup/src/modules/Playlist/PlaylistView.tsx:1
- src/popup/src/modules/Sniffer/SnifferView.tsx has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/popup/src/modules/Sniffer/SnifferView.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×23) — REDACTED:1, scripts/e2e-aes128-local.mjs:1, REDACTED:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 22 application, 27 tooling and 87 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (22 application, 27 tooling, 87 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — src/popup/src/modules/Direct/DirectController.ts
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/core/src/entities/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/core/src/entities/index.ts in the same commit, or the barrel will import a name that no longer exists. — src/core/src/entities/level-status.ts:3
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in src/background/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in src/core/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in src/popup/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/core/src/services/dependencies.ts → src/core/src/services/index.ts → src/core/src/services/dependencies.ts — src/core/src/services/dependencies.ts:1
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — src/background/src/workers/disk-mux-worker.ts:209, src/background/src/workers/disk-mux-worker.ts:229, src/background/src/services/disk-backed-fs.ts:936, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 3/4 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~2.1 `!` null assertions per 1k TypeScript source lines — 27 assertion(s) across the 12895 source line(s) of the 160 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/popup/src/modules/Job/JobView.tsx (4), src/background/src/services/disk-backed-fs.ts (3), src/core/src/store/slices/playlists-slice.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Strong | Solid. |
| Architecture | 92% | Exemplary | Strongest area. |
| Maturity | 72% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 42% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — vertical-slice architecture detected, but individual slices could not be resolved from namespaces or project layout
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> predev / > pnpm run clean && pnpm run copy-assets / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D4 Code Duplication — This repository's production source (.js, .mjs, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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'.
- P2 Observability — This repository's JavaScript/TypeScript source (5 module(s), 161 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 161 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- <select> without a programmatic label src/popup/src/modules/Settings/SettingsView.tsx:185
- <select> without a programmatic label src/popup/src/modules/Settings/SettingsView.tsx:306
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Document without a <title> src/popup/popup.html:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) src/core/src/services/dependencies.ts:1
Serious — 180 finding(s)
- No test reaches this file REDACTED:1
- No test reaches this file scripts/e2e-aes128-local.mjs:1
- No test reaches this file REDACTED:1
- No test reaches this file REDACTED:1
- No test reaches this file scripts/e2e-preparation-local.mjs:1
- No test reaches this file REDACTED:1
- No test reaches this file REDACTED:1
- No test reaches this file REDACTED:1
- No test reaches this file scripts/e2e-mkv-local.mjs:1
- No test reaches this file scripts/e2e-firefox-local.mjs:1
- No test reaches this file scripts/publish-firefox.mjs:1
- No test reaches this file src/popup/src/modules/Direct/DirectController.ts:1
- No test reaches this file scripts/build-variant.mjs:1
- No test reaches this file scripts/copy-assets.mjs:1
- No test reaches this file src/background/src/index.ts:1
- No test reaches this file scripts/e2e-job-faults.mjs:1
- No test reaches this file src/popup/src/index.tsx:1
- No test reaches this file src/popup/src/App.tsx:1
- No test reaches this file scripts/coverage-report.mjs:1
- No test reaches this file src/background/src/listeners/setTabListener.ts:1
- No test reaches this file src/popup/src/modules/Navbar/RouterModule.tsx:1
- No test reaches this file scripts/coverage-badge.mjs:1
- No test reaches this file src/background/src/listeners/index.ts:1
- Low coverage: src/core/src/controllers/download-subtitle-epic.ts src/core/src/controllers/download-subtitle-epic.ts:1
- Low coverage: src/core/src/controllers/inspect-level-epic.ts src/core/src/controllers/inspect-level-epic.ts:1
- Low coverage: src/core/src/entities/tab.ts src/core/src/entities/tab.ts:1
- Low coverage: src/core/src/store/configure-store.ts src/core/src/store/configure-store.ts:1
- Low coverage: src/core/src/store/root-reducer.ts src/core/src/store/root-reducer.ts:1
- Low coverage: src/core/src/store/slices/level-inspections-slice.ts src/core/src/store/slices/level-inspections-slice.ts:1
- Low coverage: src/core/src/store/slices/subtitles-slice.ts src/core/src/store/slices/subtitles-slice.ts:1
- Low coverage: src/core/src/use-cases/generate-sequence-iv.ts src/core/src/use-cases/generate-sequence-iv.ts:1
- Low coverage: src/core/src/use-cases/generate-track-id.ts src/core/src/use-cases/generate-track-id.ts:1
- Low coverage: src/core/src/use-cases/get-subtitle-text.ts src/core/src/use-cases/get-subtitle-text.ts:1
- Low coverage: src/core/src/use-cases/is-hls-response.ts src/core/src/use-cases/is-hls-response.ts:1
- Low coverage: src/core/src/use-cases/store-subtitle-text.ts src/core/src/use-cases/store-subtitle-text.ts:1
- Low coverage: src/popup/src/components/InlineConfirm.tsx src/popup/src/components/InlineConfirm.tsx:1
- Low coverage: src/popup/src/components/Metadata.tsx src/popup/src/components/Metadata.tsx:1
- Low coverage: src/popup/src/modules/Job/JobModule.tsx src/popup/src/modules/Job/JobModule.tsx:1
- Low coverage: src/popup/src/modules/Job/JobView.tsx src/popup/src/modules/Job/JobView.tsx:1
- Low coverage: src/popup/src/modules/Playlist/PlaylistView.tsx src/popup/src/modules/Playlist/PlaylistView.tsx:1
- Low coverage: src/popup/src/modules/Sniffer/PlaylistPreview.tsx src/popup/src/modules/Sniffer/PlaylistPreview.tsx:1
- FunctionTooLong: PlaylistView.PlaylistView src/popup/src/modules/Playlist/PlaylistView.tsx:61
- FunctionTooLong: JobView.JobView src/popup/src/modules/Job/JobView.tsx:49
- FunctionTooLong: JobView.JobDetailView src/popup/src/modules/Job/JobView.tsx:415
- FunctionTooLong: SnifferView.SnifferView src/popup/src/modules/Sniffer/SnifferView.tsx:38
- FunctionTooLong: SettingsView.SettingsView src/popup/src/modules/Settings/SettingsView.tsx:70
- FunctionTooLong: PlaylistModule.PlaylistModule src/popup/src/modules/Playlist/PlaylistModule.tsx:10
- FunctionTooLong: DownloadsView.DownloadsView src/popup/src/modules/Downloads/DownloadsView.tsx:35
- FunctionTooLong: BulkDownloadSheet.BulkDownloadSheet src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx:14
- FunctionTooLong: PlaylistPreview.PlaylistPreview src/popup/src/modules/Sniffer/PlaylistPreview.tsx:15
- FunctionTooLong: StorageSummary.StorageSummary src/popup/src/modules/Storage/StorageSummary.tsx:30
- FunctionTooLong: SnifferView.PlaylistRow src/popup/src/modules/Sniffer/SnifferView.tsx:329
- Duplicated block (12 lines × 2 locations) scripts/e2e-aes128-local.mjs:823
- Duplicated block (12 lines × 2 locations) REDACTED:147
- Duplicated block (12 lines × 2 locations) REDACTED:126
- Duplicated block (12 lines × 2 locations) src/background/src/services/m3u8-parser.ts:139
- Duplicated block (12 lines × 2 locations) src/popup/src/modules/Downloads/DownloadsController.ts:13
- Duplicated block (12 lines × 2 locations) src/popup/src/modules/Settings/SettingsView.tsx:267
- Swallowed exception (empty catch) src/background/src/workers/disk-mux-worker.ts:209
- Swallowed exception (empty catch) src/background/src/workers/disk-mux-worker.ts:229
- Swallowed exception (empty catch) src/background/src/services/disk-backed-fs.ts:936
- Swallowed exception (empty catch) src/background/src/services/disk-backed-fs.ts:1209
- Swallowed exception (empty catch) src/background/src/services/ffmpeg-muxer.ts:179
- Swallowed exception (empty catch) src/background/src/services/opfs-storage.ts:107
- Hotspot: REDACTED REDACTED:606
- Hotspot: scripts/e2e-firefox-local.mjs scripts/e2e-firefox-local.mjs:32
- Hotspot: scripts/e2e-aes128-local.mjs scripts/e2e-aes128-local.mjs:448
- Hotspot: src/background/src/services/ffmpeg-muxer.ts src/background/src/services/ffmpeg-muxer.ts:64
- Repeated repair: src/background/src/services/fetch-loader.ts src/background/src/services/fetch-loader.ts:18
- Repeated repair: src/background/src/services/m3u8-parser.ts src/background/src/services/m3u8-parser.ts:11
- Repeated repair: src/background/src/services/disk-backed-fs.ts src/background/src/services/disk-backed-fs.ts:736
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2 locations) scripts/e2e-aes128-local.mjs:798
- Duplicated block (13 lines × 2 locations) src/background/src/services/disk-backed-fs.ts:1324
- Duplicated block (13 lines × 2 locations) src/popup/src/modules/Direct/DirectController.ts:18
- Duplicated block (10 lines × 2 locations) src/background/src/services/disk-backed-fs.ts:1364
- Duplicated block (10 lines × 2 locations) src/background/src/services/opfs-storage.ts:126
- Duplicated block (10 lines × 2 locations) src/popup/src/modules/Playlist/PlaylistView.tsx:161
- Unused dependency '@typescript/native'
- Unused dependency '@typescript/native'
- Unused dependency '@typescript/native'
- REDACTED
- REDACTED
- FileTooLong: services/disk-backed-fs.ts src/background/src/services/disk-backed-fs.ts
- FileTooLong: Job/JobView.tsx src/popup/src/modules/Job/JobView.tsx
- Off the main sequence: @hls-downloader/design-system
- Off the main sequence: @hls-downloader/core
- Duplicated block (19 lines × 2 locations) scripts/e2e-firefox-local.mjs:289
- Duplicated block (19 lines × 2 locations) REDACTED:514
- Duplicated block (16 lines × 2 locations) src/design-system/src/components/ui/select.tsx:33
- Duplicated block (16 lines × 2 locations) src/popup/src/modules/Navbar/RouterView.tsx:53
- Duplicated block (14 lines × 2 locations) REDACTED:297
- Duplicated block (14 lines × 2 locations) REDACTED:833
- Duplicated block (11 lines × 2 locations) REDACTED:18
- Duplicated block (11 lines × 2 locations) src/core/src/controllers/add-playlist-epic.ts:5
- <Input> field component without a label src/popup/src/modules/Direct/DirectView.tsx:52
- Page without a main landmark src/popup/popup.html:2
- Modal dialog does not manage focus src/popup/src/components/BottomSheet.tsx:66
- Focus outline removed in CSS without a :focus replacement src/popup/src/index.css:92
- Accessibility enforcement below the top rung package.json:62
- PlaylistModule.PlaylistModule (cyclomatic 58) src/popup/src/modules/Playlist/PlaylistModule.tsx:10
- PlaylistView.PlaylistView (cyclomatic 47) src/popup/src/modules/Playlist/PlaylistView.tsx:61
- JobView.JobView (cyclomatic 43) src/popup/src/modules/Job/JobView.tsx:49
- JobView.JobDetailView (cyclomatic 34) src/popup/src/modules/Job/JobView.tsx:415
- BulkDownloadSheet.BulkDownloadSheet (cyclomatic 31) src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx:14
- SnifferView.SnifferView (cyclomatic 27) src/popup/src/modules/Sniffer/SnifferView.tsx:38
- StorageSummary.StorageSummary (cyclomatic 26) src/popup/src/modules/Storage/StorageSummary.tsx:30
- SnifferView.PlaylistRow (cyclomatic 24) src/popup/src/modules/Sniffer/SnifferView.tsx:329
- DownloadsView.DownloadsView (cyclomatic 23) src/popup/src/modules/Downloads/DownloadsView.tsx:35
- PlaylistPreview.PlaylistPreview (cyclomatic 23) src/popup/src/modules/Sniffer/PlaylistPreview.tsx:15
- JobController.buildJobViewDerived (cyclomatic 18) src/popup/src/modules/Job/JobController.ts:94
- ffmpeg-muxer.buildMuxArgs (cyclomatic 16) src/background/src/services/ffmpeg-muxer.ts:64
- JobView.JobView (cognitive 58) src/popup/src/modules/Job/JobView.tsx:49
- PlaylistView.PlaylistView (cognitive 58) src/popup/src/modules/Playlist/PlaylistView.tsx:61
- PlaylistModule.PlaylistModule (cognitive 55) src/popup/src/modules/Playlist/PlaylistModule.tsx:10
- JobView.JobDetailView (cognitive 35) src/popup/src/modules/Job/JobView.tsx:415
- PlaylistPreview.PlaylistPreview (cognitive 28) src/popup/src/modules/Sniffer/PlaylistPreview.tsx:15
- BulkDownloadSheet.BulkDownloadSheet (cognitive 27) src/popup/src/modules/Sniffer/BulkDownloadSheet.tsx:14
- disk-mux-worker.mux (cognitive 23) src/background/src/workers/disk-mux-worker.ts:128
- JobController.buildJobViewDerived (cognitive 23) src/popup/src/modules/Job/JobController.ts:94
- DownloadsView.DownloadsView (cognitive 23) src/popup/src/modules/Downloads/DownloadsView.tsx:35
- StorageSummary.StorageSummary (cognitive 21) src/popup/src/modules/Storage/StorageSummary.tsx:30
- get-subtitle-text.getSubtitleTextFactory.run (cognitive 19) src/core/src/use-cases/get-subtitle-text.ts:14
- ffmpeg-muxer.buildMuxArgs (cognitive 18) src/background/src/services/ffmpeg-muxer.ts:64
- SnifferView.PlaylistRow (cognitive 18) src/popup/src/modules/Sniffer/SnifferView.tsx:329
- fetch-loader.fetchWithRetry (cognitive 17) src/background/src/services/fetch-loader.ts:138
- SnifferView.SnifferView (cognitive 16) src/popup/src/modules/Sniffer/SnifferView.tsx:38
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking REDACTED:621
- Duplicated block with local edits (187 matched lines × 2 locations) scripts/e2e-preparation-local.mjs:95
- Duplicated block with local edits (127 matched lines × 2 locations) src/popup/src/modules/Downloads/DownloadsView.tsx:49
- Duplicated block (41 lines × 3 locations) REDACTED:338
- Duplicated block (37 lines × 2 locations) src/popup/src/modules/Playlist/PlaylistView.tsx:255
- Duplicated block with local edits (34 matched lines × 2 locations) scripts/e2e-mkv-local.mjs:18
- Duplicated block (32 lines × 2 locations) src/popup/src/modules/Settings/SettingsView.tsx:200
- Duplicated block with local edits (26 matched lines × 2 locations) scripts/e2e-aes128-local.mjs:284
- Duplicated block (25 lines × 3 locations) REDACTED:29
- Duplicated block (22 lines × 4 locations) REDACTED:388
- Duplicated block (20 lines × 4 locations) src/popup/src/modules/Job/JobView.tsx:604
- Duplicated block (18 lines × 3 locations) scripts/e2e-aes128-local.mjs:619
- Duplicated block (18 lines × 2 locations) src/popup/src/modules/Settings/SettingsController.ts:53
- Duplicated block (15 lines × 2 locations) src/popup/src/modules/Playlist/PlaylistView.tsx:312
- Duplicated block (12 lines × 4 locations) src/background/src/offscreen.ts:33
- Duplicated block (11 lines × 4 locations) src/popup/src/modules/Settings/SettingsView.tsx:174
- Duplicated block with local edits (10 matched lines × 2 locations) src/core/src/controllers/delete-job-epic.ts:9
- Duplicated block (9 lines × 2 locations) REDACTED:286
- Duplicated block with local edits (9 matched lines × 2 locations) src/background/src/services/seekable-opfs-output.ts:16
- Duplicated block (8 lines × 2 locations) REDACTED:718
- Duplicated block with local edits (8 matched lines × 2 locations) src/background/src/services/disk-backed-fs.ts:124
- Complex function main (cyclomatic 53, cognitive 125) scripts/e2e-aes128-local.mjs:448
- Complex function serve (cyclomatic 47, cognitive 61) REDACTED:193
- Complex function main (cyclomatic 46, cognitive 141) REDACTED:67
- Complex function main (cyclomatic 41, cognitive 113) REDACTED:150
- Complex function main (cyclomatic 40, cognitive 124) scripts/e2e-preparation-local.mjs:140
- Complex function JobView (cyclomatic 40, cognitive 39) src/popup/src/modules/Job/JobView.tsx:49
- Complex function main (cyclomatic 39, cognitive 53) REDACTED:606
- Complex function JobDetailView (cyclomatic 38, cognitive 36) src/popup/src/modules/Job/JobView.tsx:415
- Complex function main (cyclomatic 37, cognitive 101) REDACTED:128
- Complex function main (cyclomatic 34, cognitive 75) REDACTED:59
- Complex function main (cyclomatic 34, cognitive 53) scripts/e2e-mkv-local.mjs:94
- Complex function PlaylistModule (cyclomatic 32, cognitive 28) src/popup/src/modules/Playlist/PlaylistModule.tsx:10
- Complex function main (cyclomatic 30, cognitive 51) scripts/e2e-firefox-local.mjs:32
- Complex function PlaylistView (cyclomatic 30, cognitive 37) src/popup/src/modules/Playlist/PlaylistView.tsx:61
- Complex function buildJobViewDerived (cyclomatic 28, cognitive 25) src/popup/src/modules/Job/JobController.ts:94
- Complex function StorageSummary (cyclomatic 26, cognitive 23) src/popup/src/modules/Storage/StorageSummary.tsx:30
- Complex function (anonymous) (cyclomatic 24, cognitive 28) scripts/e2e-preparation-local.mjs:215
- Complex function (anonymous) (cyclomatic 21, cognitive 25) REDACTED:134
- Complex function SnifferView (cyclomatic 21, cognitive 16) src/popup/src/modules/Sniffer/SnifferView.tsx:38
- Complex function PlaylistRow (cyclomatic 20, cognitive 19) src/popup/src/modules/Sniffer/SnifferView.tsx:329
- src/background/src/services/disk-backed-fs.ts: 1302 lines of code src/background/src/services/disk-backed-fs.ts:1
- src/popup/src/modules/Job/JobView.tsx: 739 lines of code src/popup/src/modules/Job/JobView.tsx:1
- src/popup/src/modules/Playlist/PlaylistView.tsx: 457 lines of code src/popup/src/modules/Playlist/PlaylistView.tsx:1
- src/popup/src/modules/Sniffer/SnifferView.tsx: 438 lines of code src/popup/src/modules/Sniffer/SnifferView.tsx:1
- No lint script
- Dead file (~63 LoC) src/popup/src/modules/Direct/DirectController.ts
Minor — 26 finding(s)
- Duplicated predicate REDACTED:362
- Duplicated predicate REDACTED:372
- Duplicated predicate src/core/src/controllers/download-queue-epic.ts:39
- Duplicated predicate REDACTED:425
- Deprecated: deep-diff REDACTED:2592
- Deprecated: eslint REDACTED:2763
- Deprecated: whatwg-encoding REDACTED:4319
- redundant comment scripts/build-variant.mjs:48
- redundant comment src/core/test/root-epic.test.ts:47
- redundant comment src/design-system/src/hooks/use-localstorage.ts:11
- Mock-dominated test: passes stored mkv output container when creating the save link src/core/test/save-as-job-epic.test.ts:40
- Mock-dominated test: writes to bucket src/core/test/use-cases.test.ts:70
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:6
- Unused export 'LevelStatus' src/core/src/entities/level-status.ts:3
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
- Silent fallback default in catch src/background/src/services/disk-backed-fs.ts:360
Minor — 5 finding(s)
- Outdated (npm): @reduxjs/toolkit
- Outdated (npm): gsap
- Outdated (npm): hls.js
- Outdated (npm): lucide-react
- doc comments repeat the names src/core/test/test-utils.ts:60
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-48964d0e5aa142e78994965fb4b36558/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-48964d0e5aa142e78994965fb4b36558/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 16 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/popup/src/modules/Job/JobView.tsx` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |